From detailed guides to online courses – resources are available to provide you with the knowledge necessary to build and integrate EHR applications.

Example Relationships between Types of Standards

All of the types of standards listed above work together, and all are required in order for information to flow through the EHR. Document or content standards need messaging standards to describe how they will be transported between systems as well as terminology standards to accurately convey the information they contain in a way that can be interpreted and used by the other system. Messaging standards need transport standards to describe how they will be moved over the network. And all need privacy and security standards to ensure that information only goes to the places it’s meant to go, and is accurate and complete when it gets there.

For example, Integrating the Healthcare Enterprise (IHE) is an international initiative by health care professionals and industry to improve the way computer systems in health care share information. IHE does not create standards. Instead, it produces implementation guidance in the form of Integration Profiles, which describe a clinical information need or workflow scenario and document how to use established standards (e.g. HL7, DICOM, LOINC etc.) to accomplish integration of systems. 

This section provides high-level examples of the functions and supporting standards for a few of the EHR registries and repositories. 


Name Example Standards
Client HL7 v2 and v3 messages and terminology to support management and query/results for client identifiers and demographic data (e.g. adding a client, revising client demographic data, querying for a client record)
Provider HL7 v3 messages and terminology to support query/results for provider identifiers, profession, specialties, and demographic data (e.g. querying for a provider’s identifiers or specialization)
Consent HL7 v3 messages and terminology to support management of consent directives
Audit IHE ATNA based messages and terminology to support the automated collection of transaction logs associated with the collection, use and disclosure of PHI within eHealth Ontario systems



Name Example Standards
Clinical Documents HL7 v2, v3 messages and CDA, and terminology to support the management and query/response for many different types of clinical documents and reports (e.g. discharge summaries, assessments, consults)
Drug HL7 v3 messages and terminology to support prescribing, dispensing and management of medication information
Lab HL7 v2 messages and terminology to support the ordering of lab tests, provision of lab test results, and management of lab orders and results. LOINC is used to represent lab test result names.
Back to Top

Explore the Blueprint

Multiple views describe the many ways the blueprint supports EHR delivery.

Get Us Involved

From advisory consultations on blueprint alignment to standard selection, we can help you align, adopt and implement solutions.

Contact Us

Stay Up To Date

Published four times a year, the Blueprint Bulletin provides readers with regular insight into the elements, services and new developments associated with the Ontario eHealth blueprint.

Looks like you’re using an old browser.

To view this site, you’ll need to upgrade your browser.

Upgrade Now