Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab vs http://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationPersonalPronouns

Left:US Core Laboratory Result Observation Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab)
Right:SDOHCC Observation Personal Pronouns (http://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationPersonalPronouns)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab' vs 'http://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationPersonalPronouns'
ErrorStructureDefinition.versionValues for version differ: '7.0.0' vs '2.2.0'
InformationStructureDefinition.nameValues for name differ: 'USCoreLaboratoryResultObservationProfile' vs 'SDOHCCObservationPersonalPronouns'
InformationStructureDefinition.titleValues for title differ: 'US Core Laboratory Result Observation Profile' vs 'SDOHCC Observation Personal Pronouns'
InformationStructureDefinition.dateValues for date differ: '2023-10-17' vs '2024-08-27T17:19:22+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/us/core/StructureDefinition/us-core-observation-clinical-result' vs 'http://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationPersonalCharacteristic'
InformationStructureDefinition.shortValues for short differ: 'Measurements and simple assertions' vs 'Personal characteristic observation'
InformationStructureDefinition.definitionValues for definition differ: 'Measurements and simple assertions made about a patient, device or other subject.' vs 'For observations about the pronouns and possessive adjectives a person wishes to be addressed by.'
InformationStructureDefinition.commentValues for comment differ: '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.' vs 'For observations about the personal pronouns of an individual.'
WarningObservation.metaElements differ in definition for mustSupport: 'true' vs 'false'
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 'final | corrected | entered-in-error | unknown'
InformationStructureDefinition.definitionValues for definition differ: 'The status of the result value.' vs 'The status of the observation value.'
InformationStructureDefinition.requirementsValues for requirements differ: 'Need to track the status of individual results. Some results are finalized before the whole report is finalized.' vs 'Further constrained to values that are relevant for personal characteristic observations.'
WarningObservation.categoryElements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.shortValues for short differ: 'Laboratory Test Name' vs 'Type of observation (code / type)'
InformationStructureDefinition.definitionValues for definition differ: 'The name of the clinical test or procedure performed on a patient. A LOINC **SHALL** be used if the concept is present in LOINC.' vs 'Describes what was observed. Sometimes this is called the observation 'name'.'
InformationStructureDefinition.commentValues for comment differ: 'The typical patterns for codes are: 1) a LOINC code either as a translation from a 'local' code or as a primary code, or 2) a local code only if no suitable LOINC exists, or 3) both the local and the LOINC translation. Systems SHALL be capable of sending the local code if one exists. When using LOINC , Use either the SHORTNAME or LONG_COMMON_NAME field for the display.' vs '*All* code-value and, if present, component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. NOTE: In LOINC, System Patient is used in the modeling of codes referenced by the Personal Characteristics profiles (e.g., 72826-1 Race OMB.1997, 69490-1 Ethnicity OMB.1997, 76691-5 Gender identity, 76690-7 Sexual orientation, 90778-2 Personal pronouns – Reported, and 99502-7 Recorded sex or gender). If the draft profiles are adopted, new LOINC codes without System Patient would be needed since these profiles can also be used to capture characteristics of a provider (using an extension) or a related person (using focus).'
InformationObservation.subjectElement minimum cardinalities differ: '1' vs '0'
InformationObservation.focusElement maximum cardinalities differ: '2147483647' vs '1'
InformationStructureDefinition.shortValues for short differ: 'Encounter associated with Observation' vs 'Healthcare event during which this observation is made'
WarningObservation.encounterElements differ in definition for mustSupport: 'true' vs 'false'
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 '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](datatypes.html#timing) datatype which allow the measurement to be tied to regular life events. NOTE: dateTime is Must Support, but currently tooling does not support this.'
WarningObservation.effective[x]Elements differ in definition for mustSupport: 'true' vs 'false'
WarningObservation.performerElements differ in definition for mustSupport: 'false' vs 'true'
InformationStructureDefinition.shortValues for short differ: 'Result Value' vs 'Actual result'
InformationStructureDefinition.definitionValues for definition differ: 'The Laboratory result value. If a coded value, the valueCodeableConcept.code **SHOULD** be selected from [SNOMED CT](http://hl7.org/fhir/ValueSet/uslab-obs-codedresults) if the concept exists. If a numeric value, valueQuantity.code **SHALL** be selected from [UCUM](http://unitsofmeasure.org). A FHIR [UCUM Codes value set](http://hl7.org/fhir/STU3/valueset-ucum-units.html) that defines all UCUM codes is in the FHIR specification.' vs 'The information determined as a result of making the observation, if the information has a simple value.'
InformationStructureDefinition.requirementsValues for requirements differ: 'An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations.' vs 'An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. This is a value set is for testing purposes only and will ultimately need to be aligned with vetted value sets being developed by the Gender Harmony Project. See https://build.fhir.org/ig/HL7/fhir-gender-harmony/branches/main/terminology.html#appendix-1--proposed-value-sets'
InformationObservation.value[x]Element minimum cardinalities differ: '0' vs '1'
WarningObservation.dataAbsentReasonElements differ in definition for mustSupport: 'true' vs 'false'
InformationObservation.dataAbsentReasonElement maximum cardinalities differ: '1' vs '0'
InformationStructureDefinition.shortValues for short differ: 'Result interpretation' vs 'High, low, normal, etc.'
InformationStructureDefinition.commentValues for comment differ: 'Categorical assessment of a laboratory value, often in relation to a test's reference range. Examples include but are not limited to high, low, critical, and normal.' vs 'Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result.'
WarningObservation.interpretationElements differ in definition for mustSupport: 'true' vs 'false'
InformationObservation.interpretationElement maximum cardinalities differ: '2147483647' vs '0'
InformationObservation.bodySiteElement maximum cardinalities differ: '1' vs '0'
WarningObservation.methodElements differ in definition for mustSupport: 'false' vs 'true'
InformationObservation.methodElement minimum cardinalities differ: '0' vs '1'
WarningObservation.specimenElements differ in definition for mustSupport: 'true' vs 'false'
InformationObservation.specimenElement maximum cardinalities differ: '1' vs '0'
InformationStructureDefinition.shortValues for short differ: 'Result reference range' vs 'Provides guide for interpretation'
InformationStructureDefinition.commentValues for comment differ: 'Upper and lower limit of test values expected for a designated population of individuals. Reference range values may differ by patient characteristics, laboratory test manufacturer and laboratory test performer.' vs 'Most observations only have one generic reference range. Systems MAY choose to restrict to only supplying the relevant reference range based on knowledge about the patient (e.g., specific to the patient's age, gender, weight and other factors), but this might not be possible or appropriate. Whenever more than one reference range is supplied, the differences between them SHOULD be provided in the reference range and/or age properties.'
WarningObservation.referenceRangeElements differ in definition for mustSupport: 'true' vs 'false'
InformationObservation.referenceRangeElement maximum cardinalities differ: '2147483647' vs '0'
WarningObservation.derivedFromElements differ in definition for mustSupport: 'false' vs 'true'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-clinical-resulthttp://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationPersonalCharacteristic
    • 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-08-27T17:19:22+00:00
    • Values Differ
    .descriptionThe US Core Laboratory Result Observation Profile is based upon the US Core Observation Clinical Result Profile and, along with the US Core DiagnosticReport Profile for Laboratory Results Reporting, meets the U.S. Core Data for Interoperability (USCDI) Laboratory requirements. Laboratory results are grouped and summarized using the DiagnosticReport resource, which references Observation resources. Each Observation resource represents an individual laboratory test and result value, a “nested” panel (such as a microbial susceptibility panel) that references other observations, or rarely a laboratory test with component result values. The US Core Laboratory Result Observation Profile sets minimum expectations for the Observation resource to record, search, and fetch laboratory test results associated with a patient to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains the way the elements are used when using this profile. It provides the floor for standards development for specific use cases.Profile for observations about the pronouns and possessive adjectives a person wishes to be addressed by. This profile is intended for draft use only. For further details on this profile see [Draft Specifications for Personal Characteristics](draft_specifications_for_personal_characteristics.html).
    • Values Differ
    .experimentalfalse
    • Removed the item 'false'
    .fhirVersion4.0.1
      .jurisdiction
        ..jurisdiction[0]urn:iso:std:iso:3166#US
          .kindresource
            .nameUSCoreLaboratoryResultObservationProfileSDOHCCObservationPersonalPronouns
            • Values Differ
            .publisherHL7 International / Cross-Group ProjectsHL7 International / Patient Care
            • Values Differ
            .purpose
              .statusactive
                .titleUS Core Laboratory Result Observation ProfileSDOHCC Observation Personal Pronouns
                • Values Differ
                .typeObservation
                  .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-labhttp://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationPersonalPronouns
                  • Values Differ
                  .version7.0.02.2.0
                  • Values Differ

                  Structure

                  NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.R TypeR Description & ConstraintsCommentsdoco
                  .. Observation C0..*USCoreObservationClinicalResultProfileMeasurements and simple assertions
                  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
                  C0..*SDOHCCObservationPersonalCharacteristicPersonal characteristic 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
                  SDOH-Obs-1: Either subject or extension-Observation.subject must exist but not both
                  SDOH-Obs-2: Focus is only allowed if subject is present
                  SDOH-Obs-3: Must have either performer or derivedFrom
                    ... id Σ0..1idLogical id of this artifactΣ0..1idLogical id of this artifact
                      ... meta SΣ0..1MetaMetadata about the resourceΣ0..1MetaMetadata about the resource
                      • Elements differ in definition for mustSupport: 'true' vs 'false'
                      .... id 0..1stringUnique id for inter-element referencing
                      • Removed this element
                      .... Slices for extension 0..*ExtensionAdditional content defined by implementations
                      Slice: Unordered, Open by value:url
                      • Removed this element
                      .... versionId Σ0..1idVersion specific identifier
                      • Removed this element
                      .... lastUpdated SΣ0..1instantWhen the resource last changed
                      • Removed this element
                      .... source Σ0..1uriIdentifies where the resource comes from
                      • Removed this element
                      .... profile Σ0..*canonical(StructureDefinition)Profiles this resource claims to conform to
                      • Removed this element
                      .... security Σ0..*CodingSecurity Labels applied to this resource
                      Binding: ?? (extensible): Security Labels from the Healthcare Privacy and Security Classification System.


                      • Removed this element
                      .... tag Σ0..*CodingTags applied to this resource
                      Binding: ?? (example): Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".


                      • Removed this element
                      ... 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..1codefinal | corrected | entered-in-error | unknown
                                        Binding: ?? (required)
                                          ... Slices for category S1..*CodeableConceptClassification of type of observation
                                          Slice: Unordered, Open by pattern:$this
                                          Binding: ?? (preferred): Codes for high level observation categories.


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


                                          • Elements differ in definition for mustSupport: 'true' vs 'false'
                                          ... code SΣ1..1CodeableConceptLaboratory Test Name
                                          Binding: ?? (extensible): Laboratory LOINC Codes

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


                                          Required Pattern: {"coding":[{"system":"http://loinc.org","code":"90778-2"}]}
                                            ... subject SΣ1..1Reference(US Core Patient Profile S | Group | Device | US Core Location Profile)Who and/or what the observation is aboutSΣC0..1Reference(US Core Patient Profile)Who and/or what the observation is about
                                            • Element minimum cardinalities differ: '1' vs '0'
                                            ... focus Σ0..*Reference(Resource)What the observation is about, when it is not about the subject of record
                                            ΣC0..1Reference(RelatedPerson)What the observation is about, when it is not about the subject of record
                                            • Element maximum cardinalities differ: '2147483647' vs '1'
                                            ... encounter SΣ0..1Reference(US Core Encounter Profile)Encounter associated with ObservationΣ0..1Reference(Encounter)Healthcare event during which this observation is made
                                            • Elements differ in definition for mustSupport: 'true' vs 'false'
                                            ... effective[x] SΣC0..1dateTime S, Period, Timing, instantClinically relevant time/time-period for observation
                                            us-core-1: Datetime must be at least to day.
                                            Σ0..1dateTime, PeriodClinically relevant time/time-period for observation
                                            • Elements differ in definition for mustSupport: 'true' vs 'false'
                                            ... 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ΣC0..*Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson)Who is responsible for the observation
                                              • Elements differ in definition for mustSupport: 'false' vs 'true'
                                              ... value[x] SΣC0..1Quantity S, CodeableConcept S, string S, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodResult Value
                                              us-core-3: SHALL use UCUM for coded quantity units.
                                              us-core-4: SHOULD use Snomed CT for coded Results
                                              SΣC1..1CodeableConceptActual result
                                              Binding: ?? (preferred): Codes for personal pronouns

                                              • Element minimum cardinalities differ: '0' vs '1'
                                              .... id 0..1stringUnique id for inter-element referencing
                                              • Added this element
                                              .... Slices for extension 0..*ExtensionAdditional content defined by implementations
                                              Slice: Unordered, Open by value:url
                                              • Added this element
                                              .... coding SΣ0..*CodingCode defined by a terminology system
                                              • Added this element
                                              .... text Σ0..1stringPlain text representation of the concept
                                              • Added this element
                                              ... dataAbsentReason SC0..1CodeableConceptWhy the result is missing
                                              Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing.

                                              C0..0
                                              • Elements differ in definition for mustSupport: 'true' vs 'false'
                                              • Element maximum cardinalities differ: '1' vs '0'
                                              ... interpretation S0..*CodeableConceptResult interpretation
                                              Binding: ?? (extensible): Observation Interpretation Codes


                                              0..0
                                              • Elements differ in definition for mustSupport: 'true' vs 'false'
                                              • Element maximum cardinalities differ: '2147483647' vs '0'
                                              ... 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..0
                                                • Element maximum cardinalities differ: '1' vs '0'
                                                ... method 0..1CodeableConceptHow it was done
                                                Binding: ?? (example): Methods for simple observations.

                                                S1..1CodeableConceptHow it was done
                                                Binding: ?? (extensible): Methods for personal characteristic observations.

                                                • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                • Element minimum cardinalities differ: '0' vs '1'
                                                ... specimen S0..1Reference(US Core Specimen Profile)Specimen used for this observation0..0
                                                • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                • Element maximum cardinalities differ: '1' vs '0'
                                                ... device 0..1Reference(Device | DeviceMetric)(Measurement) Device0..1Reference(Device | DeviceMetric)(Measurement) Device
                                                  ... referenceRange SC0..*BackboneElementResult reference range
                                                  obs-3: Must have at least a low or a high or text
                                                  us-core-22: SHALL use UCUM for coded quantity units.
                                                  C0..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
                                                        .... 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
                                                                    Σ0..*Reference(Observation | QuestionnaireResponse | MolecularSequence)Related resource that belongs to the Observation group
                                                                      ... derivedFrom Σ0..*Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | Observation | MolecularSequence)Related measurements the observation is made from
                                                                      SΣC0..*Reference(DocumentReference | QuestionnaireResponse | Observation)Related measurements the observation is made from
                                                                      • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                      ... component Σ0..*BackboneElementComponent results
                                                                      Σ0..*BackboneElementComponent results
                                                                        .... 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