Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-body-weight vs http://hl7.org/fhir/us/pacio-cs/StructureDefinition/pacio-csc

Left:US Core Body Weight Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-body-weight)
Right:PACIO Cognitive Status Collection (http://hl7.org/fhir/us/pacio-cs/StructureDefinition/pacio-csc)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-body-weight' vs 'http://hl7.org/fhir/us/pacio-cs/StructureDefinition/pacio-csc'
ErrorStructureDefinition.versionValues for version differ: '7.0.0' vs '1.0.0'
InformationStructureDefinition.nameValues for name differ: 'USCoreBodyWeightProfile' vs 'CognitiveStatusCollection'
InformationStructureDefinition.titleValues for title differ: 'US Core Body Weight Profile' vs 'PACIO Cognitive Status Collection'
InformationStructureDefinition.dateValues for date differ: '2023-10-17' vs '2024-11-05T07:56:05+00:00'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 International / Cross-Group Projects' 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'
InformationStructureDefinition.shortValues for short differ: 'US Core Body Weight Profile' vs 'Measurements and simple assertions'
InformationStructureDefinition.definitionValues for definition differ: 'The FHIR Vitals Signs profile sets minimum expectations for the Observation Resource to record, search and fetch the vital signs associated with a patient.' vs 'Measurements and simple assertions made about a patient, device or other subject.'
InformationStructureDefinition.shortValues for short differ: 'Additional content defined by implementations' vs 'Extension'
InformationStructureDefinition.definitionValues for definition differ: 'May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'An Extension'
InformationStructureDefinition.requirementsValues for requirements differ: 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/extensibility.html#modifierExtension).' vs 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).'
InformationStructureDefinition.shortValues for short differ: 'Fulfills plan, proposal or order' vs 'Currently not used in CognitiveStatusCollection.'
InformationStructureDefinition.shortValues for short differ: 'Part of referenced event' vs 'Currently not used in CognitiveStatusCollection.'
InformationStructureDefinition.commentValues for comment differ: 'To link an Observation to an Encounter use `encounter`. See the [Notes](http://hl7.org/fhir/observation.html#obsgrouping) below for guidance on referencing another Observation.' vs 'To link an Observation to an Encounter use `encounter`. See the [Notes](http://hl7.org/fhir/R4/observation.html#obsgrouping) below for guidance on referencing another Observation.'
InformationStructureDefinition.shortValues for short differ: 'registered | preliminary | final | amended +' vs '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.'
WarningObservation.statusElements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.shortValues for short differ: 'Classification of type of observation' vs '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.'
WarningObservation.categoryElements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.shortValues for short differ: 'Body Weight' vs '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.'
InformationStructureDefinition.definitionValues for definition differ: 'Coded Responses from C-CDA Vital Sign Results.' vs 'Describes what was observed. Sometimes this is called the observation 'name'.'
InformationStructureDefinition.requirementsValues for requirements differ: '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).' vs 'Knowing what kind of observation is being made is essential to understanding the observation.'
WarningObservation.codeElements differ in definition for mustSupport: 'true' vs 'false'
ErrorObservation.codeUnable to resolve left value set http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113883.3.88.12.80.62 at Observation.code
InformationStructureDefinition.shortValues for short differ: 'Who and/or what the observation is about' vs 'Should only reference a Patient resource.'
WarningObservation.subjectElements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.shortValues for short differ: 'What the observation is about, when it is not about the subject of record' vs 'Currently not used in CognitiveStatusCollection.'
InformationStructureDefinition.commentValues for comment differ: 'Typically, an observation is made about the subject - a patient, or group of patients, location, or device - and the distinction between the subject and what is directly measured for an observation is specified in the observation code itself ( e.g., 'Blood Glucose') and does not need to be represented separately using this element. Use `specimen` if a reference to a specimen is required. If a code is required instead of a resource use either `bodysite` for bodysites or the standard extension [focusCode](http://hl7.org/fhir/extension-observation-focuscode.html).' vs 'Typically, an observation is made about the subject - a patient, or group of patients, location, or device - and the distinction between the subject and what is directly measured for an observation is specified in the observation code itself ( e.g., 'Blood Glucose') and does not need to be represented separately using this element. Use `specimen` if a reference to a specimen is required. If a code is required instead of a resource use either `bodysite` for bodysites or the standard extension [focusCode](http://hl7.org/fhir/R4/extension-observation-focuscode.html).'
InformationStructureDefinition.shortValues for short differ: 'Often just a dateTime for Vital Signs' vs 'Clinical relevant time for an assessment such as cognitive 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).'
InformationStructureDefinition.definitionValues for definition differ: 'Often just a dateTime for Vital Signs.' vs 'Clinical relevant time for an assessment such as cognitive 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).'
InformationStructureDefinition.commentValues for comment differ: '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/datatypes.html#timing) datatype which allow the measurement to be tied to regular life events.' vs '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).'
WarningObservation.effective[x]Elements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.shortValues for short differ: 'Date/Time this version was made available' vs 'Currently not used in CognitiveStatusCollection.'
InformationStructureDefinition.commentValues for comment differ: 'For Observations that don’t require review and verification, it may be the same as the [`lastUpdated` ](http://hl7.org/fhir/resource-definitions.html#Meta.lastUpdated) time of the resource itself. For Observations that do require review and verification for certain updates, it might not be the same as the `lastUpdated` time of the resource itself due to a non-clinically significant update that doesn’t require the new version to be reviewed and verified again.' vs 'For Observations that don’t require review and verification, it may be the same as the [`lastUpdated` ](http://hl7.org/fhir/R4/resource-definitions.html#Meta.lastUpdated) time of the resource itself. For Observations that do require review and verification for certain updates, it might not be the same as the `lastUpdated` time of the resource itself due to a non-clinically significant update that doesn’t require the new version to be reviewed and verified again.'
InformationStructureDefinition.shortValues for short differ: 'Who is responsible for the observation' vs '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.'
InformationObservation.performerElement minimum cardinalities differ: '0' vs '1'
InformationStructureDefinition.shortValues for short differ: 'Vital Signs Value' vs '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.'
InformationStructureDefinition.definitionValues for definition differ: 'Vital Signs value are typically recorded using the Quantity data type.' vs 'The information determined as a result of making the observation, if the information has a simple value.'
InformationStructureDefinition.commentValues for comment differ: '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/observation.html#notes) below.' 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.'
InformationStructureDefinition.requirementsValues for requirements differ: '9. SHALL contain exactly one [1..1] value with @xsi:type='PQ' (CONF:7305).' vs 'An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations.'
WarningObservation.value[x]Elements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.shortValues for short differ: 'Why the result is missing' vs 'Currently not used in CognitiveStatusCollection.'
WarningObservation.dataAbsentReasonElements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.shortValues for short differ: 'High, low, normal, etc.' vs 'Currently not used in CognitiveStatusCollection.'
InformationStructureDefinition.shortValues for short differ: 'Observed body part' vs 'Currently not used in CognitiveStatusCollection.'
InformationStructureDefinition.commentValues for comment differ: 'Only used if not implicit in code found in Observation.code. In many systems, this may be represented as a related observation instead of an inline component. If the use case requires BodySite to be handled as a separate resource (e.g. to identify and track separately) then use the standard extension[ bodySite](http://hl7.org/fhir/extension-bodysite.html).' vs 'Only used if not implicit in code found in Observation.code. In many systems, this may be represented as a related observation instead of an inline component. If the use case requires BodySite to be handled as a separate resource (e.g. to identify and track separately) then use the standard extension[ bodySite](http://hl7.org/fhir/R4/extension-bodysite.html).'
InformationStructureDefinition.shortValues for short differ: 'How it was done' vs 'Currently not used in CognitiveStatusCollection.'
InformationStructureDefinition.shortValues for short differ: 'Specimen used for this observation' vs 'Currently not used in CognitiveStatusCollection.'
InformationStructureDefinition.shortValues for short differ: '(Measurement) Device' vs 'Currently not used in CognitiveStatusCollection.'
InformationStructureDefinition.shortValues for short differ: 'Provides guide for interpretation' vs 'Currently not used in CognitiveStatusCollection.'
InformationStructureDefinition.requirementsValues for requirements differ: 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/extensibility.html#modifierExtension).' vs 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).'
InformationStructureDefinition.shortValues for short differ: 'Used when reporting vital signs panel components' vs 'Each cognitive status observation in the collection.'
InformationStructureDefinition.definitionValues for definition differ: 'Used when reporting vital signs panel components.' 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: '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/observation.html#obsgrouping) below. Note that a system may calculate results from [QuestionnaireResponse](http://hl7.org/fhir/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.'
WarningObservation.hasMemberElements differ in definition for mustSupport: 'false' vs '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]]) vs Reference([CanonicalType[http://hl7.org/fhir/us/pacio-cs/StructureDefinition/pacio-cs]])
InformationStructureDefinition.shortValues for short differ: 'Related measurements the observation is made from' vs 'Should point back to the SDC QuestionnaireResponse that this resource is derived from.'
InformationStructureDefinition.commentValues for comment differ: 'All the reference choices that are listed in this element can represent clinical observations and other measurements that may be the source for a derived value. The most common reference will be another Observation. For a discussion on the ways Observations can assembled in groups together, see [Notes](http://hl7.org/fhir/observation.html#obsgrouping) below.' vs 'All the reference choices that are listed in this element can represent clinical observations and other measurements that may be the source for a derived value. The most common reference will be another Observation. For a discussion on the ways Observations can assembled in groups together, see [Notes](http://hl7.org/fhir/R4/observation.html#obsgrouping) below.'
WarningObservation.derivedFromElements differ in definition for mustSupport: 'false' vs '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]]) vs Reference([CanonicalType[http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaireresponse]])
InformationStructureDefinition.shortValues for short differ: 'Component observations' vs 'Currently not used in CognitiveStatusCollection.'
InformationStructureDefinition.definitionValues for definition differ: 'Used when reporting component observation such as systolic and diastolic blood pressure.' vs '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.'
InformationStructureDefinition.commentValues for comment differ: 'For a discussion on the ways Observations can be assembled in groups together see [Notes](http://hl7.org/fhir/observation.html#notes) below.' vs 'For a discussion on the ways Observations can be assembled in groups together see [Notes](http://hl7.org/fhir/R4/observation.html#notes) below.'
WarningObservation.componentElements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.requirementsValues for requirements differ: 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/extensibility.html#modifierExtension).' vs 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).'
InformationStructureDefinition.shortValues for short differ: 'Coded vital sign result type' vs 'Type of component observation (code / type)'
WarningObservation.component.codeElements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.shortValues for short differ: 'Vital Sign Component Value' vs 'Actual component result'
InformationStructureDefinition.definitionValues for definition differ: '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.' vs 'The information determined as a result of making the observation, if the information has a simple value.'
InformationStructureDefinition.commentValues for comment differ: 'Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was derived). 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/observation.html#notes) below.' vs 'Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was derived). 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.'
InformationStructureDefinition.requirementsValues for requirements differ: '9. SHALL contain exactly one [1..1] value with @xsi:type='PQ' (CONF:7305).' vs 'An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations.'
WarningObservation.component.value[x]Elements differ in definition for mustSupport: 'true' vs 'false'
WarningObservation.component.dataAbsentReasonElements differ in definition for mustSupport: 'true' vs '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'
    .date2023-10-172024-11-05T07:56:05+00:00
    • Values Differ
    .descriptionThe US Core Body Weight Profile inherits from the US Core Vital Signs Profile. This profile sets minimum expectations for the Observation resource to record, search, and fetch body weight observations with a standard LOINC code and UCUM units of measure. It specifies which *additional* core elements, extensions, vocabularies, and value sets **SHALL** be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption.A point in time collection of cognitive 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
            .nameUSCoreBodyWeightProfileCognitiveStatusCollection
            • Values Differ
            .publisherHL7 International / Cross-Group ProjectsHL7 Patient Care Work Group
            • Values Differ
            .purpose
              .statusactive
                .titleUS Core Body Weight ProfilePACIO Cognitive Status Collection
                • Values Differ
                .typeObservation
                  .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-body-weighthttp://hl7.org/fhir/us/pacio-cs/StructureDefinition/pacio-csc
                  • Values Differ
                  .version7.0.01.0.0
                  • Values Differ

                  Structure

                  NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.R TypeR Description & ConstraintsCommentsdoco
                  .. Observation C0..*USCoreVitalSignsProfileUS Core Body Weight Profile
                  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
                  vs-2: If there is no component or hasMember element then either a value[x] or a data absent reason must be present.
                  C0..*ObservationMeasurements and simple assertions
                  obs-6: dataAbsentReason SHALL only be present if Observation.value[x] is not present
                  obs-7: If Observation.code is the same as an Observation.component.code then the value element associated with the code SHALL NOT be present
                    ... id Σ0..1idLogical id of this artifactΣ0..1idLogical id of this artifact
                      ... meta Σ0..1MetaMetadata about the resourceΣ0..1MetaMetadata about the resource
                        ... implicitRules ?!Σ0..1uriA set of rules under which this content was created?!Σ0..1uriA set of rules under which this content was created
                          ... language 0..1codeLanguage of the resource content
                          Binding: ?? (preferred): A human language.

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

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

                                          • Elements differ in definition for mustSupport: 'true' vs 'false'
                                          ... Slices for category S1..*CodeableConceptClassification of type of observation
                                          Slice: Unordered, Open by value:coding.code, value:coding.system
                                          Binding: ?? (preferred): Codes for high level observation categories.


                                          1..*CodeableConceptA 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.
                                          Slice: Unordered, Open by pattern:coding
                                          Binding: ?? (preferred): Codes for high level observation categories.


                                          • Elements differ in definition for mustSupport: 'true' vs 'false'
                                          ... code SΣ1..1CodeableConceptBody Weight
                                          Binding: ?? (extensible): Vital sign result types


                                          Required Pattern: {"coding":[{"system":"http://loinc.org","code":"29463-7"}]}
                                          Σ1..1CodeableConceptFor 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.
                                          Binding: ?? (extensible)
                                          • Elements differ in definition for mustSupport: 'true' vs 'false'
                                          • Unable to resolve left value set http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113883.3.88.12.80.62 at Observation.code
                                          ... subject SΣ1..1Reference(US Core Patient Profile)Who and/or what the observation is aboutΣ1..1Reference(US Core Patient Profile)Should only reference a Patient resource.
                                          • Elements differ in definition for mustSupport: 'true' vs 'false'
                                          ... focus Σ0..*Reference(Resource)What the observation is about, when it is not about the subject of record
                                          Σ0..*Reference(Resource)Currently not used in CognitiveStatusCollection.
                                            ... encounter Σ0..1Reference(Encounter)Healthcare event during which this observation is madeΣ0..1Reference(US Core Encounter Profile)Healthcare event during which this observation is made
                                              ... effective[x] SΣC1..1dateTime S, PeriodOften just a dateTime for Vital Signs
                                              vs-1: if Observation.effective[x] is dateTime and has a value then that value shall be precise to the day
                                              Σ1..1dateTime, PeriodClinical relevant time for an assessment such as cognitive 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 for mustSupport: 'true' vs 'false'
                                              ... issued Σ0..1instantDate/Time this version was made availableΣ0..1instantCurrently not used in CognitiveStatusCollection.
                                                ... performer Σ0..*Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson)Who is responsible for the observation
                                                Σ1..*Reference(US Core Practitioner Profile | US Core PractitionerRole Profile | US Core Organization Profile)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.
                                                • Element minimum cardinalities differ: '0' vs '1'
                                                ... Slices for value[x] SΣC0..1Quantity S, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodVital Signs Value
                                                Slice: Unordered, Open by type:$this
                                                Binding: ?? (extensible): Common UCUM units for recording Vital Signs.

                                                ΣC0..1Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodIf 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 for mustSupport: 'true' vs 'false'
                                                ... dataAbsentReason SC0..1CodeableConceptWhy the result is missing
                                                Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing.

                                                C0..1CodeableConceptCurrently not used in CognitiveStatusCollection.
                                                Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing.

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


                                                0..*CodeableConceptCurrently not used in CognitiveStatusCollection.
                                                Binding: ?? (extensible): Codes identifying interpretations of observations.


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

                                                    0..1CodeableConceptCurrently not used in CognitiveStatusCollection.
                                                    Binding: ?? (example): Codes describing anatomical locations. May include laterality.

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

                                                      0..1CodeableConceptCurrently not used in CognitiveStatusCollection.
                                                      Binding: ?? (example): Methods for simple observations.

                                                        ... specimen 0..1Reference(Specimen)Specimen used for this observation0..1Reference(Specimen)Currently not used in CognitiveStatusCollection.
                                                          ... device 0..1Reference(Device | DeviceMetric)(Measurement) Device0..1Reference(Device | DeviceMetric)Currently not used in CognitiveStatusCollection.
                                                            ... referenceRange C0..*BackboneElementProvides guide for interpretation
                                                            obs-3: Must have at least a low or a high or text
                                                            C0..*BackboneElementCurrently not used in CognitiveStatusCollection.
                                                            obs-3: Must have at least a low or a high or text
                                                              .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                .... extension 0..*ExtensionAdditional content defined by implementations
                                                                0..*ExtensionAdditional content defined by implementations
                                                                  .... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                  ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                    .... low C0..1??Low Range, if relevantC0..1??Low Range, if relevant
                                                                      .... high C0..1??High Range, if relevantC0..1??High Range, if relevant
                                                                        .... type 0..1CodeableConceptReference range qualifier
                                                                        Binding: ?? (preferred): Code for the meaning of a reference range.

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

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


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


                                                                            .... age 0..1RangeApplicable age range, if relevant0..1RangeApplicable age range, if relevant
                                                                              .... text 0..1stringText based reference range in an observation0..1stringText based reference range in an observation
                                                                                ... hasMember Σ0..*Reference(QuestionnaireResponse | MolecularSequence | Vital Signs Profile)Used when reporting vital signs panel components
                                                                                SΣ0..*Reference(PACIO Cognitive Status)Each cognitive status observation in the collection.
                                                                                • Elements differ in definition for mustSupport: 'false' vs '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]]) vs Reference([CanonicalType[http://hl7.org/fhir/us/pacio-cs/StructureDefinition/pacio-cs]])
                                                                                ... derivedFrom Σ0..*Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | MolecularSequence | Vital Signs Profile)Related measurements the observation is made from
                                                                                SΣ0..*Reference(SDC Questionnaire Response)Should point back to the SDC QuestionnaireResponse that this resource is derived from.
                                                                                • Elements differ in definition for mustSupport: 'false' vs '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]]) vs Reference([CanonicalType[http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaireresponse]])
                                                                                ... component SΣC0..*BackboneElementComponent observations
                                                                                vs-3: If there is no a value a data absent reason must be present
                                                                                Σ0..*BackboneElementCurrently not used in CognitiveStatusCollection.
                                                                                • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                                .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                                  .... extension 0..*ExtensionAdditional content defined by implementations
                                                                                  0..*ExtensionAdditional content defined by implementations
                                                                                    .... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                                    ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                                      .... code SΣ1..1CodeableConceptCoded vital sign result type
                                                                                      Binding: ?? (extensible): Vital sign result types

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

                                                                                      • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                                      .... value[x] SΣC0..1Quantity S, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodVital Sign Component Value
                                                                                      Binding: ?? (extensible): Common UCUM units for recording Vital Signs.

                                                                                      Σ0..1Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodActual component result
                                                                                      • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                                      .... dataAbsentReason SC0..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.

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


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


                                                                                        .... 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