From detailed guides to online courses – resources are available to provide you with the knowledge necessary to build and integrate EHR applications.
What is the value of Ontario’s ehealth blueprint to the health care system?
The blueprint helps guide the implementation of interoperable EHRs for the province, which will drive significant improvements to health care while reducing costs. It supports EHR planning and delivery by:
How will this view help in planning and implementing hospital and other ehealth systems?
The business view shows how you can leverage eHealth Ontario’s services, such as hosting, privacy, identify management, or health system use data, when planning and implementing hospital systems. These services can help reduce the cost of implementation and decrease time to market, while providing a richer dataset and seamless integration with other health care systems in the province.
What is the scope of the business view?
The business view specifically describes eHealth Ontario’s business, highlighting the services it offers to the health care sector while providing a framework that can be adapted by any stakeholder. The information and systems views, on the other hand, cover health care in the entire province.
What is the difference between ehealth services and support services?
eHealth Ontario provides services to two groups of stakeholders:
Ehealth services directly support health care sector stakeholders in providing health services
Support services support partners and vendors in developing ehealth services
How will the information view evolve over time in response to changes in health care?
Each new EHR program carries with it information requirements, some of which may be newly emergent or innovative. eHealth Ontario’s blueprint management process involves seeking and incorporating stakeholder feedback as well as ensuring that the blueprint evolves as new systems and solutions come online.
What are the benefits of aligning with the information view?
The information view shows how to you leverage a comprehensive set of province-wide ehealth information assets, such as health care client and provider information, client profiles, encounter records, etc., while identifying what information about a health care client is collected, included, and expected at any point in the health care system.
How will the information view help in planning and implementing ehealth systems?
The information view provides a model of the information involved in an EHR in Ontario's health care system. It serves as a reference for organizations building or buying ehealth solutions, reducing the time to design a solution, improving the quality of the solution, and ensuring integration with existing solutions. It also enables stakeholders to leverage a comprehensive set of provincial ehealth information assets. Specifically, the information view helps by:
How would the systems view help in implementing hospital and other ehealth systems?
The systems view is useful for planning, procuring and building new systems, as it gives hospitals and other stakeholders a holistic view of the critical components of Ontario's EHR including access points, registries and repositories, clinical data, and other eHealth Ontario services.
What is the difference between a registry and a repository?
A registry provides reference information about health care clients and providers as well as managing the identifiers associated with them. A repository is a store of clinical information such as lab test results, diagnostic images and reports, etc.
What are the benefits of using the provincial client and provider registries?
Registries and repositories contain reference and clinical information from hospital and community information systems. Instead of attempting to integrate these systems and repeatedly duplicating clinical data, one can use these registries to validate client and provider information, license status etc., bringing a standard approach to pushing and accessing data across the province.
Why do we need to go through the HIAL to get lab and other clinical data?
The HIAL offers a single point of access to and integration with the EHR, thus avoiding the cost and complexity of system-to-system integration. It provides a consistent approach to requesting information, authentication and authorization, consent and audit, and assembling the requested information with the correct terminology.
Multiple views describe the many ways the blueprint supports EHR delivery.
From advisory consultations on blueprint alignment to standard selection, we can help you align, adopt and implement solutions.Contact Us