Scope

The CA:FeX specification package was developed to define and guide approaches to information sharing using FHIR RESTful capabilities primarily for (but not limited to) greenfield implementations. Expectations in CA:FeX will be rooted in best practices from international FHIR specifications (e.g., IPA, QEDm, US Core, IPS, etc.) that are feasible for the Canadian market to standardize around.

At a glance, CA:FeX will provide guidance in the following areas:

• Document Exchange: Approaches for exchanging multiple resources together in the form of documents, and identification of standardized search parameters and practices for document implementers to incorporate into guides and systems
• Extending APIs with FHIR Operations: Identification of functional FHIR operations that allow implementers to abstract complexity away from requesting applications, by offering a single API call that can trigger multi-step processes to execute

The CA:FeX specification package is intended to act as a key building block within the arsenal of interoperability tools that provide vendors with the ability to anticipate or predict the minimum expectation to interact with any ecosystem interface, regardless of jurisdiction. In line with international peers, it will act as the guidance to define “Interaction Support” for all health IT ecosystem players.

The scope of CA:FeX may evolve beyond the exchange paradigms listed on the CA:FeX Exchange Patterns; however this will depend on the development of a multi-phased interoperability roadmap, the evolving needs of the Canadian health care market, and emerging trends within the international FHIR health information exchange community.

Relationship to Use Cases

CA:FeX implementation guide is provided to support the use of data exchange in Canada. This Implementation Guide does not attempt to constrain specific use cases. Instead it defines representations of how commonly needed concepts, in a Canadian context, can be applied generally. This implementation guide can then be drawn on for specific use cases and further constraints added for the needs of those cases.