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

Integration Principles

  • EHR services provide different types of service modes: these support external/public services including synchronous transactional data messaging services, asynchronous transactional data messaging services, synchronous business function services, portlet services, and batch services
  • EHR services have contracts based on web services and are discoverable: service contracts shall be stored in a single, well-known, accessible location, including contextual information (the service catalogue). Their names will describe their business functions and they will clearly define the expectations of service providers while providing service consumers a service infrastructure that is predictable, reliable, and managed.
  • EHR services are based on established standards and interoperability specifications: standardization (e.g. messaging, data types, terminology, communication) is associated with increased interoperability, reduced complexity and reduced operational and support costs, and so should be strongly encouraged. Messages are encapsulated into industry standard web services, and web services level features are used to control communication, reliable messaging and security.
  • EHR Services use a consistent set of interfaces and behaviours: the collection of external/public EHR services is offered as a consistent set of interfaces and behaviours, providing data and business services to organizations and application systems that consume its portlets and services.
  • Services to eHealth Ontario’s internal systems are abstracted from external service consumers: through this abstraction, the provincial EHR hides the complexity and heterogeneity of all its components (e.g. shared EHR resources). Consequently, these components can be upgraded, modified, or replaced with minimal or no impact to the applications that rely on them.
  • External/public services are secured: any service exposed to external access is vulnerable to attacks/penetration by unauthorized users, and must be protected through a series of security measures to identify and prevent malicious use.
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