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

Left:US Core Observation Screening Assessment Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-assessment)
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-screening-assessment' 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: 'USCoreObservationScreeningAssessmentProfile' 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/StructureDefinition/Observation' vs 'http://hl7.org/fhir/us/ecr/StructureDefinition/us-ph-transportation-details'
InformationStructureDefinition.shortValues for short differ: 'Survey Observation' 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: 'Type of observation (code / type)' vs 'Transportation details'
InformationObservation.codeExample/preferred bindings differ at Observation.code using binding from USCoreObservationScreeningAssessmentProfile
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'
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'
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.'
InformationObservation.issuedElement maximum cardinalities differ: '1' vs '0'
WarningObservation.performerElements differ in definition for mustSupport: 'true' vs 'false'
InformationObservation.performerElement maximum cardinalities differ: '2147483647' vs '0'
InformationStructureDefinition.shortValues for short differ: 'Actual result' vs 'Type of transport vehicle'
InformationStructureDefinition.definitionValues for definition differ: 'The information determined as a result of making the observation, if the information has a simple value.' vs 'All codes in the hierarchy under: SNOMED: 36030000 |Transport vehicle, device (physical object)|'
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 minimum cardinalities differ: '0' vs '1'
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'
InformationObservation.dataAbsentReasonElement maximum cardinalities differ: '1' vs '0'
InformationObservation.interpretationElement maximum cardinalities differ: '2147483647' vs '0'
InformationObservation.bodySiteElement maximum cardinalities differ: '1' vs '0'
InformationObservation.methodElement maximum cardinalities differ: '1' vs '0'
InformationObservation.specimenElement maximum cardinalities differ: '1' vs '0'
InformationObservation.deviceElement maximum cardinalities differ: '1' vs '0'
InformationObservation.referenceRangeElement maximum cardinalities differ: '2147483647' vs '0'
InformationStructureDefinition.shortValues for short differ: 'Reference to panel members or multi-select responses or multi-select responses' vs 'Related resource that belongs to the Observation group'
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 'This observation is a group observation (e.g. a battery, a panel of tests, a set of vital sign measurements) that includes the target as a member of the group.'
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.'
WarningObservation.hasMemberElements differ in definition for mustSupport: 'true' vs 'false'
InformationObservation.hasMemberElement maximum cardinalities differ: '2147483647' vs '0'
InformationStructureDefinition.shortValues for short differ: '𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: Related Observation(s) or other resource the observation is made from' vs 'Related measurements the observation is made from'
InformationStructureDefinition.definitionValues for definition differ: 'Observations or or other resource such as a QuestionnaireResponse from which this observation value is derived.' vs 'The target resource that represents a measurement from which this observation value is derived. For example, a calculated anion gap or a fetal measurement based on an ultrasound image.'
WarningObservation.derivedFromElements differ in definition for mustSupport: 'true' vs 'false'
InformationObservation.derivedFromElement maximum cardinalities differ: '2147483647' vs '0'
ErrorObservation.derivedFromType Mismatch: Reference([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-assessment], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-questionnaireresponse], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-documentreference], CanonicalType[http://hl7.org/fhir/StructureDefinition/ImagingStudy], CanonicalType[http://hl7.org/fhir/StructureDefinition/Media], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/DocumentReference], CanonicalType[http://hl7.org/fhir/StructureDefinition/ImagingStudy], CanonicalType[http://hl7.org/fhir/StructureDefinition/Media], CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/Observation], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]])
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/StructureDefinition/Observationhttp://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 Observation Screening Assessment Profile meets the requirements of the US Core Data for Interoperability (USCDI) Assessments. To promote interoperability and adoption through common implementation, it sets the minimum expectations for the Observation Resource to record, search, and fetch observations representing the questions and responses to surveys and screening and assessment tools. For example, a social history status such as education or food insecurity or an assessment of the patient's cognitive, functional, or disability status. It can represent a single response, multiple responses, and multi-select "check all that apply" type questions. It identifies which core elements, extensions, vocabularies, and value sets **SHALL** be present in the resource 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
    .experimental
      .fhirVersion4.0.1
        .jurisdiction
          ..jurisdiction[0]urn:iso:std:iso:3166#US
          • Removed the item 'urn:iso:std:iso:3166#US'
          .kindresource
            .nameUSCoreObservationScreeningAssessmentProfileFlightItinerary
            • Values Differ
            .publisherHL7 International / Cross-Group ProjectsHL7 Public Health Working Group
            • Values Differ
            .purpose
              .statusactivedraft
              • Values Differ
              .titleUS Core Observation Screening Assessment Profile
              • Removed the item 'US Core Observation Screening Assessment Profile'
              .typeObservation
                .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-assessmenthttp://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..*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..*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..1CodeableConceptType of observation (code / type)
                                Binding: ?? (preferred)
                                SΣ1..1CodeableConceptTransportation details
                                Binding: ?? (example): Codes identifying names of simple observations.


                                Required Pattern: {"coding":[{"system":"http://snomed.info/sct","code":"424483007"}]}
                                • Example/preferred bindings differ at Observation.code using binding from USCoreObservationScreeningAssessmentProfile
                                ... 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 Σ0..1Reference(Encounter)Healthcare event during which this observation is madeΣ0..0
                                • 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 SΣ0..*Reference(US Core Practitioner Profile | US Core Organization Profile | US Core Patient Profile | PractitionerRole | US Core CareTeam Profile | US Core RelatedPerson Profile)Who is responsible for the observation
                                  Σ0..0
                                  • Elements differ in definition for mustSupport: 'true' vs 'false'
                                  • Element maximum cardinalities differ: '2147483647' vs '0'
                                  ... 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Σ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 0..*CodeableConceptHigh, low, normal, etc.
                                  Binding: ?? (extensible): Codes identifying interpretations of observations.


                                  0..0
                                  • 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 0..1Reference(Specimen)Specimen used for this observation0..0
                                    • Element maximum cardinalities differ: '1' vs '0'
                                    ... device 0..1Reference(Device | DeviceMetric)(Measurement) Device0..0
                                    • Element maximum cardinalities differ: '1' vs '0'
                                    ... referenceRange C0..*BackboneElementProvides guide for interpretation
                                    obs-3: Must have at least a low or a high or text
                                    C0..0
                                    • 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 SΣ0..*Reference(US Core Observation Screening Assessment Profile S | QuestionnaireResponse | MolecularSequence)Reference to panel members or multi-select responses or multi-select responses
                                                      Σ0..0
                                                      • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                      • Element maximum cardinalities differ: '2147483647' vs '0'
                                                      ... derivedFrom SΣ0..*Reference(US Core Observation Screening Assessment Profile S | US Core QuestionnaireResponse Profile S | US Core DocumentReference Profile | ImagingStudy | Media | MolecularSequence)𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: Related Observation(s) or other resource the observation is made from
                                                      Σ0..0
                                                      • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                      • Element maximum cardinalities differ: '2147483647' vs '0'
                                                      • Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-assessment], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-questionnaireresponse], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-documentreference], CanonicalType[http://hl7.org/fhir/StructureDefinition/ImagingStudy], CanonicalType[http://hl7.org/fhir/StructureDefinition/Media], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/DocumentReference], CanonicalType[http://hl7.org/fhir/StructureDefinition/ImagingStudy], CanonicalType[http://hl7.org/fhir/StructureDefinition/Media], CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/Observation], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]])
                                                      ... component Σ0..*BackboneElementComponent results
                                                      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