Specimen-eu-lab

Summary

Details of the specimen(s) provided for testing.

Profile Views

Refer to Profile Descriptions for a definition of the different profile view formats.

Command 'tree' could not render: Resource was not found for 'canonical=http://hl7.eu/fhir/laboratory/StructureDefinition/Specimen-eu-lab'
Command 'tree' could not render: Resource was not found for 'canonical=http://hl7.eu/fhir/laboratory/StructureDefinition/Specimen-eu-lab'
Command 'tree' could not render: Resource was not found for 'canonical=http://hl7.eu/fhir/laboratory/StructureDefinition/Specimen-eu-lab'

Additional Guidance

meta.profile

This element SHALL be populated using the appropriate value from the table on the Profiles page.

identifier

This element SHOULD be populated with at least one unique, persistent business identifier for the specimen, assigned by the requesting organisation.

Where an ODS Code is used to identify the organisation responsible for the identifier, the Local identifier using ODS Code as the organisation guidance should be followed.

Example

"identifier": [
    {
      "system": "https://example.nhs.uk/specimen-identifier/gp-practice",
      "value": "GP123456"
    }
]

accessionIdentifier

This element SHOULD be populated with a unique, persistent business identifier for the specimen, assigned by the performing laboratory when the specimen is received.

Where the laboratory uses its own identifier namespace, the Local identifier using own system URI guidance should be followed.

Example

"accessionIdentifier": {
    "system": "https://example.nhs.uk/specimen-accessionIdentifier/laboratory",
    "value": "LAB123456"
}

status

This element SHOULD be populated with a value taken from the SpecimenStatus ValueSet.

type

The type of specimen that was collected.

Specimen type is currently represented as text in PMIP EDIFACT (NHS003). To facilitate the initial adoption of FHIR and minimise the impact on existing systems and processes, Specimen.type SHALL continue to be represented as text (using the text element of CodeableConcept), rather than using SNOMED CT coded concepts. For example:

"type": {
    "text": "Venous blood specimen"
}

For further information relating to the use of the text element of CodeableConcept, refer to the base FHIR R4 Specification.

subject

Reference to the Patient.

receivedTime

The date and time the specimen was received by the laboratory.

collection.collected[x]

The clinically relevant date and time, or time-period, when the specimen was collected from the patient.

The presence of [x] in an element name is used to indicate a choice of data type. The [x] part of the element name is replaced with an appropriate data type, in title-case format e.g. effectiveDateTime.

collection.fastingStatus[x]

Indicates whether the patient was fasting at the time the specimen was collected, for example:

"collection": {
    "collectedDateTime": "2022-02-09T10:01:23+00:00",
    "fastingStatusCodeableConcept": {
        "coding": [
            {
                "system": "http://terminology.hl7.org/CodeSystem/v2-0916",
                "code": "F",
                "display": "Patient was fasting prior to the procedure."
            }
        ]
    }
}

request

This element SHOULD be populated only when the test request was made prior to specimen collection

It is also possible to link a ServiceRequest to a Specimen using the ServiceRequest.specimen element. This method SHOULD be used when a test is requested and the specimen has already been collected.

For further information refer to:

note

Comments relating to the specimen.