Overview

Medical events API is a set of web services designed to provide methods of communication between eHealth Medical Data Storage and medical information systems (MIS).

Concept

Medical events API is based on the international framework for exchanging digital health records - FHIR( Release 3 (STU)). Most of the major resources, data types, data structures and their way of interpretation are inherited from FHIR. However, there are minor сhanges described in Apiary.

Definitions and Statements

1. An interaction between the doctor and the patient (such as consultation) is represented using Encounter resource. Each encounter describes ONE SINGLE problem of the patient`s (represents ICPC event for Primary Care).
   A doctor can create several encounters during one visit.
2. Visit is an additional administrative resource that helps to group encounters that happened during one session of communication.
3. Encounters are also grouped by episodes of care. Episode of care - is a set of encounters related to one problem.
4. Encounters can go along with conditions, observations, immunizations, allergy intolerances.
5. To provide consistency of the data, collected during one encounter (including conditions, observations, immunizations, allergy intolerances), it should be submitted as one data package.
6. Physician is obligated to sign a data package with his(her) digital signature.
7. Visit is submitted as a part of the package but it is not to sign. (Visit is not mandatory in case of doctor created several encounters during one visit.)
8. Episode is not included to the package. It is created using a separate route and it is not to sign.

Sequence flow

In order to provide a consistency of submitted data the established flow should be followed:

See how async job processing performs here: Medical events Technical Documentation#AsyncjobprocessingSequencediagram.

Access to the resources are managed by ABAC module.

For all PATCH / POST methods, the display_value fields are filled in automatically by the System and can be seen later by the user on GET requests.

List of web-services