Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-pulse-oximetry vs http://hl7.org/fhir/us/mcode/StructureDefinition/mcode-cancer-stage

Left:US Core Pulse Oximetry Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-pulse-oximetry)
Right:Cancer Stage Profile (http://hl7.org/fhir/us/mcode/StructureDefinition/mcode-cancer-stage)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-pulse-oximetry' vs 'http://hl7.org/fhir/us/mcode/StructureDefinition/mcode-cancer-stage'
ErrorStructureDefinition.versionValues for version differ: '6.1.0' vs '3.0.0'
InformationStructureDefinition.nameValues for name differ: 'USCorePulseOximetryProfile' vs 'CancerStage'
InformationStructureDefinition.titleValues for title differ: 'US Core Pulse Oximetry Profile' vs 'Cancer Stage Profile'
InformationStructureDefinition.statusValues for status differ: 'active' vs 'draft'
InformationStructureDefinition.dateValues for date differ: '2022-04-20' vs '2023-10-25T20:34:07+00:00'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 International - Cross-Group Projects' vs 'HL7 International / Clinical Interoperability Council'
WarningStructureDefinition.abstractValues for abstract differ: 'false' vs 'true'
ErrorStructureDefinition.baseDefinitionValues for baseDefinition differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-vital-signs' vs 'http://hl7.org/fhir/StructureDefinition/Observation'
InformationStructureDefinition.shortValues for short differ: 'US Core Pulse Oximetry Profile' vs 'Measurements and simple assertions'
InformationStructureDefinition.definitionValues for definition differ: '\-' vs 'Measurements and simple assertions made about a patient, device or other subject.'
InformationStructureDefinition.commentValues for comment differ: '\-' vs 'Used for simple observations such as device measurements, laboratory atomic results, vital signs, height, weight, smoking status, comments, etc. Other resources are used to provide context for observations such as laboratory reports, etc.'
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.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.'
InformationStructureDefinition.shortValues for short differ: '(USCDI) registered | preliminary | final | amended +' vs 'registered | preliminary | final | amended +'
InformationStructureDefinition.shortValues for short differ: '(USCDI) Classification of type of observation' vs 'Classification of type of observation'
WarningObservation.categoryElements differ in definition for mustSupport: 'true' vs 'false'
InformationObservation.categoryElement minimum cardinalities differ: '1' vs '0'
InformationStructureDefinition.shortValues for short differ: '(USCDI) Oxygen Saturation by Pulse Oximetry' vs 'The type of stage information reported.'
InformationStructureDefinition.definitionValues for definition differ: 'Coded Responses from C-CDA Vital Sign Results.' vs 'The kind of stage reported, e.g., a pathologic TNM stage, a Lugano lymphoma stage, or a Rai stage for leukemia. This element identifies the type of value that is reported in Observation.value and is necessary for the correct interpretation of that value. The distinction between Observation.code and Observation.method is important. Observation.code identifies the kind of stage being reported while Observation.method represents the staging system used to determine the code. Observation.code may imply the staging system. For example, the SNOMED CT 103420007 says the reported value is a modified Dukes stage, implying the Modified Dukes staging system (SNOMED CT 385359000) was used to determine the stage. When the staging system is implied by Observation.code, Observation.method is not required. However, when Observation.code does not imply a staging system (for example, if the code is SNOMED CT 385388004 Lymphoma stage), then the staging system must be specified in Observation.method. The value (Observation.valueCodeableConcept) may also imply certain things about the kind of stage being reported. For example, the value cN0 implies the value is a clinical stage. However, even if the value is partly or wholly self-identifying, it is not a reliable indicator of the type of stage being reported or the method of staging. Therefore, Observation.code must in all cases be reported.'
InformationStructureDefinition.commentValues for comment differ: 'The code (59408-5 Oxygen saturation in Arterial blood by Pulse oximetry) is included as an additional observation code to FHIR Core vital Oxygen Saturation code (2708-6 Oxygen saturation in Arterial blood).' vs '*All* code-value and, if present, component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation.'
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.'
InformationStructureDefinition.shortValues for short differ: '(USCDI) Who and/or what the observation is about' vs 'Who and/or what the observation is about'
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 patient associated with staging assessment.'
InformationObservation.subjectElement minimum cardinalities differ: '1' vs '0'
InformationStructureDefinition.shortValues for short differ: 'What the observation is about, when it is not about the subject of record' vs 'The cancer condition associated with staging assessment.'
InformationStructureDefinition.definitionValues for definition differ: 'The actual focus of an observation when it is not the patient of record representing something or someone associated with the patient such as a spouse, parent, fetus, or donor. For example, fetus observations in a mother's record. The focus of an observation could also be an existing condition, an intervention, the subject's diet, another observation of the subject, or a body structure such as tumor or implanted device. An example use case would be using the Observation resource to capture whether the mother is trained to change her child's tracheostomy tube. In this example, the child is the patient of record and the mother is the focus.' vs 'Staging is associated with a particular primary cancer condition. Observation.focus is used to point back to that condition.'
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 '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).'
WarningObservation.focusElements differ in definition for mustSupport: 'false' vs 'true'
InformationStructureDefinition.shortValues for short differ: '(USCDI) 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.'
InformationObservation.effective[x]Element minimum cardinalities differ: '1' vs '0'
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: '(USCDI) Vital Signs Value' vs 'The value of the stage'
InformationStructureDefinition.definitionValues for definition differ: 'Vital Signs value are typically recorded using the Quantity data type.' vs 'The stage, stage group, category, or classification resulting from the staging evaluation.'
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.'
InformationStructureDefinition.shortValues for short differ: '(USCDI) Why the result is missing' vs 'Why the result is missing'
WarningObservation.dataAbsentReasonElements 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/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).'
InformationStructureDefinition.shortValues for short differ: 'How it was done' vs 'The staging system used.'
InformationStructureDefinition.definitionValues for definition differ: 'Indicates the mechanism used to perform the observation.' vs 'The staging system or protocol used to determine the stage, stage group, or category of the cancer based on its extent. When the staging system is implied by Observation.code, Observation.method is not required. However, when Observation.code does not imply a staging system (for example, if the code is SNOMED CT 385388004 Lymphoma stage), then the staging system must be specified in Observation.method. '
WarningObservation.methodElements differ in definition for mustSupport: 'false' vs 'true'
InformationStructureDefinition.shortValues for short differ: '(Measurement) Device' vs 'Not used in this profile'
InformationStructureDefinition.definitionValues for definition differ: 'The device used to generate the observation data.' vs 'Not used in this profile'
InformationStructureDefinition.shortValues for short differ: 'Provides guide for interpretation' vs 'Not used in this profile'
InformationStructureDefinition.definitionValues for definition differ: 'Guidance on how to interpret the value by comparison to a normal or recommended range. Multiple reference ranges are interpreted as an 'OR'. In other words, to represent two distinct target populations, two `referenceRange` elements would be used.' vs 'Not used in this profile'
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 'Prognostic factors contributing to stage determination.'
InformationStructureDefinition.definitionValues for definition differ: 'Used when reporting vital signs panel components.' vs 'References to the prognostic factors affecting the stage, for example, the T, N, and M categories.'
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.'
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: '(USCDI) Used when reporting flow rates or oxygen concentration.' vs 'Component results'
InformationStructureDefinition.definitionValues for definition differ: 'Used when reporting flow rates or oxygen concentration.' 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: '(USCDI) Type of component observation (code / type)' vs 'Type of component observation (code / type)'
WarningObservation.component.codeElements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.shortValues for short differ: '(USCDI) 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 '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.'
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'
InformationStructureDefinition.shortValues for short differ: '(USCDI) Why the component result is missing' vs 'Why the component result is missing'
WarningObservation.component.dataAbsentReasonElements differ in definition for mustSupport: 'true' vs 'false'

