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. Business Context
    3. Business Events
    4. L1: Send, Receive, Revoke

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

Level 1 System Capabilities

Systems with Level 1 capabilities provide the minimum requirements for systems to participate in the exchange of an electronic referral request.

L1: Send, Receive, Revoke

To support the electronic exchange of referral information from a system the basic requirements are below.1

A Source System claiming compliance with Level 1 SHALL have the ability to generate and transmit a valid message to a Target System when:

  • A new Service Request is created, assigned to a Performer HCP (or Case Assigner) and submitted
  • A message to Revoke the Service Request when it has been incorrectly assigned or submitted in error

A Target System claiming compliance with Level 1 SHALL have the ability to receive and appropriately process a valid message received from a Source System when:

  • A new Service Request is created, assigned to a Performer HCP (or Case Assigner) and submitted
  • A message to Revoke the Service Request when it has been incorrectly assigned or submitted in error

Note: 1 Without the ability to participate in the bi-directional exchange of information a system is insufficient for closed loop eReferral or eConsult.

State Machine

In Level 1 integrations, the focus of messages is always on the service request. The exchange of information is triggered as the Requester HCP (or delegate) performs actions that change its state.

statemachine-L1

Noting that the Requester HCP is driving the states of this diagram and determine referral completion.

Trigger Events & Interactions

The table below illustrates real-life trigger events associated with Level 1 solutions the specific event codes within the FHIR message. This list is not intended to be exhaustive.

Party Action / Trigger Sending System Focus of Message State Change Event Code Receiving System Expected action upon receipt of message
Requester HCP Creates and submits a request Source System ServiceRequest (CA:eReC) request activated add-service-request Target System Create a Service Record for the request and initiate processing
Requester HCP Revokes a request Source System ServiceRequest (CA:eReC) request revoked revoke-service-request Target System Remove the Service Record and terminate processing

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