IPS and PS-CA
This version of the PS-CA Implementation Guide has been superseded by a newer version. Other releases of the PS-CA Implementation Guide may be found on a table on the Home Page of this Project.
This project leverages the ongoing effort from the IPS project which has an established content and data model informed by FprEN 17269:2019 from CEN/TC 251 which uses both the HL7® CDA and HL7® FHIR® standards.
However, the PS-CA Use Cases and the implementation ecosystem are not identical to IPS. For example, the PS-CA specification has to account for jurisdictional differences in the following: system capabilities, established charting practices, and change management capacity. Notably, the PS-CA also has to account for creation of the Patient Summary-CA through provider-generated summaries (as a result of an encounter to provide a snapshot of the patient's health care), as well as machine-generated summaries (created automatically by provincial electronic health records).
As a result, the PS-CA has applied a slightly different approach in implementing the data model from the original IPS project. While the elements within the IPS data model remain the same, the expectations for when and how the elements are implemented require a more nuanced approach.
The Patient Summary-CA Canadian Edition project leverages an iterative, consensus-driven, version-based approach for publishing specification content. For more information on the development process and roadmap, implementors are encouraged to review PS-CA Specification Preface.
Scope of Coverage for PS-CA Version 1.0 - Trial Implementation
Given the aggressive timelines of the first phase of the Patient Summary project and input from detailed consultation with participating jurisdictions, it was recommended a national FHIR profile set that covers a sub set of data domains for Version 1.0.
The remainder of the IPS data domains and updates to Phase 1 profiles will be followed shortly and will be based on implementation experience.
Domains
The HL7 IPS specification lists a number of data domains as mandatory; however, there is also an expectation that jurisdictional policy variations may mandate some or other data domains being required in those locales.
Taking all these into consideration and the desire to offer vendor solutions the ability to configure rather than customize PS solutions across the country, the recommendation was made to relax the cardinality of the data domains from Required to Recommended. This will allow for a single national standard where jurisdictions can still express a desire to require certain domains through implementation guidance, without a need for changing the national standard.
PS-CA Version 1.0 - Trial Implementation Profiles
Implementers are encouraged to begin by reviewing the PS-CA Library of Profiles page which describes the Patient Summary Composition Structure & Profiles (e.g., sections that make up the data model content for the PS-CA).
Differences between the IPS-UV and PS-CA V1.0
Differences between the IPS-UV STU1 and PS-CA V1 are largely limited to areas where further localization was required as well as areas where the PS-CA needed to relax system conformance expectations in the first version to align to current state jurisdictional capabilities.
See Evolution of Specification for information on how the PS-CA will evolve over time to ensure support of the remaining elements in IPS-UV that were not included in the first trial implementation specification.
Differences between this IPS-UV STU 1 profiles & the PS-CA V1 profiles are noted on the respective profiles pages.