Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab vs http://hl7.org/fhir/us/physical-activity/StructureDefinition/pa-observation-evs-days-per-week

Left:US Core Laboratory Result Observation Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab)
Right:PA Vital Sign Days per Week (http://hl7.org/fhir/us/physical-activity/StructureDefinition/pa-observation-evs-days-per-week)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab' vs 'http://hl7.org/fhir/us/physical-activity/StructureDefinition/pa-observation-evs-days-per-week'
ErrorStructureDefinition.versionValues for version differ: '6.0.0-ballot' vs '1.0.0-ballot'
InformationStructureDefinition.nameValues for name differ: 'USCoreLaboratoryResultObservationProfile' vs 'PAObservationEVSDaysPerWeek'
InformationStructureDefinition.titleValues for title differ: 'US Core Laboratory Result Observation Profile' vs 'PA Vital Sign Days per Week'
InformationStructureDefinition.dateValues for date differ: '2022-11-19' vs '2023-03-28T18:30:00+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/us/core/StructureDefinition/us-core-observation-clinical-result' vs 'http://hl7.org/fhir/us/physical-activity/StructureDefinition/pa-observation-evs'
WarningObservationElements differ in definition: '\-' vs 'A profile for observations that capture a patient's average days per week of moderate-to-vigorous physical activity.'
WarningObservationElements differ in comments: '\-' vs '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.'
InformationObservation.implicitRulesElement maximum cardinalities differ: '1' vs '0'
WarningObservation.modifierExtensionElements differ in short: 'Extensions that cannot be ignored' vs 'Extension'
WarningObservation.modifierExtensionElements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'An Extension'
InformationObservation.modifierExtensionElement maximum cardinalities differ: '2147483647' vs '0'
WarningObservation.statusElements differ in short: 'registered | preliminary | final | amended +' vs 'final | amended | corrected | entered-in-error'
WarningObservation.statusElements differ in comments: 'This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.' vs 'In the vast majority of cases, the status value will be 'final'. Systems are not expected to distinguish amended and corrected results.'
WarningObservation.categoryElements differ in definition for mustSupport: 'true' vs 'false'
WarningObservation.codeElements differ in short: 'Laboratory Test Name' vs 'Type of observation (code / type)'
WarningObservation.codeElements differ in definition: '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'.'
WarningObservation.codeElements differ in comments: '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.'
WarningObservation.subjectElements differ in short: 'Who and/or what the observation is about' vs 'A reference from one resource to another'
WarningObservation.subjectElements differ in definition: 'The patient, or group of patients, location, or device this observation is about and into whose record the observation is placed. If the actual focus of the observation is different from the subject (or a sample of, part, or region of the subject), the `focus` element or the `code` itself specifies the actual focus of the observation.' vs 'A reference from one resource to another.'
WarningObservation.subjectElements differ in comments: 'One would expect this element to be a cardinality of 1..1. The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.' vs 'References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. A variety of resources might provide support for asserting this condition, however at minimum, systems must support the Physical Activity Vital Sign observations.'
InformationObservation.focusElement maximum cardinalities differ: '2147483647' vs '0'
InformationObservation.effective[x]Element minimum cardinalities differ: '0' vs '1'
WarningObservation.performerElements differ in short: 'Who is responsible for the observation' vs 'A reference from one resource to another'
WarningObservation.performerElements differ in definition: 'Who was responsible for asserting the observed value as 'true'.' vs 'A reference from one resource to another.'
WarningObservation.performerElements differ in definition for mustSupport: 'false' vs 'true'
ErrorObservation.performerType Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Practitioner], CanonicalType[http://hl7.org/fhir/StructureDefinition/PractitionerRole], CanonicalType[http://hl7.org/fhir/StructureDefinition/Organization], CanonicalType[http://hl7.org/fhir/StructureDefinition/CareTeam], CanonicalType[http://hl7.org/fhir/StructureDefinition/Patient], CanonicalType[http://hl7.org/fhir/StructureDefinition/RelatedPerson]]) vs Reference([CanonicalType[http://hl7.org/fhir/us/physical-activity/StructureDefinition/reference-rest-or-logical]])([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitionerrole], CanonicalType[http://hl7.org/fhir/StructureDefinition/RelatedPerson]])
WarningObservation.value[x]Elements differ in short: 'Result Value' vs 'Actual result'
WarningObservation.value[x]Elements differ in definition: 'The Laboratory result value. If a coded value, the valueCodeableConcept.code **SHOULD** be selected from [SNOMED CT] if the concept exists. If a numeric value, valueQuantity.code **SHALL** be selected from [UCUM]. A FHIR [UCUM Codes value set] 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.'
WarningObservation.dataAbsentReasonElements differ in definition for mustSupport: 'true' vs 'false'
WarningObservation.noteElements differ in comments: 'May include general statements about the observation, or statements about significant, unexpected or unreliable results values, or information about its source when relevant to its interpretation.' vs 'May include general statements about the observation, or statements about significant, unexpected or unreliable results values, or information about its source when relevant to its interpretation. Comments allows supporting and qualifying information'
WarningObservation.noteElements differ in definition for mustSupport: 'false' vs 'true'
WarningObservation.note.author[x]Elements differ in short: 'Individual responsible for the annotation' vs 'A reference from one resource to another'
WarningObservation.note.author[x]Elements differ in definition: 'The individual responsible for making the annotation.' vs 'A reference from one resource to another.'
WarningObservation.note.author[x]Elements differ in comments: 'Organization is used when there's no need for specific attribution as to who made the comment.' vs 'References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.'
WarningObservation.note.author[x]Elements differ in definition for mustSupport: 'false' vs 'true'
InformationObservation.note.author[x]Element minimum cardinalities differ: '0' vs '1'
WarningObservation.note.timeElements differ in definition for mustSupport: 'false' vs 'true'
InformationObservation.note.timeElement minimum cardinalities differ: '0' vs '1'
WarningObservation.note.textElements differ in definition for mustSupport: 'false' vs 'true'
InformationObservation.bodySiteElement maximum cardinalities differ: '1' vs '0'
WarningObservation.specimenElements differ in definition for mustSupport: 'true' vs 'false'
InformationObservation.specimenElement maximum cardinalities differ: '1' vs '0'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-clinical-resulthttp://hl7.org/fhir/us/physical-activity/StructureDefinition/pa-observation-evs
    • 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-11-192023-03-28T18:30:00+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 when using this profile. It provides the floor for standards development for specific use cases.A profile for observations that capture a patient's average days per week of moderate-to-vigorous physical activity.
    • Values Differ
    .experimentalfalse
    • Removed the item 'false'
    .fhirVersion4.0.1
      .jurisdiction
        ..jurisdiction[0]urn:iso:std:iso:3166#US
          .kindresource
            .nameUSCoreLaboratoryResultObservationProfilePAObservationEVSDaysPerWeek
            • Values Differ
            .publisherHL7 International - Cross-Group ProjectsHL7 International - Patient Care WG
            • Values Differ
            .purpose
              .statusactive
                .titleUS Core Laboratory Result Observation ProfilePA Vital Sign Days per Week
                • Values Differ
                .typeObservation
                  .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-labhttp://hl7.org/fhir/us/physical-activity/StructureDefinition/pa-observation-evs-days-per-week
                  • Values Differ
                  .version6.0.0-ballot1.0.0-ballot
                  • Values Differ

                  Structure

                  NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.L TypeL Description & ConstraintsCommentsdoco
                  .. Observation C0..*USCoreObservationClinicalResultProfileMeasurements and simple assertions
                  C0..*PAObservationEVSMeasurements and simple assertions
                  • Elements differ in definition: '\-' vs 'A profile for observations that capture a patient's average days per week of moderate-to-vigorous physical activity.'
                  • Elements differ in comments: '\-' vs '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.'
                  ... 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..0
                      • Element maximum cardinalities differ: '1' vs '0'
                      ... 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..*ExtensionAdditional content defined by implementations
                              ... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
                              ?!0..0
                              • Elements differ in short: 'Extensions that cannot be ignored' vs 'Extension'
                              • Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'An Extension'
                              • Element maximum cardinalities differ: '2147483647' vs '0'
                              ... 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 | amended | corrected | entered-in-error
                                    Binding: ?? (required)
                                    • Elements differ in short: 'registered | preliminary | final | amended +' vs 'final | amended | corrected | entered-in-error'
                                    • Elements differ in comments: 'This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.' vs 'In the vast majority of cases, the status value will be 'final'. Systems are not expected to distinguish amended and corrected results.'
                                    ... 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 pattern:$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: ?? (required)
                                    Required Pattern: {"coding":[{"system":"http://loinc.org","code":"89555-7"}]}
                                    • Elements differ in short: 'Laboratory Test Name' vs 'Type of observation (code / type)'
                                    • Elements differ in definition: '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".'
                                    • Elements differ in comments: '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.'
                                    ... subject SΣ1..1Reference(US Core Patient Profile)Who and/or what the observation is aboutSΣ1..1Reference(US Core Patient Profile)A reference from one resource to another
                                    • Elements differ in short: 'Who and/or what the observation is about' vs 'A reference from one resource to another'
                                    • Elements differ in definition: 'The patient, or group of patients, location, or device this observation is about and into whose record the observation is placed. If the actual focus of the observation is different from the subject (or a sample of, part, or region of the subject), the `focus` element or the `code` itself specifies the actual focus of the observation.' vs 'A reference from one resource to another.'
                                    • Elements differ in comments: 'One would expect this element to be a cardinality of 1..1. The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.' vs 'References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. A variety of resources might provide support for asserting this condition, however at minimum, systems must support the Physical Activity Vital Sign observations.'
                                    ... focus ΣTU0..*Reference(Resource)What the observation is about, when it is not about the subject of record
                                    Σ0..0
                                    • Element maximum cardinalities differ: '2147483647' vs '0'
                                    ... 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ΣC0..1dateTime S, Period, Timing, instantClinically relevant time/time-period for observationSΣ1..1dateTimeClinically relevant time/time-period for observation
                                      Slice: Unordered, Closed by type:$this
                                      • Element minimum cardinalities differ: '0' vs '1'
                                      ... issued Σ0..1instantDate/Time this version was made availableΣ0..1instantDate/Time this version was made available
                                        ... performer Σ0..*Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson)Who is responsible for the observation
                                        SΣ0..*Reference(US Core Patient Profile S | US Core Practitioner Profile S | US Core PractitionerRole Profile | RelatedPerson)A reference from one resource to another
                                        • Elements differ in short: 'Who is responsible for the observation' vs 'A reference from one resource to another'
                                        • Elements differ in definition: 'Who was responsible for asserting the observed value as "true".' vs 'A reference from one resource to another.'
                                        • Elements differ in definition for mustSupport: 'false' vs 'true'
                                        • Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Practitioner], CanonicalType[http://hl7.org/fhir/StructureDefinition/PractitionerRole], CanonicalType[http://hl7.org/fhir/StructureDefinition/Organization], CanonicalType[http://hl7.org/fhir/StructureDefinition/CareTeam], CanonicalType[http://hl7.org/fhir/StructureDefinition/Patient], CanonicalType[http://hl7.org/fhir/StructureDefinition/RelatedPerson]]) vs Reference([CanonicalType[http://hl7.org/fhir/us/physical-activity/StructureDefinition/reference-rest-or-logical]])([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitionerrole], CanonicalType[http://hl7.org/fhir/StructureDefinition/RelatedPerson]])
                                        ... value[x] SΣC0..1Quantity S, CodeableConcept S, string S, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodResult Value
                                        us-core-4: SHOULD use Snomed CT for coded Results
                                        SΣC0..1QuantityActual result
                                        Slice: Unordered, Closed by type:$this
                                        • Elements differ in short: 'Result Value' vs 'Actual result'
                                        • Elements differ in definition: 'The Laboratory result value. If a coded value, the valueCodeableConcept.code **SHOULD** be selected from [SNOMED CT] if the concept exists. If a numeric value, valueQuantity.code **SHALL** be selected from [UCUM]. A FHIR [UCUM Codes value set] 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.'
                                        ... dataAbsentReason SC0..1CodeableConceptWhy the result is missing
                                        Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing.

                                        C0..1CodeableConceptWhy the result is missing
                                        Binding: ?? (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: ?? (extensible): Codes identifying interpretations of observations.


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


                                          ... note 0..*AnnotationComments about the observation
                                          S0..*AnnotationComments about the observation
                                          • Elements differ in comments: 'May include general statements about the observation, or statements about significant, unexpected or unreliable results values, or information about its source when relevant to its interpretation.' vs 'May include general statements about the observation, or statements about significant, unexpected or unreliable results values, or information about its source when relevant to its interpretation. Comments allows supporting and qualifying information'
                                          • Elements differ in definition for mustSupport: 'false' vs 'true'
                                          .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                            .... Slices for extension 0..*ExtensionAdditional content defined by implementations
                                            Slice: Unordered, Open by value:url
                                            0..*ExtensionAdditional content defined by implementations
                                            Slice: Unordered, Open by value:url
                                              .... author[x] Σ0..1Reference(Practitioner | Patient | RelatedPerson | Organization), stringIndividual responsible for the annotationSΣ1..1Reference(Practitioner S | Patient S | RelatedPerson)A reference from one resource to another
                                              • Elements differ in short: 'Individual responsible for the annotation' vs 'A reference from one resource to another'
                                              • Elements differ in definition: 'The individual responsible for making the annotation.' vs 'A reference from one resource to another.'
                                              • Elements differ in comments: 'Organization is used when there's no need for specific attribution as to who made the comment.' vs 'References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.'
                                              • Elements differ in definition for mustSupport: 'false' vs 'true'
                                              • Element minimum cardinalities differ: '0' vs '1'
                                              .... time Σ0..1dateTimeWhen the annotation was madeSΣ1..1dateTimeWhen the annotation was made
                                              • Elements differ in definition for mustSupport: 'false' vs 'true'
                                              • Element minimum cardinalities differ: '0' vs '1'
                                              .... text Σ1..1markdownThe annotation - text content (as markdown)SΣ1..1markdownThe annotation - text content (as markdown)
                                              • Elements differ in definition for mustSupport: 'false' vs 'true'
                                              ... 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.

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

                                                ... 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 C0..*BackboneElementProvides guide for interpretation
                                                  C0..*BackboneElementProvides guide for interpretation
                                                    .... 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
                                                                        Σ0..*Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | Observation | MolecularSequence)Related measurements the observation is made from
                                                                        Slice: Unordered, Open by pattern:code
                                                                          ... 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