Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab vs http://hl7.org/fhir/us/pacio-pfe/StructureDefinition/pfe-observation-abstract

Left:US Core Laboratory Result Observation Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab)
Right:Personal Functioning and Engagement Abstract Observation (http://hl7.org/fhir/us/pacio-pfe/StructureDefinition/pfe-observation-abstract)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab' vs 'http://hl7.org/fhir/us/pacio-pfe/StructureDefinition/pfe-observation-abstract'
ErrorStructureDefinition.versionValues for version differ: '7.0.0' vs '2.0.0-ballot'
InformationStructureDefinition.nameValues for name differ: 'USCoreLaboratoryResultObservationProfile' vs 'PFEAbstractObservation'
InformationStructureDefinition.titleValues for title differ: 'US Core Laboratory Result Observation Profile' vs 'Personal Functioning and Engagement Abstract Observation'
InformationStructureDefinition.dateValues for date differ: '2023-10-17' vs '2024-08-13T15:12:12+00:00'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 International / Cross-Group Projects' vs 'HL7 International / Patient Care'
WarningStructureDefinition.abstractValues for abstract differ: 'false' vs 'true'
ErrorStructureDefinition.baseDefinitionValues for baseDefinition differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-clinical-result' vs 'http://hl7.org/fhir/StructureDefinition/Observation'
WarningObservation.metaElements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.shortValues for short differ: 'Additional content defined by implementations' vs 'Extension'
InformationStructureDefinition.definitionValues for definition differ: 'May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'An Extension'
InformationStructureDefinition.shortValues for short differ: 'registered | preliminary | final | amended +' vs 'Should have the value 'final' when the observation is complete and there are no further actions needed. Otherwise, another value from the value set may appropriately be used.'
InformationStructureDefinition.requirementsValues for requirements differ: 'Used for filtering what observations are retrieved and displayed.' vs 'To identify that observation is derived from a questionnaire, is related to personal functioning and engagement, and optionally to identify the domain(s) it falls under.'
InformationStructureDefinition.shortValues for short differ: 'Laboratory Test Name' vs 'Type of observation (code / type)'
InformationStructureDefinition.definitionValues for definition differ: 'The name of the clinical test or procedure performed on a patient. A LOINC **SHALL** be used if the concept is present in LOINC.' vs 'Describes what was observed. Sometimes this is called the observation 'name'.'
InformationStructureDefinition.commentValues for comment differ: 'The typical patterns for codes are: 1) a LOINC code either as a translation from a 'local' code or as a primary code, or 2) a local code only if no suitable LOINC exists, or 3) both the local and the LOINC translation. Systems SHALL be capable of sending the local code if one exists. When using LOINC , Use either the SHORTNAME or LONG_COMMON_NAME field for the display.' vs '*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.shortValues for short differ: 'Encounter associated with Observation' vs 'Healthcare event during which this observation is made'
WarningObservation.encounterElements differ in definition for mustSupport: 'true' vs 'false'
InformationObservation.effective[x]Element minimum cardinalities differ: '0' vs '1'
WarningObservation.performerElements differ in definition for mustSupport: 'false' vs 'true'
InformationObservation.performerElement minimum cardinalities differ: '0' vs '1'
InformationStructureDefinition.shortValues for short differ: 'Result Value' vs 'Actual result'
InformationStructureDefinition.definitionValues for definition differ: 'The Laboratory result value. If a coded value, the valueCodeableConcept.code **SHOULD** be selected from [SNOMED CT](http://hl7.org/fhir/ValueSet/uslab-obs-codedresults) if the concept exists. If a numeric value, valueQuantity.code **SHALL** be selected from [UCUM](http://unitsofmeasure.org). A FHIR [UCUM Codes value set](http://hl7.org/fhir/STU3/valueset-ucum-units.html) that defines all UCUM codes is in the FHIR specification.' vs 'The information determined as a result of making the observation, if the information has a simple value.'
WarningObservation.dataAbsentReasonElements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.shortValues for short differ: 'Result interpretation' vs 'High, low, normal, etc.'
InformationStructureDefinition.commentValues for comment differ: 'Categorical assessment of a laboratory value, often in relation to a test's reference range. Examples include but are not limited to high, low, critical, and normal.' vs 'Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result.'
WarningObservation.interpretationElements differ in definition for mustSupport: 'true' vs 'false'
WarningObservation.specimenElements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.shortValues for short differ: 'Result reference range' vs 'Provides guide for interpretation'
InformationStructureDefinition.commentValues for comment differ: 'Upper and lower limit of test values expected for a designated population of individuals. Reference range values may differ by patient characteristics, laboratory test manufacturer and laboratory test performer.' vs 'Most observations only have one generic reference range. Systems MAY choose to restrict to only supplying the relevant reference range based on knowledge about the patient (e.g., specific to the patient's age, gender, weight and other factors), but this might not be possible or appropriate. Whenever more than one reference range is supplied, the differences between them SHOULD be provided in the reference range and/or age properties.'
WarningObservation.referenceRangeElements differ in definition for mustSupport: 'true' vs 'false'

Metadata

NameValueComments
.abstractfalsetrue
  • Values Differ
.baseDefinitionhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-clinical-resulthttp://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'
.date2023-10-172024-08-13T15:12:12+00:00
  • Values Differ
