Pan-Canadian Patient Summary (PS-CA) CI Build

DFT - For a full list of available versions, see the Directory of published versions

Business and Legal Requirements

These requirements enable independent organizations to execute a collaborative process or service.

ID	Description	Status
BR1-01	A Patient Summary-CA Solution SHOULD provide the ability to manage the versioning, storage, preservation, destruction, and archiving of Patient Summaries produced and consumed by authorized users of the system in accordance with jurisdictional policies.	Approved
BR1-02	A Patient Summary-CA Solution SHOULD provide a healthcare provider with the option to review and sign-off the Patient Summary content before it is made available to PS-CA Consumers. Note: If the healthcare provider determines that changes are required to the Patient Summary prior to sign-off, the HCP will make the updates in the patient's chart. If the changes affect the Patient Summary content, a new Patient Summary will be created for review/sign-off by the HCP.	Approved
BR1-03	A Patient Summary-CA Solution SHOULD provide a healthcare provider with the ability to invalidate a Patient Summary if they determine it was entered in error or is invalid as required by jurisdictional policy.	Approved
BR1-04	A Patient Summary-CA Solution SHOULD adhere to data retention policies set by local/jurisdictional policies and system requirements.	Approved
BR1-05	A Patient Summary-CA Solution SHALL provide the ability for an authorized PS consumer (e.g. authorized health care provider) to ascertain the source of information (person, organization, or system) of a current PS and, depending on the jurisdictional implementation, a historical PS.	Approved
BR1-06	A Patient Summary-CA Solution MAY provide the ability to extract and save discrete data from a Patient Summary based on a request by an authorized system user. Note: Implementers are expected to follow applicable jurisdictional privacy and security policies when supporting data extraction, download, or storage.	Approved
BR1-07	A PS-CA Producer SHOULD reasonably ensure that the health information contained in a Patient Summary-CA is accurate, sufficiently complete and up to date to meet the specified clinical purpose. Note: PS-CA review and update processes will vary across different healthcare systems, depending on implementation patterns and jurisdictional policies.	Approved
BR1-08	A Patient Summary-CA Solution SHOULD be able to comply with a legal hold from an authorized entity based on jurisdictional policies. Note: Legal hold policies prevent deletion of any electronically stored information on the PS-CA that may be imminent for a legal case.	Approved
BR1-09	A Patient Summary-CA Solution SHOULD be able to omit or mask data in a PS-CA in compliance with local/jurisdictional privacy policies.	Approved
BR1-10	A Patient Summary-CA Solution SHOULD have the ability to produce a Patient Summary in compliance with a subject of care's consent directives in accordance with local/jurisdictional standards and/or policies. Note: For example, local/jurisdictional standards may include associating consent directives with PHI in the Patient Summary which cover concepts of maintaining association, processing consent directives, blocking transmission of PHI in Patient summary where consent directives are violated or no exception of a disclosure is outlined by law or by jurisdictional policy, and notifications to requesters when data is blocked due to consent directives.	Approved
BR1-11	A Patient Summary-CA Solution SHOULD enable limiting the sharing of health information to what is clinically necessary and sufficient, in accordance with governing legislation and the Patient Summary-CA specification. Note: For example, the clinician will have the ability to create the PS-CA with a subset of the data domains defined within the PS-CA Interoperability Specifications	Approved
BR1-12	A Patient Summary-CA Solution SHOULD have the ability to indicate or make the PS-CA Consumer (e.g. a healthcare provider) aware that information about the subject of care has been omitted or masked based on consent directives and jurisdictional policies.	Approved
BR1-13	A Patient Summary-CA Solution SHOULD provide the Patient/Subject of Care, or their authorized representative (e.g., caregiver, legal decision-maker), access to their Patient Summary in accordance with jurisdictional policies and legislative provisions.	Approved
BR1-14	A Patient Summary-CA Solution SHOULD limit access to only authorized PS-CA Producers and PS-CA Consumers, which may include both human actors (e.g., healthcare providers, patients) and systems (e.g., healthcare applications, digital platforms).	Approved
BR1-15	A Patient Summary-CA Solution SHALL have the ability to create a Patient Summary that includes a minimum of three required data domains: Medication Summary, Allergies and Intolerances, and Problem List. In cases where data is unavailable (e.g., not present in the source system) or is not allowed from a legal and policy perspective, the solution SHALL include an emptyReason field to indicate the absence of data.	Approved
BR1-16	A Patient Summary-CA Solution SHOULD support the ability for a patient or their authorized representative (e.g., caregiver, legal decision-maker) to request or trigger the creation of a Patient Summary, in accordance with jurisdictional policies and legislative provisions.	Approved

Use Case and Business Requirement Mapping

The following table provides traceability between the Use Cases and Requirements. The 'X' identifies that the requirement is either mandatory or optional in support of the use case.

Requirements	UC-01	UC-02	UC-03	UC-04	UC-05
	HCP Creates PS	HCP Views/Consumes PS	Patient Views/Consumes PS	HCP Creates a PS On-Demand	Patient Mediated Access and Exchange of their Patient Summary
BR1-01	X	X	X	X	X
BR1-02	X	X		X
BR1-03	X	X		X	X
BR1-04	X	X	X	X	X
BR1-05	X	X	X	X	X
BR1-06	X	X		X	X
BR1-07	X	X		X
BR1-08	X	X	X	X	X
BR1-09	X	X		X	X
BR1-10	X	X		X	X
BR1-11	X			X	X
BR1-12	X	X		X	X
BR1-13			X		X
BR1-14	X	X	X	X	X
BR1-15	X			X	X