Pathology and Laboratory Medicine Reporting test result stored event
This event notifies subscribers when a Pathology and Laboratory Medicine Reporting test report is stored within Patient Data Manager (PDM) using Multicast Notification Service (MNS).
It is intended for systems that need to keep local patient records aligned by reacting to updates as they occur.
This event is in development
The pathology-laboratory-reporting-test-result-stored-1 event will be in production in 2027.
Overview
This event notifies subscribers when a Pathology and Laboratory Medicine Reporting test report is stored within Patient Data Manager (PDM) using Multicast Notification Service (MNS).
It is intended for systems that need to keep local patient records aligned by reacting to updates as they occur.
- Publisher: Pathology and Laboratory Medicine Reporting
- Event name: pathology-laboratory-reporting-test-result-stored-1
- Delivery mechanism: Multicast Notification Service (MNS)
- Payload type: Notification (event only)
- Data retrieval: Patient Data Manager (PDM)
- Specification: Pathology and Laboratory Medicine Reporting - FHIR API
For general guidance on using MNS, refer to the MNS service page.
Event status
This event is currently in development.
When should I use this event?
Use this event if your GP system:
- needs to make pathology test reports available to clinical users
- stores local copies of pathology test reports
- can retrieve pathology test reports from PDM when notified
- can process pathology test reports in accordance with the DAPB4101: Pathology and Laboratory Medicine Reporting Information Standard
- can acknowledge the processing of a test report by posting a FHIR message bundle to PDM
Example use case
- to notify GP practices that a pathology test report has been produced in response to a request submitted by their organisation
When should I not use this event?
This event may not be suitable if:
-
You have not onboarded to Patient Data Manager to both retrieve and post resources
-
Your system does not support the processing of pathology test reports aligned to the DAPB4101: Pathology and Laboratory Medicine Reporting Information Standard
Event structure
This event is available in FHIR format. FHIR events can be published by anybody.
| CloudEvents | FHIR | Type | Mandatory | Cardinality | Description |
|---|---|---|---|---|---|
| specversion | n/a | String | M | 1..1 | Indicates this is a version1 CloudEvent. Always "1.0" |
| id | id | GUID | M | 1..1 | GUID - for this event |
| source | source | URI | M | 1..1 | The publisher of the event. Not the original service which triggered the change |
| type | event-type | String | M | 1..1 | The name of the event will always be pathology-laboratory-reporting-test-result-stored-1 |
| time | timestamp | Timestamp | M | 1..1 | NHS number of the patient |
| versionid | version-id | String | M | 1..1 | This is the version of this event that is being received |
Event example
{
"resourceType": "Bundle",
"id": "56e9d7db-d70a-48bf-95f8-e779a741382a",
"type": "history",
"timestamp": "2020-06-01T13:00:00Z",
"entry": [
{
"fullUrl": "urn:uuid:56e9d7db-d70a-48bf-95f8-e779a741382a",
"resource": {
"resourceType": "Parameters",
"meta": {
"profile": [
"http://hl7.org/fhir/uv/subscriptions-backport/StructureDefinition/backport-subscription-status-r4"
]
},
"id": "56e9d7db-d70a-48bf-95f8-e779a741382a",
"parameter": [
{
"name": "subscription",
"valueReference": {
"reference": "https://api.service.nhs.uk/multicast-notification-service/subscriptions"
}
},
{
"name": "status",
"valueCode": "active"
},
{
"name": "type",
"valueCode": "event-notification"
},
{
"name": "notification-event",
"part": [
{
"name": "event-number",
"valueString": "1"
},
{
"name": "timestamp",
"valueInstant": "2020-06-01T13:00:00Z"
},
{
"name": "focus",
"valueReference": {
"reference": "https://api.service.nhs.uk/patient-data-manager/FHIR/R4/Bundle/<bundle-id>"
}
}
]
},
{
"name": "additional-context",
"part": [
{
"name": "event-type",
"valueString": "pathology-laboratory-reporting-test-result-stored-1"
},
{
"name": "source",
"valueUri": "uk.nhs.pathology-laboratory-reporting"
},
{
"name": "subject",
"valueReference": {
"identifier": {
"value": "9912003888"
}
}
}
]
}
]
},
"request": {
"method": "GET",
"url": "https://api.service.nhs.uk/multicast-notification-service/subscriptions"
},
"response": {
"status": "200"
}
}
]
}
Subscription filters
You can filter the events you want to receive using the criteria field in the subscription payload. You should only be subscribing to events relevant to your general practice organisation(s) and must not create filters wider than required.
This event can be filtered on:
| Filter name | Filter subscription type | Description |
|---|---|---|
| requestingOrganisationODS | String | Identifies the organisation requesting the pathology report |
| requestingOrganisationODS_manufsacturer_org | String | Identfies the GP IT supplier requesting the pathology report |
Onboarding
To subscribe to this event:
-
Complete onboarding to Patient Data Manager as both a data consumer and data publisher
-
Complete onboarding for MNS as a subscriber
-
Use the Subscription API to create a subscription
-
Configure an endpoint to receive event notifications
Refer to Subscribe to Multicast Notification Service for further guidance.
Versioning
This is the only version of the pathology-laboratory-reporting-test-result-stored-1 event
Testing
This events is available to test in the Path To Live (PTL) environments.
To test receiving an event, a pathology test report needs to be posted to the Pathology and Laboratory Medicine – FHIR API (Pathology API). You can do this yourself if you have onboarded as a data publisher to the Pathology API in PTL. Alternatively, contact the Pathology API team for support.
Last edited: 24 June 2026 10:14 am