• Content
• Detailed Descriptions
• Examples
• Example operations
• XML
• JSON

StructureDefinition: ehealth-observation

Introduction

An Observation contains the result of a measurement performed by the Patient. It is based on a ProcedureRequest that contains information about what to measure and when to measure.

In addition to the result and context, the Observation also contains information about the device used to perform the measurement and reference ranges copied from the ProcedureRequest. Reference ranges can change over time, so the copy ensures that the reference range at the time of measurement is preserved.

The eHealth Infrastructure will assist in calculating qualities of the measurement. The observation will be annotated with these qualities.

Scope and Usage

In the eHealth Infrastructure the Observation resource is used in conjunction with the following resources.

• Media
  • Some Observations may be accompanied by media. E.g. images.
• QuestionnaireResponse
  • Some activities may involve answering a Questionnaire. The answer is captured in a QuestionnaireResponse. Questionnaires can be used for standalone information about the health of the patient, or they can be used to provide context information for Observations.
• Communication
  • Communication resources can be used to annotate Observations. See the profile ehealth-communication for further details.
• Provenance
  • In certain circumstances data from Observations and QuestionnaireResponses can be reused. When this happens, a Provenance resource will identify the source of the original data.
  • Provenance is also used to link correlated resources submitted together.

Submitting Observation bundles

Observations can be submitted using the submit-measurement operation. It is possible to submit a bundle of related resources containing:

• Observations
• Media
• QuestionnaireResponses
• Provenances

The submit-measurement operation is intended for uploading single measurements, not bulk uploads. Uploading large batches of resources is considered misuse.

The entire bundle is validated and then saved in a single transaction.

Observations are generally immutable once the bundle is saved. Further information about the observation can be added in separate resources like Provenance and Communication.

Marking Observations as “reused”

When a submitted Observation is actually reuse of a previous measurement, this must be marked by the submitter by added a Provenance resource with certain pre-defined properties.

• Provenance
  • .target must reference all reused resources in the submitted bundle; e.g. the Observation, QuestionnaireResponse or Media containing a copy of the reused values.
  • .activity must have value “Quotation” (“wasQuotedFrom”) from FHIR ValueSet https://www.hl7.org/fhir/stu3/codesystem-w3c-provenance-activity-type.html#w3c-provenance-activity-type-Quotation
  • .policy must have value “http://ehealth.sundhed.dk/policy/ehealth/reuse-by-patient”
  • .agent.whoReference must reference the Patient who decided to reuse
  • .entity.role = “quotation”
  • .entity.what = must be reference to Observation, QuestionnaireResponse or Media being reused.

The Provenance resource needs not be supplied for resources which are not being used. However, for non-reused resources, a Provenance resource with .activity = “Primary-Source” can be used to indicate a newly obtained (not reused) Observation, QuestionnaireResponse or Media.

Marking Resources submitted in same bundle

When an Observation-bundle is submitted the eHealth Infrastructure will automatically create a Provenance resource, which identifies the resources which were submitted in the same bundle.

The search-measurements operation can return the resources submitted as part of the same bundle.

Searching for Observations

It is possible to search for Observations based on:

• context
• subject
• code
• period
• deviceMeasuringQuality
• situationQuality
• operationQuality

At least one of “subject” and “context” must be provided. “period” searches on range of “effective”.

See Searching for more information about searching in REST, messaging, and services.

Formal Views of Profile Content

The official URL for this profile is:

http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-observation

This profile builds on Observation.

This profile was published on Fri Jul 01 12:30:20 UTC 2022 as a draft by ehealth.sundhed.dk.

Description of Profiles, Differentials, Snapshots, and how the XML and JSON presentations work.

 

Terminology Bindings

Path	Conformance	ValueSet
Observation.language	extensible	Common Languages Max Binding: All Languages
Observation.status	required	ObservationStatus
Observation.category	preferred	Observation Category Codes
Observation.code	required	ObservationCodes
Observation.dataAbsentReason	extensible	Observation Value Absent Reason
Observation.interpretation	extensible	Observation Interpretation Codes
Observation.bodySite	example	SNOMED CT Body Structures
Observation.method	example	Observation Methods
Observation.referenceRange.type	extensible	ReferenceRangeType
Observation.referenceRange.appliesTo	example	Observation Reference Range Applies To Codes
Observation.related.type	required	ObservationRelationshipType
Observation.component.code	required	ObservationCodes
Observation.component.dataAbsentReason	extensible	Observation Value Absent Reason
Observation.component.interpretation	extensible	Observation Interpretation Codes

Constraints

Id	Path	Details	Requirements
dom-2	Observation	If the resource is contained in another resource, it SHALL NOT contain nested Resources : contained.contained.empty()
dom-1	Observation	If the resource is contained in another resource, it SHALL NOT contain any narrative : contained.text.empty()
dom-4	Observation	If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated : contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-3	Observation	If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource : contained.where(('#'+id in %resource.descendants().reference).not()).empty()
obs-7	Observation	If code is the same as a component code then the value element associated with the code SHALL NOT be present : value.empty() or component.code.where( (coding.code = %resource.code.coding.code) and (coding.system = %resource.code.coding.system)).empty()
obs-6	Observation	dataAbsentReason SHALL only be present if Observation.value[x] is not present : dataAbsentReason.empty() or value.empty()
ele-1	Observation.extension:quality	All FHIR elements must have a @value or children : hasValue() | (children().count() > id.count())
ext-1	Observation.extension:quality	Must have either extensions or value[x], not both : extension.exists() != value.exists()
ele-1	Observation.referenceRange	All FHIR elements must have a @value or children : hasValue() | (children().count() > id.count())
obs-3	Observation.referenceRange	Must have at least a low or a high or text : low.exists() or high.exists() or text.exists()
ele-1	Observation.related	All FHIR elements must have a @value or children : hasValue() | (children().count() > id.count())
ele-1	Observation.component	All FHIR elements must have a @value or children : hasValue() | (children().count() > id.count())

.