Generated Narrative: MessageDefinition referral-order-status

url: MessageDefinition Referral Order Status (O51)

version: 0.1.0

name: ReferralOrderStatus

title: Referral Order Status (O51)

status: Draft

experimental: true

date: 2026-11-01

publisher: Kevin Mayfield

contact: https://github.com/KevinMayfield/PatientCareCoordination

description:

FHIR Message equivalent of the IHE 360X HL7 v2.5.1 OSU^O51^OSU_O51 order status update. The Referral Task carries the status (status, businessStatus, statusReason); for an interim note [PCC-59] or outcome [PCC-57] the message also carries the clinical document referenced from Task.output.

The message does not carry a Patient resource. Both sides of the exchange already know the patient from the referral, so Task.for identifies the patient by NHS Number (for.identifier), Task.requester the referrer (professional code) and Task.owner the Referral Recipient (service identifier), alongside the references.

360X ORC-1 / ORC-5 Task.businessStatus
Accept [PCC-55] OK / IP accepted
Decline [PCC-55, PCC-56] UA / CA declined
Deferred (NHS, indicative) OH / HD deferred
Redirected (NHS, indicative) RU / RP redirected
Interim Consultation Note [PCC-59] SC / A interim-report
Referral Outcome [PCC-57] SC / CM completed
Cancel Request [PCC-58] CA / CA cancel-requested
Cancel Confirmation [PCC-58] CR / CA cancelled

jurisdiction: United Kingdom of Great Britain and Northern Ireland

event: event: O51 (OSU – Order Status Update)

category: Notification

Focus

-CodeProfileMinMax
*TaskReferral Task11

responseRequired: Never

 <status value="draft"/> <experimental value="true"/> <date value="2026-11-01"/> <publisher value="Kevin Mayfield"/> <contact> <telecom> <system value="url"/> <value value="https://github.com/KevinMayfield/PatientCareCoordination"/> </telecom> </contact> <description value="FHIR Message equivalent of the IHE 360X HL7 v2.5.1 `OSU^O51^OSU_O51` order status update. The [Referral Task](StructureDefinition-ReferralTask.html) carries the status (`status`, `businessStatus`, `statusReason`); for an interim note [PCC-59] or outcome [PCC-57] the message also carries the clinical document referenced from `Task.output`. The message does **not** carry a `Patient` resource. Both sides of the exchange already know the patient from the referral, so `Task.for` identifies the patient by NHS Number (`for.identifier`), `Task.requester` the referrer (professional code) and `Task.owner` the Referral Recipient (service identifier), alongside the references. | 360X | ORC-1 / ORC-5 | Task.businessStatus | |---|---|---| | Accept [PCC-55] | OK / IP | accepted | | Decline [PCC-55, PCC-56] | UA / CA | declined | | Deferred (NHS, indicative) | OH / HD | deferred | | Redirected (NHS, indicative) | RU / RP | redirected | | Interim Consultation Note [PCC-59] | SC / A | interim-report | | Referral Outcome [PCC-57] | SC / CM | completed | | Cancel Request [PCC-58] | CA / CA | cancel-requested | | Cancel Confirmation [PCC-58] | CR / CA | cancelled |"/> <jurisdiction> <coding> <system value="urn:iso:std:iso:3166"/> <code value="GB"/> <display value="United Kingdom of Great Britain and Northern Ireland"/> </coding> </jurisdiction> <eventCoding> <system value="http://terminology.hl7.org/CodeSystem/v2-0003"/> <code value="O51"/> </eventCoding> <category value="notification"/> <focus> <code value="Task"/> <profile value="https://fhir.acmeexample.org.uk/PatientCareCoordination/StructureDefinition/ReferralTask"/> <min value="1"/> <max value="1"/> </focus> <responseRequired value="never"/> </MessageDefinition>