Fulfillment converts a scheduled referral into a performed service
Service fulfillment begins when the patient arrives and the operational system can tie the real-world encounter back to the booked referral, the right patient identity, and the exact service plan.
In imaging, the classic chain is modality worklist to acquisition to archive to reporting worklist. Other referral types follow the same principle even when the payloads differ: the servicing team needs a reliable execution context and a clean transition into documentation or results.
Fulfillment and reporting message flow
Loading diagram...
This figure is narrower than the full referral ecosystem, which is exactly why it teaches well. It shows how one scheduled order crosses acquisition, storage, reporting, and viewing boundaries before the requester can treat the work as closed.
DICOM Modality Worklist information model
Official DICOM section describing the information model that lets modalities query scheduled patient and procedure context.
Read the worklist modelDICOM Modality Performed Procedure Step
Official DICOM section describing the performed procedure state transitions reported back from the modality.
Read the MPPS workflowResult delivery closes the loop only when the outcome is traceable
A final report is not just narrative text. It is a closure artifact that must identify the patient, the performed service, and often the underlying study or observations that support the conclusion.
DiagnosticReport example
Representative report payload showing how the final interpretation links back to both the patient and the performed imaging study.
Click on an annotation to highlight it in the JSON
Narrative and traceability both matter
Clinicians need readable conclusions, but systems also need machine-readable links back to the order, the service instance, and the evidence that supports closure.
For a new learner, this is the important point: the final report is only one artifact in the closure chain. It usually depends on linked findings, study identifiers, and retrievable image context that other systems must still be able to navigate.
DiagnosticReport - FHIR v4.0.1
Official HL7 definition for diagnostic report payloads and their relationship to observations and imaging studies.
Read the DiagnosticReport resourceHL7 v2.4 Chapter 7: Observation Reporting
Reference chapter for the ORU-style result reporting messages used in many legacy integrations.
Read HL7 Chapter 7Unable-to-perform and amended-result states still belong in the loop
Operationally, not every referral ends with a clean performed-study path. Patients may not arrive, contraindications may emerge at point of care, duplicate orders may be cancelled, or a previously final report may need amendment after new information appears.
The receiving platform still has to close the loop in those cases. If teams only model the happy path, requesters are left guessing whether the work is delayed, cancelled, clinically unsafe, or complete but later corrected.
Fulfillment exception and closure states
Loading diagram...
Contained HISO 10011.3 referral implementation guide
Contained legacy implementation guide that still illustrates closure, discharge, and other referral status transitions beyond the happy path.
Read HISO 10011.3 (contained guide)DiagnosticReport - FHIR v4.0.1
FHIR result resource definition, including report status handling such as final and amended.
Review report status behaviorKnowledge Check
Test your understanding with this quiz. You need to answer all questions correctly to mark this section as complete.