Actor Conformance

A system conforming to the CA:FeX Interoperability Specifications shall claim conformance at the level of a Use Case Actor (first columns of the Tables in Core Interoperability Specification Requirements). A system may claim conformance to one or more Use Case Actors among:

• Data Source
• Data Consumer
• Data Recipient
• Data Responder

Data Source and Data Consumer use case actor roles will primarily be taken up by EMR clinical solution vendors. Data Recipient and Data Responder use case actor roles can be taken up either by EMR clinical solution vendors or jurisdictions depending on the implementation approach that the jurisdiction decides to adopt. Similarly, the Data Consumer can be a Patient Portal, in which case the use case actor can be taken up either by a vendor or jurisdiction depending on the approach and policies defined regarding patient / subject of care access to their personal health information (PHI).

In order to implement a system that fully supports the CA:FeX Interoperability Specifications, the system shall be able to demonstrate that it conforms to every required actor and transaction for which it is claiming conformance.

Constraints on Use Case Actors 

The section below captures some of the design constraints on use case actors when developing functionality to support the services mapped to them.

Note: The scope of this section is limited to the constraints that are applicable to actors and transactions defined for CA:FeX Interoperability Specifications (See section CA:FeX Actors and Transactions). The key services supported by CA:FeX are:

• Submit Data
• Search Data
• Retrieve Data

The following section provides key design constraints for implementation of these two required services using RESTful APIs based on CA:FeX and FHIR standards. To support these services, the following three RESTful transactions have been defined:

For more details on these transactions please see CA:FeX Implementation Guide:

• Document Exchange
• Data Exchange