STU 3 Candidate

This page is part of the FHIR Specification (v1.4.0: STU 3 Ballot 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

U.S. Data Access Framework (DAF) Vital Signs Profile vs QICore-Observation

Messages

A series of messages from the comparison algorithm. Errors indicate that solutions cannot be interoperable across both implementation guides (or that there are structural flaws in the definition of at least one).

PathMessage
Errors Detected
(None)
Warnings about the comparison
Observation.referenceRange.lowStructureDefinition U.S. Data Access Framework (DAF) Vital Signs Profile has a constraint that is not found in QICore-Observation and it is uncertain whether they are compatible (not(exists(f:code)) or exists(f:system))
Observation.referenceRange.lowStructureDefinition U.S. Data Access Framework (DAF) Vital Signs Profile has a constraint that is not found in QICore-Observation and it is uncertain whether they are compatible (not(exists(f:comparator)))
Observation.referenceRange.highStructureDefinition U.S. Data Access Framework (DAF) Vital Signs Profile has a constraint that is not found in QICore-Observation and it is uncertain whether they are compatible (not(exists(f:code)) or exists(f:system))
Observation.referenceRange.highStructureDefinition U.S. Data Access Framework (DAF) Vital Signs Profile has a constraint that is not found in QICore-Observation and it is uncertain whether they are compatible (not(exists(f:comparator)))
Notes about differences (e.g. definitions)
Observation.extensionElements differ in definition for short:
"Additional Content defined by implementations"
"Extension"
Observation.extensionElements differ in definition for definition:
"May be used to represent additional information that is not part of the basic definition of the resource. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension."
"An Extension"
Observation.codeElements differ in definition for short:
"Coded Responses from C-CDA Vital Sign Results"
"Type of observation (code / type)"
Observation.codeElements differ in definition for definition:
"Coded Responses from C-CDA Vital Sign Results."
"Describes what was observed. Sometimes this is called the observation "name"."
Observation.codeElements differ in definition for 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."
Observation.codeElements differ in definition for binding.description:
"This identifies the vital sign result type."
"LOINC codes"
Observation.effective[x]Elements differ in definition for short:
"Often just a dateTime for Vital Signs"
"Clinically relevant time/time-period for observation"
Observation.effective[x]Elements differ in definition for definition:
"Often just a dateTime for Vital Signs."
"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."
Observation.value[x]Elements differ in definition for short:
"Vital Sign Value recorded with UCUM"
"Actual result"
Observation.value[x]Elements differ in definition for definition:
"Vital Sign Value recorded with UCUM."
"The information determined as a result of making the observation, if the information has a simple value."
Observation.value[x]Elements differ in definition for requirements:
"9. SHALL contain exactly one [1..1] value with @xsi:type="PQ" (CONF:7305)."
"An observation exists to have a value, though it may not if it is in error, or it represents a group of observations."
Observation.value[x]Elements differ in definition for binding.description:
"Common UCUM units for recording Vital Signs"
"SNOMED CT for coded results"
Observation.value[x].codeElements differ in definition for short:
"Coded responses from the common UCUM units for vital signs value set."
"Coded form of the unit"
Observation.value[x].codeElements differ in definition for definition:
"Coded responses from the common UCUM units for vital signs value set."
"A computer processable form of the unit in some unit representation system."
Observation.relatedElements differ in definition for short:
"Used when reporting systolic and diastolic blood pressure."
"Resource related to this observation"
Observation.relatedElements differ in definition for definition:
"Used when reporting systolic and diastolic blood pressure."
"A reference to another resource (usually another Observation but could also be a QuestionnaireAnswer) whose relationship is defined by the relationship type code."

Intersection

The intersection of the 2 constraint statements. This is what resource authors (either client or server) would need to conform to produce content valid against both implementation guides.

NameFlagsCard.TypeDescription & Constraintsdoco
.. Observation I0..*ObservationMeasurements and simple assertions
obs-6: dataAbsentReason SHALL only be present if Observation.value[x] is not present
obs-7: Component code SHALL not be same as observation code
... meta ∑0..1MetaMetadata about the resource
... implicitRules ?! ∑0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: IETF BCP-47 (required)
... text 0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... observation-bodyPosition 0..1CodeableConceptleft: Additional Content defined by implementations; right: Extension
URL: http://hl7.org/fhir/StructureDefinition/observation-bodyPosition
Binding: Body Position (preferred)
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier S1..*IdentifierUnique Id for this particular observation
... status ?! S∑1..1coderegistered | preliminary | final | amended +
Binding: ObservationStatus (required)
... category 0..1CodeableConceptClassification of type of observation
Binding: Observation Category Codes (example)
... code S ∑1..1CodeableConceptleft: Coded Responses from C-CDA Vital Sign Results; right: Type of observation (code / type)
Binding: C-CDA Vital Sign Result (extensible)
... subject S ∑1..1Reference(DAF-Patient)Who and/or what this is about
... encounter S0..1Reference(DAF-Encounter)Healthcare event during which this observation is made
... effective[x] S ∑1..1dateTime, Periodleft: Often just a dateTime for Vital Signs; right: Clinically relevant time/time-period for observation
... issued S ∑0..1instantDate/Time this was made available
... performer S ∑0..1Reference(DAF-Pract | DAF-Patient | DAF-RelatedPerson | DAF-Organization)Who is responsible for the observation
... valueQuantity S ∑0..1Quantityleft: Vital Sign Value recorded with UCUM; right: Actual result
Binding: Common UCUM units (required)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... value S ∑0..1decimalNumerical value (with implicit precision)
.... comparator ?! ∑0..1code< | <= | >= | > - how to understand the value
Binding: QuantityComparator (required)
.... unit S ∑0..1stringUnit representation
.... system S ∑0..1uriSystem that defines coded unit form
.... code S ∑0..1codeleft: Coded responses from the common UCUM units for vital signs value set.; right: Coded form of the unit
... dataAbsentReason S0..1CodeableConceptWhy the result is missing
Binding: Observation Value Absent Reason (extensible)
... interpretation S0..1CodeableConceptHigh, low, normal, etc.
Binding: Observation Interpretation Codes (extensible)
... comment 0..1stringComments about result
... bodySite S0..1CodeableConceptObserved body part
Binding: SNOMED CT Body Structures (example)
... method S0..1CodeableConceptHow it was done
Binding: Observation Methods (example)
... specimen S0..1Reference(QICore-Specimen)Specimen used for this observation
... device 0..1Reference(QICore-Device | DeviceMetric)(Measurement) Device
... referenceRange S I0..1BackboneElementProvides guide for interpretation
obs-3: Must have at least a low or a high or text
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?! ∑0..*ExtensionExtensions that cannot be ignored
.... low S I0..1SimpleQuantityLow Range, if relevant
Binding: Common UCUM units (required)
qty-3: If a code for the unit is present, the system SHALL also be present
sqty-1: The comparator is not used on a SimpleQuantity
..... extension 0..*ExtensionAdditional Content defined by implementations
..... value S ∑0..1decimalNumerical value (with implicit precision)
..... unit S ∑0..1stringUnit representation
..... system S ∑0..1uriSystem that defines coded unit form
..... code S ∑0..1codeCoded form of the unit
.... high S I0..1SimpleQuantityHigh Range, if relevant
Binding: Common UCUM units (required)
qty-3: If a code for the unit is present, the system SHALL also be present
sqty-1: The comparator is not used on a SimpleQuantity
..... extension 0..*ExtensionAdditional Content defined by implementations
..... value S ∑0..1decimalNumerical value (with implicit precision)
..... unit S ∑0..1stringUnit representation
..... system S ∑0..1uriSystem that defines coded unit form
..... code S ∑0..1codeCoded form of the unit
.... meaning S0..1CodeableConceptIndicates the meaning/use of this range of this range
Binding: Observation Reference Range Meaning Codes (example)
.... age 0..1RangeApplicable age range, if relevant
.... text S0..1stringText based reference range in an observation
... related S ∑0..1BackboneElementleft: Used when reporting systolic and diastolic blood pressure.; right: Resource related to this observation
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?! ∑0..*ExtensionExtensions that cannot be ignored
.... type S1..1codehas-member | derived-from | sequel-to | replaces | qualified-by | interfered-by
Binding: ObservationRelationshipType (required)
.... target S1..1Reference(DAF-VitalSigns)Resource that is related to this one
... component ∑0..*BackboneElementComponent results
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?! ∑0..*ExtensionExtensions that cannot be ignored
.... code ∑1..1CodeableConceptType of component observation (code / type)
Binding: LOINC Codes (example)
.... value[x] ∑0..1Quantity, CodeableConcept, string, Range, Ratio, SampledData, Attachment, time, dateTime, PeriodActual component result
.... dataAbsentReason 0..1CodeableConceptWhy the component result is missing
Binding: Observation Value Absent Reason (extensible)
.... referenceRange 0..*Provides guide for interpretation of component result

doco Documentation for this format

Union

The union of the 2 constraint statements. This is what resource authors (either client or server) would need to be able to handle to accept content valid against either implementation guides.

NameFlagsCard.TypeDescription & Constraintsdoco
.. Observation I0..*ObservationMeasurements and simple assertions
obs-6: dataAbsentReason SHALL only be present if Observation.value[x] is not present
obs-7: Component code SHALL not be same as observation code
... meta ∑0..1MetaMetadata about the resource
... implicitRules ?! ∑0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: IETF BCP-47 (required)
... text 0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension 0..*Extensionleft: Additional Content defined by implementations; right: Extension
Binding: Body Position (example)
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier S0..*IdentifierUnique Id for this particular observation
... status ?! S∑1..1coderegistered | preliminary | final | amended +
Binding: ObservationStatus (required)
... category 0..1CodeableConceptClassification of type of observation
Binding: Observation Category Codes (example)
... code S ∑1..1CodeableConceptleft: Coded Responses from C-CDA Vital Sign Results; right: Type of observation (code / type)
Binding: ???? (extensible)
... subject S ∑0..1Reference(#1 | Group | QICore-Device | QICore-Location)Who and/or what this is about
... encounter S0..1Reference(#4)Healthcare event during which this observation is made
... effective[x] S ∑0..1dateTime, Periodleft: Often just a dateTime for Vital Signs; right: Clinically relevant time/time-period for observation
... issued S ∑0..1instantDate/Time this was made available
... performer S ∑0..*Reference(#3 | #1 | #5 | #2)Who is responsible for the observation
... valueQuantity S ∑0..1Quantity, CodeableConcept, string, Range, Ratio, SampledData, Attachment, time, dateTime, Periodleft: Vital Sign Value recorded with UCUM; right: Actual result
Binding: ???? (required)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... value S ∑0..1decimalNumerical value (with implicit precision)
.... comparator ?! ∑0..1code< | <= | >= | > - how to understand the value
Binding: QuantityComparator (required)
.... unit S ∑0..1stringUnit representation
.... system S ∑0..1uriSystem that defines coded unit form
.... code S ∑0..1codeleft: Coded responses from the common UCUM units for vital signs value set.; right: Coded form of the unit
... dataAbsentReason S0..1CodeableConceptWhy the result is missing
Binding: Observation Value Absent Reason (extensible)
... interpretation S0..1CodeableConceptHigh, low, normal, etc.
Binding: Observation Interpretation Codes (extensible)
... comment 0..1stringComments about result
... bodySite S0..1CodeableConceptObserved body part
Binding: SNOMED CT Body Structures (example)
... method S0..1CodeableConceptHow it was done
Binding: Observation Methods (example)
... specimen S0..1Reference(Specimen)Specimen used for this observation
... device 0..1Reference(Device | DeviceMetric)(Measurement) Device
... referenceRange S I0..*BackboneElementProvides guide for interpretation
obs-3: Must have at least a low or a high or text
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?! ∑0..*ExtensionExtensions that cannot be ignored
.... low S0..1SimpleQuantityLow Range, if relevant
Binding: Common UCUM units (example)
..... extension 0..*ExtensionAdditional Content defined by implementations
..... value S ∑0..1decimalNumerical value (with implicit precision)
..... unit S ∑0..1stringUnit representation
..... system S ∑0..1uriSystem that defines coded unit form
..... code S ∑0..1codeCoded form of the unit
.... high S0..1SimpleQuantityHigh Range, if relevant
Binding: Common UCUM units (example)
..... extension 0..*ExtensionAdditional Content defined by implementations
..... value S ∑0..1decimalNumerical value (with implicit precision)
..... unit S ∑0..1stringUnit representation
..... system S ∑0..1uriSystem that defines coded unit form
..... code S ∑0..1codeCoded form of the unit
.... meaning S0..1CodeableConceptIndicates the meaning/use of this range of this range
Binding: Observation Reference Range Meaning Codes (example)
.... age 0..1RangeApplicable age range, if relevant
.... text S0..1stringText based reference range in an observation
... related S ∑0..*BackboneElementleft: Used when reporting systolic and diastolic blood pressure.; right: Resource related to this observation
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?! ∑0..*ExtensionExtensions that cannot be ignored
.... type S0..1codehas-member | derived-from | sequel-to | replaces | qualified-by | interfered-by
Binding: ObservationRelationshipType (required)
.... target S1..1Reference(#41 | QuestionnaireResponse)Resource that is related to this one
... component ∑0..*BackboneElementComponent results
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?! ∑0..*ExtensionExtensions that cannot be ignored
.... code ∑1..1CodeableConceptType of component observation (code / type)
Binding: LOINC Codes (example)
.... value[x] ∑0..1Quantity, CodeableConcept, string, Range, Ratio, SampledData, Attachment, time, dateTime, PeriodActual component result
.... dataAbsentReason 0..1CodeableConceptWhy the component result is missing
Binding: Observation Value Absent Reason (extensible)
.... referenceRange 0..*Provides guide for interpretation of component result

doco Documentation for this format