As of 2020, all medical institutions that have concluded contracts with the NHSU under the medical guarantees program are required to send data to the central component of the electronic healthcare system. For this, the MIS used by these medical institutions must be connected to eHealth. The decision to connect an MIS is made by the State Enterprise “Electronic Health”: after testing the functionality for compliance with the technical regulations.
In the screenshot below, you can see the general Ehealth scheme as of 2021.
General scheme of the modules of the Administrator of the PMD and the Doctor's Workplace of the PMD of the Ehealth System
In general terms, to integrate one program into another, you need to integrate an API. And therefore, analyzing the documentation and API methods is very important.
The method documentation is available at the link https://ehealthmisapi1.docs.apiary.io/#reference/p...
But there is also a document whose requirements must be met when integrating an MIS into Ehealth
The complexity also lies in the fact that the structure and names in your program and in Ehealth - are different and need to be matched for integration.
For example, there is a process of maintaining medical records about a patient. In your system, a patient consultation may be called an "appointment", and these consultations are linked only by patient, while in Ehealth there is an "episode" that includes "visits". And until a diagnosis is made, the doctor does not close the episode.
In practice, for successful Ehealth integration, your program must meet the integration requirements. Let us give an example for the Episode.
The user must be provided with the ability to perform the following actions in accordance with the System API specification:
- create “Епізод МД” (method "Create Episode");
- find an MD Episode by search parameters;
- update parameters of “Епізоду МД” available for editing (method "Update Episode");
- mark an MD Episode as “введений помилково” (method "Cancel Episode") with the user's mandatory indication of “підстав визначення помилкового внесення ЕМЗ” (parameter "explanatory_letter") and indication of the reason (parameter "status_reason");
-close Епізод МД (method "Close Episode") with mandatory indication by the
user of “обґрунтування підстав закриття Епізоду МД” (parameter "closing_summary");
Episode validation https://e-health-ua.atlassian.net/wiki/spaces/EH/pages/583402023/Create+Episode
In addition to the main integrated functions and directories (diagnoses, list of declarations, employees, clinic departments, cities, streets, user roles, equipment, etc.), there must also be an electronic signature system. Since the doctor must sign the diagnosis, and this must be done with their key.
