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

Observation vs QuestionnaireResponse

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
ObservationBase Type is not compatible (Observation/QuestionnaireResponse)
ObservationDifferent number of children at Observation (28/17)
Warnings about the comparison
ObservationStructureDefinition Observation has a constraint that is not found in QuestionnaireResponse and it is uncertain whether they are compatible (not(exists(f:dataAbsentReason)) or (not(exists(*[starts-with(local-name(.), 'value')]))))
ObservationStructureDefinition Observation has a constraint that is not found in QuestionnaireResponse and it is uncertain whether they are compatible (not(exists(f:component/f:code)) or count(for $coding in f:code/f:coding return parent::*/f:component/f:code/f:coding[f:code/@value=$coding/f:code/@value and f:system/@value=$coding/f:system/@value])=0)
Notes about differences (e.g. definitions)
ObservationElements differ in definition for short:
"Measurements and simple assertions"
"A structured set of questions and their answers"
ObservationElements differ in definition for definition:
"Measurements and simple assertions made about a patient, device or other subject."
"A structured set of questions and their answers. The questions are ordered and grouped into coherent subsets, corresponding to the structure of the grouping of the underlying questions."

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.

No intersection could be generated

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.

No union could be generated