Conformance Requirements & Must Support

CA:FeX IG makes use of conformance language such as SHALL, SHOULD and MAY to describe the behavior of systems. The meaning of these words shall be interpreted as per the FHIR core specification.

The following Conformance resources set the minimum expectations for the CA:FeX server behaviors for health information exchange:

• CA:FeX Server CapabilityStatement: This Conformance instance defines the expected capabilities of a server when conforming to the CA:FeX Implementation Guide.

Principles

The following principles are applied when creating the CA:FeX capability statements:

• Start with the capabilities defined in the national health information exchange specifications to:
  • Increase the opportunity for Digital Health / mHealth application reuse across North America
  • Reduce developer / vendor effort to adapt to Canadian requirements
• Identify the commonalities between US Core, IHE QEDm, and IPA, and address the differences in a way to:
  • Avoid any additional constraints not commonly found across similarly scoped guides (unless strictly necessary), and
  • Relax the capabilities wherever appropriate

Must Support

Since, there are no profiles released in this CA:FeX version, there are no must-support elements guidance or expectations defined in this specification.