Metadata

NameValueComments
.abstractfalsetrue
  • Values Differ
.baseDefinitionhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-vital-signshttp://hl7.org/fhir/StructureDefinition/Observation
  • Values Differ
.copyrightUsed by permission of HL7 International, all rights reserved Creative Commons License
  • Removed the item 'Used by permission of HL7 International, all rights reserved Creative Commons License'
.date2022-04-202023-10-25T20:34:07+00:00
  • Values Differ
.descriptionTo promote interoperability and adoption through common implementation, this profile sets minimum expectations for the Observation resource to record, search, and fetch pulse oximetry and inspired oxygen observations with a standard LOINC codes and UCUM units of measure. It is based on the US Core Vital Signs Profile and identifies which *additional* core elements, extensions, vocabularies, and value sets **SHALL** be present and constrains the way the elements are used when using the profile. It provides the floor for standards development for specific use cases.Parent profile for observations regarding cancer stage, grade, classification, or risk group. The stage is an assessment of the extent of the cancer in the body, according to a given cancer staging classification system. Profiles for different staging systems (e.g., TNM stage group, Rai stage, FIGO stage, etc.) must derive from this profile. Despite its name, the CancerStage profile can also be used as a parent for cancer grade, classification, and risk grouping. This is because the structure of the profiles are the same or very similar. The key elements are the code, method, value, and optionally, prognostic factors referenced in the hasMember element.
  • Values Differ
