Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-assessment vs http://hl7.org/fhir/us/cancer-reporting/StructureDefinition/us-pathology-grouper-observation

Left:US Core Observation Screening Assessment Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-assessment)
Right:US Pathology Grouper Observation (http://hl7.org/fhir/us/cancer-reporting/StructureDefinition/us-pathology-grouper-observation)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-assessment' vs 'http://hl7.org/fhir/us/cancer-reporting/StructureDefinition/us-pathology-grouper-observation'
ErrorStructureDefinition.versionValues for version differ: '8.0.0-ballot' vs '1.0.1'
InformationStructureDefinition.nameValues for name differ: 'USCoreObservationScreeningAssessmentProfile' vs 'USPathologyGrouperObservation'
InformationStructureDefinition.titleValues for title differ: 'US Core Observation Screening Assessment Profile' vs 'US Pathology Grouper Observation'
InformationStructureDefinition.dateValues for date differ: '2024-11-16' vs '2024-12-16T21:09:11+00:00'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 International / Cross-Group Projects' vs 'HL7 International / Orders and Observations'
ErrorStructureDefinition.baseDefinitionValues for baseDefinition differ: 'http://hl7.org/fhir/StructureDefinition/Observation' vs 'http://hl7.org/fhir/us/cancer-reporting/StructureDefinition/ihe-sdc-ecc-Observation'
InformationStructureDefinition.shortValues for short differ: 'Survey Observation' vs 'Measurements and simple assertions'
InformationStructureDefinition.shortValues for short differ: 'Business Identifier for observation' vs 'The SDC instanceGUID'
InformationStructureDefinition.definitionValues for definition differ: 'A unique identifier assigned to this observation.' vs 'The identifier should match the SDC answer instanceGUID. If an answer instanceGUID is not available a Question instanceGUID shall be used'
WarningObservation.identifierElements differ in definition for mustSupport: 'false' vs 'true'
InformationObservation.identifierElement minimum cardinalities differ: '0' vs '1'
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'
InformationStructureDefinition.shortValues for short differ: 'Type of observation (code / type)' vs 'SDC section ID'
InformationStructureDefinition.definitionValues for definition differ: 'Describes what was observed. Sometimes this is called the observation 'name'.' vs 'The code should match the section ID from the SDC form.'
WarningObservation.codeElements differ in definition for mustSupport: 'true' vs 'false'
InformationObservation.subjectElement minimum cardinalities differ: '1' vs '0'
InformationStructureDefinition.definitionValues for definition differ: 'The time or time-period the observed value is asserted as being true. For biological subjects - e.g., human patients - this is usually called the 'physiologically relevant time'.' 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.' 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'
WarningObservation.performerElements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.shortValues for short differ: 'Actual result' vs 'In a grouper Observation this value is blank'
InformationStructureDefinition.definitionValues for definition differ: 'The information determined as a result of making the observation, if the information has a simple value.' vs 'The value should match the from the SDC form. Unique Observations should be created for each multi-select answer'
InformationStructureDefinition.commentValues for comment differ: '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](http://hl7.org/fhir/R4/observation.html#notes) below.'
InformationObservation.value[x]Element maximum cardinalities differ: '1' vs '0'
InformationStructureDefinition.commentValues for comment differ: ''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'
InformationStructureDefinition.shortValues for short differ: 'Reference to panel members or multi-select responses or multi-select responses' vs 'Sub-questions of the Section'
InformationStructureDefinition.definitionValues for definition differ: 'Aggregate set of Observations that represent question answer pairs for both multi-question surveys, screenings, and assessments and multi-select questions.' vs 'hasMember should be used to capture all sub-questions of the Section'
InformationStructureDefinition.commentValues for comment differ: '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](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.'
InformationStructureDefinition.shortValues for short differ: 'Related measurements the observation is made from' vs 'parent observation reference'
InformationStructureDefinition.definitionValues for definition differ: 'Observations or or other resource such as a QuestionnaireResponse from which this observation value is derived.' vs 'derivedFrom should be used to capture a parent Observation or the parent DocumentReference'
InformationStructureDefinition.shortValues for short differ: 'Component results' vs 'additional entry'
InformationStructureDefinition.definitionValues for definition differ: 'Some observations have multiple component observations. These component observations are expressed as separate code value pairs that share the same attributes. Examples include systolic and diastolic component observations for blood pressure measurement and multiple component observations for genetics observations.' vs 'Any additional list item response fields which were filled in should be captured in the component as their appropriate value type'
WarningObservation.componentElements differ in definition for mustSupport: 'false' vs 'true'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/Observationhttp://hl7.org/fhir/us/cancer-reporting/StructureDefinition/ihe-sdc-ecc-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'
    .date2024-11-162024-12-16T21:09:11+00:00
    • Values Differ
    .descriptionThe US Core Observation Screening Assessment Profile inherits from the FHIR [Observation](https://hl7.org/fhir/R4/observation.html) resource; refer to it for scope and usage definitions. This profile meets the requirements of the U.S. Core Data for Interoperability (USCDI) *Health Status Assessments* Data Class. 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 cognitive, functional, or disability status. It can represent a single response, multiple responses, and multi-select "check all that apply" type questions. This profile 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. Before reviewing this profile, implementers are encouraged to read the Screening and Assessments guidance page, which documents the process of recording responses and capturing assertions/determinations resulting from surveys and questionnaires.This Observation Profile describes how to represent a Section from IHE SDC as a 'grouper' Observation. It is a parent Observation and the Observation.value[x] element should be left blank. The Observation.code element should represent the Section's @ID and @title.
    • Values Differ
    .experimental
      .fhirVersion4.0.1
        .jurisdiction
          ..jurisdiction[0]urn:iso:std:iso:3166#US
            .kindresource
              .nameUSCoreObservationScreeningAssessmentProfileUSPathologyGrouperObservation
              • Values Differ
              .publisherHL7 International / Cross-Group ProjectsHL7 International / Orders and Observations
              • Values Differ
              .purpose
                .statusactive
                  .titleUS Core Observation Screening Assessment ProfileUS Pathology Grouper Observation
                  • Values Differ
                  .typeObservation
                    .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-assessmenthttp://hl7.org/fhir/us/cancer-reporting/StructureDefinition/us-pathology-grouper-observation
                    • Values Differ
                    .version8.0.0-ballot1.0.1
                    • Values Differ

                    Structure

                    NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.R TypeR Description & ConstraintsCommentsdoco
                    .. Observation C0..*ObservationSurvey Observation
                    obs-6: dataAbsentReason SHALL only be present if Observation.value[x] is not present
                    obs-7: If Observation.code is the same as an Observation.component.code then the value element associated with the code SHALL NOT be present
                    us-core-2: If there is no component or hasMember element then either a value[x] or a data absent reason must be present
                    C0..*ObservationSDCeCCMeasurements and simple assertions
                    obs-6: dataAbsentReason SHALL only be present if Observation.value[x] is not present
                    obs-7: If Observation.code is the same as an Observation.component.code then the value element associated with the code SHALL NOT be present
                      ... 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
                                      SΣ1..*IdentifierThe SDC instanceGUID
                                      • Elements differ in definition for mustSupport: 'false' vs 'true'
                                      • Element minimum cardinalities differ: '0' vs '1'
                                      ... basedOn Σ0..*Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest)Fulfills plan, proposal or order
                                      Σ0..*Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest)Fulfills plan, proposal or order
                                        ... partOf Σ0..*Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy)Part of referenced event
                                        Σ0..*Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy)Part of referenced event
                                          ... status ?!SΣ1..1coderegistered | preliminary | final | amended +
                                          Binding: ?? (required): Codes providing the status of an observation.

                                          ?!Σ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:$this
                                          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..1CodeableConceptType of observation (code / type)
                                          Binding: ?? (preferred)
                                          Σ1..1CodeableConceptSDC section ID
                                          Binding: ?? (extensible)
                                          • Elements differ in definition for mustSupport: 'true' vs 'false'
                                          ... subject SΣ1..1Reference(US Core Patient Profile(6.1.0) S | Group | Device | US Core Location Profile(6.1.0))Who and/or what the observation is aboutSΣ0..1Reference(US Core Patient Profile(6.1.0))Who and/or what the observation is about
                                          • Element minimum cardinalities differ: '1' vs '0'
                                          ... focus Σ0..*Reference(Resource)What the observation is about, when it is not about the subject of record
                                          Σ0..*Reference(Resource)What the observation is about, when it is not about the subject of record
                                            ... encounter Σ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.
                                              Σ0..1dateTime, Period, Timing, instantClinically relevant time/time-period for observation
                                              • 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 SΣ0..*Reference(US Core Practitioner Profile(6.1.0) S | US Core Patient Profile(6.1.0) S | US Core Organization Profile(6.1.0) | PractitionerRole | US Core CareTeam Profile(6.1.0) | US Core RelatedPerson Profile(6.1.0))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 result
                                                us-core-3: SHALL use UCUM for coded quantity units.
                                                SΣC0..0
                                                • Element maximum cardinalities differ: '1' vs '0'
                                                ... dataAbsentReason SC0..1CodeableConceptWhy the result is missing
                                                Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing.

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

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


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


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

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

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

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

                                                        ... specimen 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)(Measurement) Device
                                                            ... referenceRange C0..*BackboneElementProvides guide for interpretation
                                                            obs-3: Must have at least a low or a high or text
                                                            C0..*BackboneElementProvides guide for interpretation
                                                            obs-3: Must have at least a low or a high or text
                                                              .... 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 SΣ0..*Reference(US Core Observation Screening Assessment Profile S | QuestionnaireResponse | MolecularSequence)Reference to panel members or multi-select responses or multi-select responses
                                                                                SΣ0..*Reference(IHE SDC/eCP on FHIR Observation)Sub-questions of the Section
                                                                                  ... derivedFrom SΣ0..*Reference(US Core Observation Screening Assessment Profile S | US Core QuestionnaireResponse Profile(6.1.0) S | US Core DocumentReference Profile(6.1.0) | ImagingStudy | Media | MolecularSequence)Related measurements the observation is made from
                                                                                  SΣ0..*Reference(IHE SDC/eCP on FHIR Observation)parent observation reference
                                                                                    ... component Σ0..*BackboneElementComponent results
                                                                                    SΣ0..*BackboneElementadditional entry
                                                                                    • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                                    .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                                      .... extension 0..*ExtensionAdditional content defined by implementations
                                                                                      0..*ExtensionAdditional content defined by implementations
                                                                                        .... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                                        ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                                          .... code Σ1..1CodeableConceptType of component observation (code / type)
                                                                                          Binding: ?? (example): Codes identifying names of simple observations.

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

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

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

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


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


                                                                                                  .... referenceRange 0..*See referenceRange (Observation)Provides guide for interpretation of component result
                                                                                                  0..*See referenceRange (Observation)Provides guide for interpretation of component result

                                                                                                    doco Documentation for this format