.descriptionThe US Core Laboratory Result Observation Profile is based upon the US Core Observation Clinical Result Profile and, along with the US Core DiagnosticReport Profile for Laboratory Results Reporting, meets the U.S. Core Data for Interoperability (USCDI) Laboratory requirements. Laboratory results are grouped and summarized using the DiagnosticReport resource, which references Observation resources. Each Observation resource represents an individual laboratory test and result value, a “nested” panel (such as a microbial susceptibility panel) that references other observations, or rarely a laboratory test with component result values. The US Core Laboratory Result Observation Profile sets minimum expectations for the Observation resource to record, search, and fetch laboratory test results associated with a patient to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains the way the elements are used when using this profile. It provides the floor for standards development for specific use cases.An abstract profile representing the cross-cutting requirements for Personal Functioning and Engagement Observation instances. This profile is not intended to be used directly. Implementers should use specific profiles that layer these requirements on top of specific US Core Observation profiles.
  • Values Differ
.experimentalfalse
  • Removed the item 'false'
.fhirVersion4.0.1
    .jurisdiction
      ..jurisdiction[0]urn:iso:std:iso:3166#US
        .kindresource
          .nameUSCoreLaboratoryResultObservationProfilePFEAbstractObservation
          • Values Differ
          .publisherHL7 International / Cross-Group ProjectsHL7 International / Patient Care
          • Values Differ
          .purpose
            .statusactive
              .titleUS Core Laboratory Result Observation ProfilePersonal Functioning and Engagement Abstract Observation
              • Values Differ
              .typeObservation
                .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-labhttp://hl7.org/fhir/us/pacio-pfe/StructureDefinition/pfe-observation-abstract
                • Values Differ
                .version7.0.02.0.0-ballot
                • Values Differ

                Structure

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


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


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

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

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

                                      ?!SΣ1..1codeShould have the value 'final' when the observation is complete and there are no further actions needed. Otherwise, another value from the value set may appropriately be used.
                                      Binding: ?? (required): Codes providing the status of an observation.

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


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


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

                                          SΣ1..1CodeableConceptType of observation (code / type)
                                          Binding: ?? (example)
                                            ... subject SΣ1..1Reference(US Core Patient Profile S | Group | Device | US Core Location Profile)Who and/or what the observation is aboutSΣ1..1Reference(Patient | Group | Device | Location)Who and/or what the observation is about
                                              ... focus Σ0..*Reference(Resource)What the observation is about, when it is not about the subject of record
                                              Σ0..*Reference(Resource)What the observation is about, when it is not about the subject of record
                                                ... encounter SΣ0..1Reference(US Core Encounter Profile)Encounter associated with ObservationΣ0..1Reference(Encounter)Healthcare event during which this observation is made
                                                • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                ... effective[x] SΣC0..1dateTime S, Period, Timing, instantClinically relevant time/time-period for observation
                                                us-core-1: Datetime must be at least to day.
                                                SΣ1..1dateTime, Period, Timing, instantClinically relevant time/time-period for observation
                                                • Element minimum cardinalities differ: '0' vs '1'
                                                ... issued Σ0..1instantDate/Time this version was made availableΣ0..1instantDate/Time this version was made available
                                                  ... performer Σ0..*Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson)Who is responsible for the observation
                                                  SΣ1..*Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson)Who is responsible for the observation
                                                  • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                  • Element minimum cardinalities differ: '0' vs '1'
                                                  ... value[x] SΣC0..1Quantity S, CodeableConcept S, string S, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodResult Value
                                                  us-core-3: SHALL use UCUM for coded quantity units.
                                                  us-core-4: SHOULD use Snomed CT for coded Results
                                                  SΣC0..1Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodActual result
                                                    ... 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 S0..*CodeableConceptResult interpretation
                                                    Binding: ?? (extensible): Observation Interpretation Codes


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


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

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

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

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

                                                          ... specimen S0..1Reference(US Core Specimen Profile)Specimen used for this observation0..1Reference(Specimen)Specimen used for this observation
                                                          • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                          ... device 0..1Reference(Device | DeviceMetric)(Measurement) Device0..1Reference(Device | DeviceMetric)(Measurement) Device
                                                            ... referenceRange SC0..*BackboneElementResult reference range
                                                            obs-3: Must have at least a low or a high or text
                                                            us-core-22: SHALL use UCUM for coded quantity units.
                                                            C0..*BackboneElementProvides guide for interpretation
                                                            obs-3: Must have at least a low or a high or text
                                                            • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                            .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                              .... extension 0..*ExtensionAdditional content defined by implementations
                                                              0..*ExtensionAdditional content defined by implementations
                                                                .... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                  .... low C0..1??Low Range, if relevantC0..1??Low Range, if relevant
                                                                    .... high C0..1??High Range, if relevantC0..1??High Range, if relevant
                                                                      .... type 0..1CodeableConceptReference range qualifier
                                                                      Binding: ?? (preferred): Code for the meaning of a reference range.

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

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


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


                                                                          .... age 0..1RangeApplicable age range, if relevant0..1RangeApplicable age range, if relevant
                                                                            .... text 0..1stringText based reference range in an observation0..1stringText based reference range in an observation
                                                                              ... hasMember Σ0..*Reference(Observation | QuestionnaireResponse | MolecularSequence)Related resource that belongs to the Observation group
                                                                              Σ0..*Reference(Observation | QuestionnaireResponse | MolecularSequence)Related resource that belongs to the Observation group
                                                                                ... derivedFrom Σ0..*Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | Observation | MolecularSequence)Related measurements the observation is made from
                                                                                Σ0..*Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | Observation | MolecularSequence)Related measurements the observation is made from
                                                                                  ... 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: ?? (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