The following design constraints and assumptions for the Pan Canadian Patient Summary Interoperability Specifications v1 Trial Implementation
- All Use Case Actors/Users are logged into the system. The Use Case Actors/Users are authenticated and appropriately authorized for all data exchange transactions.
- Our recommendation is that the Use Case Actors/Users obtain a valid access token from the Authorization Server that is used within each transaction and is based on the IUA IHE Profile.
- Patient Summary-CA is created from local data sources for Release 1
- There may be exceptions to the source data of some of the data domains of the Patient Summary-CA across jurisdictions in Canada. For example, for some jurisdictions, the immunization data will be pulled from the provincial immunization repository.
- The implementation pattern in-scope for Release 1 will be based on the MHD IHE Profile. Additional details about this profile can be found in pan-Canadian Patient Summary – Companion Guide to Reference Architecture v1.
Additional information on design constraints and assumptions can be found in the Patient Summary – Companion Guide to Use Cases and Definitions.
Actor Mapping to Interoperability Specification
The Use Case Actors and the Services they support are described at a functional level in the Patient Summary – Companion Guide to Use Cases and Definitions. Services may be Mandatory, Recommended or Optional. The Use Case Actor, Service(s) and optionality are conveyed in the first three columns of Tables 1 to 3 in the section below.
The second part of the table (columns 4-7) provides the mapping for the Use Case Actor to the detailed specifications (such as IHE Profiles, Profile Actors, Optionality) that systems shall implement to exchange healthcare information in the context of these Use Cases.
For a selected Use Case Actor (a single row in the table), the system shall implement all the requirements (some optionality when allowed) listed in the second part of the table (columns 4-7). This includes the referenced healthcare profiles, the standards specified and terminology standards. For each Profile Actor (whether mandatory, recommended, or optional), the last column references the detailed specification the IHE profile for PS-CA requirements. These specifications may be found in Appendices to this specification document or in other referenced companion guides.
Legend
OPT = Optionality for the service supported by the use case actor and technical actors
M = Mandatory
R = Recommended
O = Optional
Table 1. Interoperability Conformance Requirements for Use Case 1: HCP Creates PS-CA
PS-CA USE CASE 1: HCP Creates PS-CA | MAPPING TO SECTIONS FROM THIS AND REFERENCED INTEROPERABILITY SPECIFICATIONS | |||||
---|---|---|---|---|---|---|
USE CASE ACTOR | SERVICE SUPPORTED | OPT | TECHNICAL ACTOR | OPT | PROFILE/ STANDARD | REFERENCED SPECIFICATION AND STANDARDS |
PS-CA Producer · | Authenticate User | R | Client (EMR) | R | Internet User Assertion (IUA) | Refer to Appendix A – IUA Profile Overview |
Identify Patient | O | Client (EMR) | R | Use Existing Standards Employed by the Clinical System | N/A | |
O | Patient Demographic Consumer | R | PDQm | Refer to Appendix A – PDQm Profile Overview | ||
Retrieve clinical data from local data sources | R | Client (EMR) | R | Use Existing Standards Employed by the Clinical System | N/A | |
Assemble and review Patient Summary | R | Client (EMR) | R | Use Existing Standards Employed by the Clinical System | N/A | |
Update Current Valuesets and ConceptMaps | O | Client (EMR) | R | SVCM | Refer to Appendix A – SVCM Profile Overview | |
Omit or Mask Data based on Jurisdictional Policy | O | Client (EMR) | O | Jurisdictional Requirement | N/A | |
Save PS-CA to Document Repository | R | Client (EMR) | R | Use Existing Standards Employed by the Clinical System | N/A | |
M | Document Source | M | MHD | Refer to Appendix A – MHD Profile Overview | ||
HIE Central Infrastructure | Identify Patient | O | Patient Identity Registry | R | PMIR | Refer to Appendix A – PMIR Profile Overview |
Document Repository (Local to PS-CA Producer or Central) | Save PS-CA to Document Repository | M | Document Recipient | M | MHD | Refer to Appendix A – MHD Profile Overview |
Table 2. Interoperability Conformance Requirements for Use Case 2: HCP Views/ Consumes PS-CA
PS-CA USE CASE 2: HCP Views/Consumes PS-CA | MAPPING TO SECTIONS FROM THIS AND REFERENCED INTEROPERABILITY SPECIFICATIONS | |||||
---|---|---|---|---|---|---|
USE CASE ACTOR | SERVICE SUPPORTED | OPT | TECHNICAL ACTOR | OPT | PROFILE/ STANDARD | REFERENCED SPECIFICATION AND STANDARDS |
PS-CA Consumer · | Authenticate User | R | Client (EMR) | R | Internet User Assertion (IUA) | Refer to Appendix A – IUA Profile Overview |
Identify Patient | O | Client (EMR) | R | Use Existing Standards Employed by the Clinical System | N/A | |
O | Patient Demographic Consumer | R | PDQm | Refer to Appendix A – PDQm Profile Overview | ||
Retrieve PS-CA from Document Repository | R | Client (EMR) | R | Use Existing Standards Employed by the Clinical System | N/A | |
M | Document Consumer | M | MHD | Refer to Appendix A – MHD Profile Overview | ||
Download/Print PS-CA | O | Client (EMR) | R | Use Existing Standards Employed by the Clinical System | N/A | |
Update Current ValueSets and ConceptMaps | O | Client (EMR) | R | SVCM | Refer to Appendix A – SVCM Profile Overview | |
HIE Central Infrastructure | Identify Patient | O | Patient Identity Registry | R | PMIR | Refer to Appendix A – PMIR Profile Overview |
Document Repository (Local to PS-CA Producer or Central) | Retrieve PS-CA from Document Repository | M | Document Responder | M | MHD | Refer to Appendix A – MHD Profile Overview |
Table 3. Interoperability Conformance Requirements for Use Case 3: Patient Views/Consumes PS-CA
PS-CA USE CASE 3: Patient Views/Consumes PS-CA | MAPPING TO SECTIONS FROM THIS AND REFERENCED INTEROPERABILITY SPECIFICATIONS | |||||
---|---|---|---|---|---|---|
USE CASE ACTOR | SERVICE SUPPORTED | OPT | TECHNICAL ACTOR | OPT | PROFILE/ STANDARD | REFERENCED SPECIFICATION AND STANDARDS |
Patient Portal · | Authenticate User | R | Client (EMR) | R | Internet User Assertion (IUA) | Refer to Appendix A – IUA Profile Overview |
Identify Patient | O | Client (EMR) | R | Use Existing Standards Employed by the Clinical System | N/A | |
O | Patient Demographic Consumer | R | PDQm | Refer to Appendix A – PDQm Profile Overview | ||
Retrieve PS-CA from Document Repository | R | Client (EMR) | R | Use Existing Standards Employed by the Clinical System | N/A | |
R | Document Consumer | R | MHD | Refer to Appendix A – MHD Profile Overview | ||
Render to Specific Format (PDF) | R | Client (EMR) | R | Use Existing Standards Employed by the Clinical System | Refer to pan-Canadian Patient Summary - Companion Guide to Reference Architecture | |
Download/Print PS-CA | O | Client (EMR) | R | Use Existing Standards Employed by the Clinical System | N/A | |
Save to Portable Media | O | Client (EMR) | R | Use Existing Standards Employed by the Clinical System | Refer to Appendix A | |
O | Portable Media Creator | R | XDM | Refer to Appendix A – XDM Profile Overview | ||
HIE Central Infrastructure | Identify Patient | O | Patient Identity Registry | R | PMIR | Refer to Appendix A – 6.5. PMIR Profile Overview |
PS-CA Producer | Retrieve PS-CA from Document Repository | M | Document Responder | M | MHD | Refer to Appendix A – MHD Profile Overview |
Document Repository (Local or Central) | Retrieve PS-CA from Document Repository | M | Document Responder | M | MHD | Refer to Appendix A – MHD Profile Overview |