Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-sexual-orientation vs http://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationRaceOMB

Left:US Core Observation Sexual Orientation Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-sexual-orientation)
Right:SDOHCC Observation Race OMB (http://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationRaceOMB)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-sexual-orientation' vs 'http://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationRaceOMB'
ErrorStructureDefinition.versionValues for version differ: '6.0.0-ballot' vs '2.0.0'
InformationStructureDefinition.nameValues for name differ: 'USCoreObservationSexualOrientationProfile' vs 'SDOHCCObservationRaceOMB'
InformationStructureDefinition.titleValues for title differ: 'US Core Observation Sexual Orientation Profile' vs 'SDOHCC Observation Race OMB'
InformationStructureDefinition.statusValues for status differ: 'active' vs 'draft'
InformationStructureDefinition.dateValues for date differ: '2022-04-20' vs '2022-11-21T18:34:14+00:00'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 International - Cross-Group Projects' vs 'HL7 International - Patient Care WG'
ErrorStructureDefinition.baseDefinitionValues for baseDefinition differ: 'http://hl7.org/fhir/StructureDefinition/Observation' vs 'http://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationPersonalCharacteristic'
WarningObservationElements differ in short: 'Measurements and simple assertions' vs 'Race observation'
WarningObservationElements differ in definition: '\-' vs 'For race observations that use Office of Management and Budget (OMB) race category codes and CDC race codes.'
WarningObservationElements differ in comments: '\-' vs 'For observations about the race of an individual.'
WarningObservation.extensionElements differ in short: 'Additional content defined by implementations' vs 'Extension'
WarningObservation.extensionElements differ in definition: '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'
WarningObservation.statusElements differ in short: 'registered | preliminary | final | amended +' vs 'final | corrected | entered-in-error | unknown'
WarningObservation.statusElements differ in definition: 'The status of the result value.' vs 'The status of the observation value.'
WarningObservation.statusElements differ in requirements: '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.'
InformationObservation.categoryElement minimum cardinalities differ: '0' vs '1'
WarningObservation.codeElements differ in short: 'Sexual Orientation' vs 'Type of observation (code / type)'
WarningObservation.codeElements differ in comments: '*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.' 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'
WarningObservation.effective[x]Elements differ in definition: 'This records the time during which the patient had identified their emotional, romantic, sexual, or affectional attraction to another person.' vs '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.'
WarningObservation.effective[x]Elements differ in 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.' 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] 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'
WarningObservation.value[x]Elements differ in definition for mustSupport: 'false' vs 'true'
InformationObservation.value[x]Element maximum cardinalities differ: '1' vs '0'
WarningObservation.dataAbsentReasonElements differ in definition for mustSupport: 'false' vs 'true'
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.methodElements differ in binding.description: 'Methods for simple observations.' vs 'Methods for personal characteristic observations.'
InformationObservation.specimenElement maximum cardinalities differ: '1' vs '0'
InformationObservation.referenceRangeElement maximum cardinalities differ: '2147483647' vs '0'
WarningObservation.derivedFromElements differ in definition for mustSupport: 'false' vs 'true'
WarningObservation.componentElements differ in definition: 'Some observations have multiple component observations. These component observations are expressed as separate code value pairs that share the same attributes. Examples include systolic and diastolic component observations for blood pressure measurement and multiple component observations for genetics observations.' vs 'Some observations have multiple component observations. These component observations are expressed as separate code value pairs that share the same attributes.'
WarningObservation.componentElements differ in comments: 'For a discussion on the ways Observations can be assembled in groups together see [Notes] below.' vs 'For a discussion on the ways Observations can be assembled in groups together see [Notes] below. NOTE: The same LOINC code is used for all three components of this draft profile. If the profile is adopted as part of the US Core standard, new LOINC codes (possibly a panel) will be needed to represent the components (e.g., a new LOINC code for detailed race and for text description of race).'
WarningObservation.componentElements differ in requirements: 'Component observations share the same attributes in the Observation resource as the primary observation and are always treated a part of a single observation (they are not separable). However, the reference range for the primary observation value is not inherited by the component values and is required when appropriate for each component observation.' vs 'Component observations share the same attributes in the Observation resource as the primary observation and are always treated a part of a single observation (they are not separable).'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/Observationhttp://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'
    .date2022-04-202022-11-21T18:34:14+00:00
    • Values Differ
    .descriptionThe US Core Observation Sexual Orientation Profile meets the U.S. Core Data for Interoperability (USCDI) v2 'Sexual Orientation' requirements. this profile sets minimum expectations for the Observation resource to record, search, and fetch sexual orientation observations 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 when using this profile. It provides the floor for standards development for specific use cases.Profile for race observations that use Office of Management and Budget (OMB) race category codes and CDC race codes. This profile is intended for draft use only. The Cross-Group Projects work group granted a variance to US Core on 06/23/2022 - Jira ticket FHIR-37582. 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
            .nameUSCoreObservationSexualOrientationProfileSDOHCCObservationRaceOMB
            • Values Differ
            .publisherHL7 International - Cross-Group ProjectsHL7 International - Patient Care WG
            • Values Differ
            .purpose
              .statusactivedraft
              • Values Differ
              .titleUS Core Observation Sexual Orientation ProfileSDOHCC Observation Race OMB
              • Values Differ
              .typeObservation
                .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-sexual-orientationhttp://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationRaceOMB
                • Values Differ
                .version6.0.0-ballot2.0.0
                • Values Differ

                Structure

                NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.L TypeL Description & ConstraintsCommentsdoco
                .. Observation C0..*ObservationMeasurements and simple assertions
                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..*SDOHCCObservationPersonalCharacteristicRace observation
                SDOH-Race-1: Must have either a dataAbsentReason or at least one of the defined race components but not both
                • Elements differ in short: 'Measurements and simple assertions' vs 'Race observation'
                • Elements differ in definition: '\-' vs 'For race observations that use Office of Management and Budget (OMB) race category codes and CDC race codes.'
                • Elements differ in comments: '\-' vs 'For observations about the race of an individual.'
                ... 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: CommonLanguages (preferred): A human language.

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

                      Additional BindingsPurpose
                      AllLanguagesMax 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
                            • Elements differ in short: 'Additional content defined by implementations' vs 'Extension'
                            • Elements differ in definition: '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'
                            ... 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: ObservationStatus (required)
                                    ?!SΣ1..1codefinal | corrected | entered-in-error | unknown
                                    Binding: SDOHCC ValueSet Observation Status (required)
                                    • Elements differ in short: 'registered | preliminary | final | amended +' vs 'final | corrected | entered-in-error | unknown'
                                    • Elements differ in definition: 'The status of the result value.' vs 'The status of the observation value.'
                                    • Elements differ in requirements: '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.'
                                    ... category 0..*CodeableConceptClassification of type of observation
                                    Binding: ObservationCategoryCodes (preferred): Codes for high level observation categories.


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


                                    • Element minimum cardinalities differ: '0' vs '1'
                                    ... code SΣ1..1CodeableConceptSexual Orientation
                                    Binding: LOINCCodes (example): Codes identifying names of simple observations.


                                    Required Pattern: {"coding":[{"system":"http://loinc.org","code":"76690-7"}]}
                                    SΣ1..1CodeableConceptType of observation (code / type)
                                    Binding: LOINCCodes (preferred)
                                    Required Pattern: {"coding":[{"system":"http://loinc.org","code":"72826-1"}]}
                                    • Elements differ in short: 'Sexual Orientation' vs 'Type of observation (code / type)'
                                    • Elements differ in comments: '*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.' 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).'
                                    ... subject SΣ1..1Reference(US Core Patient 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 Σ0..1Reference(Encounter)Healthcare event during which this observation is madeΣ0..1Reference(Encounter)Healthcare event during which this observation is made
                                      ... effective[x] SΣ0..1dateTime S, Period, Timing, instantClinically relevant time/time-period for observationΣ0..1dateTime, PeriodClinically relevant time/time-period for observation
                                      • Elements differ in definition: 'This records the time during which the patient had identified their emotional, romantic, sexual, or affectional attraction to another person.' vs '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.'
                                      • Elements differ in 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.' 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] datatype which allow the measurement to be tied to regular life events. NOTE: dateTime is Must Support, but currently tooling does not support this.'
                                      • 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'
                                        ... Slices for value[x] ΣC0..1Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodActual result
                                        Slice: Unordered, Open by type:$this
                                        SΣC0..0
                                        • Elements differ in definition for mustSupport: 'false' vs 'true'
                                        • Element maximum cardinalities differ: '1' vs '0'
                                        ... dataAbsentReason C0..1CodeableConceptWhy the result is missing
                                        Binding: DataAbsentReason (extensible): Codes specifying why the result (Observation.value[x]) is missing.

                                        SC0..1CodeableConceptWhy the result is missing
                                        Binding: SDOHCC ValueSet Observation DataAbsentReason (required)
                                        • Elements differ in definition for mustSupport: 'false' vs 'true'
                                        ... interpretation 0..*CodeableConceptHigh, low, normal, etc.
                                        Binding: ObservationInterpretationCodes (extensible): Codes identifying interpretations of observations.


                                        0..0
                                        • Element maximum cardinalities differ: '2147483647' vs '0'
                                        ... note 0..*AnnotationComments about the observation
                                        0..*AnnotationComments about the observation
                                          ... bodySite 0..1CodeableConceptObserved body part
                                          Binding: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality.

                                          0..0
                                          • Element maximum cardinalities differ: '1' vs '0'
                                          ... method 0..1CodeableConceptHow it was done
                                          Binding: ObservationMethods (example): Methods for simple observations.

                                          S1..1CodeableConceptHow it was done
                                          Binding: SDOHCC ValueSet Observation Method (extensible): Methods for personal characteristic observations.

                                          • Elements differ in definition for mustSupport: 'false' vs 'true'
                                          • Element minimum cardinalities differ: '0' vs '1'
                                          • Elements differ in binding.description: 'Methods for simple observations.' vs 'Methods for personal characteristic observations.'
                                          ... specimen 0..1Reference(Specimen)Specimen used for this observation0..0
                                          • Element maximum cardinalities differ: '1' vs '0'
                                          ... device 0..1Reference(Device | DeviceMetric)(Measurement) Device0..1Reference(Device | DeviceMetric)(Measurement) Device
                                            ... referenceRange C0..*BackboneElementProvides guide for interpretation
                                            C0..0
                                            • 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..1SimpleQuantityLow Range, if relevantC0..1SimpleQuantityLow Range, if relevant
                                                    .... high C0..1SimpleQuantityHigh Range, if relevantC0..1SimpleQuantityHigh Range, if relevant
                                                      .... type 0..1CodeableConceptReference range qualifier
                                                      Binding: ObservationReferenceRangeMeaningCodes (preferred): Code for the meaning of a reference range.

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

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


                                                        0..*CodeableConceptReference range population
                                                        Binding: ObservationReferenceRangeAppliesToCodes (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
                                                                ΣC0..*BackboneElementComponent results
                                                                Slice: Unordered, Open by pattern:code, type:value, value:value
                                                                • Elements differ in definition: 'Some observations have multiple component observations. These component observations are expressed as separate code value pairs that share the same attributes. Examples include systolic and diastolic component observations for blood pressure measurement and multiple component observations for genetics observations.' vs 'Some observations have multiple component observations. These component observations are expressed as separate code value pairs that share the same attributes.'
                                                                • Elements differ in comments: 'For a discussion on the ways Observations can be assembled in groups together see [Notes] below.' vs 'For a discussion on the ways Observations can be assembled in groups together see [Notes] below. NOTE: The same LOINC code is used for all three components of this draft profile. If the profile is adopted as part of the US Core standard, new LOINC codes (possibly a panel) will be needed to represent the components (e.g., a new LOINC code for detailed race and for text description of race).'
                                                                • Elements differ in requirements: 'Component observations share the same attributes in the Observation resource as the primary observation and are always treated a part of a single observation (they are not separable). However, the reference range for the primary observation value is not inherited by the component values and is required when appropriate for each component observation.' vs 'Component observations share the same attributes in the Observation resource as the primary observation and are always treated a part of a single observation (they are not separable).'
                                                                .... 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: LOINCCodes (example): Codes identifying names of simple observations.

                                                                      Σ1..1CodeableConceptType of component observation (code / type)
                                                                      Binding: LOINCCodes (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: DataAbsentReason (extensible): Codes specifying why the result (Observation.value[x]) is missing.

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

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


                                                                            0..*CodeableConceptHigh, low, normal, etc.
                                                                            Binding: ObservationInterpretationCodes (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