ServiceRequest-eu-lab

Summary

The test request that a test report is based on.

The associated test report is represented using DiagnosticReport and is linked to ServiceRequest using DiagnosticReport.basedOn. Refer to the profile description for DiagnosticReport-eu-lab for further information.

If multiple tests or test groups are requested as part of the same “event” (generally by the same practitioner at the same time for the same subject), an instance of ServiceRequest is required for each requested test or test group.

Resource Link

• R4 Resource (Base): ServiceRequest

Profile Views

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

Additional Guidance

meta.profile

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

identifier

The ServiceRequest.identifier represents the identifier assigned to the request by the requesting organisation, such as the GP practice.

The identifier should contain:

• Identifier.system — identifies the namespace in which the identifier is unique.
• Identifier.value — contains the identifier assigned to the request.

Where the requesting organisation assigns the identifier, the identifier should be qualified according to the relevant local identifier guidance.

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

Example

{
  "identifier": [
    {
      "system": "https://example.nhs.uk/service-request-identifier/gp-practice",
      "value": "REQ123456"
    }
  ]
}

Identifier unavailable

The ServiceRequest.identifier is mandatory in this profile. However, the identifier may not be available where it has not been provided by the source or LIM system.

This element SHOULD be populated with one or more unique, persistent business identifiers for the test request, assigned by the requesting organisation and/or performing organisation.

If the relevant data is not available, the standard FHIR data-absent-reason extension SHALL be used. The extension SHALL be populated with a reason code of unknown, as illustrated below:

"identifier": {
    "extension": [
        {
            "url": "http://hl7.org/fhir/StructureDefinition/data-absent-reason",
            "valueCode": "unknown"
        }
    ],
},

status

This element SHOULD be populated with a value of active, taken from the RequestStatus ValueSet.

Additional values from this ValueSet MAY need to be supported in the future.

intent

This element SHOULD be populated with a value of order, taken from the RequestIntent ValueSet.

Additional values from this ValueSet MAY need to be supported in the future.

category

This element SHOULD be populated with the following value, taken from the ServiceRequestCategoryCodes ValueSet:

"category": {
    "coding": [
        {
            "system": "http://snomed.info/sct",
            "code": "108252007",
            "display": "Laboratory procedure"
        }
    ]
}

subject

Reference to the Patient.

authoredOn

The date and time of the test request.

requester

The originator of the test request.

The requesting organisation SHALL always be identified using ServiceRequest.requester, either:

• directly by referencing an Organization, or
• indirectly by referencing a PractitionerRole that is associated with the requesting organisation.

Where the requesting practitioner is known, this SHALL be represented using a PractitionerRole that references both:

• the requesting Organization, and
• the requesting Practitioner.

performer

Reference to the performing Organization.

reasonCode

The reason for the test request, in coded or textual form.

reasonReference

Reference to one or more patient conditions that are relevant to the test request, as provided by the requester.

specimen

This element SHOULD be populated only when a test is requested and the specimen has already been collected.

It is also possible to link a Specimen to a ServiceRequest using the Specimen.request element. This method SHOULD be used when the test request was made prior to specimen collection.

For further information refer to:

• the description of the Specimen-eu-lab profile in this implementation guide, and
• the notes relating to the use of the ServiceRequest resource in the base FHIR R4 Specification.

note

Any other comments relating to the test request, as provided by the requester. Clinical information relating to the test request SHOULD be conveyed using ServiceRequest.reasonCode and/or ServiceRequest.reasonReference.