Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab vs http://hl7.org/fhir/us/reportofilltraveler/StructureDefinition/FlightItinerary

Left:US Core Laboratory Result Observation Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab)
Right:FlightItinerary (http://hl7.org/fhir/us/reportofilltraveler/StructureDefinition/FlightItinerary)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab' vs 'http://hl7.org/fhir/us/reportofilltraveler/StructureDefinition/FlightItinerary'
ErrorStructureDefinition.versionValues for version differ: '7.0.0-ballot' vs '0.1.0'
InformationStructureDefinition.nameValues for name differ: 'USCoreLaboratoryResultObservationProfile' vs 'FlightItinerary'
InformationStructureDefinition.statusValues for status differ: 'active' vs 'draft'
InformationStructureDefinition.dateValues for date differ: '2023-10-17' vs '2024-03-01T17:24:54+00:00'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 International / Cross-Group Projects' vs 'HL7 Public Health Working Group'
InformationStructureDefinition.jurisdictionRemoved the item 'urn:iso:std:iso:3166#US'
ErrorStructureDefinition.baseDefinitionValues for baseDefinition differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-clinical-result' vs 'http://hl7.org/fhir/us/ecr/StructureDefinition/us-ph-transportation-details'
InformationStructureDefinition.shortValues for short differ: 'Measurements and simple assertions' vs 'US Public Health Transportation Details'
InformationStructureDefinition.definitionValues for definition differ: '\-' vs 'Measurements and simple assertions made about a patient, device or other subject.'
InformationStructureDefinition.commentValues for comment differ: '\-' vs 'Used for simple observations such as device measurements, laboratory atomic results, vital signs, height, weight, smoking status, comments, etc. Other resources are used to provide context for observations such as laboratory reports, etc.'
InformationObservation.implicitRulesElement maximum cardinalities differ: '1' vs '0'
InformationObservation.containedElement maximum cardinalities differ: '2147483647' vs '0'
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'
InformationObservation.basedOnElement maximum cardinalities differ: '2147483647' vs '0'
InformationObservation.partOfElement maximum cardinalities differ: '2147483647' vs '0'
WarningObservation.statusElements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.shortValues for short differ: 'Classification of type of observation' vs 'Transportation'
InformationObservation.categoryElement maximum cardinalities differ: '2147483647' vs '1'
InformationStructureDefinition.shortValues for short differ: 'Laboratory Test Name' vs 'Transportation details'
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.'
WarningObservation.subjectElements differ in definition for mustSupport: 'true' vs 'false'
InformationObservation.subjectElement minimum cardinalities differ: '1' vs '0'
InformationObservation.focusElement maximum cardinalities differ: '2147483647' vs '0'
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.encounterElement maximum cardinalities differ: '1' vs '0'
InformationStructureDefinition.shortValues for short differ: 'Clinically relevant time/time-period for observation' vs 'Date or period of transportation'
InformationObservation.issuedElement maximum cardinalities differ: '1' vs '0'
InformationObservation.performerElement maximum cardinalities differ: '2147483647' vs '0'
InformationStructureDefinition.shortValues for short differ: 'Result Value' vs 'Type of transport vehicle'
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 'All codes in the hierarchy under: SNOMED: 36030000 |Transport vehicle, device (physical object)|'
InformationObservation.value[x]Element minimum cardinalities differ: '0' vs '1'
WarningObservation.dataAbsentReasonElements differ in definition for mustSupport: 'true' vs 'false'
InformationObservation.dataAbsentReasonElement maximum cardinalities differ: '1' vs '0'
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'
InformationObservation.interpretationElement maximum cardinalities differ: '2147483647' vs '0'
InformationObservation.bodySiteElement maximum cardinalities differ: '1' vs '0'
InformationObservation.methodElement maximum cardinalities differ: '1' vs '0'
WarningObservation.specimenElements differ in definition for mustSupport: 'true' vs 'false'
InformationObservation.specimenElement maximum cardinalities differ: '1' vs '0'
InformationObservation.deviceElement maximum cardinalities differ: '1' vs '0'
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'
InformationObservation.referenceRangeElement maximum cardinalities differ: '2147483647' vs '0'
InformationStructureDefinition.commentValues for comment differ: 'When using this element, an observation will typically have either a value or a set of related resources, although both may be present in some cases. For a discussion on the ways Observations can assembled in groups together, see [Notes](http://hl7.org/fhir/R4/observation.html#obsgrouping) below. Note that a system may calculate results from [QuestionnaireResponse](questionnaireresponse.html) into a final score and represent the score as an Observation.' vs 'When using this element, an observation will typically have either a value or a set of related resources, although both may be present in some cases. For a discussion on the ways Observations can assembled in groups together, see [Notes](http://hl7.org/fhir/R4/observation.html#obsgrouping) below. Note that a system may calculate results from [QuestionnaireResponse](http://hl7.org/fhir/R4/questionnaireresponse.html) into a final score and represent the score as an Observation.'
InformationObservation.hasMemberElement maximum cardinalities differ: '2147483647' vs '0'
InformationObservation.derivedFromElement maximum cardinalities differ: '2147483647' vs '0'
InformationStructureDefinition.shortValues for short differ: 'Component results' vs 'Information about the mode of transportation (ship name, flight number, seat number, etc.)'
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 'Information about the mode of transportation (ship name, flight number, seat number, etc.)'
WarningObservation.componentElements differ in definition for mustSupport: 'false' vs 'true'
InformationObservation.componentElement maximum cardinalities differ: '2147483647' vs '0'
InformationStructureDefinition.shortValues for short differ: 'Type of component observation (code / type)' vs 'Type of transportation information'
InformationStructureDefinition.definitionValues for definition differ: 'Describes what was observed. Sometimes this is called the observation 'code'.' vs 'Type of transportation information (ship name, flight number, seat number, etc.)'
WarningObservation.component.codeElements differ in definition for mustSupport: 'false' vs 'true'
WarningObservation.component.value[x]Elements differ in definition for mustSupport: 'false' vs 'true'
InformationObservation.component.value[x]Element minimum cardinalities differ: '0' vs '1'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-clinical-resulthttp://hl7.org/fhir/us/ecr/StructureDefinition/us-ph-transportation-details
    • 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-03-01T17:24:54+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.Flight information for an ill traveler
    • Values Differ
    .experimentalfalse
    • Removed the item 'false'
    .fhirVersion4.0.1
      .jurisdiction
        ..jurisdiction[0]urn:iso:std:iso:3166#US
        • Removed the item 'urn:iso:std:iso:3166#US'
        .kindresource
          .nameUSCoreLaboratoryResultObservationProfileFlightItinerary
          • Values Differ
          .publisherHL7 International / Cross-Group ProjectsHL7 Public Health Working Group
          • Values Differ
          .purpose
            .statusactivedraft
            • Values Differ
            .titleUS Core Laboratory Result Observation Profile
            • Removed the item 'US Core Laboratory Result Observation Profile'
            .typeObservation
              .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-labhttp://hl7.org/fhir/us/reportofilltraveler/StructureDefinition/FlightItinerary
              • Values Differ
              .version7.0.0-ballot0.1.0
              • Values Differ

              Structure

              NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.L TypeL 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..*USPublicHealthTransportationDetailsUS Public Health Transportation Details
              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..0
                    • Element maximum cardinalities differ: '1' vs '0'
                    ... 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..0
                        • Element maximum cardinalities differ: '2147483647' vs '0'
                        ... 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..0
                              • Element maximum cardinalities differ: '2147483647' vs '0'
                              ... partOf Σ0..*Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy)Part of referenced event
                              		Σ0..0
                              • Element maximum cardinalities differ: '2147483647' vs '0'
                              ... 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.


                              Required Pattern: preliminary
                              • Elements differ in definition for mustSupport: 'true' vs 'false'
                              ... Slices for category S1..*CodeableConceptClassification of type of observation
                              Slice: Unordered, Open by pattern:$this
                              Binding: ?? (preferred): Codes for high level observation categories.


                              		S1..1CodeableConceptTransportation
                              Binding: ?? (preferred): Codes for high level observation categories.



                              Required Pattern: {"coding":[{"system":"http://terminology.hl7.org/CodeSystem/v3-ActClass","code":"TRNS"}]}
                              • Element maximum cardinalities differ: '2147483647' vs '1'
                              ... code SΣ1..1CodeableConceptLaboratory Test Name
                              Binding: ?? (extensible): Laboratory LOINC Codes

                              		SΣ1..1CodeableConceptTransportation details
                              Binding: ?? (example): Codes identifying names of simple observations.


                              Required Pattern: {"coding":[{"system":"http://snomed.info/sct","code":"424483007"}]}
                                ... subject SΣ1..1Reference(US Core Patient Profile S | Group | Device | US Core Location Profile)Who and/or what the observation is aboutΣ0..1Reference(Patient | Group | Device | Location)Who and/or what the observation is about
                                • Elements differ in definition for mustSupport: 'true' vs 'false'
                                • 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..0
                                • Element maximum cardinalities differ: '2147483647' vs '0'
                                ... encounter SΣ0..1Reference(US Core Encounter Profile)Encounter associated with ObservationΣ0..0
                                • Elements differ in definition for mustSupport: 'true' vs 'false'
                                • Element maximum cardinalities differ: '1' vs '0'
                                ... 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, PeriodDate or period of transportation
                                  ... issued Σ0..1instantDate/Time this version was made availableΣ0..0
                                  • Element maximum cardinalities differ: '1' vs '0'
                                  ... performer Σ0..*Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson)Who is responsible for the observation
                                  		Σ0..0
                                  • Element maximum cardinalities differ: '2147483647' vs '0'
                                  ... 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ΣC1..1CodeableConceptType of transport vehicle
                                  Binding: ?? (required): Transport Vehicle Type


                                  Required Pattern: {"coding":[{"system":"http://snomed.info/sct","code":"261325004","display":"Airliner"}]}
                                  • Element minimum cardinalities differ: '0' vs '1'
                                  ... dataAbsentReason SC0..1CodeableConceptWhy the result is missing
                                  Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing.

                                  		C0..0
                                  • Elements differ in definition for mustSupport: 'true' vs 'false'
                                  • Element maximum cardinalities differ: '1' vs '0'
                                  ... interpretation S0..*CodeableConceptResult interpretation
                                  Binding: ?? (extensible): Observation Interpretation Codes


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

                                    		0..0
                                    • Element maximum cardinalities differ: '1' vs '0'
                                    ... method 0..1CodeableConceptHow it was done
                                    Binding: ?? (example): Methods for simple observations.

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

                                              		0..1CodeableConceptReference range qualifier
                                              Binding: ?? (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..0
                                                      • Element maximum cardinalities differ: '2147483647' vs '0'
                                                      ... derivedFrom Σ0..*Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | Observation | MolecularSequence)Related measurements the observation is made from
                                                      		Σ0..0
                                                      • Element maximum cardinalities differ: '2147483647' vs '0'
                                                      ... component Σ0..*BackboneElementComponent results
                                                      		SΣ0..0
                                                      • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                      • Element maximum cardinalities differ: '2147483647' vs '0'
                                                      .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                        .... extension 0..*ExtensionAdditional content defined by implementations
                                                        		0..*ExtensionAdditional content defined by implementations
                                                          .... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                          		?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                            .... code Σ1..1CodeableConceptType of component observation (code / type)
                                                            Binding: ?? (example): Codes identifying names of simple observations.

                                                            		SΣ1..1CodeableConceptType of transportation information
                                                            Binding: ?? (example): Codes identifying names of simple observations.

                                                            • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                            .... value[x] Σ0..1Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodActual component resultSΣ1..1Quantity, CodeableConcept, string, integer, time, dateTime, PeriodActual component result
                                                            • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                            • Element minimum cardinalities differ: '0' vs '1'
                                                            .... 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