Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-assessment vs http://hl7.org/fhir/us/mcode/StructureDefinition/mcode-cancer-stage-group

Left:US Core Observation Screening Assessment Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-assessment)
Right:Cancer Stage Group Profile (http://hl7.org/fhir/us/mcode/StructureDefinition/mcode-cancer-stage-group)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-assessment' vs 'http://hl7.org/fhir/us/mcode/StructureDefinition/mcode-cancer-stage-group'
ErrorStructureDefinition.versionValues for version differ: '6.0.0-ballot' vs '2.1.0'
InformationStructureDefinition.nameValues for name differ: 'USCoreObservationScreeningAssessmentProfile' vs 'CancerStageGroup'
InformationStructureDefinition.titleValues for title differ: 'US Core Observation Screening Assessment Profile' vs 'Cancer Stage Group Profile'
InformationStructureDefinition.dateValues for date differ: '2022-04-20' vs '2023-01-13T14:44:53+00:00'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 International - Cross-Group Projects' vs 'HL7 International Clinical Interoperability Council'
WarningObservationElements differ in short: 'Survey Observation' vs 'Measurements and simple assertions'
WarningObservationElements differ in definition: '\-' vs 'Measurements and simple assertions made about a patient, device or other subject.'
WarningObservationElements differ in comments: '\-' vs 'Used for simple observations such as device measurements, laboratory atomic results, vital signs, height, weight, smoking status, comments, etc. Other resources are used to provide context for observations such as laboratory reports, etc.'
WarningObservation.codeElements differ in short: 'Type of observation (code / type)' vs 'The type of stage information reported.'
WarningObservation.codeElements differ in definition: 'Describes what was observed. Sometimes this is called the observation 'name'.' vs 'The type of staging performed, e.g., clinically by oncologist, by a pathologist on a specimen, or other method. This information is required, although it may be redundant with the stage code recorded in Observation.valueCodeableConcept (for example, the 'c' in cN0 represents clinical staging).'
InformationObservation.codeExample/preferred bindings differ at Observation.code using binding from USCoreObservationScreeningAssessmentProfile
WarningObservation.subjectElements differ in definition: 'The patient, or group of patients, location, or device this observation is about and into whose record the observation is placed. If the actual focus of the observation is different from the subject (or a sample of, part, or region of the subject), the `focus` element or the `code` itself specifies the actual focus of the observation.' vs 'The patient associated with staging assessment.'
InformationObservation.subjectElement minimum cardinalities differ: '1' vs '0'
WarningObservation.focusElements differ in short: 'What the observation is about, when it is not about the subject of record' vs 'The cancer condition associated with staging assessment.'
WarningObservation.focusElements differ in definition: '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.'
WarningObservation.focusElements differ in definition for mustSupport: 'false' vs 'true'
WarningObservation.effective[x]Elements differ in definition: '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'.' 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.'
WarningObservation.effective[x]Elements differ in comments: 'At least a date should be present unless this observation is a historical report.' 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] datatype which allow the measurement to be tied to regular life events.'
WarningObservation.performerElements differ in definition for mustSupport: 'true' vs 'false'
WarningObservation.value[x]Elements differ in comments: 'An observation may have a value if it represents an individual survey, screening, or assessment question and answer pair. An observation should not have a value if it represents a multi-question or multi-select “check all that apply” responses. 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.' 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] below.'
WarningObservation.dataAbsentReasonElements differ in comments: ''Null' or exceptional values can be represented two ways in FHIR Observations. One way is to simply include them in the value set and represent the exceptions in the value. The alternate way is to use the value element for actual observations and use the explicit dataAbsentReason element to record exceptional values. For a given LOINC question, if the LOINC answer list includes concepts such as 'unknown' or 'not available', they should be used for Observation.value. Where these concepts are not part of the value set for Observation.value, the Observation.dataAbsentReason can be used if necessary and appropriate.' vs 'Null or exceptional values can be represented two ways in FHIR Observations. One way is to simply include them in the value set and represent the exceptions in the value. For example, measurement values for a serology test could be 'detected', 'not detected', 'inconclusive', or 'specimen unsatisfactory'. The alternate way is to use the value element for actual observations and use the explicit dataAbsentReason element to record exceptional values. For example, the dataAbsentReason code 'error' could be used when the measurement was not completed. Note that an observation may only be reported if there are values to report. For example differential cell counts values may be reported only when > 0. Because of these options, use-case agreements are required to interpret general observations for null or exceptional values.'
WarningObservation.dataAbsentReasonElements differ in definition for mustSupport: 'true' vs 'false'
WarningObservation.methodElements differ in definition for mustSupport: 'false' vs 'true'
WarningObservation.deviceElements differ in short: '(Measurement) Device' vs 'Not used in this profile'
WarningObservation.deviceElements differ in definition: 'The device used to generate the observation data.' vs 'Not used in this profile'
WarningObservation.referenceRangeElements differ in short: 'Provides guide for interpretation' vs 'Not used in this profile'
WarningObservation.referenceRangeElements differ in definition: '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'
WarningObservation.hasMemberElements differ in short: 'Reference to panel or multi-select responses' vs 'Prognostic factors contributing to stage determination.'
WarningObservation.hasMemberElements differ in definition: 'Aggregate set of Observations that represent question answer pairs for both multi-question surveys, screenings, and assessments and multi-select questions.' vs 'References to the prognostic factors affecting the stage, for example, the T, N, and M categories.'
WarningObservation.hasMemberElements differ in comments: 'This grouping element is used to represent surveys, screenings, and assessments that group several questions together or individual questions with “check all that apply” responses. For example in the simplest case a flat multi-question survey where the 'panel' observation is the survey instrument itself and instead of an `Observation.value` the `hasMember` element references other Observation that represent the individual questions answer pairs. When there is a heirarchical grouping of questions, the observation 'panels' can be nested. Because surveys, screenings, and assessments can be arbitrarily complex structurally, not all structures can be represented using this Observation grouping pattern.' 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] below. Note that a system may calculate results from [QuestionnaireResponse] into a final score and represent the score as an Observation.'
WarningObservation.hasMemberElements differ in definition for mustSupport: 'true' vs 'false'
WarningObservation.derivedFromElements differ in short: 'Related Observation(s) or other resource the observation is made from' vs 'Related measurements the observation is made from'
WarningObservation.derivedFromElements differ in definition: 'Observations or or other resource such as a QuestionnaireResponse from which this observation value is derived.' vs 'The target resource that represents a measurement from which this observation value is derived. For example, a calculated anion gap or a fetal measurement based on an ultrasound image.'
WarningObservation.derivedFromElements differ in definition for mustSupport: 'true' vs 'false'
ErrorObservation.derivedFromType Mismatch: Reference([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-assessment], CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-documentreference], CanonicalType[http://hl7.org/fhir/StructureDefinition/ImagingStudy], CanonicalType[http://hl7.org/fhir/StructureDefinition/Media], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/DocumentReference], CanonicalType[http://hl7.org/fhir/StructureDefinition/ImagingStudy], CanonicalType[http://hl7.org/fhir/StructureDefinition/Media], CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/Observation], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]])

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/Observation
      .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-01-13T14:44:53+00:00
      • Values Differ
      .descriptionThe US Core Observation Screening Assessment Profile meets the requirements of the US Core Data for Interoperability (USCDI) Assessments. To promote interoperability and adoption through common implementation, it sets the minimum expectations for the Observation Resource to record, search, and fetch observations representing the questions and responses to surveys and screening and assessment tools. For example, a social history status such as education or food insecurity or an assessment of the patient's cognitive, functional, or disability status. It can represent a single response, multiple responses, and multi-select "check all that apply" type questions. It identifies which core elements, extensions, vocabularies, and value sets **SHALL** be present in the resource when using this profile. It provides the floor for standards development for specific use cases.An assessment of the extent of the cancer in the body, according to a given cancer staging classification system. This profile can be used with any staging system, but it is specifically targeted for non-TNM staging systems, since specialized TNM staging profiles are provided.
      • Values Differ
      .experimental
        .fhirVersion4.0.1
          .jurisdiction
            ..jurisdiction[0]urn:iso:std:iso:3166#US
              .kindresource
                .nameUSCoreObservationScreeningAssessmentProfileCancerStageGroup
                • Values Differ
                .publisherHL7 International - Cross-Group ProjectsHL7 International Clinical Interoperability Council
                • Values Differ
                .purpose
                  .statusactive
                    .titleUS Core Observation Screening Assessment ProfileCancer Stage Group Profile
                    • Values Differ
                    .typeObservation
                      .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-assessmenthttp://hl7.org/fhir/us/mcode/StructureDefinition/mcode-cancer-stage-group
                      • Values Differ
                      .version6.0.0-ballot2.1.0
                      • Values Differ

                      Structure

                      NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.L TypeL Description & ConstraintsCommentsdoco
                      .. Observation C0..*ObservationSurvey Observation
                      us-core-2: If there is no component or hasMember element then either a value[x] or a data absent reason must be present
                      us-core-3: SHALL use UCUM for coded quantity units.
                      C0..*ObservationMeasurements and simple assertions
                      • Elements differ in short: 'Survey Observation' vs 'Measurements and simple assertions'
                      • Elements differ in definition: '\-' vs 'Measurements and simple assertions made about a patient, device or other subject.'
                      • Elements differ in comments: '\-' vs 'Used for simple observations such as device measurements, laboratory atomic results, vital signs, height, weight, smoking status, comments, etc. Other resources are used to provide context for observations such as laboratory reports, etc.'
                      ... id Σ0..1idLogical id of this artifactΣ0..1idLogical id of this artifact
                        ... meta Σ0..1MetaMetadata about the resourceΣ0..1MetaMetadata about the resource
                          ... implicitRules ?!Σ0..1uriA set of rules under which this content was created?!Σ0..1uriA set of rules under which this content was created
                            ... language 0..1codeLanguage of the resource content
                            Binding: todo (preferred): A human language.

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

                            Additional BindingsPurpose
                            todoMax 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..1coderegistered | preliminary | final | amended +
                                            Binding: todo (required): Codes providing the status of an observation.

                                            ?!SΣ1..1coderegistered | preliminary | final | amended +
                                            Binding: todo (required): Codes providing the status of an observation.

                                              ... Slices for category S1..*CodeableConceptClassification of type of observation
                                              Slice: Unordered, Open by pattern:$this
                                              Binding: todo (preferred): Codes for high level observation categories.


                                              S1..*CodeableConceptClassification of type of observation
                                              Slice: Unordered, Open by pattern:$this
                                              Binding: todo (preferred): Codes for high level observation categories.


                                                ... code SΣ1..1CodeableConceptType of observation (code / type)
                                                Binding: todo (preferred)
                                                SΣ1..1CodeableConceptThe type of stage information reported.
                                                Binding: todo (preferred)
                                                • Elements differ in short: 'Type of observation (code / type)' vs 'The type of stage information reported.'
                                                • Elements differ in definition: 'Describes what was observed. Sometimes this is called the observation "name".' vs 'The type of staging performed, e.g., clinically by oncologist, by a pathologist on a specimen, or other method. This information is required, although it may be redundant with the stage code recorded in Observation.valueCodeableConcept (for example, the 'c' in cN0 represents clinical staging).'
                                                • Example/preferred bindings differ at Observation.code using binding from USCoreObservationScreeningAssessmentProfile
                                                ... subject SΣ1..1Reference(http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient)Who and/or what the observation is aboutSΣ0..1Reference(http://hl7.org/fhir/us/mcode/StructureDefinition/mcode-cancer-patient)Who and/or what the observation is about
                                                • Elements differ in definition: 'The patient, or group of patients, location, or device this observation is about and into whose record the observation is placed. If the actual focus of the observation is different from the subject (or a sample of, part, or region of the subject), the `focus` element or the `code` itself specifies the actual focus of the observation.' vs 'The patient associated with staging assessment.'
                                                • 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(http://hl7.org/fhir/us/mcode/StructureDefinition/mcode-primary-cancer-condition)The cancer condition associated with staging assessment.
                                                • Elements differ in short: 'What the observation is about, when it is not about the subject of record' vs 'The cancer condition associated with staging assessment.'
                                                • Elements differ in definition: '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.'
                                                • 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ΣC0..1dateTime S, Period, Timing, instantClinically relevant time/time-period for observation
                                                  us-core-1: Datetime must be at least to day.
                                                  SΣ0..1dateTime, Period, Timing, instantClinically relevant time/time-period for observation
                                                  • Elements differ in definition: '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".' 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.'
                                                  • Elements differ in comments: 'At least a date should be present unless this observation is a historical report.' 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] datatype which allow the measurement to be tied to regular life events.'
                                                  ... issued Σ0..1instantDate/Time this version was made availableΣ0..1instantDate/Time this version was made available
                                                    ... performer SΣ0..*Reference(http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner S | http://hl7.org/fhir/us/core/StructureDefinition/us-core-organization | http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient | PractitionerRole | http://hl7.org/fhir/us/core/StructureDefinition/us-core-careteam | http://hl7.org/fhir/us/core/StructureDefinition/us-core-relatedperson)Who is responsible for the observation
                                                    Σ0..*Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson)Who is responsible for the observation
                                                    • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                    ... value[x] SΣC0..1Quantity S, CodeableConcept S, string S, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodActual resultSΣC0..1CodeableConceptActual result
                                                    Binding: todo (preferred)
                                                    • Elements differ in comments: 'An observation may have a value if it represents an individual survey, screening, or assessment question and answer pair. An observation should not have a value if it represents a multi-question or multi-select “check all that apply” responses. 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.' 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] below.'
                                                    ... dataAbsentReason SC0..1CodeableConceptWhy the result is missing
                                                    Binding: todo (extensible): Codes specifying why the result (Observation.value[x]) is missing.

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

                                                    • Elements differ in comments: '"Null" or exceptional values can be represented two ways in FHIR Observations. One way is to simply include them in the value set and represent the exceptions in the value. The alternate way is to use the value element for actual observations and use the explicit dataAbsentReason element to record exceptional values. For a given LOINC question, if the LOINC answer list includes concepts such as 'unknown' or 'not available', they should be used for Observation.value. Where these concepts are not part of the value set for Observation.value, the Observation.dataAbsentReason can be used if necessary and appropriate.' vs 'Null or exceptional values can be represented two ways in FHIR Observations. One way is to simply include them in the value set and represent the exceptions in the value. For example, measurement values for a serology test could be "detected", "not detected", "inconclusive", or "specimen unsatisfactory". The alternate way is to use the value element for actual observations and use the explicit dataAbsentReason element to record exceptional values. For example, the dataAbsentReason code "error" could be used when the measurement was not completed. Note that an observation may only be reported if there are values to report. For example differential cell counts values may be reported only when > 0. Because of these options, use-case agreements are required to interpret general observations for null or exceptional values.'
                                                    • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                    ... interpretation 0..*CodeableConceptHigh, low, normal, etc.
                                                    Binding: todo (extensible): Codes identifying interpretations of observations.


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


                                                      ... note 0..*AnnotationComments about the observation
                                                      0..*AnnotationComments about the observation
                                                        ... bodySite 0..1CodeableConceptObserved body part
                                                        Binding: todo (example): Codes describing anatomical locations. May include laterality.

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

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

                                                          S0..1CodeableConceptHow it was done
                                                          Binding: todo (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
                                                            • Elements differ in short: '(Measurement) Device' vs 'Not used in this profile'
                                                            • Elements differ in definition: 'The device used to generate the observation data.' vs 'Not used in this profile'
                                                            ... referenceRange C0..*BackboneElementProvides guide for interpretation
                                                            C0..*BackboneElementNot used in this profile
                                                            • Elements differ in short: 'Provides guide for interpretation' vs 'Not used in this profile'
                                                            • Elements differ in definition: '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'
                                                            .... 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..1QuantityLow Range, if relevantC0..1QuantityLow Range, if relevant
                                                                    .... high C0..1QuantityHigh Range, if relevantC0..1QuantityHigh Range, if relevant
                                                                      .... type 0..1CodeableConceptReference range qualifier
                                                                      Binding: todo (preferred): Code for the meaning of a reference range.

                                                                      0..1CodeableConceptReference range qualifier
                                                                      Binding: todo (preferred): Code for the meaning of a reference range.

                                                                        .... appliesTo 0..*CodeableConceptReference range population
                                                                        Binding: todo (example): Codes identifying the population the reference range applies to.


                                                                        0..*CodeableConceptReference range population
                                                                        Binding: todo (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 SΣ0..*Reference(http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-assessment S | QuestionnaireResponse | MolecularSequence)Reference to panel or multi-select responses
                                                                              Σ0..*Reference(Observation | QuestionnaireResponse | MolecularSequence)Prognostic factors contributing to stage determination.
                                                                              • Elements differ in short: 'Reference to panel or multi-select responses' vs 'Prognostic factors contributing to stage determination.'
                                                                              • Elements differ in definition: 'Aggregate set of Observations that represent question answer pairs for both multi-question surveys, screenings, and assessments and multi-select questions.' vs 'References to the prognostic factors affecting the stage, for example, the T, N, and M categories.'
                                                                              • Elements differ in comments: 'This grouping element is used to represent surveys, screenings, and assessments that group several questions together or individual questions with “check all that apply” responses. For example in the simplest case a flat multi-question survey where the "panel" observation is the survey instrument itself and instead of an `Observation.value` the `hasMember` element references other Observation that represent the individual questions answer pairs. When there is a heirarchical grouping of questions, the observation "panels" can be nested. Because surveys, screenings, and assessments can be arbitrarily complex structurally, not all structures can be represented using this Observation grouping pattern.' 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] below. Note that a system may calculate results from [QuestionnaireResponse] into a final score and represent the score as an Observation.'
                                                                              • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                              ... derivedFrom SΣ0..*Reference(http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-assessment S | QuestionnaireResponse | http://hl7.org/fhir/us/core/StructureDefinition/us-core-documentreference | ImagingStudy | Media | MolecularSequence)Related Observation(s) or other resource the observation is made from
                                                                              Σ0..*Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | Observation | MolecularSequence)Related measurements the observation is made from
                                                                              • Elements differ in short: 'Related Observation(s) or other resource the observation is made from' vs 'Related measurements the observation is made from'
                                                                              • Elements differ in definition: 'Observations or or other resource such as a QuestionnaireResponse from which this observation value is derived.' vs 'The target resource that represents a measurement from which this observation value is derived. For example, a calculated anion gap or a fetal measurement based on an ultrasound image.'
                                                                              • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                              • Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-assessment], CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-documentreference], CanonicalType[http://hl7.org/fhir/StructureDefinition/ImagingStudy], CanonicalType[http://hl7.org/fhir/StructureDefinition/Media], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/DocumentReference], CanonicalType[http://hl7.org/fhir/StructureDefinition/ImagingStudy], CanonicalType[http://hl7.org/fhir/StructureDefinition/Media], CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/Observation], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]])
                                                                              ... component Σ0..*BackboneElementComponent results
                                                                              Σ0..*BackboneElementComponent results
                                                                                .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                                  .... extension 0..*ExtensionAdditional content defined by implementations
                                                                                  0..*ExtensionAdditional content defined by implementations
                                                                                    .... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                                    ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                                      .... code Σ1..1CodeableConceptType of component observation (code / type)
                                                                                      Binding: todo (example): Codes identifying names of simple observations.

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

                                                                                        .... value[x] Σ0..1Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodActual component resultΣ0..1Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodActual component result
                                                                                          .... dataAbsentReason C0..1CodeableConceptWhy the component result is missing
                                                                                          Binding: todo (extensible): Codes specifying why the result (Observation.value[x]) is missing.

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

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


                                                                                            0..*CodeableConceptHigh, low, normal, etc.
                                                                                            Binding: todo (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