DFT - The specification is currently in development 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.¹

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: ¹ 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.

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

¹ completed:

• Requesters are not responsible for completing eReferrals.
• Requesters are responsible for indicating eConsults as completed by using ServiceRequest.status:completed.

² unknown: this code is discouraged but can still be used.​

³ entered-in-error: Functionally similar to Revoked status.

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 (L1)	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 (L1)	Target System	Remove the Service Record and terminate processing

---