Page History

How to Provide Feedback

...

The ballot release of the CA:FeX v2.2.0 DFT-Ballot will be available on June 1stMay 30th, 2025.

The timeline for ballot submissions is June 1st2nd, 2025 to June 30th, 2025.

...

• Review the CA:FeX Specifications in Simplifier.net, from the corresponding link in the table above or on the Release page.

...

• All Collaborators are invited to document their ballot comments using the CA:FeX v2.2.0 DFT-Ballot spreadsheet, available here. 
• Send an email to [email protected] , with Subject Line " CA:FeX ", including the CA:FeX v2.2.0 DFT Submission spreadsheet as an attachment.
• We kindly ask that each organization submit all comments within one spreadsheet submission. 
• Upon submission, you will receive an acknowledgment email with a reference number. Feedback will be triaged by the Infoway Lead to support the eReferral/eConsult the CA:FeX Working Group with decisioning/voting blocks.

...

To learn more about the balloting cycle process, please visit the IO Specifications Publication Model page.

Release Notes

...

• Created the CA:FeX Home page with introductory content for the guide
• Expanded the Project Background with additional context
• Migrated content from Infoscribe (CA:FeX v2.1.0 DFT-Ballot) to Simplifier:
  • Use Cases
  • Sequence Diagrams
  • Interoperability Recommendations Tables – refocused on best practices
• Restructured content into three top-level sections: Business Context, Technical Context, and Actor and Conformance Options
• Added Technical Overview page
• Created Technical Actors and Actor Options pages
• Merged and updated conformance content in Conformance Requirements
• Updated Capability Statements to reflect new actors and exchange options
• Removed deprecated search parameters clinical-type and clinical-date
• Updated Option C documentation to clarify single-resource exchange pattern
• Defined clear conformance expectations for all supported CA:FeX operations
• Clarified profile/extension guidance to emphasize use of base FHIR resources when exchanged
• Merged response guidance into RESTful API Interactions page
• Expanded $docref guidance with clarification on patient.id vs patient.identifier