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
Overview
eReferrals and eConsults are created, submitted, tracked and managed electronically. When provider workflow considerations are addressed, eReferrals/eConsults have the potential to streamline and improve the patient referral and provider-to-provider consultation process compared to traditional paper-based or fax-based methods.
This specification defines messaging patterns to support models of eReferral and eConsult where system integrations are needed to enable clinical workflow and information sharing.
Business Model Components
| Component | Description |
|---|---|
| eReferral vs eConsult | Definitions, similarities and differences between eReferrals and eConsults. |
| Service Record | Definition and set of information included in a Service Record. |
| Participants | People, Organizations and Systems contributing to the Service Record during the service lifecycle. |
Approaches to implementing eReferral Exchange
This section identifies a few different eReferral eConsult related business models that are supported by this specification.
| Business Model | Description |
|---|---|
| Single RMS Model | A single referral management system supporting the exchange of Service requests, Appointments and Secure Communications between Requester HCPs and Performer HCPs. |
| Point to Point Model | Health Care Providers (HCP)s who participate in referral workflows work within different Referral Management Systems (RMS) that each retain and manage separate instances of the Service Record that must be kept in sync. |
| Single Entry Models | A centralized entity performs services in support of the Requester HCP and/or Performer HCP within a service area and/or referral pathway. Single Entry Models may be implemented using the Single RMS Model or within a network of RMS solutions integrated using the Point to Point Model. |
Example Single Entry Models
| Example | Description |
|---|---|
| Example: Central Access and Triage (CAT) Model | A shared enterprise RMS is used to manage a shared Service Record that the Requester HCP, CAT team (Case Assigner with additional responsibilities) and Performer HCP all contribute to. |
| Example: Central Intake in Point to Point | A RMS used by Central Intake is a Target for requests from Requester HCPs and can be seen as a Source of Referrals to Performer HCPs within an existing network of Point to Point integrations. |