Pathology and Laboratory Medicine Reporting test result acknowledgement

This event notifies subscribers via the Multicast Notification Service (MNS) when a Pathology and Laboratory Medicine Reporting test report acknowledgement is stored within Patient Data Manager (PDM).

Overview

It is intended to support systems to manage the transfer of clinical responsibility for Pathology and Laboratory Medicine test reports.

Publisher: Patient Data Manager on behalf of a Pathology and Laboratory Medicine test report consumer
Event name: pathology-laboratory-reporting-test-result-stored-1-ack-1
Delivery mechanism: Multicast Notification Service
Payload type: Notification (event only)
Data retrieval: Pathology and Laboratory Medicine Reporting - FHIR API

For general guidance on using MNS, refer to the MNS service page.

Status

This event is in development.

When should I use this event?

Use this event if you are a pathology and laboratory medicine test reporting system that:

sends test reports via the Pathology and Laboratory Medicine Reporting - FHIR API
needs to receive test report acknowledgements that are sent by a test report consumer
can process test report acknowledgements in accordance with the Acknowledgement Framework aligned to the DAPB4101: Pathology and Laboratory Medicine Reporting Information Standard

Example use cases:

To notify a pathology and laboratory medicine test reporting system that:

a test report has been received by a test report consumer and they have taken clinical responsibility for the report
a test report has been received by a test report consumer but there was an issue with processing the report that needs to be resolved

When should I not use this event?

This event may not be suitable if:

you have not onboarded to the Pathology and Laboratory Medicine Reporting - FHIR API
your system does not support the processing of pathology test report acknowledgements in accordance with the Acknowledgement Framework aligned to the DAPB4101: Pathology and Laboratory Medicine Reporting Information Standard

How this event works

This event follows a notification and retrieval pattern:

A test report consumer has acknowledged a pathology and laboratory medicine test report
An event is published
A notification is sent to the subscribed system
Your system receives the notification
Your system calls the Pathology and Laboratory Medicine Reporting - FHIR API to retrieve the acknowledgement
Your system retrieves and applies the latest data

Event structure

This event is available in FHIR format. FHIR events are accessible to both internal and external subscribers.

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-ack-1
time	timestamp	Timestamp	M	1..1	The time of the event ISO 8601
versionid	version-id	string	M	1..1	This is the version of this event that is being received

Event example

{
  "specversion": "1.0",
  "id": "c76c04cd-5665-4429-86c9-dc107597a32e",
  "source": "ABC123",
  "type": "pathology-laboratory-reporting-test-result-stored-1-ack-1",
  "time": "2026-07-17T09:58:31+00:00",
  "dataref": "https://api.service.nhs.uk/patient-data-manager/FHIR/R4/Bundle/bd3cc096-92d6-4949-8b1e-67a6298ce523",
  "filtering": {
    "destination": "P.TAB-4PQ"
  }
}

Event filtering

You can filter the events you want to receive using the criteria field in the subscription payload. You should only subscribe to events you need and must not create filters wider than required.

Available filters

Filter name	Type	Description
destination	string	A destination filter element references the Test Reporting system the acknowledgement is directed to

Onboarding

To subscribe to this event, you will need to:

complete onboarding to Pathology and Laboratory Medicine Reporting – FHIR API
complete onboarding to MNS
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.

Testing

This event is available to test in the Path to Live (PTL) environments.

Versioning

This is the first and only version of this event.

Last edited: 29 September 2026 2:16 pm