D: Performer HCP requests information
The following sequence diagram shows the messaging flow when the Performer HCP requests additional information from the Requester HCP (Referring Provider) and the Requester HCP (Referring Provider) responds to the request.
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 requests Requester HCP for additional information
| Element | Value |
|---|---|
| Bundle.meta.extension.submissionMetadata | metadata for: Submitting Site; EMR Vendor Name; EMR Product Name; Submission Implementation Guide (IG) Type; Submission Implementation Guide (IG) Version; Service Delivery Site; Authoring Provider ID |
| Bundle.id | UUID |
| Bundle.meta.lastUpdated | date/time |
| Bundel.meta.security | "R" |
| Bundle.identifier.value | UUID |
| Bundle.identifier.system | "urn:ietf:rfc:3986" |
| Bundle.type | "message" |
| Bundle.timestamp | current date/time |
| Bundle.entry:MessageHeader | MessageHeader |
| Bundle.entry:Focus | Communication |
| MessageHeader.id | UUID |
| MessageHeader.meta.lastUpdated | date/time |
| MessageHeader.eventCoding | "send-communication-from-provider" |
| MessageHeader.destination.endpoint | CAT RMS endpoint |
| MessageHeader.author.reference | Performer HCP UUID |
| MessageHeader.author.type | "PractitionerRole" |
| MessageHeader.source.endpoint | Performer HCP endpoint |
| MessageHeader.focus | Communication |
| Communication.id | UUID |
| Communication.identifier | TBC if used UUID |
| Communication.basedOn.identifier.value | ServiceRequest provincial identifier |
| Communication.basedOn.identifier.system | "https://fhir.alberta.ca/NamingSystem/ca-ab-eref-id" |
| Communication.status | "completed" |
| Communicaiton.category | "rfi" |
| Communication.subject.identifier.value | Patient identifier |
| Communication.subject.identifier.system | as appropriate |
| Communication.sent | current date/time |
| Communication.recipient.identifier.value | CAT identifier (HealthcareService) |
| Communication.recipient.identifier.system | "https://fhir.alberta.ca/NamingSystem/ca-ab-eref-healthcare-service-id" |
| Communication.sender.reference | Requester HCP UUID |
| Communication.sender.type | "PractitionerRole" |
| Communication.payload.contentString | message to indicate what information is requested |
Step 3: CAT sends requests for additional information to Requester HCP
See Step 1 in CAT requests information message flow
Step 4a: Requester HCP provides additional information (through Communication)
See Step 2a in CAT requests information message flow
Step 4.b: Requester HCP provides additional information (through updated ServiceRequest)
See Step 2b in CAT requests information message flow
Step 6a: CAT sends Performer HCP additional information
See Step 2a in CAT requests information message flow with changes as below:
| Element | Value |
|---|---|
| MessageHeader.destination.endpoint | Performer HCP EMR endpoint |
| MessageHeader.source.endpoint | CAT RMS endpoint |
| Communication.recipient.reference | Requester HCP UUID |
| Communication.recipient.type | "PractitionerRole" |
| Communication.sender.identifier.value | CAT identifier (HealthcareService) |
| Communication.sender.identifier.system | "https://fhir.alberta.ca/NamingSystem/ca-ab-eref-healthcare-service-id" |
Step 6b: CAT sends Performer HCP additional information
See Step 2b in CAT requests information message flow with changes as below:
| Element | Value |
|---|---|
| MessageHeader.destination.endpoint | Performer HCP EMR endpoint |
| MessageHeader.source.endpoint | CAT RMS endpoint |
| Communication.recipient.reference | Requester HCP UUID |
| Communication.recipient.type | "PractitionerRole" |
| Communication.sender.identifier.value | CAT identifier (HealthcareService) |
| Communication.sender.identifier.system | "https://fhir.alberta.ca/NamingSystem/ca-ab-eref-healthcare-service-id" |