NameCard.TypeConstraints and Usage
.  Observation 0..* Observation dom-2: If the resource is contained in another resource, it SHALL NOT contain nested Resources
dom-3: If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
dom-4: If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
dom-5: If a resource is contained in another resource, it SHALL NOT have a security label
dom-6: A resource should have narrative for robust management
obs-6: dataAbsentReason SHALL only be present if Observation.value[x] is not present
obs-7: If Observation.code is the same as an Observation.component.code then the value element associated with the code SHALL NOT be present
Definition:
Measurements and simple assertions made about a patient, device or other subject.


Comments:
Used for simple observations such as device measurements, laboratory atomic results, vital signs, height, weight, smoking status, comments, etc. Other resources are used to provide context for observations such as laboratory reports, etc.

..  status 1..1 code Binding:ObservationStatus (required): Codes providing the status of an observation.


ele-1: All FHIR elements must have a @value or children
Definition:
The status of the result value.


Comments:
This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.

..  effective[x]
     (effectiveDateTime)
0..1 dateTime ele-1: All FHIR elements must have a @value or children
Definition:
The time or time-period the observed value is asserted as being true. For biological subjects - e.g. human patients - this is usually called the "physiologically relevant time". This is usually either the time of the procedure or of specimen collection, but very often the source of the date/time is not known, only the date/time itself.


Comments:
At least a date should be present unless this observation is a historical report. For recording imprecise or "fuzzy" times (For example, a blood glucose measurement taken "after breakfast") use the Timing datatype which allow the measurement to be tied to regular life events.