Visit the HL7 website
Visit the FHIR website

Pan-Canadian eReferral-eConsult (CA:eReC) v1.1.0-DFT-Ballot

1.1.0-DFT-Ballot   Canada flag
  • Index
  • Home
  • Business Context
    • Business Models
    • Use Cases
    • Business Events
    • Business Rules
    • Privacy and Security Guidance
    • Provincial Considerations
  • Technical Context
    • Technical Foundation
    • Integration Patterns
    • Messaging
    • Sequence Diagrams
    • Conformance Requirements
  • FHIR Artifacts
    • Messaging Events
    • Resource Profiles
    • Extensions
    • Terminology
    • Examples
    • Capability Statements
    • Downloads
    • ---
    • Appointment (CA:eReC)
    • Bundle (CA:eReC)
    • Communication (CA:eReC)
    • DocumentReference (CA:eReC)
    • Location (CA:eReC)
    • MessageHeader (CA:eReC)
    • Organization (CA:eReC)
    • Patient (CA:eReC)
    • Practitioner (CA:eReC)
    • PractitionerRole (CA:eReC)
    • HealthcareService (CA:eReC)
    • QuestionnaireResponse (CA:eReC)
    • ServiceRequest (CA:eReC)
    • Task (CA:eReC)
  • Change Log
    1. Index
    2. Technical Context
    3. Messaging
    4. Referral Outcome Information

preBallot - The specification is currently in ballot review and subject to change. . . . For a full list of available versions, see the Directory of published versions


Referral Outcome Information

Different referral requests and pathways will have different outcomes. As with other business flows, implementers SHALL anticipate the need to discuss expected outcomes of different ServiceRequests and any information to be shared when a ServiceRequest reaches a terminal state (i.e.: completed, cancelled, failed, or rejected).

A referral or consult request is completed when the Performer marks the Task as completed, although in some cases the Requester may have to mark the ServiceRequest as completed.

Below are approaches in use:

Request completed by Performer

In the typical case where a ServiceRequest is accepted by an eReC Performer and then completed by its users, an update to the 'process-request' Task SHOULD be used to share information with the requester about the ServiceRequest outcome, where:

  • the MessageHeader.event SHALL be 'notify-update-process-request'
  • the MessageHeader.focus SHALL be a reference to Task resources, where:
    • Task.code is 'process-request'
    • Task.status is 'completed'
  • Task.output MAY reference one or more resources that are related to the action on the current ServiceRequest (e.g.: a Communication containing a plan of care)
Request completed by Requester

In some cases, the requester of a referral or consult may be required to confirm that the request has been completed.

Note : The task.code is used to differentiate between the eReferral compared to an eConsult request. For eConsult, task.code is 'process-request-consult' and for eReferral the task.code is 'process-request'

In case of an eConsult the workflow will be as follows:

Business Event Message EventCode Target System Details
Specialist provides response notify-update-process-request eReC Requester Task.code is "process-request-consult"
Task.status is "completed"
Task.output.valueReference() references the service plan or response (Communication) Communication.payload.contentString contains the specialist's consult response
Requester confirms that request has been completed notify-update-service-request eReC Performer ServiceRequest.status is "completed"
Requester revokes request revoke-service-request eReC Performer ServiceRequest.status is "revoked"
Requester cancels bad request and resubmits to new Target revoke-service-request followed by add-service-request eReC Performer ServiceRequest.status is "revoked" followed by a new ServiceRequest where the ServiceRequest.status is "active"
Performer responds to consult request suggesting eReferral notify-update-process-request eReC Requester Task.code is "process-request-consult"
Task.status is "completed"
Task.output.valueReference() references the service plan or response (Communication)
Communication.payload.contentString contains the specialist's consult response
.extension:PatientNeedsToBeSeen - PatientNeedsToBeSeen is set to true

Table of Contents | IG © based on FHIR R4 | Package package:ca.infoway.io.erec@1.1.1-dft-ballot | Version History
HL7® and FHIR® are the registered trademarks of Health Level Seven International