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
Actor Groupings
Grouped Actors are actors which are implemented together on a single system to provide more complex functionalities. For a grouping to occur, an actor from this profile (Column 1 - eReC Actor) shall implement all the required transactions and/or content modules in this profile in addition to all the transactions required for the grouped actor (Column 2 - Actor to be grouped with).
| eReC Actor | Actor to be grouped with | Optionality of grouping | Notes |
|---|---|---|---|
| eReC Requester | eReC Informer | Optional | Note 1 |
| eReC Performer | eReC Informer | Optional | Note 2 |
| eReC Performer | eReC Requester | Optional | Note 3 |
| eReC Performer | eReC Informer (Link) | Optional | Note 4 |
| eReC Requester | eReC Recipient (Link) | Optional | Notes: 5,6 |
Note 1:
Grouping an eReC Informer with an eReC Requester on a system provides the ability for the system to send a copy of a service record sent to an eReC Performer system as well as updates made in response to information received from an eReC Performer system to be shared with other interested parties and/or other systems used by a Requester HCP.
Note 2:
Grouping an eReC Informer with an eReC Performer on a system provides the ability for the system to send a copy of a service record created or updated in response to information received from an eReC Receiver to be shared with other interested parties and/or other systems used by a Performer HCP.
Note 3:
In systems used to support Example: Central Intake in Point to Point and Example: Central Access and Triage (CAT) Model business models, the eReC Requester may need to transmit service requests that have been created or reassigned by the Central Intake or CAT team to a Performer HCP(s) who work on another system(s).
Note 4:
In systems used to support Example: Central Intake in Point to Point and Example: Central Access and Triage (CAT) Model business models, the eReC Informer (link) may be implemented to share information about and updates to service requests that have been created or reassigned by the Central Intake or CAT teams to a Requester HCP(s) that work on another system(s). The Link option relates to the ability for the system to associate service requests received by the eReC Performer to new requests created and managed within the system in messages sent by the eReC Informer. See: L3: Advanced Workflows
Note 5:
Where Example: Central Intake in Point to Point and Example: Central Access and Triage (CAT) Model business models are in use, implementing an eReC Recipient (Link) with the eReC Requester on the system used by the Requester HCP provides a mechanism for the system to receive information about and updates to a service request that has been created or reassigned by the Central Intake or CAT teams. The Link option relates to the ability for the system to associate service requests received by the eReC Recipient with existing requests created and managed within the system. See: L3: Advanced Workflows
Note 6:
Where this grouping exists, the system may receive two streams of updates related to a request sent from the system used by the Central Intake or CAT team:
- eReC Requester: will receive FHIR messages that provide notifications focused on services (Tasks) performed by the organization operating Central Intake or CAT with the purpose of conveying acceptance, completion, etc of the request received from the Requester HCP / eReC Requester.
- eReC Recipient: will receives notifications update to service record created and managed on the system used by the Central Intake or CAT team with the purpose of passing along information about downstream services requested from and performed by the Performer HCP.