Use cases

Use cases are designed to support the common data content standard and architecture products. These business scenarios provide an association to real-life encounters in a variety of health care settings such as primary health care, community health and hospitals. Clinical outcomes are numerous; as such, this use case narrative is meant to capture approximately 80% of the most common scenarios. Each use case sets the context of pre-existing conditions, defines the key actors and their interactions, and provides alternative outcomes to the encounter.

Development approach The use case development approach has drawn upon knowledge from several sources. These include an extensive pan-Canadian health care environmental scan along with input from experts with first-hand experience in clinical settings. These important features help to validate the architectural outputs that form the foundation for the common data content standard and architecture products of the Pan-Canadian Health Data Content Framework.

The audiences for the use cases are individuals with lived experience, people and communities, health care providers, governing bodies, organization leaders, researchers and technical users, as well as members of the public who would like to know more about the components of the data content standard and architecture products.

Each use case has the following structure: - Definition: Relevant definitions for each of the data categories pertaining to the use case are centralized in the PCHDCF Business Glossary. - Basic flow: The standard set of steps that patients (clients) and clinicians will go through in the use case. - Alternate flows: The steps that patients (clients) and clinicians will go through if different steps are required.

Each flow has the following sections: - Actors: Lists individuals involved in the use case. - Pre-conditions: Describes requirements to start the specific flow. - Post-conditions: Describes the result of the flow.

Use Case Template Each use case is in a standard template with the following headings: - Step: Identifies the sequence of the activity in the use case. - Description: Provides an explanation of the activities included in the use case step. - Data elements collected: Provides a list of the data elements recorded in each step of the use case. - Result: Describes the outcome of each step of the use case.