CSA Z1635:22

Preface This is the first edition of CSA Z1635, Functional requirements and core data set for a Canadian paramedic information system (CPIS). This Standard provides the foundation and data framework for the development of a comprehensive Canadian paramedic information system (CPIS). It aims to facilitate standardized data collection related to paramedicine and to enable organizations to share their data, knowledge, and experiences with relevant stakeholders. CSA Group acknowledges that the development of this Standard was made possible, in part, by the financial support of the Justice Institute of British Columbia (JIBC) and British Columbia Emergency Health Services (BCEHS), under the Canadian Safety and Security Program, a federal program led by Defence Research and Development Canada’s Centre for Security Science (DRDC CSS) in partnership with Public Safety Canada. This Standard has been developed in compliance with Standards Council of Canada requirements for National Standards of Canada. It has been published as a National Standard of Canada by CSA Group. Scope 1.1 Inclusions This Standard defines a blueprint for the development of a CPIS, including functional characteristics and a core data set to support paramedicine. It provides guidance regarding data elements, data sharing requirements, and the information needs of key stakeholders. 1.2 Exclusions This Standard is not a CPIS. It provides the guidance to develop a CPIS and its associated data framework. CPIS stakeholder data sets are not included in the initial CPIS Standard. Future standards will address data sets focused on the particular data needs of specific stakeholder groups. Note: The Technical Committee plans to include requirements and definitions for wait times in a future edition of this Standard. 1.3 Terminology In this Standard, "shall" is used to express a requirement, i.e., a provision that the user is obliged to satisfy in order to comply with the standard; "should" is used to express a recommendation or that which is advised but not required; and "may" is used to express an option or that which is permissible within the limits of the Standard. Notes accompanying clauses do not include requirements or alternative requirements; the purpose of a note accompanying a clause is to separate from the text explanatory or informative material. Notes to tables and figures are considered part of the table or figure and may be written as requirements. Annexes are designated normative (mandatory) or informative (non-mandatory) to define their application.