F: Performer HCP declines and CAT reassigns
The following sequence diagram shows the messaging flow when the Performer HCP (Service Provider) declines the service request and the CAT reassigns to another Performer HCP.
See Participants for more information.
Element and Value
Refer to Primary Flow for DocumentReference, HealthcareService, Location, Patient, Practitioner, and PractitionerRole elements.
Step 1: Performer HCP notifies CAT of decline of service request
See Step 10 in Primary Flow message flow with changes as below:
| Element | Value |
|---|---|
| Task.status | "rejected" |
| Task.businessStatus | "rejected-by-performer" |
| Task.businessStatus.extension.BusinessStatusReason | as appropriate |
| Task.note | as appropriate |
Step 3: CAT sends service request to another Performer HCP
See Step 6 in Primary Flow message flow
Step 4: CAT notifies Requester HCP of assignment to another Performer HCP
See Step 7 in Primary Flow message flow with changes as below:
| Element | Value |
|---|---|
| MessageHeader.reason | "service-request-reassigned" |
Step 5: Performer HCP acknowledges service request from CAT
See Step 8 in Primary Flow message flow