Actor Mapping to Interoperability Specification
The Use Case Actors and the Services they support are described at a functional level in the Use Cases and Definitions section of the CA:FeX Interoperability Specifications. Services may be Required or Optional. The Use Case Actor, Service(s) and optionality are conveyed in the first three columns of Tables 1 and 2 in the section below. The second part of the table (columns 4-7) provides the mapping for the Use Case Actor to the detailed specifications (such as Technical Actors and Optionality) that systems shall implement to exchange healthcare information in the context of these use cases. The purpose of the tables below is to map the use case actors to the technical actors and the services they are supporting. These tables are aligned with the flow captured in the sequence diagrams which are included in the Sequence Diagram section.
For a selected Use Case Actor (a single row in the table), the system shall implement all of the requirements (some optionality when allowed) listed in the second part of the table (columns 4-7). This includes the referenced healthcare profiles, the standards specified and terminology standards. For Technical Actors, which map to CA:FeX or an IHE Profile (CA:FeX, PDQm, PMIR, etc.), the last column provides the reference location of the specification. Links for these referenced specifications have been included in the tables below. Additionally, the below table does not showcase all of the possible combinations of IHE profiles and transactions that can be used for a particular implementation pattern. For example, 'Identify Patient' service can use PIXm in place of PDQm if the preferred implementation pattern is PIXm/PMIR.
Versioning
This is an evolving specification; the release cycle assumes some degree of change will happen across versions. (Read more about the versioning protocol here.) There will be a process in place to monitor changes in the current versions of the IHE profiles which will be incorporated in future versions of the CA:FeX Interoperability Specifications based on our interoperability roadmap.
Published Versions
The following describes the published versions in scope for the required and optional IHE Profiles that have been referenced in this specification. Refer to the Reference Architecture RA v0.1.0 DFT for details:
- IUA: Revision 2.1 - Trial Implementation
- PDQm: v2.3.0: Trial Implementation based on FHIR R4
- PMIR: Revision 1.3 – Trial Implementation
Legend
R = Required
O = Optional
Table 1 Interoperability Conformance Requirements for Use Case 1: Create and Submit Document
USE CASE 1: Create and Submit Document | MAPPING TO SECTIONS FROM THIS AND REFERENCED INTEROPERABILITY SPECIFICATIONS | |||||
USE CASE ACTOR | SERVICE SUPPORTED | OPT | TECHNICAL ACTOR | OPT | PROFILE/ STANDARD | REFERENCED SPECIFICATION AND STANDARDS |
Producer | Authenticate User | O | Client (e.g. EMR) | O | Internet User Authorization (IUA) | Refer to the Cross Profile Considerations section: Internet User Authorization (IUA) Grouping. |
Identify Patient | O | Client (e.g. EMR) | O | Use Existing Standards Employed by the Clinical System | N/A | |
O | Patient Demographic Consumer | O | PDQm | Refer to PDQm within the RA v0.1.0 DFT. | ||
Retrieve Clinical Data (Patient Identifer) | R | Client (e.g. EMR) | R | Use Existing Standards Employed by the Clinical System | N/A | |
Assemble and Review Document | R | Client (e.g. EMR) | R | Use Existing Standards Employed by the Clinical System | N/A | |
Omit or Mask Data based on Jurisdictional Policy | O | Client (e.g. EMR) | O | Jurisdictional Requirement | N/A | |
Save Document to Clinical Data Repository | R | Client (e.g. EMR) | R | Use Existing Standards Employed by the Clinical System | N/A | |
R | Data Source | R | CA:FeX | Refer to Submit a Document in the Exchanging Documents in FHIR section. | ||
Clinical Data Repository (Central) | Save Bundle to Clinical Data Repository | R | Data Recipient | R | CA:FeX | Refer to Submit a Document in the Exchanging Documents FHIR section. |
Central Infrastructure | Identify Patient | O | Patient Identity Registry | O | PMIR | Refer to PMIR within the RA v0.1.0 DFT. |
Table 2 Interoperability Conformance Requirements for Use Case 2: Query and Retrieve Document
USE CASE 2: Query and Retrieve Document | MAPPING TO SECTIONS FROM THIS AND REFERENCED INTEROPERABILITY SPECIFICATIONS | |||||
USE CASE ACTOR | SERVICE SUPPORTED | OPT | TECHNICAL ACTOR | OPT | PROFILE/ STANDARD | REFERENCED SPECIFICATION AND STANDARDS |
Consumer | Authenticate User | O | Client (e.g. EMR) | O | Internet User Authorization (IUA) | Refer to the Cross Profile Considerations section: Internet User Authorization (IUA) Grouping. |
Identify Patient | O | Client (e.g. EMR) | O | Use Existing Standards Employed by the Clinical System | N/A | |
O | Patient Demographic Consumer | O | PDQm | Refer to PDQm within the RA v0.1.0 DFT. | ||
Request Search Document (Patient Identifier) | R | Client (e.g. EMR) | R | Use Existing Standards Employed by the Clinical System | N/A | |
Request Document (Resource ID) | R | Client (e.g. EMR) | R | Use Existing Standards Employed by the Clinical System | N/A | |
| Return searchset Bundle | R | Data Consumer | R | CA:FeX | Refer to Search for a Document in the Exchanging Documents in FHIR section. | |
| Return document Bundle | R | Data Consumer | R | CA:FeX | Refer to Retrieve a Document in the Exchanging Documents in FHIR section. | |
Clinical Data Repository (Central) | Retrieve Resources from Clinical Data Repository | R | Data Responder | R | CA:FeX | Refer to Search for a Document in the Exchanging Documents in FHIR section. |
Retrieve Bundle from Clinical Data Repository | R | Data Responder | R | CA:FeX | Refer to Retrieve a Document in the Exchanging Documents in FHIR section. | |
Central Infrastructure | Identify Patient | O | Patient Identity Registry | O | PMIR | Refer to PMIR within the RA v0.1.0 DFT. |