Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-occupation vs http://hl7.org/fhir/us/pacio-pfe/StructureDefinition/pfe-collection

Left:US Core Observation Occupation Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-occupation)
Right:Personal Functioning and Engagement Collection (http://hl7.org/fhir/us/pacio-pfe/StructureDefinition/pfe-collection)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-occupation' vs 'http://hl7.org/fhir/us/pacio-pfe/StructureDefinition/pfe-collection'
ErrorStructureDefinition.versionValues for version differ: '7.0.0-ballot' vs '1.9.0'
InformationStructureDefinition.nameValues for name differ: 'USCoreObservationOccupationProfile' vs 'PFECollection'
InformationStructureDefinition.titleValues for title differ: 'US Core Observation Occupation Profile' vs 'Personal Functioning and Engagement Collection'
InformationStructureDefinition.statusValues for status differ: 'active' vs 'draft'
InformationStructureDefinition.dateValues for date differ: '2023-10-17' vs '2024-04-16T20:59:30+00:00'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 International / Cross-Group Projects' vs 'HL7 International / Patient Care'
ErrorStructureDefinition.baseDefinitionValues for baseDefinition differ: 'http://hl7.org/fhir/StructureDefinition/Observation' vs 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-survey'
InformationStructureDefinition.shortValues for short differ: 'Past Or Present Occupation' vs 'Survey Observation'
InformationStructureDefinition.definitionValues for definition differ: 'Related data elements for a current or previous job.' vs '\-'
InformationStructureDefinition.commentValues for comment differ: 'A person can have more than one job at the same time and multiple jobs over time' vs '\-'
InformationStructureDefinition.shortValues for short differ: 'Additional content defined by implementations' vs 'Extension'
InformationStructureDefinition.definitionValues for definition differ: 'May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'An Extension'
InformationStructureDefinition.shortValues for short differ: 'registered | preliminary | final | amended +' vs 'Should have the value 'final' when all the observatons are complete and there are no further actions needed. Otherwise, another value from the value set may appropriately be used.'
InformationStructureDefinition.requirementsValues for requirements differ: 'Used for filtering what observations are retrieved and displayed.' vs 'To identify that observation is derived from a questionnaire, is related to personal functioning and engagement, and optionally to identify the domain(s) it falls under.'
InformationObservation.categoryElement minimum cardinalities differ: '0' vs '2'
InformationStructureDefinition.shortValues for short differ: 'Occupation history' vs 'For a Post-Acute Care structured assessment resource such as an instrument or screen, use a LOINC code to identify the instrument/screen name or panel/section title to indicate the kind of assessment.'
InformationObservation.codeExample/preferred bindings differ at Observation.code using binding from PFECollection
InformationStructureDefinition.shortValues for short differ: 'Clinically relevant time/time-period for observation' vs 'Clinical relevant time for an assessment such as post-acute care observations performed with structured evaluation tools is the time the evaluation occurs, i.e., when the clinician obtains the answers entered in the tool. However, the only timing available may be when then tool is completed by the clinician. That timing is generally documented as a point in time (dateTime).'
InformationStructureDefinition.definitionValues for definition differ: '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.' vs 'Clinical relevant time for an assessment such as post-acute care observations performed with structured evaluation tools is the time the evaluation occurs, i.e., when the clinician obtains the answers entered in the tool. However, the only timing available may be when then tool is completed by the clinician. That timing is generally documented as a point in time (dateTime).'
InformationStructureDefinition.commentValues for comment differ: '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](http://hl7.org/fhir/R4/datatypes.html#timing) datatype which allow the measurement to be tied to regular life events.' vs 'The use of effective[x] and dateTime versus Period is subject to implementer workflow and needs. In most situations, an observation is considered as a point in time, even if the assessment occurred over a period of time. Period is included in this implementation guide to provide additional flexibility for specific use cases. However, it is expected most observations will be recorded using DateTime. Furthermore, any retrieval of information should return the relevant if DateTime is requested, even if the original observation was recorded as a period. Some implementers may choose to use additional functions in there retrieves to 'normalize' intervals, as is done in Clinical Quality Language (CQL).'
WarningObservation.effective[x]Elements differ in definition for mustSupport: 'false' vs 'true'
InformationObservation.effective[x]Element minimum cardinalities differ: '0' vs '1'
InformationStructureDefinition.shortValues for short differ: 'Who is responsible for the observation' vs 'The person who performed the assessment. The preferred way to specify the performer is to use the PractitionerRole resource to provide both the practitioner and organization.'
WarningObservation.performerElements differ in definition for mustSupport: 'false' vs 'true'
InformationObservation.performerElement minimum cardinalities differ: '0' vs '1'
InformationStructureDefinition.commentValues for comment differ: 'An observation may have; 1) a single value here, 2) both a value and a set of related or component values, or 3) only a set of related or component values. If a value is present, the datatype for this element should be determined by Observation.code. A CodeableConcept with just a text would be used instead of a string if the field was usually coded, or if the type associated with the Observation.code defines a coded value. For additional guidance, see the [Notes section](http://hl7.org/fhir/R4/observation.html#notes) below.' vs 'An observation may have a value if it represents an individual survey question and answer pair. An observation should not have a value if it represents a multi-question survey or multi-select “check all that apply” question. If a value is present, the datatype for this element should be determined by Observation.code. A CodeableConcept with just a text would be used instead of a string if the field was usually coded, or if the type associated with the Observation.code defines a coded value.'
WarningObservation.value[x]Elements differ in definition for mustSupport: 'false' vs 'true'
InformationObservation.value[x]Element minimum cardinalities differ: '1' vs '0'
InformationObservation.value[x]Element maximum cardinalities differ: '1' vs '0'
ErrorObservation.value[x]Element minimum cardinalities conflict: '1..1' vs '0..0': No instances can be valid against both profiles
InformationStructureDefinition.commentValues for comment differ: 'Null or exceptional values can be represented two ways in FHIR Observations. One way is to simply include them in the value set and represent the exceptions in the value. For example, measurement values for a serology test could be 'detected', 'not detected', 'inconclusive', or 'specimen unsatisfactory'. The alternate way is to use the value element for actual observations and use the explicit dataAbsentReason element to record exceptional values. For example, the dataAbsentReason code 'error' could be used when the measurement was not completed. Note that an observation may only be reported if there are values to report. For example differential cell counts values may be reported only when > 0. Because of these options, use-case agreements are required to interpret general observations for null or exceptional values.' vs ''Null' or exceptional values can be represented two ways in FHIR Observations. One way is to simply include them in the value set and represent the exceptions in the value. The alternate way is to use the value element for actual observations and use the explicit dataAbsentReason element to record exceptional values. For a given LOINC question, if the LOINC answer list includes concepts such as 'unknown' or 'not available', they should be used for Observation.value. Where these concepts are not part of the value set for Observation.value, the Observation.dataAbsentReason can be used if necessary and appropriate.'
WarningObservation.dataAbsentReasonElements differ in definition for mustSupport: 'false' vs 'true'
InformationStructureDefinition.shortValues for short differ: 'Related resource that belongs to the Observation group' vs 'Each post-acute care observation in the collection. May also be another collection to support nested sections.'
InformationStructureDefinition.definitionValues for definition differ: 'This observation is a group observation (e.g. a battery, a panel of tests, a set of vital sign measurements) that includes the target as a member of the group.' vs 'Aggregate set of Observations that represent question answer pairs for both multi-question surveys and multi-select questions.'
InformationStructureDefinition.commentValues for comment differ: 'When using this element, an observation will typically have either a value or a set of related resources, although both may be present in some cases. For a discussion on the ways Observations can assembled in groups together, see [Notes](http://hl7.org/fhir/R4/observation.html#obsgrouping) below. Note that a system may calculate results from [QuestionnaireResponse](questionnaireresponse.html) into a final score and represent the score as an Observation.' vs 'This grouping element is used to represent surveys that group several questions together or individual questions with “check all that apply” responses. For example in the simplest case a flat multi-question survey where the 'panel' observation is the survey instrument itself and instead of an `Observation.value` the `hasMember` element references other Observation that represent the individual questions answer pairs. In a survey that has a heirarchical grouping of questions, the observation 'panels' can be nested. Because surveys can be arbitrarily complex structurally, not all survey structures can be represented using this Observation grouping pattern.'
WarningObservation.hasMemberElements differ in definition for mustSupport: 'false' vs 'true'
InformationStructureDefinition.shortValues for short differ: 'Related measurements the observation is made from' vs 'Should point back to the QuestionnaireResponse that this resource is derived from.'
InformationStructureDefinition.definitionValues for definition differ: 'The target resource that represents a measurement from which this observation value is derived. For example, a calculated anion gap or a fetal measurement based on an ultrasound image.' vs 'Observations or QuestionnaireResponses from which this observation value is derived.'
WarningObservation.derivedFromElements differ in definition for mustSupport: 'false' vs 'true'
ErrorObservation.derivedFromType Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/DocumentReference], CanonicalType[http://hl7.org/fhir/StructureDefinition/ImagingStudy], CanonicalType[http://hl7.org/fhir/StructureDefinition/Media], CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/Observation], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]]) vs Reference([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-questionnaireresponse], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-survey]])
WarningObservation.componentElements differ in definition for mustSupport: 'true' vs 'false'
InformationObservation.componentElement maximum cardinalities differ: '2147483647' vs '0'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/Observationhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-survey
    • Values Differ
    .copyrightUsed by permission of HL7 International, all rights reserved Creative Commons License
    • Removed the item 'Used by permission of HL7 International, all rights reserved Creative Commons License'
    .date2023-10-172024-04-16T20:59:30+00:00
    • Values Differ
    .descriptionThe US Core Occupation Observation Profile is based upon the core FHIR Observation Resource and implements the US Core Data for Interoperability (USCDI) Occupation and Occupation Industry requirements. This profile promotes interoperability and adoption through common implementation by setting minimum expectations for the Observation resource to record, search, and fetch a patient's past or present job as occupation and industry, in other words, the type of work and type of business that compensates for work or assigns work to an unpaid worker or volunteer. In the context of this profile, a job is defined as a work situation, or a training or volunteer position held for a specified period. It identifies which core elements, extensions, vocabularies, and value sets **SHALL** be present and constrains the way the elements are used and constrains the way the elements are used when using the profile. It provides the floor for standards development for specific use cases.A point in time collection of post-acute care observations for a patient. This profile is used for exchanging a set of observation data collected through the use of a structured resource (e.g., assessment tool, instrument, or screen) with multiple questions.
    • Values Differ
    .experimentalfalse
    • Removed the item 'false'
    .fhirVersion4.0.1
      .jurisdiction
        ..jurisdiction[0]urn:iso:std:iso:3166#US
          .kindresource
            .nameUSCoreObservationOccupationProfilePFECollection
            • Values Differ
            .publisherHL7 International / Cross-Group ProjectsHL7 International / Patient Care
            • Values Differ
            .purpose
              .statusactivedraft
              • Values Differ
              .titleUS Core Observation Occupation ProfilePersonal Functioning and Engagement Collection
              • Values Differ
              .typeObservation
                .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-occupationhttp://hl7.org/fhir/us/pacio-pfe/StructureDefinition/pfe-collection
                • Values Differ
                .version7.0.0-ballot1.9.0
                • Values Differ

                Structure

                NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.R TypeR Description & ConstraintsCommentsdoco
                .. Observation C0..*ObservationPast Or Present Occupation
                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
                C0..*USCoreObservationSurveyProfileSurvey Observation
                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
                us-core-2: If there is no component or hasMember element then either a value[x] or a data absent reason must be present
                us-core-3: SHALL use UCUM for coded quantity units.
                  ... id Σ0..1idLogical id of this artifactΣ0..1idLogical id of this artifact
                    ... meta Σ0..1MetaMetadata about the resourceΣ0..1MetaMetadata about the resource
                      ... implicitRules ?!Σ0..1uriA set of rules under which this content was created?!Σ0..1uriA set of rules under which this content was created
                        ... language 0..1codeLanguage of the resource content
                        Binding: ?? (preferred): A human language.

                        Additional BindingsPurpose
                        ??Max Binding
                        0..1codeLanguage of the resource content
                        Binding: ?? (preferred): A human language.

                        Additional BindingsPurpose
                        ??Max Binding
                          ... text 0..1NarrativeText summary of the resource, for human interpretation0..1NarrativeText summary of the resource, for human interpretation
                            ... contained 0..*ResourceContained, inline Resources
                            0..*ResourceContained, inline Resources
                              ... extension 0..*ExtensionAdditional content defined by implementations
                              0..*ExtensionExtension
                              Slice: Unordered, Open by value:url
                                ... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
                                ?!0..*ExtensionExtensions that cannot be ignored
                                  ... identifier Σ0..*IdentifierBusiness Identifier for observation
                                  Σ0..*IdentifierBusiness Identifier for observation
                                    ... basedOn Σ0..*Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest)Fulfills plan, proposal or order
                                    Σ0..*Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest)Fulfills plan, proposal or order
                                      ... partOf Σ0..*Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy)Part of referenced event
                                      Σ0..*Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy)Part of referenced event
                                        ... status ?!SΣ1..1coderegistered | preliminary | final | amended +
                                        Binding: ?? (required): Codes providing the status of an observation.

                                        ?!SΣ1..1codeShould have the value 'final' when all the observatons are complete and there are no further actions needed. Otherwise, another value from the value set may appropriately be used.
                                        Binding: ?? (required): Codes providing the status of an observation.

                                          ... Slices for category S0..*CodeableConceptClassification of type of observation
                                          Slice: Unordered, Open by pattern:$this
                                          Binding: ?? (preferred): Codes for high level observation categories.


                                          S2..*CodeableConceptClassification of type of observation
                                          Slice: Unordered, Open by pattern:$this
                                          Binding: ?? (preferred): Codes for high level observation categories.


                                          • Element minimum cardinalities differ: '0' vs '2'
                                          ... code SΣ1..1CodeableConceptOccupation history
                                          Binding: ?? (example): Codes identifying names of simple observations.


                                          Required Pattern: {"coding":[{"system":"http://loinc.org","code":"11341-5"}]}
                                          SΣ1..1CodeableConceptFor a Post-Acute Care structured assessment resource such as an instrument or screen, use a LOINC code to identify the instrument/screen name or panel/section title to indicate the kind of assessment.
                                          Binding: ?? (preferred)
                                          • Example/preferred bindings differ at Observation.code using binding from PFECollection
                                          ... subject SΣ1..1Reference(US Core Patient Profile)Who and/or what the observation is aboutSΣ1..1Reference(US Core Patient Profile)Who and/or what the observation is about
                                            ... focus Σ0..*Reference(Resource)What the observation is about, when it is not about the subject of record
                                            Σ0..*Reference(Resource)What the observation is about, when it is not about the subject of record
                                              ... encounter Σ0..1Reference(Encounter)Healthcare event during which this observation is madeΣ0..1Reference(Encounter)Healthcare event during which this observation is made
                                                ... Slices for effective[x] Σ0..1dateTime, Period, Timing, instantClinically relevant time/time-period for observation
                                                Slice: Unordered, Open by type:$this
                                                SΣC1..1dateTime S, PeriodClinical relevant time for an assessment such as post-acute care observations performed with structured evaluation tools is the time the evaluation occurs, i.e., when the clinician obtains the answers entered in the tool. However, the only timing available may be when then tool is completed by the clinician. That timing is generally documented as a point in time (dateTime).
                                                us-core-1: Datetime must be at least to day.
                                                • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                • Element minimum cardinalities differ: '0' vs '1'
                                                ... issued Σ0..1instantDate/Time this version was made availableΣ0..1instantDate/Time this version was made available
                                                  ... performer Σ0..*Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson)Who is responsible for the observation
                                                  SΣ1..*Reference(US Core Practitioner Profile S | US Core PractitionerRole Profile | US Core Organization Profile)The person who performed the assessment. The preferred way to specify the performer is to use the PractitionerRole resource to provide both the practitioner and organization.
                                                  • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                  • Element minimum cardinalities differ: '0' vs '1'
                                                  ... Slices for value[x] ΣC1..1CodeableConceptActual result
                                                  Slice: Unordered, Closed by type:$this
                                                  SΣC0..0
                                                  • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                  • Element minimum cardinalities differ: '1' vs '0'
                                                  • Element maximum cardinalities differ: '1' vs '0'
                                                  • Element minimum cardinalities conflict: '1..1' vs '0..0': No instances can be valid against both profiles
                                                  ... dataAbsentReason C0..1CodeableConceptWhy the result is missing
                                                  Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing.

                                                  SC0..1CodeableConceptWhy the result is missing
                                                  Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing.

                                                  • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                  ... interpretation 0..*CodeableConceptHigh, low, normal, etc.
                                                  Binding: ?? (extensible): Codes identifying interpretations of observations.


                                                  0..*CodeableConceptHigh, low, normal, etc.
                                                  Binding: ?? (extensible): Codes identifying interpretations of observations.


                                                    ... note 0..*AnnotationComments about the observation
                                                    0..*AnnotationComments about the observation
                                                      ... bodySite 0..1CodeableConceptObserved body part
                                                      Binding: ?? (example): Codes describing anatomical locations. May include laterality.

                                                      0..1CodeableConceptObserved body part
                                                      Binding: ?? (example): Codes describing anatomical locations. May include laterality.

                                                        ... method 0..1CodeableConceptHow it was done
                                                        Binding: ?? (example): Methods for simple observations.

                                                        0..1CodeableConceptHow it was done
                                                        Binding: ?? (example): Methods for simple observations.

                                                          ... specimen 0..1Reference(Specimen)Specimen used for this observation0..1Reference(Specimen)Specimen used for this observation
                                                            ... device 0..1Reference(Device | DeviceMetric)(Measurement) Device0..1Reference(Device | DeviceMetric)(Measurement) Device
                                                              ... referenceRange C0..*BackboneElementProvides guide for interpretation
                                                              obs-3: Must have at least a low or a high or text
                                                              C0..*BackboneElementProvides guide for interpretation
                                                              obs-3: Must have at least a low or a high or text
                                                                .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                  .... extension 0..*ExtensionAdditional content defined by implementations
                                                                  0..*ExtensionAdditional content defined by implementations
                                                                    .... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                    ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                      .... low C0..1??Low Range, if relevantC0..1??Low Range, if relevant
                                                                        .... high C0..1??High Range, if relevantC0..1??High Range, if relevant
                                                                          .... type 0..1CodeableConceptReference range qualifier
                                                                          Binding: ?? (preferred): Code for the meaning of a reference range.

                                                                          0..1CodeableConceptReference range qualifier
                                                                          Binding: ?? (preferred): Code for the meaning of a reference range.

                                                                            .... appliesTo 0..*CodeableConceptReference range population
                                                                            Binding: ?? (example): Codes identifying the population the reference range applies to.


                                                                            0..*CodeableConceptReference range population
                                                                            Binding: ?? (example): Codes identifying the population the reference range applies to.


                                                                              .... age 0..1RangeApplicable age range, if relevant0..1RangeApplicable age range, if relevant
                                                                                .... text 0..1stringText based reference range in an observation0..1stringText based reference range in an observation
                                                                                  ... hasMember Σ0..*Reference(Observation | QuestionnaireResponse | MolecularSequence)Related resource that belongs to the Observation group
                                                                                  SΣ0..*Reference(Personal Functioning and Engagement Single Observation)Each post-acute care observation in the collection. May also be another collection to support nested sections.
                                                                                  • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                                  ... derivedFrom Σ0..*Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | Observation | MolecularSequence)Related measurements the observation is made from
                                                                                  SΣ0..*Reference(US Core QuestionnaireResponse Profile S | US Core Observation Survey Profile S)Should point back to the QuestionnaireResponse that this resource is derived from.
                                                                                  • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                                  • Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/DocumentReference], CanonicalType[http://hl7.org/fhir/StructureDefinition/ImagingStudy], CanonicalType[http://hl7.org/fhir/StructureDefinition/Media], CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/Observation], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]]) vs Reference([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-questionnaireresponse], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-survey]])
                                                                                  ... Slices for component SΣ0..*BackboneElementComponent results
                                                                                  Slice: Unordered, Open by pattern:code
                                                                                  Σ0..0
                                                                                  • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                                  • Element maximum cardinalities differ: '2147483647' vs '0'
                                                                                  .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                                    .... extension 0..*ExtensionAdditional content defined by implementations
                                                                                    0..*ExtensionAdditional content defined by implementations
                                                                                      .... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                                      ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                                        .... code Σ1..1CodeableConceptType of component observation (code / type)
                                                                                        Binding: ?? (example): Codes identifying names of simple observations.

                                                                                        Σ1..1CodeableConceptType of component observation (code / type)
                                                                                        Binding: ?? (example): Codes identifying names of simple observations.

                                                                                          .... value[x] Σ0..1Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodActual component resultΣ0..1Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodActual component result
                                                                                            .... dataAbsentReason C0..1CodeableConceptWhy the component result is missing
                                                                                            Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing.

                                                                                            C0..1CodeableConceptWhy the component result is missing
                                                                                            Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing.

                                                                                              .... interpretation 0..*CodeableConceptHigh, low, normal, etc.
                                                                                              Binding: ?? (extensible): Codes identifying interpretations of observations.


                                                                                              0..*CodeableConceptHigh, low, normal, etc.
                                                                                              Binding: ?? (extensible): Codes identifying interpretations of observations.


                                                                                                .... referenceRange 0..*See referenceRange (Observation)Provides guide for interpretation of component result
                                                                                                0..*See referenceRange (Observation)Provides guide for interpretation of component result

                                                                                                  doco Documentation for this format