Visit the HL7 website
Visit the FHIR website

Pan-Canadian eReferral-eConsult (CA:eReC) CIBuild

current   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. FHIR Artifacts
    3. Examples

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

Examples

Examples Defined in This Guide

These examples show the message Bundles that are created for the messaging transactions.

Example Description Source Target
eReCm-1 - Send new service request Bundle This example is for an initial referral request. It contains a ServiceRequest with the referral information, a Patient, a PractitionerRole with the linked Practitioner, Organization, and Location, and a HealthcareService providing information about the requested service. eReC Requester eReC Performer
eReCm-6 - Notify new request processing Bundle This example is for a task that indicates the referral request has been received by the eReC Performer and the request processing is initiated. It contains a Task with the information and references the ServiceRequest via an identifier. eReC Performer eReC Requester
eReCm-7 - Notify update request processing Bundle This example is for a task that indicates that the referral has been accepted by the eReC Performer. It contains the Task with the status change in Task.status. The ServiceRequest is referenced via an identifier. eReC Performer eReC Requester
eReCm-10 - Send communication from performer Bundle This example is for an eReC Performer requesting additional information about a specific referral through a Communication using a Request for Information (RFI). The Communication contains the request for clarification or additional information in Communication.payload. The original ServiceRequest is referenced via an identifier. eReC Performer eReC Requester
eReCm-9 - Send communication from requester Bundle This example is for an eReC Requester responding back to a Request for Information (RFI). The Communication contains the requested clarification or additional information in Communication.payload, and the Communication it is responding to is referenced in Communication.inResponseTo and included in the bundle. The original ServiceRequest is referenced both with an identifier and a uuid along with other supporting resources. eReC Requester eReC Performer
eReCm-3 - Notify update service request Bundle This example is for an eReC Requester indicating that the ServiceRequest has has been updated with the requested additional information. It contains the additional information as a DocumentReference which is referenced in ServiceRequest.subject and included in the bundle, along with other referenced resources. eReC Requester eReC Performer
eReCm-4 - Notify data correction Bundle This example is for an eReC Performer indicating that patient demographic information has been updated in the Patient resource. It contains the received ServiceRequest with an update to the ServiceRequest.subject (Patient) which is referenced and included in the bundle, along with other referenced resources. eReC Performer eReC Requester
eReCm-8 - Notify new appointment Bundle This example is for indicating that an appointment has been created for the patient for a specific referral. It contains an Appointment with the scheduling and location information. The ServiceRequest and other supporting resources are referenced with uuids and included in the bundle. eReC Performer eReC Requester
eReCm-5 - Revoke service request Bundle This example is for an eReC Requester to revoke a referral that was previously sent to the eReC Performer. It contains a ServiceRequest with the referral information, a Patient, a PractitionerRole with the linked Practitioner, Organization, and Location, and a HealthcareService providing information about the requested service. eReC Requester eReC Performer
eReCm-2 - Notify new service record Bundle This example is for a Central System informing interested parties (eReC Recipients) that a referral has been made to a selected eReC Performer, which replaces the initial referral received. The initial ServiceRequest and the ServiceRequest that replaced it are both included in the bundle, along with information from the linked HealthcareServices, Practitioners, Organizations and the Patient. eReC Informer eReC Recipient
eReCm-11 - Notify update service record Bundle This example is for a Central System informing interested parties (eReC Recipients) that a referral made to an eReC Performer, which replaced the initial referral received, has been accepted. It contains a Task with status on the work being performed by the eReC Performer. The initial ServiceRequest and the ServiceRequest that replaced it are both included in the bundle, along with information from the linked HealthcareServices, Practitioners, Organizations and the Patient. eReC Informer eReC Recipient

Table of Contents | IG © based on FHIR R4 | Package project:CA-eReC | Version History
HL7® and FHIR® are the registered trademarks of Health Level Seven International