Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-bmi vs http://hl7.org/fhir/us/pacio-fs/StructureDefinition/pacio-fsc

Left:US Core BMI Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-bmi)
Right:PACIO Functional Status Collection (http://hl7.org/fhir/us/pacio-fs/StructureDefinition/pacio-fsc)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-bmi' vs 'http://hl7.org/fhir/us/pacio-fs/StructureDefinition/pacio-fsc'
ErrorStructureDefinition.versionValues for version differ: '4.0.0' vs '1.0.0'
InformationStructureDefinition.nameValues for name differ: 'USCoreBMIProfileProfile' vs 'FunctionalStatusCollection'
InformationStructureDefinition.titleValues for title differ: 'US Core BMI Profile' vs 'PACIO Functional Status Collection'
InformationStructureDefinition.dateValues for date differ: '2020-11-17' vs '2021-11-03T18:56:23+00:00'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 International - US Realm Steering Committee' vs 'HL7 Patient Care Work Group'
ErrorStructureDefinition.baseDefinitionValues for baseDefinition differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-vital-signs' vs 'http://hl7.org/fhir/StructureDefinition/Observation'
WarningObservationElements differ in short: 'US Core Body Mass Index (BMI) Profile' 'Measurements and simple assertions'
WarningObservationElements differ in definition: 'Defines constraints on Observation to represent Body Mass Index (BMI) observations with a standard LOINC code and UCUM units of measure. This profile is derived from the US Core Vital Signs Profile.' 'Measurements and simple assertions made about a patient, device or other subject.'
WarningObservation.extensionElements differ in short: 'Additional content defined by implementations' 'Extension'
WarningObservation.extensionElements differ in definition: '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.' 'An Extension'
WarningObservation.basedOnElements differ in short: 'Fulfills plan, proposal or order' 'Currently not used in FunctionalStatusCollection.'
WarningObservation.partOfElements differ in short: 'Part of referenced event' 'Currently not used in FunctionalStatusCollection.'
WarningObservation.statusElements differ in short: 'registered | preliminary | final | amended +' 'Should have the value 'final' when all the observatons are complete and there are no further actions needed. Otherwise, another value from the value set may appropriately be used.'
ErrorObservation.statusElements differ in definition for mustSupport: 'true' 'false'
WarningObservation.categoryElements differ in short: 'Classification of type of observation' 'A second category code may be used along with the code “functioning”. For example, for assessment tool/survey instrument observations use “survey” as a second code.'
ErrorObservation.categoryElements differ in definition for mustSupport: 'true' 'false'
WarningObservation.codeElements differ in short: 'Coded Responses from C-CDA Vital Sign Results' 'For a Post-Acute Care structured assessment resource such as an instrument or screen, use a LOINC code to identify the instrument/screen name or panel/section title to indicate the kind of assessment.'
WarningObservation.codeElements differ in definition: 'Coded Responses from C-CDA Vital Sign Results.' 'Describes what was observed. Sometimes this is called the observation 'name'.'
WarningObservation.codeElements differ in requirements: '5. SHALL contain exactly one [1..1] code, where the @code SHOULD be selected from ValueSet HITSP Vital Sign Result Type 2.16.840.1.113883.3.88.12.80.62 DYNAMIC (CONF:7301).' 'Knowing what kind of observation is being made is essential to understanding the observation.'
ErrorObservation.codeElements differ in definition for mustSupport: 'true' 'false'
WarningObservation.subjectElements differ in short: 'Who and/or what the observation is about' 'Should only reference a Patient resource.'
ErrorObservation.subjectElements differ in definition for mustSupport: 'true' 'false'
WarningObservation.focusElements differ in short: 'What the observation is about, when it is not about the subject of record' 'Currently not used in FunctionalStatusCollection.'
WarningObservation.effective[x]Elements differ in short: 'Often just a dateTime for Vital Signs' 'Clinical relevant time for an assessment such as functional assessments performed with structured evaluation tools is the time the evaluation occurs, i.e., when the clinician obtains the answers entered in the tool. However, the only timing available may be when then tool is completed by the clinician. That timing is generally documented as a point in time (dateTime).'
WarningObservation.effective[x]Elements differ in definition: 'Often just a dateTime for Vital Signs.' 'Clinical relevant time for an assessment such as functional assessments performed with structured evaluation tools is the time the evaluation occurs, i.e., when the clinician obtains the answers entered in the tool. However, the only timing available may be when then tool is completed by the clinician. That timing is generally documented as a point in time (dateTime).'
WarningObservation.effective[x]Elements differ in comments: 'At least a date should be present unless this observation is a historical report. For recording imprecise or 'fuzzy' times (For example, a blood glucose measurement taken 'after breakfast') use the [Timing] datatype which allow the measurement to be tied to regular life events.' 'The use of effective[x] and dateTime versus Period is subject to implementer workflow and needs. In most situations, an observation is considered as a point in time, even if the assessment occurred over a period of time. Period is included in this implementation guide to provide additional flexibility for specific use cases. However, it is expected most observations will be recorded using DateTime. Furthermore, any retrieval of information should return the relevant if DateTime is requested, even if the original observation was recorded as a period. Some implementers may choose to use additional functions in there retrieves to 'normalize' intervals, as is done in Clinical Quality Language (CQL).'
ErrorObservation.effective[x]Elements differ in definition for mustSupport: 'true' 'false'
WarningObservation.issuedElements differ in short: 'Date/Time this version was made available' 'Currently not used in FunctionalStatusCollection.'
WarningObservation.performerElements differ in short: 'Who is responsible for the observation' 'The person who performed the assessment. The preferred way to specify the performer is to use the PractitionerRole resource to provide both the practitioner and organization.'
WarningObservation.value[x]Elements differ in short: 'Vital Signs Value' 'If used, should use the CodeableConcept datatype whenever possible to provide a suitable code to define the concept for the observation data. When capturing a collection of related observations, typically this field is not used. If the outcome of an assessment includes one or more summary scores, leave this field unused and use the 'hasMember' field to point to one or more Observation resources with each of which has a score provided in the 'value' field.'
WarningObservation.value[x]Elements differ in definition: 'Vital Signs value are typically recorded using the Quantity data type.' 'The information determined as a result of making the observation, if the information has a simple value.'
WarningObservation.value[x]Elements differ in requirements: '9. SHALL contain exactly one [1..1] value with @xsi:type='PQ' (CONF:7305).' 'An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations.'
ErrorObservation.value[x]Elements differ in definition for mustSupport: 'true' 'false'
WarningObservation.dataAbsentReasonElements differ in short: 'Why the result is missing' 'Currently not used in FunctionalStatusCollection.'
ErrorObservation.dataAbsentReasonElements differ in definition for mustSupport: 'true' 'false'
WarningObservation.interpretationElements differ in short: 'High, low, normal, etc.' 'Currently not used in FunctionalStatusCollection.'
WarningObservation.bodySiteElements differ in short: 'Observed body part' 'Currently not used in FunctionalStatusCollection.'
WarningObservation.methodElements differ in short: 'How it was done' 'Currently not used in FunctionalStatusCollection.'
WarningObservation.specimenElements differ in short: 'Specimen used for this observation' 'Currently not used in FunctionalStatusCollection.'
WarningObservation.deviceElements differ in short: '(Measurement) Device' 'Currently not used in FunctionalStatusCollection.'
WarningObservation.referenceRangeElements differ in short: 'Provides guide for interpretation' 'Currently not used in FunctionalStatusCollection.'
WarningObservation.hasMemberElements differ in short: 'Used when reporting vital signs panel components' 'Each functional status observation in the collection.'
WarningObservation.hasMemberElements differ in definition: 'Used when reporting vital signs panel components.' '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.'
ErrorObservation.hasMemberElements differ in definition for mustSupport: 'false' 'true'
ErrorObservation.hasMemberType Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence], CanonicalType[http://hl7.org/fhir/StructureDefinition/vitalsigns]]) Reference([CanonicalType[http://hl7.org/fhir/us/pacio-fs/StructureDefinition/pacio-fs]])
WarningObservation.derivedFromElements differ in short: 'Related measurements the observation is made from' 'Should point back to the SDC QuestionnaireResponse that this resource is derived from.'
ErrorObservation.derivedFromElements differ in definition for mustSupport: 'false' 'true'
ErrorObservation.derivedFromType Mismatch: 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/MolecularSequence], CanonicalType[http://hl7.org/fhir/StructureDefinition/vitalsigns]]) Reference([CanonicalType[http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaireresponse]])
WarningObservation.componentElements differ in short: 'Component observations' 'Currently not used in FunctionalStatusCollection.'
WarningObservation.componentElements differ in definition: 'Used when reporting component observation such as systolic and diastolic blood pressure.' '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.'
ErrorObservation.componentElements differ in definition for mustSupport: 'true' 'false'
ErrorObservation.component.codeElements differ in definition for mustSupport: 'true' 'false'
WarningObservation.component.codeElements differ in binding.description: 'The vital sign codes from the base FHIR and US Core Vital Signs.' 'Codes identifying names of simple observations.'
WarningObservation.component.value[x]Elements differ in short: 'Vital Sign Component Value' 'Actual component result'
WarningObservation.component.value[x]Elements differ in definition: 'Vital Signs value are typically recorded using the Quantity data type. For supporting observations such as cuff size could use other datatypes such as CodeableConcept.' 'The information determined as a result of making the observation, if the information has a simple value.'
WarningObservation.component.value[x]Elements differ in requirements: '9. SHALL contain exactly one [1..1] value with @xsi:type='PQ' (CONF:7305).' 'An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations.'
ErrorObservation.component.value[x]Elements differ in definition for mustSupport: 'true' 'false'
ErrorObservation.component.dataAbsentReasonElements differ in definition for mustSupport: 'true' 'false'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-vital-signshttp://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'
    .date2020-11-172021-11-03T18:56:23+00:00
    • Values Differ
    .descriptionDefines constraints on Observation to represent Body Mass Index (BMI) observations with a standard LOINC code and UCUM units of measure. This profile is derived from the US Core Vital Signs Profile.A point in time collection of functional status observations for a patient. This profile is used for exchanging a set of observation data collected through the use of a structured resource (e.g. assessment tool, instrument, or screen).
    • Values Differ
    .experimentalfalse
    • Removed the item 'false'
    .fhirVersion4.0.1
      .jurisdiction
        ..jurisdiction[0]urn:iso:std:iso:3166#US
          .kindresource
            .nameUSCoreBMIProfileProfileFunctionalStatusCollection
            • Values Differ
            .publisherHL7 International - US Realm Steering CommitteeHL7 Patient Care Work Group
            • Values Differ
            .purpose
              .statusactive
                .titleUS Core BMI ProfilePACIO Functional Status Collection
                • Values Differ
                .typeObservation
                  .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-bmihttp://hl7.org/fhir/us/pacio-fs/StructureDefinition/pacio-fsc
                  • Values Differ
                  .version4.0.01.0.0
                  • Values Differ

                  Structure

                  NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.L TypeL Description & ConstraintsCommentsdoco
                  .. Observation II
                  • Elements differ in short: "US Core Body Mass Index (BMI) Profile" "Measurements and simple assertions"
                  • Elements differ in definition: "Defines constraints on Observation to represent Body Mass Index (BMI) observations with a standard LOINC code and UCUM units of measure. This profile is derived from the US Core Vital Signs Profile." "Measurements and simple assertions made about a patient, device or other subject."
                  ... id ΣΣ
                    ... meta ΣΣ
                      ... implicitRules ?!Σ?!Σ
                        ... language
                          ... text
                            ... contained
                              ... extension ExtensionExtension
                              • Elements differ in short: "Additional content defined by implementations" "Extension"
                              • Elements differ in definition: "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." "An Extension"
                              ... modifierExtension ?!?!
                                ... identifier ΣΣ
                                  ... basedOn ΣΣ
                                  • Elements differ in short: "Fulfills plan, proposal or order" "Currently not used in FunctionalStatusCollection."
                                  ... partOf ΣΣ
                                  • Elements differ in short: "Part of referenced event" "Currently not used in FunctionalStatusCollection."
                                  ... status ?!SΣ?!Σ
                                  • Elements differ in short: "registered | preliminary | final | amended +" "Should have the value 'final' when all the observatons are complete and there are no further actions needed. Otherwise, another value from the value set may appropriately be used."
                                  • Elements differ in definition for mustSupport: "true" "false"
                                  ... Slices for category S
                                  • Elements differ in short: "Classification of type of observation" "A second category code may be used along with the code “functioning”. For example, for assessment tool/survey instrument observations use “survey” as a second code."
                                  • Elements differ in definition for mustSupport: "true" "false"
                                  ... code SΣΣ
                                  • Elements differ in short: "Coded Responses from C-CDA Vital Sign Results" "For a Post-Acute Care structured assessment resource such as an instrument or screen, use a LOINC code to identify the instrument/screen name or panel/section title to indicate the kind of assessment."
                                  • Elements differ in definition: "Coded Responses from C-CDA Vital Sign Results." "Describes what was observed. Sometimes this is called the observation "name"."
                                  • Elements differ in requirements: "5. SHALL contain exactly one [1..1] code, where the @code SHOULD be selected from ValueSet HITSP Vital Sign Result Type 2.16.840.1.113883.3.88.12.80.62 DYNAMIC (CONF:7301)." "Knowing what kind of observation is being made is essential to understanding the observation."
                                  • Elements differ in definition for mustSupport: "true" "false"
                                  ... subject SΣΣ
                                  • Elements differ in short: "Who and/or what the observation is about" "Should only reference a Patient resource."
                                  • Elements differ in definition for mustSupport: "true" "false"
                                  ... focus ΣΣ
                                  • Elements differ in short: "What the observation is about, when it is not about the subject of record" "Currently not used in FunctionalStatusCollection."
                                  ... encounter ΣΣ
                                    ... effective[x] SΣIΣ
                                    • Elements differ in short: "Often just a dateTime for Vital Signs" "Clinical relevant time for an assessment such as functional assessments performed with structured evaluation tools is the time the evaluation occurs, i.e., when the clinician obtains the answers entered in the tool. However, the only timing available may be when then tool is completed by the clinician. That timing is generally documented as a point in time (dateTime)."
                                    • Elements differ in definition: "Often just a dateTime for Vital Signs." "Clinical relevant time for an assessment such as functional assessments performed with structured evaluation tools is the time the evaluation occurs, i.e., when the clinician obtains the answers entered in the tool. However, the only timing available may be when then tool is completed by the clinician. That timing is generally documented as a point in time (dateTime)."
                                    • Elements differ in comments: "At least a date should be present unless this observation is a historical report. For recording imprecise or "fuzzy" times (For example, a blood glucose measurement taken "after breakfast") use the [Timing] datatype which allow the measurement to be tied to regular life events." "The use of effective[x] and dateTime versus Period is subject to implementer workflow and needs. In most situations, an observation is considered as a point in time, even if the assessment occurred over a period of time. Period is included in this implementation guide to provide additional flexibility for specific use cases. However, it is expected most observations will be recorded using DateTime. Furthermore, any retrieval of information should return the relevant if DateTime is requested, even if the original observation was recorded as a period. Some implementers may choose to use additional functions in there retrieves to 'normalize' intervals, as is done in Clinical Quality Language (CQL)."
                                    • Elements differ in definition for mustSupport: "true" "false"
                                    ... issued ΣΣ
                                    • Elements differ in short: "Date/Time this version was made available" "Currently not used in FunctionalStatusCollection."
                                    ... performer ΣΣ
                                    • Elements differ in short: "Who is responsible for the observation" "The person who performed the assessment. The preferred way to specify the performer is to use the PractitionerRole resource to provide both the practitioner and organization."
                                    ... Slices for value[x] SΣIΣI
                                    • Elements differ in short: "Vital Signs Value" "If used, should use the CodeableConcept datatype whenever possible to provide a suitable code to define the concept for the observation data. When capturing a collection of related observations, typically this field is not used. If the outcome of an assessment includes one or more summary scores, leave this field unused and use the 'hasMember' field to point to one or more Observation resources with each of which has a score provided in the 'value' field."
                                    • Elements differ in definition: "Vital Signs value are typically recorded using the Quantity data type." "The information determined as a result of making the observation, if the information has a simple value."
                                    • Elements differ in requirements: "9. SHALL contain exactly one [1..1] value with @xsi:type="PQ" (CONF:7305)." "An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations."
                                    • Elements differ in definition for mustSupport: "true" "false"
                                    ... dataAbsentReason SII
                                    • Elements differ in short: "Why the result is missing" "Currently not used in FunctionalStatusCollection."
                                    • Elements differ in definition for mustSupport: "true" "false"
                                    ... interpretation
                                    • Elements differ in short: "High, low, normal, etc." "Currently not used in FunctionalStatusCollection."
                                    ... note
                                      ... bodySite
                                      • Elements differ in short: "Observed body part" "Currently not used in FunctionalStatusCollection."
                                      ... method
                                      • Elements differ in short: "How it was done" "Currently not used in FunctionalStatusCollection."
                                      ... specimen
                                      • Elements differ in short: "Specimen used for this observation" "Currently not used in FunctionalStatusCollection."
                                      ... device
                                      • Elements differ in short: "(Measurement) Device" "Currently not used in FunctionalStatusCollection."
                                      ... referenceRange II
                                      • Elements differ in short: "Provides guide for interpretation" "Currently not used in FunctionalStatusCollection."
                                      .... id
                                        .... extension ExtensionExtension
                                          .... modifierExtension ?!Σ?!Σ
                                            .... low II
                                              .... high II
                                                .... type
                                                  .... appliesTo
                                                    .... age
                                                      .... text
                                                        ... hasMember ΣSΣ
                                                        • Elements differ in short: "Used when reporting vital signs panel components" "Each functional status observation in the collection."
                                                        • Elements differ in definition: "Used when reporting vital signs panel components." "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."
                                                        • Elements differ in definition for mustSupport: "false" "true"
                                                        • Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence], CanonicalType[http://hl7.org/fhir/StructureDefinition/vitalsigns]]) Reference([CanonicalType[http://hl7.org/fhir/us/pacio-fs/StructureDefinition/pacio-fs]])
                                                        ... derivedFrom ΣSΣ
                                                        • Elements differ in short: "Related measurements the observation is made from" "Should point back to the SDC QuestionnaireResponse that this resource is derived from."
                                                        • Elements differ in definition for mustSupport: "false" "true"
                                                        • Type Mismatch: 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/MolecularSequence], CanonicalType[http://hl7.org/fhir/StructureDefinition/vitalsigns]]) Reference([CanonicalType[http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaireresponse]])
                                                        ... component SΣIΣ
                                                        • Elements differ in short: "Component observations" "Currently not used in FunctionalStatusCollection."
                                                        • Elements differ in definition: "Used when reporting component observation such as systolic and diastolic blood pressure." "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."
                                                        • Elements differ in definition for mustSupport: "true" "false"
                                                        .... id
                                                          .... extension ExtensionExtension
                                                            .... modifierExtension ?!Σ?!Σ
                                                              .... code SΣΣ
                                                              • Elements differ in definition for mustSupport: "true" "false"
                                                              • Elements differ in binding.description: "The vital sign codes from the base FHIR and US Core Vital Signs." "Codes identifying names of simple observations."
                                                              .... value[x] SΣIΣ
                                                              • Elements differ in short: "Vital Sign Component Value" "Actual component result"
                                                              • Elements differ in definition: "Vital Signs value are typically recorded using the Quantity data type. For supporting observations such as cuff size could use other datatypes such as CodeableConcept." "The information determined as a result of making the observation, if the information has a simple value."
                                                              • Elements differ in requirements: "9. SHALL contain exactly one [1..1] value with @xsi:type="PQ" (CONF:7305)." "An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations."
                                                              • Elements differ in definition for mustSupport: "true" "false"
                                                              .... dataAbsentReason SII
                                                              • Elements differ in definition for mustSupport: "true" "false"
                                                              .... interpretation
                                                                .... referenceRange

                                                                  doco Documentation for this format