Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab vs http://hl7.org/fhir/us/vitals/StructureDefinition/body-weight

Left:US Core Laboratory Result Observation Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab)
Right:Body Weight (http://hl7.org/fhir/us/vitals/StructureDefinition/body-weight)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab' vs 'http://hl7.org/fhir/us/vitals/StructureDefinition/body-weight'
ErrorStructureDefinition.versionValues for version differ: '7.0.0' vs '2.0.0'
InformationStructureDefinition.nameValues for name differ: 'USCoreLaboratoryResultObservationProfile' vs 'BodyWeight'
InformationStructureDefinition.titleValues for title differ: 'US Core Laboratory Result Observation Profile' vs 'Body Weight'
InformationStructureDefinition.statusValues for status differ: 'active' vs 'draft'
InformationStructureDefinition.dateValues for date differ: '2023-10-17' vs '2024-10-09T23:56:46+00:00'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 International / Cross-Group Projects' vs 'HL7 International - Clinical Information Modeling Initiative'
InformationStructureDefinition.copyrightValues for copyright differ: 'Used by permission of HL7 International, all rights reserved Creative Commons License' vs 'Logica Health, all rights reserved Creative Commons License'
InformationStructureDefinition.jurisdictionRemoved the item 'urn:iso:std:iso:3166#US'
InformationStructureDefinition.jurisdictionAdded the item 'http://unstats.un.org/unsd/methods/m49/m49.htm#001'
ErrorStructureDefinition.baseDefinitionValues for baseDefinition differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-clinical-result' vs 'http://hl7.org/fhir/StructureDefinition/bodyweight'
InformationStructureDefinition.shortValues for short differ: 'Measurements and simple assertions' vs 'FHIR Body Weight Profile'
InformationStructureDefinition.definitionValues for definition differ: 'Measurements and simple assertions made about a patient, device or other subject.' vs 'This profile defines how to represent body weight observations in FHIR using a standard LOINC code and UCUM units of measure.'
WarningObservation.metaElements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.shortValues for short differ: 'Additional content defined by implementations' vs 'Extension'
InformationStructureDefinition.definitionValues for definition differ: 'May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'An Extension'
InformationStructureDefinition.requirementsValues for requirements differ: 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).' vs 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/extensibility.html#modifierExtension).'
InformationStructureDefinition.commentValues for comment differ: 'To link an Observation to an Encounter use `encounter`. See the [Notes](http://hl7.org/fhir/R4/observation.html#obsgrouping) below for guidance on referencing another Observation.' vs 'To link an Observation to an Encounter use `encounter`. See the [Notes](http://hl7.org/fhir/observation.html#obsgrouping) below for guidance on referencing another Observation.'
InformationStructureDefinition.shortValues for short differ: 'Laboratory Test Name' vs 'Body weight'
InformationStructureDefinition.definitionValues for definition differ: 'The name of the clinical test or procedure performed on a patient. A LOINC **SHALL** be used if the concept is present in LOINC.' vs 'Body Weight.'
InformationStructureDefinition.commentValues for comment differ: 'The typical patterns for codes are: 1) a LOINC code either as a translation from a 'local' code or as a primary code, or 2) a local code only if no suitable LOINC exists, or 3) both the local and the LOINC translation. Systems SHALL be capable of sending the local code if one exists. When using LOINC , Use either the SHORTNAME or LONG_COMMON_NAME field for the display.' vs 'additional codes that translate or map to this code are allowed. For example a more granular LOINC code or code that is used locally in a system.'
InformationStructureDefinition.requirementsValues for requirements differ: 'Knowing what kind of observation is being made is essential to understanding the observation.' vs '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).'
InformationStructureDefinition.commentValues for comment differ: 'Typically, an observation is made about the subject - a patient, or group of patients, location, or device - and the distinction between the subject and what is directly measured for an observation is specified in the observation code itself ( e.g., 'Blood Glucose') and does not need to be represented separately using this element. Use `specimen` if a reference to a specimen is required. If a code is required instead of a resource use either `bodysite` for bodysites or the standard extension [focusCode](http://hl7.org/fhir/R4/extension-observation-focuscode.html).' vs 'Typically, an observation is made about the subject - a patient, or group of patients, location, or device - and the distinction between the subject and what is directly measured for an observation is specified in the observation code itself ( e.g., 'Blood Glucose') and does not need to be represented separately using this element. Use `specimen` if a reference to a specimen is required. If a code is required instead of a resource use either `bodysite` for bodysites or the standard extension [focusCode](http://hl7.org/fhir/extension-observation-focuscode.html).'
InformationStructureDefinition.shortValues for short differ: 'Encounter associated with Observation' vs 'Healthcare event during which this observation is made'
WarningObservation.encounterElements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.shortValues for short differ: 'Clinically relevant time/time-period for observation' vs 'Often just a dateTime for Vital Signs'
InformationStructureDefinition.definitionValues for definition differ: 'The time or time-period the observed value is asserted as being true. For biological subjects - e.g. human patients - this is usually called the 'physiologically relevant time'. This is usually either the time of the procedure or of specimen collection, but very often the source of the date/time is not known, only the date/time itself.' vs 'Often just a dateTime for Vital Signs.'
InformationStructureDefinition.commentValues for comment differ: 'At least a date should be present unless this observation is a historical report. For recording imprecise or 'fuzzy' times (For example, a blood glucose measurement taken 'after breakfast') use the [Timing](http://hl7.org/fhir/R4/datatypes.html#timing) datatype which allow the measurement to be tied to regular life events.' vs 'At least a date should be present unless this observation is a historical report. For recording imprecise or 'fuzzy' times (For example, a blood glucose measurement taken 'after breakfast') use the [Timing](http://hl7.org/fhir/datatypes.html#timing) datatype which allow the measurement to be tied to regular life events.'
InformationObservation.effective[x]Element minimum cardinalities differ: '0' vs '1'
InformationStructureDefinition.commentValues for comment differ: 'For Observations that don’t require review and verification, it may be the same as the [`lastUpdated` ](http://hl7.org/fhir/R4/resource-definitions.html#Meta.lastUpdated) time of the resource itself. For Observations that do require review and verification for certain updates, it might not be the same as the `lastUpdated` time of the resource itself due to a non-clinically significant update that doesn’t require the new version to be reviewed and verified again.' vs 'For Observations that don’t require review and verification, it may be the same as the [`lastUpdated` ](http://hl7.org/fhir/resource-definitions.html#Meta.lastUpdated) time of the resource itself. For Observations that do require review and verification for certain updates, it might not be the same as the `lastUpdated` time of the resource itself due to a non-clinically significant update that doesn’t require the new version to be reviewed and verified again.'
InformationStructureDefinition.shortValues for short differ: 'Result Value' vs 'Vital Signs value are recorded using the Quantity data type. For supporting observations such as Cuff size could use other datatypes such as CodeableConcept.'
InformationStructureDefinition.definitionValues for definition differ: 'The Laboratory result value. If a coded value, the valueCodeableConcept.code **SHOULD** be selected from [SNOMED CT](http://hl7.org/fhir/ValueSet/uslab-obs-codedresults) if the concept exists. If a numeric value, valueQuantity.code **SHALL** be selected from [UCUM](http://unitsofmeasure.org). A FHIR [UCUM Codes value set](http://hl7.org/fhir/STU3/valueset-ucum-units.html) that defines all UCUM codes is in the FHIR specification.' vs 'Vital Signs value are recorded using the Quantity data type. For supporting observations such as Cuff size could use other datatypes such as CodeableConcept.'
InformationStructureDefinition.commentValues for comment differ: 'An observation may have; 1) a single value here, 2) both a value and a set of related or component values, or 3) only a set of related or component values. If a value is present, the datatype for this element should be determined by Observation.code. A CodeableConcept with just a text would be used instead of a string if the field was usually coded, or if the type associated with the Observation.code defines a coded value. For additional guidance, see the [Notes section](http://hl7.org/fhir/R4/observation.html#notes) below.' vs 'An observation may have; 1) a single value here, 2) both a value and a set of related or component values, or 3) only a set of related or component values. If a value is present, the datatype for this element should be determined by Observation.code. A CodeableConcept with just a text would be used instead of a string if the field was usually coded, or if the type associated with the Observation.code defines a coded value. For additional guidance, see the [Notes section](http://hl7.org/fhir/observation.html#notes) below.'
InformationStructureDefinition.requirementsValues for requirements differ: 'An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations.' vs '9. SHALL contain exactly one [1..1] value with @xsi:type='PQ' (CONF:7305).'
InformationStructureDefinition.shortValues for short differ: 'Result interpretation' vs 'High, low, normal, etc.'
InformationStructureDefinition.commentValues for comment differ: 'Categorical assessment of a laboratory value, often in relation to a test's reference range. Examples include but are not limited to high, low, critical, and normal.' vs 'Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result.'
WarningObservation.interpretationElements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.commentValues for comment differ: 'Only used if not implicit in code found in Observation.code. In many systems, this may be represented as a related observation instead of an inline component. If the use case requires BodySite to be handled as a separate resource (e.g. to identify and track separately) then use the standard extension[ bodySite](http://hl7.org/fhir/R4/extension-bodysite.html).' vs 'Only used if not implicit in code found in Observation.code. In many systems, this may be represented as a related observation instead of an inline component. If the use case requires BodySite to be handled as a separate resource (e.g. to identify and track separately) then use the standard extension[ bodySite](http://hl7.org/fhir/extension-bodysite.html).'
WarningObservation.specimenElements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.shortValues for short differ: 'Result reference range' vs 'Provides guide for interpretation'
InformationStructureDefinition.commentValues for comment differ: 'Upper and lower limit of test values expected for a designated population of individuals. Reference range values may differ by patient characteristics, laboratory test manufacturer and laboratory test performer.' vs 'Most observations only have one generic reference range. Systems MAY choose to restrict to only supplying the relevant reference range based on knowledge about the patient (e.g., specific to the patient's age, gender, weight and other factors), but this might not be possible or appropriate. Whenever more than one reference range is supplied, the differences between them SHOULD be provided in the reference range and/or age properties.'
WarningObservation.referenceRangeElements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.requirementsValues for requirements differ: 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).' vs 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/extensibility.html#modifierExtension).'
InformationStructureDefinition.shortValues for short differ: 'Related resource that belongs to the Observation group' vs 'Used when reporting vital signs panel components'
InformationStructureDefinition.definitionValues for definition differ: 'This observation is a group observation (e.g. a battery, a panel of tests, a set of vital sign measurements) that includes the target as a member of the group.' vs 'Used when reporting vital signs panel components.'
InformationStructureDefinition.commentValues for comment differ: 'When using this element, an observation will typically have either a value or a set of related resources, although both may be present in some cases. For a discussion on the ways Observations can assembled in groups together, see [Notes](http://hl7.org/fhir/R4/observation.html#obsgrouping) below. Note that a system may calculate results from [QuestionnaireResponse](questionnaireresponse.html) into a final score and represent the score as an Observation.' vs 'When using this element, an observation will typically have either a value or a set of related resources, although both may be present in some cases. For a discussion on the ways Observations can assembled in groups together, see [Notes](http://hl7.org/fhir/observation.html#obsgrouping) below. Note that a system may calculate results from [QuestionnaireResponse](http://hl7.org/fhir/questionnaireresponse.html) into a final score and represent the score as an Observation.'
ErrorObservation.hasMemberType Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Observation], CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence], CanonicalType[http://hl7.org/fhir/StructureDefinition/vitalsigns]])
InformationStructureDefinition.commentValues for comment differ: 'All the reference choices that are listed in this element can represent clinical observations and other measurements that may be the source for a derived value. The most common reference will be another Observation. For a discussion on the ways Observations can assembled in groups together, see [Notes](http://hl7.org/fhir/R4/observation.html#obsgrouping) below.' vs 'All the reference choices that are listed in this element can represent clinical observations and other measurements that may be the source for a derived value. The most common reference will be another Observation. For a discussion on the ways Observations can assembled in groups together, see [Notes](http://hl7.org/fhir/observation.html#obsgrouping) below.'
InformationStructureDefinition.shortValues for short differ: 'Component results' vs 'Used when reporting systolic and diastolic blood pressure.'
InformationStructureDefinition.definitionValues for definition differ: '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 'Used when reporting systolic and diastolic blood pressure.'
InformationStructureDefinition.commentValues for comment differ: 'For a discussion on the ways Observations can be assembled in groups together see [Notes](http://hl7.org/fhir/R4/observation.html#notes) below.' vs 'For a discussion on the ways Observations can be assembled in groups together see [Notes](http://hl7.org/fhir/observation.html#notes) below.'
WarningObservation.componentElements differ in definition for mustSupport: 'false' vs 'true'
InformationStructureDefinition.requirementsValues for requirements differ: 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).' vs 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/extensibility.html#modifierExtension).'
WarningObservation.component.codeElements differ in definition for mustSupport: 'false' vs 'true'
InformationStructureDefinition.shortValues for short differ: 'Actual component result' vs 'Vital Sign Value recorded with UCUM'
InformationStructureDefinition.definitionValues for definition differ: 'The information determined as a result of making the observation, if the information has a simple value.' vs 'Vital Sign Value recorded with UCUM.'
InformationStructureDefinition.commentValues for comment differ: 'Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was derived). If a value is present, the datatype for this element should be determined by Observation.code. A CodeableConcept with just a text would be used instead of a string if the field was usually coded, or if the type associated with the Observation.code defines a coded value. For additional guidance, see the [Notes section](http://hl7.org/fhir/R4/observation.html#notes) below.' vs 'Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was derived). If a value is present, the datatype for this element should be determined by Observation.code. A CodeableConcept with just a text would be used instead of a string if the field was usually coded, or if the type associated with the Observation.code defines a coded value. For additional guidance, see the [Notes section](http://hl7.org/fhir/observation.html#notes) below.'
InformationStructureDefinition.requirementsValues for requirements differ: 'An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations.' vs '9. SHALL contain exactly one [1..1] value with @xsi:type='PQ' (CONF:7305).'
WarningObservation.component.value[x]Elements differ in definition for mustSupport: 'false' vs 'true'
WarningObservation.component.dataAbsentReasonElements differ in definition for mustSupport: 'false' vs 'true'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-clinical-resulthttp://hl7.org/fhir/StructureDefinition/bodyweight
    • Values Differ
    .copyrightUsed by permission of HL7 International, all rights reserved Creative Commons LicenseLogica Health, all rights reserved Creative Commons License
    • Values Differ
    .date2023-10-172024-10-09T23:56:46+00:00
    • Values Differ
    .descriptionThe US Core Laboratory Result Observation Profile is based upon the US Core Observation Clinical Result Profile and, along with the US Core DiagnosticReport Profile for Laboratory Results Reporting, meets the U.S. Core Data for Interoperability (USCDI) Laboratory requirements. Laboratory results are grouped and summarized using the DiagnosticReport resource, which references Observation resources. Each Observation resource represents an individual laboratory test and result value, a “nested” panel (such as a microbial susceptibility panel) that references other observations, or rarely a laboratory test with component result values. The US Core Laboratory Result Observation Profile sets minimum expectations for the Observation resource to record, search, and fetch laboratory test results associated with a patient to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains the way the elements are used when using this profile. It provides the floor for standards development for specific use cases.The measured mass of an individual's body.
    • Values Differ
    .experimentalfalse
    • Removed the item 'false'
    .fhirVersion4.0.1
      .jurisdiction
        ..jurisdiction[0]urn:iso:std:iso:3166#US
        • Removed the item 'urn:iso:std:iso:3166#US'
        ..jurisdiction[1]http://unstats.un.org/unsd/methods/m49/m49.htm#001
        • Added the item 'http://unstats.un.org/unsd/methods/m49/m49.htm#001'
        .kindresource
          .nameUSCoreLaboratoryResultObservationProfileBodyWeight
          • Values Differ
          .publisherHL7 International / Cross-Group ProjectsHL7 International - Clinical Information Modeling Initiative
          • Values Differ
          .purpose
            .statusactivedraft
            • Values Differ
            .titleUS Core Laboratory Result Observation ProfileBody Weight
            • Values Differ
            .typeObservation
              .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-labhttp://hl7.org/fhir/us/vitals/StructureDefinition/body-weight
              • Values Differ
              .version7.0.02.0.0
              • Values Differ

              Structure

              NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.R TypeR Description & ConstraintsCommentsdoco
              .. Observation C0..*USCoreObservationClinicalResultProfileMeasurements and simple assertions
              obs-6: dataAbsentReason SHALL only be present if Observation.value[x] is not present
              obs-7: If Observation.code is the same as an Observation.component.code then the value element associated with the code SHALL NOT be present
              us-core-2: If there is no component or hasMember element then either a value[x] or a data absent reason must be present
              C0..*observation-bodyweightFHIR Body Weight Profile
              obs-6: dataAbsentReason SHALL only be present if Observation.value[x] is not present
              obs-7: If Observation.code is the same as an Observation.component.code then the value element associated with the code SHALL NOT be present
              vs-2: If there is no component or hasMember element then either a value[x] or a data absent reason must be present.
                ... id Σ0..1idLogical id of this artifactΣ0..1idLogical id of this artifact
                  ... meta SΣ0..1MetaMetadata about the resourceΣ0..1MetaMetadata about the resource
                  • Elements differ in definition for mustSupport: 'true' vs 'false'
                  .... id 0..1stringUnique id for inter-element referencing
                  • Removed this element
                  .... Slices for extension 0..*ExtensionAdditional content defined by implementations
                  Slice: Unordered, Open by value:url
                  • Removed this element
                  .... versionId Σ0..1idVersion specific identifier
                  • Removed this element
                  .... lastUpdated SΣ0..1instantWhen the resource last changed
                  • Removed this element
                  .... source Σ0..1uriIdentifies where the resource comes from
                  • Removed this element
                  .... profile Σ0..*canonical(StructureDefinition)Profiles this resource claims to conform to
                  • Removed this element
                  .... security Σ0..*CodingSecurity Labels applied to this resource
                  Binding: ?? (extensible): Security Labels from the Healthcare Privacy and Security Classification System.


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


                  • Removed this element
                  ... implicitRules ?!Σ0..1uriA set of rules under which this content was created?!Σ0..1uriA set of rules under which this content was created
                    ... language 0..1codeLanguage of the resource content
                    Binding: ?? (preferred): A human language.

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

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

                                    ?!SΣ1..1coderegistered | preliminary | final | amended +
                                    Binding: ?? (required)
                                      ... Slices for category S1..*CodeableConceptClassification of type of observation
                                      Slice: Unordered, Open by pattern:$this
                                      Binding: ?? (preferred): Codes for high level observation categories.


                                      S1..*CodeableConceptClassification of type of observation
                                      Slice: Unordered, Open by value:coding.code, value:coding.system
                                      Binding: ?? (preferred): Codes for high level observation categories.


                                        ... code SΣ1..1CodeableConceptLaboratory Test Name
                                        Binding: ?? (extensible): Laboratory LOINC Codes

                                        SΣ1..1CodeableConceptBody weight
                                        Binding: ?? (extensible): This identifies the vital sign result type.

                                          .... id 0..1stringUnique id for inter-element referencing
                                          • Added this element
                                          .... Slices for extension 0..*ExtensionAdditional content defined by implementations
                                          Slice: Unordered, Open by value:url
                                          • Added this element
                                          .... Slices for coding Σ0..*CodingCode defined by a terminology system
                                          Slice: Unordered, Open by value:code, value:system
                                          • Added this element
                                          .... text Σ0..1stringPlain text representation of the concept
                                          • Added this element
                                          ... subject SΣ1..1Reference(US Core Patient Profile S | Group | Device | US Core Location Profile)Who and/or what the observation is aboutSΣ1..1Reference(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 SΣ0..1Reference(US Core Encounter Profile)Encounter associated with ObservationΣ0..1Reference(Encounter)Healthcare event during which this observation is made
                                              • Elements differ in definition for mustSupport: 'true' vs 'false'
                                              ... effective[x] SΣC0..1dateTime S, Period, Timing, instantClinically relevant time/time-period for observation
                                              us-core-1: Datetime must be at least to day.
                                              SΣC1..1dateTime, PeriodOften just a dateTime for Vital Signs
                                              vs-1: if Observation.effective[x] is dateTime and has a value then that value shall be precise to the day
                                              • 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
                                                Σ0..*Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson)Who is responsible for the observation
                                                  ... value[x] SΣC0..1Quantity S, CodeableConcept S, string S, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodResult Value
                                                  us-core-3: SHALL use UCUM for coded quantity units.
                                                  us-core-4: SHOULD use Snomed CT for coded Results
                                                  SΣC0..1QuantityVital Signs value are recorded using the Quantity data type. For supporting observations such as Cuff size could use other datatypes such as CodeableConcept.
                                                  Slice: Unordered, Closed by type:$this
                                                    ... dataAbsentReason SC0..1CodeableConceptWhy the result is missing
                                                    Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing.

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

                                                      ... interpretation S0..*CodeableConceptResult interpretation
                                                      Binding: ?? (extensible): Observation Interpretation Codes


                                                      0..*CodeableConceptHigh, low, normal, etc.
                                                      Binding: ?? (extensible)
                                                      • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                      ... note 0..*AnnotationComments about the observation
                                                      0..*AnnotationComments about the observation
                                                        ... bodySite 0..1CodeableConceptObserved body part
                                                        Binding: ?? (example): Codes describing anatomical locations. May include laterality.

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

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

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

                                                            ... specimen S0..1Reference(US Core Specimen Profile)Specimen used for this observation0..1Reference(Specimen)Specimen used for this observation
                                                            • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                            ... device 0..1Reference(Device | DeviceMetric)(Measurement) Device0..1Reference(Device | DeviceMetric)(Measurement) Device
                                                              ... referenceRange SC0..*BackboneElementResult reference range
                                                              obs-3: Must have at least a low or a high or text
                                                              us-core-22: SHALL use UCUM for coded quantity units.
                                                              C0..*BackboneElementProvides guide for interpretation
                                                              obs-3: Must have at least a low or a high or text
                                                              • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                              .... 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(QuestionnaireResponse | MolecularSequence | Vital Signs Profile)Used when reporting vital signs panel components
                                                                                • Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Observation], CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence], CanonicalType[http://hl7.org/fhir/StructureDefinition/vitalsigns]])
                                                                                ... derivedFrom Σ0..*Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | Observation | MolecularSequence)Related measurements the observation is made from
                                                                                Σ0..*Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | MolecularSequence | Vital Signs Profile)Related measurements the observation is made from
                                                                                  ... component Σ0..*BackboneElementComponent results
                                                                                  SΣC0..*BackboneElementUsed when reporting systolic and diastolic blood pressure.
                                                                                  vs-3: If there is no a value a data absent reason must be present
                                                                                  • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                                  .... 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.

                                                                                        SΣ1..1CodeableConceptType of component observation (code / type)
                                                                                        Binding: ?? (extensible): This identifies the vital sign result type.

                                                                                        • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                                        .... value[x] Σ0..1Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodActual component resultSΣC0..1Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodVital Sign Value recorded with UCUM
                                                                                        Binding: ?? (extensible): Common UCUM units for recording Vital Signs.

                                                                                        • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                                        .... dataAbsentReason C0..1CodeableConceptWhy the component result is missing
                                                                                        Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing.

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

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


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


                                                                                          .... 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