.experimentalfalse
  • Removed the item 'false'
.fhirVersion4.0.1
    .jurisdiction
      ..jurisdiction[0]urn:iso:std:iso:3166#US
        .kindresource
          .nameUSCorePulseOximetryProfileCancerStage
          • Values Differ
          .publisherHL7 International - Cross-Group ProjectsHL7 International / Clinical Interoperability Council
          • Values Differ
          .purpose
            .statusactivedraft
            • Values Differ
            .titleUS Core Pulse Oximetry ProfileCancer Stage Profile
            • Values Differ
            .typeObservation
              .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-pulse-oximetryhttp://hl7.org/fhir/us/mcode/StructureDefinition/mcode-cancer-stage
              • Values Differ
              .version6.1.03.0.0
              • Values Differ

              Structure

              NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.L TypeL Description & ConstraintsCommentsdoco
              .. Observation C0..*USCoreVitalSignsProfileUS Core Pulse Oximetry Profile
              C0..*ObservationThis is an abstract profile. Child profiles: CLLBinetStage, CLLRaiStage, GynecologicTumorFIGOStage, LymphomaStage, MelanomaBreslowDepthStage, MelanomaClarkLevel, MyelomaISSStage, MyelomaRISSStage, ProstateGleasonGradeGroup, TNMStageGroup
              Measurements and simple assertions
                ... 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..*ExtensionAdditional content defined by implementations
                              ... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
                              ?!0..*ExtensionExtensions that cannot be ignored
                                ... identifier Σ0..*IdentifierBusiness Identifier for observation
                                Σ0..*IdentifierBusiness Identifier for observation
                                  ... basedOn Σ0..*Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest)Fulfills plan, proposal or order
                                  Σ0..*Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest)Fulfills plan, proposal or order
                                    ... partOf Σ0..*Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy)Part of referenced event
                                    Σ0..*Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy)Part of referenced event
                                      ... status ?!SΣ1..1code(USCDI) registered | preliminary | final | amended +
                                      Binding: ?? (required)
                                      ?!SΣ1..1coderegistered | preliminary | final | amended +
                                      Binding: ?? (required): Codes providing the status of an observation.

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


                                        0..*CodeableConceptClassification 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'
                                        ... code SΣ1..1CodeableConcept(USCDI) Oxygen Saturation by Pulse Oximetry
                                        Binding: ?? (extensible): The vital sign codes from the base FHIR and US Core Vital Signs.

                                        SΣ1..1CodeableConceptThe type of stage information reported.
                                        Binding: ?? (preferred)
                                          .... 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
                                          .... Slices for coding SΣ2..*Coding(USCDI) Code defined by a terminology system
                                          Slice: Unordered, Open by pattern:$this
                                          • Removed this element
                                          .... text Σ0..1stringPlain text representation of the concept
                                          • Removed this element
                                          ... subject SΣ1..1Reference(US Core Patient Profile)(USCDI) Who and/or what the observation is aboutSΣ0..1Reference(Cancer Patient Profile)Who and/or what the observation is about
                                          • Element minimum cardinalities differ: '1' vs '0'
                                          ... focus ΣTU0..*Reference(Resource)What the observation is about, when it is not about the subject of record
                                          SΣ0..*Reference(Primary Cancer Condition Profile)The cancer condition associated with staging assessment.
                                          • Elements differ in definition for mustSupport: 'false' vs 'true'
                                          ... 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, Period(USCDI) Often just a dateTime for Vital SignsSΣ0..1dateTime, Period, Timing, instantClinically relevant time/time-period for observation
                                            • Element minimum cardinalities differ: '1' vs '0'
                                            ... issued Σ0..1instantDate/Time this version was made availableΣ0..1instantDate/Time this version was made available
                                              ... performer Σ0..*Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson)Who is responsible for the observation
                                              Σ0..*Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson)Who is responsible for the observation
                                                ... Slices for value[x] SΣC0..1Quantity S, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period(USCDI) Vital Signs Value
                                                Slice: Unordered, Open by type:$this
                                                Binding: ?? (extensible): Common UCUM units for recording Vital Signs.

                                                SΣC0..1CodeableConceptThe value of the stage
                                                Binding: ?? (example)
                                                  ... dataAbsentReason SC0..1CodeableConcept(USCDI) Why the result is missing
                                                  Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing.

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

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


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


                                                    ... note 0..*AnnotationComments about the observation
                                                    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.

                                                        S0..1CodeableConceptThe staging system used.
                                                        Binding: ?? (extensible)
                                                        • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                        ... specimen 0..1Reference(Specimen)Specimen used for this observation0..1Reference(Specimen)Specimen used for this observation
                                                          ... device 0..1Reference(Device | DeviceMetric)(Measurement) Device0..1Reference(Device | DeviceMetric)Not used in this profile
                                                            ... referenceRange C0..*BackboneElementProvides guide for interpretation
                                                            C0..*BackboneElementNot used in this profile
                                                              .... 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(QuestionnaireResponse | MolecularSequence | Vital Signs Profile)Used when reporting vital signs panel components
                                                                                Σ0..*Reference(Observation | QuestionnaireResponse | MolecularSequence)Prognostic factors contributing to stage determination.
                                                                                • 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 | ImagingStudy | Media | QuestionnaireResponse | Observation | MolecularSequence)Related measurements the observation is made from
                                                                                  ... Slices for component SΣC0..*BackboneElement(USCDI) Used when reporting flow rates or oxygen concentration.
                                                                                  Slice: Unordered, Open by pattern:code
                                                                                  Σ0..*BackboneElementComponent results
                                                                                  • 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..1CodeableConcept(USCDI) Type of component observation (code / type)
                                                                                        Binding: ?? (extensible): The vital sign codes from the base FHIR and US Core Vital Signs.

                                                                                        Σ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, Period(USCDI) Vital Sign Component Value
                                                                                        Binding: ?? (extensible): Common UCUM units for recording Vital Signs.

                                                                                        Σ0..1Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodActual component result
                                                                                        • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                                        .... dataAbsentReason SC0..1CodeableConcept(USCDI) Why 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..*See referenceRange (Observation)Provides guide for interpretation of component result

                                                                                            doco Documentation for this format