Schema: Observation - Test Group Header

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 will not be populated or consumed

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

Test Group Header - 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

The status of the test group header.

In GP systems, these are most likely to be ‘final’. However, ‘preliminary’ reports are possible as, for example, some work can be sub-contracted to other labs. If the system is not able to determine the status of a test group header then it should default to the ‘unknown’ value.

code

The clinical code that represents the name of the test group - for example, Full blood count.

subject

A reference to the patient who the observation is about.

context

A reference to the Encounter profile representing the consultation the test group is associated to.

effective[x]

The date and time when the test was performed.

issued

The date and time that the result was issued by the laboratory or other report provider.

Is this is not provided for a test group header result then it should inherit the date from the DiagnosticReport.

performer

Reference to the resource for the Organization that carried out the tests. A Practitioner resource may also be referenced here but only where an organization is reference is provided.

interpretation

A human-readable clinical summary relating to a test result and/or additional notes provided by the laboratory - for example, the specimen has haemolysed or has leaked.

comment

Notes that relate to the test group header that were written by the performing organization.

For example, the sample has haemolysed or has leaked.

specimen

Reference to the specimen on which these results were based.

related

Reference(s) to the test result(s) observation(s) that make up the test group.

This will be qualified using the related.type ‘has-member’.