Care Coordination and 360 Referrals (Proof of Concept)
0.1.0 - proof-of-concept
Care Coordination and 360 Referrals (Proof of Concept) - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
Referral Cancellation [PCC-58] - the Referral Initiator asks for the referral to be cancelled; the Referral Recipient confirms the cancellation, or carries on with the next step if it cannot cancel.
sequenceDiagram
participant RI as Referral Initiator
participant RR as Referral Recipient
RI ->> RR: Cancel Request<br/>OSU^O51 CA/CA / Task cancel-requested
alt can cancel
RR ->> RI: Cancel Confirmation<br/>OSU^O51 CR/CA / Task cancelled
else too late
RR ->> RI: Next workflow step<br/>e.g. Referral Outcome [PCC-57]
end
| Actor | Optionality |
|---|---|
| Referral Initiator | O - if it sends a Cancel Request it SHALL handle a Cancel Confirmation and any other reply |
| Referral Recipient | O - it is not required to confirm every request |
| Data item | 360X HL7 v2 | FHIR |
|---|---|---|
| Order control | ORC-1 CA |
Referral Task businessStatus cancel-requested (Task status unchanged) |
| Referral ID | ORC-2 | basedOn.identifier, focus |
| Order status | ORC-5 CA |
- |
| Ordering provider and facility | ORC-12 and ORC-21 (required) - the referrer; someone else with authority may cancel | Task.requester unchanged; who cancelled in Provenance |
| Reason | ORC-16 (at least text) | statusReason, e.g. no-longer-required |
With a shared FHIR server the Referral Initiator may instead set
ServiceRequest.status to revoked; the Referral Recipient still decides whether
the Task can be cancelled.
| Data item | 360X HL7 v2 | FHIR |
|---|---|---|
| Order control | ORC-1 CR |
Task status cancelled |
| Referral ID | ORC-2 | basedOn.identifier, focus |
| Order status | ORC-5 CA |
businessStatus cancelled |
| Ordering provider and facility | ORC-12 and ORC-21 - the referrer, required in this guide (360X leaves ORC-12 empty) | - |
SIU^S15).