Data mapping resources
Resources to assist HIS-users in mapping their system to the MHA PDS specification.
| Resource | Purpose | File |
|---|---|---|
| MHA PDS Logical Data Dictionary | All data elements and code tables for most up to date version of MHA PDS 1.0. | |
| HIS to PDS Data Mapping Template | Based on Logical Data Dictionary; template designed to assist providers in mapping data elements collected within the hospital information system to the MHA PDS submission solution. | |
| Reference Data Dictionary | Readable format of Data Dictionary; includes background information on MHA PDS and greater emphasis on data collection tips. Note: please see Logical Data Dictionary or Mapping Template for up to date functional centre list (including 713 codes) | |
| Functional centre list | Some ambulatory functional centres (713 *) were added to the MHA PDS to accommodate more hospital services. |
Implementation guides
Resources to assist in developing a FHIR submission for the MHA PDS.
| Resource | Purpose | File |
|---|---|---|
| Vendor Implementation Guide | Guidance for FHIR implementation of MHA PDS specification. Please read. | |
| MHA PDS HL7 FHIR IG | Business context, use cases and business rules, as well as FHIR profiles including structure definitions (JSON), operations, examples (JSON), terminologies, identifiers, and conformance requirements for submitting data using HL7 FHIR® Please defer to Vendor Implementation Guide (above) when questions arise. | Ontario Mental Health and Addictions Provincial Data Set HL7® FHIR® Implementation Guide – DRAFT v0.9.2 |
Connectivity documentation
Resources required to connect to the ONE Access Gateway (OAG) through OAuth2.
| Resource | Purpose | File |
|---|---|---|
| OAuth and OAG Provider Integration Guide | The purpose of this document is to provide guidance to Clients on how Client Applications can achieve integration with Ontario Health’s ONE Access Provider Gateway (OAG) when using Tokens obtained from Ontario Health’s Open Authorization (OAuth) service. | |
| OAuth2 Specification | This document contains a general overview of OpenID Connect (OIDC) and the way it is set up and used with the ONE ID Provincial Federation Model. OIDC comprises the OAuth (Open Authorization) 2.0 protocol for authorization purposes and the OpenID protocol for authentication purposes. The document builds upon the generally available OAuth 2.0 and OpenID specifications by detailing the attributes and values necessary for participation in the ONE ID federation. |
Security requirements
The following tests/assessments are required to be performed on the MHA PDS submission solution prior to go-live.
- Penetration Test Report
- SOC2 Type 2 Audit report or 3rd party security assessment report (i.e. TRA)
- No outstanding critical or high level risks prior to production connectivity
- Committed to address any medium level risks within agreed upon timeframe
