Schema: Observation

Introduction

The headings below list the elements of the Observation resource and describe how to populate and consume them.

Important: Any element not specifically listed below wi be populated or consumed.

Tip: You’ll find it helpful to read it in conjunction with the underlying observation profile definition.

Filing comments - Observation Resource Elements

id

The logical identifier of the observation resource.

meta.profile

The observation profile URL.

Fixed value https://fhir.nhs.uk/STU3/StructureDefinition/CareConnect-GPC-Observation-1

identifier

This will be populated with a globally unique and persistent identifier (that is, it doesn’t change between requests and therefore stored with the source data).

status

For filing comments this is a set value of ‘unknown’.

code

Fixed value of 37331000000100 for Comment note.

subject

A reference to the patient who the observation is about.

context

A reference to the Encounter profile representing the consultation the test report is filed against.

effective[x]

The dateTime when the ‘Test report’, ‘Test group’ or ‘Test result’ was filed into the patient record.

issued

The date time that the time/comment was recorded in the GP system.

performer

Reference to the resource for the organisation and/or practitioner that filed the ‘Test report’, ‘Test group’ or ‘Test result’ was filed into the patient record.

value[x]

Where a ‘Test group’ or ‘Test result’ has been filed the value should match the code from the ‘Test group header’ or ‘Test result’ resource respectively.

comment

Notes added by the GP practice clinician about the ‘Test report’, ‘Test group’ or ‘Test result’ that has been filed into the patient record.

related

Reference to the test result or test group header that the filing comments resource relates to. Where the filing comments relate to the test report, the reference is made from the ‘Test report’ to the filing comment only.

This will be qualified using the related.type ‘derived-from’.