The requirements definition contains a consolidation of interoperability and solution requirements to support the pan-Canadian Patient Summary Interoperability Specifications. The requirements include:
- interoperability requirements which can be tested/validated through prototyping; and
- a broad set of requirements for consideration and to support and provide guidance to stakeholders in their PS-CA implementations. For example, supporting requirements may refer to local/jurisdictional policies and/or standards indicating that an implementer should validate specific requirement needs, if any, within a jurisdiction.
The requirements refer to a standardized expression of actors, entities, and user-system interactions, which will be further defined within the pan-Canadian Patient Summary - Companion Guide to Reference Architecture. Definitions of the terms used throughout the requirements may be found in the PS-CA Specification: Glossary of Terms & Acronyms.
Additional requirements may emerge and will be included in subsequent releases of the PS-CA specifications.
Requirements Structure
The Requirements have been defined within three categories (Business/Legal, Information Semantic, and Technical) and two subcategories (Interoperability and Solution), with three priority types (Shall, Should, and May), as described below:
Requirements Categories | |
---|---|
Business/Legal Requirements |
|
Information Semantic Requirements |
|
Technical Requirements |
|
Requirements Subcategories | |
Interoperability Requirements |
|
Solution Requirements |
|
Requirements Priorities | |
Shall |
|
Should |
|
May |
|
Shall not |
|
Requirements Identification
Each requirement is identified with a:
Requirement ID: The first 3 characters of the requirement ID (e.g., BR#) represents the category assignment, followed by "-##" representing the requirement number within the category. For example:
- BR1-001 = First requirement within the Business/Legal Requirements category
- BR2-001 = First requirement within the Information/Semantic Requirements category
- BR3-001 = First requirement within the Technical Requirement category
- Definition
- Requirement Subcategory: Interoperability or Solution
- Type (i.e., Priority): Mandatory, Recommended or Optional