Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-vital-signs vs http://hl7.org/fhir/us/bfdr/StructureDefinition/Observation-present-job

Left:US Core Vital Signs Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-vital-signs)
Right:Observation - Present Job (http://hl7.org/fhir/us/bfdr/StructureDefinition/Observation-present-job)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-vital-signs' vs 'http://hl7.org/fhir/us/bfdr/StructureDefinition/Observation-present-job'
ErrorStructureDefinition.versionValues for version differ: '7.0.0' vs '2.0.0'
InformationStructureDefinition.nameValues for name differ: 'USCoreVitalSignsProfile' vs 'ObservationPresentJob'
InformationStructureDefinition.titleValues for title differ: 'US Core Vital Signs Profile' vs 'Observation - Present Job'
InformationStructureDefinition.dateValues for date differ: '2023-10-17' vs '2024-10-15T13:57:58+00:00'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 International / Cross-Group Projects' vs 'HL7 International / Public Health'
ErrorStructureDefinition.baseDefinitionValues for baseDefinition differ: 'http://hl7.org/fhir/StructureDefinition/vitalsigns' vs 'http://hl7.org/fhir/us/odh/StructureDefinition/odh-PastOrPresentJob'
InformationStructureDefinition.shortValues for short differ: 'US Core Vital Signs Profile' vs 'Past Or Present Job'
InformationStructureDefinition.definitionValues for definition differ: 'The FHIR Vitals Signs profile sets minimum expectations for the Observation Resource to record, search and fetch the vital signs associated with a patient.' vs 'Related data elements for a current or previous job, as reported by the person, i.e., a work situation or position held for a specified time period. A person can have more than one job at the same time and multiple jobs over time, so the data related to each job must remain in the record in perpetuity. Each job should be recorded in a separate instance of PastOrPresentJob. A person’s job can be a social determinant of their health and information about a person’s job can support patient care, population health, and public health. In patient care, knowledge of a person’s past or present job(s) can impact recognition, diagnosis, management, and treatment of injuries and illnesses. These data also can be used for clinical decision support and to prompt discussion of preventive care measures. For example, a record of jobs that require prolonged time in the sun might prompt a health care provider to inquire if the person wears protective clothing or sunscreen while working. At a minimum, it is important to have a record of a person’s current job(s); i.e., the job(s) in which a person is engaged at the time that he or she presents to a health care provider, regardless of duration, and to retain that information over time. In the event a person recently stopped working (e.g. retired without another job, became unemployed or disabled and unable to work), the most recent job(s) is used instead of the current job(s).'
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/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/R4/extensibility.html#modifierExtension).'
InformationStructureDefinition.shortValues for short differ: 'Fulfills plan, proposal or order' vs 'The plan, proposal or order that is fulfilled in whole or in part by this observation'
InformationStructureDefinition.definitionValues for definition differ: 'A plan, proposal or order that is fulfilled in whole or in part by this event. For example, a MedicationRequest may require a patient to have laboratory test performed before it is dispensed.' vs 'The plan, proposal or order that is fulfilled in whole or in part by this observation.'
ErrorObservation.basedOnType Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/CarePlan], CanonicalType[http://hl7.org/fhir/StructureDefinition/DeviceRequest], CanonicalType[http://hl7.org/fhir/StructureDefinition/ImmunizationRecommendation], CanonicalType[http://hl7.org/fhir/StructureDefinition/MedicationRequest], CanonicalType[http://hl7.org/fhir/StructureDefinition/NutritionOrder], CanonicalType[http://hl7.org/fhir/StructureDefinition/ServiceRequest]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/ServiceRequest]])
InformationStructureDefinition.shortValues for short differ: 'Part of referenced event' vs 'The larger procedure that this particular observation is a component or step'
InformationStructureDefinition.definitionValues for definition differ: 'A larger event of which this particular Observation is a component or step. For example, an observation as part of a procedure.' vs 'The larger procedure that this particular observation is a component or step.'
InformationStructureDefinition.commentValues for comment differ: '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.' vs '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.'
ErrorObservation.partOfType Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/MedicationAdministration], CanonicalType[http://hl7.org/fhir/StructureDefinition/MedicationDispense], CanonicalType[http://hl7.org/fhir/StructureDefinition/MedicationStatement], CanonicalType[http://hl7.org/fhir/StructureDefinition/Procedure], CanonicalType[http://hl7.org/fhir/StructureDefinition/Immunization], CanonicalType[http://hl7.org/fhir/StructureDefinition/ImagingStudy]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Procedure]])
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'
InformationObservation.categoryElement maximum cardinalities differ: '2147483647' vs '1'
InformationStructureDefinition.shortValues for short differ: 'Coded vital sign result type' vs 'Type of observation (code / type)'
InformationStructureDefinition.definitionValues for definition differ: 'Coded Responses from C-CDA Vital Sign Results.' vs 'Describes what was observed. Sometimes this is called the observation 'name'.'
InformationStructureDefinition.requirementsValues for requirements differ: '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 definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.shortValues for short differ: 'Who and/or what the observation is about' vs 'The subject of an observation'
InformationStructureDefinition.definitionValues for definition differ: '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 'The subject of an observation.'
WarningObservation.subjectElements differ in definition for mustSupport: 'true' vs 'false'
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/extension-observation-focuscode.html).' vs 'This is used only when conveying job information of person(s) who share a home with a patient who is a child. It represents the relationship of the person holding this Job Occupation to the patient.'
InformationStructureDefinition.shortValues for short differ: 'Often just a dateTime for Vital Signs' vs 'Clinically relevant time/time-period for observation'
InformationStructureDefinition.definitionValues for definition differ: 'Often just a dateTime for Vital Signs.' vs 'The time or time-period the observed value is asserted as being true. For biological subjects - e.g. human patients - this is usually called the 'physiologically relevant time'. This is usually either the time of the procedure or of specimen collection, but very often the source of the date/time is not known, only the date/time itself.'
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/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/R4/datatypes.html#timing) datatype which allow the measurement to be tied to regular life events.'
WarningObservation.effective[x]Elements differ in definition for mustSupport: 'true' vs 'false'
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/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/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.'
InformationStructureDefinition.shortValues for short differ: 'Vital Signs Value' vs 'Actual result'
InformationStructureDefinition.definitionValues for definition differ: '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.'
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/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/R4/observation.html#notes) below.'
InformationStructureDefinition.requirementsValues for requirements differ: '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'
InformationStructureDefinition.shortValues for short differ: 'Why the result is missing' vs 'The reason that there is no value available for the Occupation.'
InformationStructureDefinition.definitionValues for definition differ: 'Provides a reason why the expected value in the element Observation.value[x] is missing.' vs 'The reason that there is no value available for the Occupation.'
WarningObservation.dataAbsentReasonElements differ in definition for mustSupport: 'true' vs 'false'
InformationObservation.interpretationElement maximum cardinalities differ: '2147483647' vs '0'
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/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/R4/extension-bodysite.html).'
InformationObservation.bodySiteElement maximum cardinalities differ: '1' vs '0'
InformationObservation.methodElement maximum cardinalities differ: '1' vs '0'
InformationObservation.specimenElement maximum cardinalities differ: '1' vs '0'
InformationObservation.deviceElement maximum cardinalities differ: '1' vs '0'
InformationObservation.referenceRangeElement maximum cardinalities differ: '2147483647' vs '0'
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/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/R4/extensibility.html#modifierExtension).'
InformationStructureDefinition.shortValues for short differ: 'Used when reporting vital signs panel components' vs 'Related resource that belongs to the Observation group'
InformationStructureDefinition.definitionValues for definition differ: '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.'
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/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.' 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/R4/observation.html#obsgrouping) below. Note that a system may calculate results from [QuestionnaireResponse](http://hl7.org/fhir/R4/questionnaireresponse.html) into a final score and represent the score as an Observation.'
InformationObservation.hasMemberElement maximum cardinalities differ: '2147483647' vs '0'
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/StructureDefinition/Observation], CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]])
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/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/R4/observation.html#obsgrouping) below.'
InformationStructureDefinition.shortValues for short differ: 'Component observations' vs 'Component results'
InformationStructureDefinition.definitionValues for definition differ: '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.'
InformationStructureDefinition.commentValues for comment differ: 'For a discussion on the ways Observations can be assembled in groups together see [Notes](http://hl7.org/fhir/observation.html#notes) below.' vs 'For a discussion on the ways Observations can be assembled in groups together see [Notes](http://hl7.org/fhir/R4/observation.html#notes) below.'
WarningObservation.componentElements 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/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/R4/extensibility.html#modifierExtension).'
InformationStructureDefinition.shortValues for short differ: 'Coded vital sign result type' vs 'Type of component observation (code / type)'
WarningObservation.component.codeElements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.shortValues for short differ: 'Vital Sign Component Value' vs 'Actual component result'
InformationStructureDefinition.definitionValues for definition differ: '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.'
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/observation.html#notes) below.' vs 'If there is no coded value available for the Industry, the narrative description SHALL be expressed using originalText. The CDC_Census system has been used by public health programs to classify industry and occupation when only a text description has been collected. The PHIN VADS Hot Topics for ODH includes crosswalk tables from Industry_NAICS_Detail_(ODH) values to Industry_CDC_Census_2010 values.'
InformationStructureDefinition.requirementsValues for requirements differ: '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'
InformationObservation.component.referenceRangeElement maximum cardinalities differ: '2147483647' vs '0'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/vitalsignshttp://hl7.org/fhir/us/odh/StructureDefinition/odh-PastOrPresentJob
    • Values Differ
    .copyrightUsed by permission of HL7 International, all rights reserved Creative Commons License
    • Removed the item 'Used by permission of HL7 International, all rights reserved Creative Commons License'
    .date2023-10-172024-10-15T13:57:58+00:00
    • Values Differ
    .descriptionThis profile is based on the base [FHIR Vital Signs Profile](http://hl7.org/fhir/R4/observation-vitalsigns.html) and defines *additional* constraints on the Observation resource to represent vital signs observations. It specifies which core elements, extensions, vocabularies, and value sets **SHALL** be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. This US Core profiles that are derived from this profile are listed below.Used to send text-string present job information from Jurisdictions to NCHS, and coded versions from NCHS to Jurisdictions.
    • Values Differ
    .experimentalfalse
    • Removed the item 'false'
    .fhirVersion4.0.1
      .jurisdiction
        ..jurisdiction[0]urn:iso:std:iso:3166#US
          .kindresource
            .nameUSCoreVitalSignsProfileObservationPresentJob
            • Values Differ
            .publisherHL7 International / Cross-Group ProjectsHL7 International / Public Health
            • Values Differ
            .purpose
              .statusactive
                .titleUS Core Vital Signs ProfileObservation - Present Job
                • Values Differ
                .typeObservation
                  .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-vital-signshttp://hl7.org/fhir/us/bfdr/StructureDefinition/Observation-present-job
                  • 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..*observation-vitalsignsUS Core Vital Signs 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.
                  C0..*PastOrPresentJobPast Or Present Job
                  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
                    ... id Σ0..1idLogical id of this artifactΣ0..1idLogical id of this artifact
                      ... meta Σ0..1MetaMetadata about the resourceΣ0..1MetaMetadata about the resource
                        ... implicitRules ?!Σ0..1uriA set of rules under which this content was created?!Σ0..1uriA set of rules under which this content was created
                          ... language 0..1codeLanguage of the resource content
                          Binding: ?? (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(ServiceRequest)The plan, proposal or order that is fulfilled in whole or in part by this observation
                                      • Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/CarePlan], CanonicalType[http://hl7.org/fhir/StructureDefinition/DeviceRequest], CanonicalType[http://hl7.org/fhir/StructureDefinition/ImmunizationRecommendation], CanonicalType[http://hl7.org/fhir/StructureDefinition/MedicationRequest], CanonicalType[http://hl7.org/fhir/StructureDefinition/NutritionOrder], CanonicalType[http://hl7.org/fhir/StructureDefinition/ServiceRequest]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/ServiceRequest]])
                                      ... partOf Σ0..*Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy)Part of referenced event
                                      Σ0..*Reference(Procedure)The larger procedure that this particular observation is a component or step
                                      • Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/MedicationAdministration], CanonicalType[http://hl7.org/fhir/StructureDefinition/MedicationDispense], CanonicalType[http://hl7.org/fhir/StructureDefinition/MedicationStatement], CanonicalType[http://hl7.org/fhir/StructureDefinition/Procedure], CanonicalType[http://hl7.org/fhir/StructureDefinition/Immunization], CanonicalType[http://hl7.org/fhir/StructureDefinition/ImagingStudy]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Procedure]])
                                      ... status ?!SΣ1..1coderegistered | preliminary | final | amended +
                                      Binding: ?? (required)
                                      ?!Σ1..1coderegistered | preliminary | final | amended +
                                      Binding: ?? (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: ?? (preferred): Codes for high level observation categories.


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


                                      • Elements differ in definition for mustSupport: 'true' vs 'false'
                                      • Element minimum cardinalities differ: '1' vs '0'
                                      • Element maximum cardinalities differ: '2147483647' vs '1'
                                      .... id 0..1stringUnique id for inter-element referencing
                                      • Added this element
                                      .... Slices for extension 0..*ExtensionAdditional content defined by implementations
                                      Slice: Unordered, Open by value:url
                                      • Added this element
                                      .... Slices for coding Σ1..*CodingCode defined by a terminology system
                                      Slice: Unordered, Open by value:code
                                      • Added this element
                                      .... text Σ0..1stringPlain text representation of the concept
                                      • Added this element
                                      ... code SΣ1..1CodeableConceptCoded vital sign result type
                                      Binding: ?? (extensible): Vital sign result types

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

                                      • Elements differ in definition for mustSupport: 'true' vs 'false'
                                      .... 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 Σ1..*CodingCode defined by a terminology system
                                      Slice: Unordered, Open by value:code
                                      • Added this element
                                      .... text Σ0..1stringPlain text representation of the concept
                                      • Added this element
                                      ... subject SΣ1..1Reference(US Core Patient Profile)Who and/or what the observation is aboutΣ1..1Reference(Patient - Vital Records)The subject of an observation
                                      • Elements differ in definition for mustSupport: 'true' vs 'false'
                                      ... focus Σ0..*Reference(Resource)What the observation is about, when it is not about the subject of record
                                      Σ0..*Reference(Related Person - Parent Vital Records)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ΣC1..1dateTime S, 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
                                          Σ1..1PeriodClinically relevant time/time-period for observation
                                          Slice: Unordered, Closed by type:$this
                                          • Elements differ in definition for mustSupport: 'true' vs 'false'
                                          ... issued Σ0..1instantDate/Time this version was made availableΣ0..1instantDate/Time this version was made available
                                            ... performer Σ0..*Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson)Who is responsible for the observation
                                            Σ0..*Reference(Practitioner | Organization | US Core Patient Profile | RelatedPerson)Who is responsible for the observation
                                              ... value[x] SΣC0..1Quantity S, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodVital Signs Value
                                              Binding: ?? (extensible): Common UCUM units for recording Vital Signs.

                                              ΣC0..1CodeableConceptActual result
                                              Slice: Unordered, Closed by type:$this
                                              • Elements differ in definition for mustSupport: 'true' vs 'false'
                                              ... dataAbsentReason SC0..1CodeableConceptWhy the result is missing
                                              Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing.

                                              C0..1CodeableConceptThe reason that there is no value available for the Occupation.
                                              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..0
                                              • Element maximum cardinalities differ: '2147483647' vs '0'
                                              ... note 0..*AnnotationComments about the observation
                                              0..*AnnotationComments about the observation
                                                ... bodySite 0..1CodeableConceptObserved body part
                                                Binding: ?? (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..0
                                                • Element maximum cardinalities differ: '1' vs '0'
                                                ... specimen 0..1Reference(Specimen)Specimen used for this observation0..0
                                                • Element maximum cardinalities differ: '1' vs '0'
                                                ... device 0..1Reference(Device | DeviceMetric)(Measurement) Device0..0
                                                • Element maximum cardinalities differ: '1' vs '0'
                                                ... referenceRange C0..*BackboneElementProvides guide for interpretation
                                                obs-3: Must have at least a low or a high or text
                                                C0..0
                                                • Element maximum cardinalities differ: '2147483647' vs '0'
                                                .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                  .... extension 0..*ExtensionAdditional content defined by implementations
                                                  0..*ExtensionAdditional content defined by implementations
                                                    .... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                    ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                      .... low C0..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: ?? (extensible): 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: ?? (extensible): 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
                                                                  Σ0..0
                                                                  • Element maximum cardinalities differ: '2147483647' vs '0'
                                                                  • 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/StructureDefinition/Observation], CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]])
                                                                  ... derivedFrom Σ0..*Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | MolecularSequence | Vital Signs Profile)Related measurements the observation is made from
                                                                  Σ0..*Reference(DocumentReference | Media | QuestionnaireResponse | Observation)Related measurements the observation is made from
                                                                    ... component SΣC0..*BackboneElementComponent observations
                                                                    vs-3: If there is no a value a data absent reason must be present
                                                                    Σ0..*BackboneElementComponent results
                                                                    Slice: Unordered, Open by value:code.coding.code
                                                                    • 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
                                                                          .... code SΣ1..1CodeableConceptCoded vital sign result type
                                                                          Binding: ?? (extensible): Vital sign result types

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

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

                                                                          Σ0..1Quantity, CodeableConcept, string, Range, Ratio, SampledData, time, dateTime, PeriodActual component result
                                                                          • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                          .... dataAbsentReason SC0..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.

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


                                                                            .... referenceRange 0..*See referenceRange (Observation)Provides guide for interpretation of component result
                                                                            0..0
                                                                            • Element maximum cardinalities differ: '2147483647' vs '0'

                                                                            doco Documentation for this format