Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-heart-rate vs http://hl7.org/fhir/us/ecr/StructureDefinition/us-ph-travel-history

Left:US Core Heart Rate Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-heart-rate)
Right:US Public Health Travel History (http://hl7.org/fhir/us/ecr/StructureDefinition/us-ph-travel-history)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-heart-rate' vs 'http://hl7.org/fhir/us/ecr/StructureDefinition/us-ph-travel-history'
ErrorStructureDefinition.versionValues for version differ: '4.1.0' vs '2.0.0'
InformationStructureDefinition.nameValues for name differ: 'USCoreHeartRateProfile' vs 'USPublicHealthTravelHistory'
InformationStructureDefinition.titleValues for title differ: 'US Core Heart Rate Profile' vs 'US Public Health Travel History'
InformationStructureDefinition.dateValues for date differ: '2020-11-17' vs '2022-01-18T12:57:33+00:00'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 International - Cross-Group Projects' vs 'HL7 Public Health Work Group (http://www.hl7.org/Special/committees/pher/index.cfm)'
ErrorStructureDefinition.baseDefinitionValues for baseDefinition differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-vital-signs' vs 'http://hl7.org/fhir/StructureDefinition/Observation'
WarningObservationElements differ in short: 'US Core Heart Rate Profile' vs 'US Public Health Travel History'
WarningObservationElements differ in definition: 'Defines constraints on Observation to represent heart rate observations with a standard LOINC code and UCUM units of measure. This profile is derived from the US Core Vital Signs Profile.' vs 'Measurements and simple assertions made about a patient, device or other subject.'
WarningObservation.statusElements differ in definition for mustSupport: 'true' vs 'false'
WarningObservation.categoryElements differ in definition for mustSupport: 'true' vs 'false'
InformationObservation.categoryElement minimum cardinalities differ: '1' vs '0'
WarningObservation.codeElements differ in short: 'Heart Rate' vs 'Type of observation (code / type)'
WarningObservation.codeElements differ in definition: 'Coded Responses from C-CDA Vital Sign Results.' vs 'Describes what was observed. Sometimes this is called the observation 'name'.'
WarningObservation.codeElements differ in requirements: '5. SHALL contain exactly one [1..1] code, where the @code SHOULD be selected from ValueSet HITSP Vital Sign Result Type 2.16.840.1.113883.3.88.12.80.62 DYNAMIC (CONF:7301).' vs 'Knowing what kind of observation is being made is essential to understanding the observation.'
WarningObservation.codeElements differ in binding.description: 'The vital sign codes from the base FHIR and US Core Vital Signs.' vs 'Codes identifying names of simple observations.'
WarningObservation.effective[x]Elements differ in short: 'Often just a dateTime for Vital Signs' vs 'Date or period of time spent in the location'
WarningObservation.effective[x]Elements differ in definition: 'Often just a dateTime for Vital Signs.' vs 'It is important to accurately capture the most accurate dates possible. The focus should be on date of arrival and date of departure.'
InformationObservation.effective[x]Element minimum cardinalities differ: '1' vs '0'
WarningObservation.value[x]Elements differ in short: 'Vital Signs Value' vs 'Actual result'
WarningObservation.value[x]Elements differ in definition: 'Vital Signs value are typically recorded using the Quantity data type.' vs 'The information determined as a result of making the observation, if the information has a simple value.'
WarningObservation.value[x]Elements differ in requirements: '9. SHALL contain exactly one [1..1] value with @xsi:type='PQ' (CONF:7305).' 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.'
WarningObservation.value[x]Elements differ in definition for mustSupport: 'true' vs 'false'
WarningObservation.dataAbsentReasonElements differ in definition for mustSupport: 'true' vs 'false'
WarningObservation.hasMemberElements differ in short: 'Used when reporting vital signs panel components' vs 'Related resource that belongs to the Observation group'
WarningObservation.hasMemberElements differ in definition: 'Used when reporting vital signs panel components.' vs '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.'
WarningObservation.hasMemberElements differ in definition for mustSupport: 'false' vs 'true'
ErrorObservation.hasMemberType Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence], CanonicalType[http://hl7.org/fhir/StructureDefinition/vitalsigns]]) vs Reference([CanonicalType[http://hl7.org/fhir/us/ecr/StructureDefinition/us-ph-transportation-details], CanonicalType[http://hl7.org/fhir/us/ecr/StructureDefinition/us-ph-exposure-contact-information]])
WarningObservation.componentElements differ in short: 'Component observations' vs 'Component results'
WarningObservation.componentElements differ in definition: 'Used when reporting component observation such as systolic and diastolic blood pressure.' vs '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.'
InformationObservation.componentElement minimum cardinalities differ: '0' vs '1'
WarningObservation.component.codeElements differ in definition for mustSupport: 'true' vs 'false'
WarningObservation.component.codeElements differ in binding.description: 'The vital sign codes from the base FHIR and US Core Vital Signs.' vs 'Codes identifying names of simple observations.'
WarningObservation.component.value[x]Elements differ in short: 'Vital Sign Component Value' vs 'Actual component result'
WarningObservation.component.value[x]Elements differ in definition: 'Vital Signs value are typically recorded using the Quantity data type. For supporting observations such as cuff size could use other datatypes such as CodeableConcept.' vs 'The information determined as a result of making the observation, if the information has a simple value.'
WarningObservation.component.value[x]Elements differ in requirements: '9. SHALL contain exactly one [1..1] value with @xsi:type='PQ' (CONF:7305).' 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.'
WarningObservation.component.value[x]Elements differ in definition for mustSupport: 'true' vs 'false'
WarningObservation.component.dataAbsentReasonElements differ in definition for mustSupport: 'true' vs 'false'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-vital-signshttp://hl7.org/fhir/StructureDefinition/Observation
    • 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'
    .date2020-11-172022-01-18T12:57:33+00:00
    • Values Differ
    .descriptionDefines constraints on Observation to represent heart rate observations with a standard LOINC code and UCUM units of measure. This profile is derived from the US Core Vital Signs Profile.This Observation profile represents a patient's travel history. The following data for a patient can be recorded: * travel history as a string, an address, or a coded location * the date or period of time spent in the location (Observation.effectiveTime) * it is important to accurately capture the most accurate dates possible * the focus should be on date of arrival and date of departure * the concepts of dates as related to travel are especially useful for determining need for Federal Public Health Notifications (FPHNs) and these dates are used to alert foreign ministries of health about their residents who may have been contacts of cases, or if a flight that was outbound from the USA had an infectious traveler on it * most uses will involve a single location (Observation.component), however, it is possible to specify multiple locations (but there is only a single effectiveTime) * this allows for cases where a patient cannot remember exact dates of travel (e.g. I traveled to London, Paris, and Berlin in July and August 2016) * free text describing the travel history details and location (Observation.component.valueCodeableConcept.text element) * use Observation.component.codeableConcept to record a coded location * use Observationcomponent.extension to record a specific address * where a more granular address than state is known (e.g. city, street) it is appropriate to use the extension to record an address rather than using the coded location
    • Values Differ
    .experimentalfalse
      .fhirVersion4.0.1
        .jurisdiction
          ..jurisdiction[0]urn:iso:std:iso:3166#US
            .kindresource
              .nameUSCoreHeartRateProfileUSPublicHealthTravelHistory
              • Values Differ
              .publisherHL7 International - Cross-Group ProjectsHL7 Public Health Work Group (http://www.hl7.org/Special/committees/pher/index.cfm)
              • Values Differ
              .purpose
                .statusactive
                  .titleUS Core Heart Rate ProfileUS Public Health Travel History
                  • Values Differ
                  .typeObservation
                    .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-heart-ratehttp://hl7.org/fhir/us/ecr/StructureDefinition/us-ph-travel-history
                    • Values Differ
                    .version4.1.02.0.0
                    • Values Differ

                    Structure

                    NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.L TypeL Description & ConstraintsCommentsdoco
                    .. Observation I0..*USCoreVitalSignsProfileUS Core Heart Rate Profile
                    I0..*ObservationUS Public Health Travel History
                    • Elements differ in short: 'US Core Heart Rate Profile' vs 'US Public Health Travel History'
                    • Elements differ in definition: 'Defines constraints on Observation to represent heart rate observations with a standard LOINC code and UCUM units of measure. This profile is derived from the US Core Vital Signs Profile.' vs 'Measurements and simple assertions made about a patient, device or other subject.'
                    ... id Σ0..1stringLogical id of this artifactΣ0..1stringLogical 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)
                          Max Binding: AllLanguages: A human language.

                          0..1codeLanguage of the resource content
                          Binding: CommonLanguages (preferred)
                          Max Binding: AllLanguages: A human language.

                            ... 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..*ExtensionAdditional content defined by implementations
                                  ... 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)
                                          ?!Σ1..1coderegistered | preliminary | final | amended +
                                          Binding: ObservationStatus (required): Codes providing the status of an observation.

                                          • Elements differ in definition for mustSupport: 'true' vs 'false'
                                          ... Slices for category S1..*CodeableConceptClassification of type of observation
                                          Slice: Unordered, Open by value:coding.code, value:coding.system
                                          Binding: ObservationCategoryCodes (preferred): Codes for high level observation categories.


                                          0..*CodeableConceptClassification of type of observation
                                          Binding: ObservationCategoryCodes (preferred): Codes for high level observation categories.


                                          • Elements differ in definition for mustSupport: 'true' vs 'false'
                                          • Element minimum cardinalities differ: '1' vs '0'
                                          ... code SΣ1..1CodeableConceptHeart Rate
                                          Binding: US Core Vital Signs ValueSet (extensible): The vital sign codes from the base FHIR and US Core Vital Signs.


                                          Required Pattern: {"coding":[{"system":"http://loinc.org","code":"8867-4"}]}
                                          SΣ1..1CodeableConceptType of observation (code / type)
                                          Binding: LOINCCodes (example): Codes identifying names of simple observations.


                                          Required Pattern: {"coding":[{"system":"http://snomed.info/sct","code":"420008001"}]}
                                          • Elements differ in short: 'Heart Rate' vs 'Type of observation (code / type)'
                                          • Elements differ in definition: 'Coded Responses from C-CDA Vital Sign Results.' vs 'Describes what was observed. Sometimes this is called the observation "name".'
                                          • Elements differ in requirements: '5. SHALL contain exactly one [1..1] code, where the @code SHOULD be selected from ValueSet HITSP Vital Sign Result Type 2.16.840.1.113883.3.88.12.80.62 DYNAMIC (CONF:7301).' vs 'Knowing what kind of observation is being made is essential to understanding the observation.'
                                          • Elements differ in binding.description: 'The vital sign codes from the base FHIR and US Core Vital Signs.' vs 'Codes identifying names of simple observations.'
                                          ... subject SΣ1..1Reference(US Core Patient Profile)Who and/or what the observation is aboutSΣ1..1Reference(US Public Health Patient)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
                                                ... effective[x] SΣI1..1dateTime S, PeriodOften just a dateTime for Vital SignsSΣ0..1dateTime, Period, Timing, instantDate or period of time spent in the location
                                                • Elements differ in short: 'Often just a dateTime for Vital Signs' vs 'Date or period of time spent in the location'
                                                • Elements differ in definition: 'Often just a dateTime for Vital Signs.' vs 'It is important to accurately capture the most accurate dates possible. The focus should be on date of arrival and date of departure.'
                                                • Element minimum cardinalities differ: '1' vs '0'
                                                ... 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
                                                  Σ0..*Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson)Who is responsible for the observation
                                                    ... Slices for value[x] SΣI0..1QuantityVital Signs Value
                                                    Slice: Unordered, Closed by type:$this
                                                    Binding: VitalSignsUnits (extensible): Common UCUM units for recording Vital Signs.

                                                    ΣI0..1Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodActual result
                                                    • Elements differ in short: 'Vital Signs Value' vs 'Actual result'
                                                    • Elements differ in definition: 'Vital Signs value are typically recorded using the Quantity data type.' vs 'The information determined as a result of making the observation, if the information has a simple value.'
                                                    • Elements differ in requirements: '9. SHALL contain exactly one [1..1] value with @xsi:type="PQ" (CONF:7305).' 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.'
                                                    • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                    ... dataAbsentReason SI0..1CodeableConceptWhy the result is missing
                                                    Binding: DataAbsentReason (extensible): Codes specifying why the result (Observation.value[x]) is missing.

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

                                                    • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                    ... 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.


                                                      ... 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..1CodeableConceptObserved body part
                                                        Binding: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality.

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

                                                          0..1CodeableConceptHow it was done
                                                          Binding: ObservationMethods (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 I0..*BackboneElementProvides guide for interpretation
                                                                obs-3: Must have at least a low or a high or text
                                                                I0..*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 I0..1SimpleQuantityLow Range, if relevantI0..1SimpleQuantityLow Range, if relevant
                                                                          .... high I0..1SimpleQuantityHigh Range, if relevantI0..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(QuestionnaireResponse | MolecularSequence | Vital Signs Profile)Used when reporting vital signs panel components
                                                                                    SΣ0..*Reference(US Public Health Transportation Details | US Public Health Exposure Contact Information)Related resource that belongs to the Observation group
                                                                                    • Elements differ in short: 'Used when reporting vital signs panel components' vs 'Related resource that belongs to the Observation group'
                                                                                    • Elements differ in definition: 'Used when reporting vital signs panel components.' vs '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.'
                                                                                    • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                                    • Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence], CanonicalType[http://hl7.org/fhir/StructureDefinition/vitalsigns]]) vs Reference([CanonicalType[http://hl7.org/fhir/us/ecr/StructureDefinition/us-ph-transportation-details], CanonicalType[http://hl7.org/fhir/us/ecr/StructureDefinition/us-ph-exposure-contact-information]])
                                                                                    ... derivedFrom Σ0..*Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | MolecularSequence | Vital Signs Profile)Related measurements the observation is made from
                                                                                    Σ0..*Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | Observation | MolecularSequence)Related measurements the observation is made from
                                                                                      ... component SΣI0..*BackboneElementComponent observations
                                                                                      SΣ1..*BackboneElementComponent results
                                                                                      Slice: Unordered, Open by value:code
                                                                                      • Elements differ in short: 'Component observations' vs 'Component results'
                                                                                      • Elements differ in definition: 'Used when reporting component observation such as systolic and diastolic blood pressure.' vs '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.'
                                                                                      • Element minimum cardinalities differ: '0' vs '1'
                                                                                      .... 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 SΣ1..1CodeableConceptType of component observation (code / type)
                                                                                            Binding: US Core Vital Signs ValueSet (extensible): The vital sign codes from the base FHIR and US Core Vital Signs.

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

                                                                                            • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                                            • Elements differ in binding.description: 'The vital sign codes from the base FHIR and US Core Vital Signs.' vs 'Codes identifying names of simple observations.'
                                                                                            .... value[x] SΣI0..1Quantity S, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodVital Sign Component Value
                                                                                            Binding: VitalSignsUnits (extensible): Common UCUM units for recording Vital Signs.

                                                                                            Σ0..1Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodActual component result
                                                                                            • Elements differ in short: 'Vital Sign Component Value' vs 'Actual component result'
                                                                                            • Elements differ in definition: 'Vital Signs value are typically recorded using the Quantity data type. For supporting observations such as cuff size could use other datatypes such as CodeableConcept.' vs 'The information determined as a result of making the observation, if the information has a simple value.'
                                                                                            • Elements differ in requirements: '9. SHALL contain exactly one [1..1] value with @xsi:type="PQ" (CONF:7305).' 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.'
                                                                                            • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                                            .... dataAbsentReason SI0..1CodeableConceptWhy the component result is missing
                                                                                            Binding: DataAbsentReason (extensible): Codes specifying why the result (Observation.value[x]) is missing.

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

                                                                                            • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                                            .... 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