OntarioMD works with physicians, EMR
vendors, the Ministry of Health and Long-Term Care, eHealth Ontario and other
stakeholders, to develop and manage provincial EMR Specifications. The EMR
Specifications cover a range of clinical, business and technical requirements
that certified EMR offerings must
support. An EMR Specification may contain one or more documents that contain
all the necessary information an EMR vendor needs to know to implement the
EMR Specifications define a minimum set of consistent,
repeatable requirements and obligations that drive EMR maturity in three
- Foundation: e.g.: data,
identity, privacy and security, hosting
- EHR Connectivity and Tooling: e.g.: HRM, OLIS
e.g.: primary care baseline functionality, specialty specific requirements
New and/or updated EMR Specifications will be introduced
over time which will continue to advance the maturity of EMRs. EMR vendors with certified EMR offerings will
be notified of any pending/new/updated EMR Specifications and may be required
to update their EMR offerings and be validated on the incremental requirements
to maintain their EMR Certification status.
The following provides a brief overview and partial list of
EMR Specifications in each of their respective categories:
Purpose and Benefits
EMR Core Data Set
logical data elements that all certified EMRs support.
Helps ensure certified EMRs have the data required
to participate in the provincial EHR and enhance physicians’ use of EMRs.
EMR Hosting (for Hosted Offerings Only)
Defines requirements for the hosted EMR (e.g., application,
infrastructure, privacy & security, etc.) and business services the EMR
vendor must provide.
Addresses physician barriers to
adoption of ‘cloud-based’ EMRs by ensuring certified hosted EMRs are secure,
highly available, and meet performance targets.
EMR Data Migration
Defines how to
physically migrate a portion of a patient’s record from one EMR offering to
Helps physicians adhere to CPSO record keeping
policies and decrease EMR data migration time and costs by specifying the
data that needs to be migrated and the responsibilities of the stakeholders