14.04.26 (inclusive)

Under discussion

Idea

ICT tasks

Medical

Other technological solutions

Software/ IS

Currently, clinics are facing duplication of manual accounting and excessive workload on administrators. Records from external applications (for example, iDoctor) have to be transferred to the clinic calendar manually, which leads to human errors, data loss and low operational efficiency.

Creation of a gateway for automatic data exchange between DCH and third-party services (medical aggregators, external laboratories). The problem to be solved: Currently, clinics are faced with duplication of manual accounting and excessive workload on administrators. Records from external applications (for example, iDoctor) have to be transferred to the clinic calendar manually, which leads to human errors, data loss and low operational efficiency. The purpose of the development: Ensure seamless synchronization of the clinic's schedule with third-party lead generation services and automate the receipt of test results from partner laboratories. Expected effect: Elimination of double bookings (overlapping records), reduction of manual labor of administrators by 35-50%, acceleration of diagnosis due to automatic uploading of analyzes to the EMC. Roles: The administrator / Operator of the CC sees the source of the record (aggregator) in the calendar. The doctor gets access to the results of laboratory tests directly in the patient's chart. Superuser (DCH Admin) — configures API keys for integrations. Functional requirements: Automatic creation of an entry in the DCH calendar when booking a slot by a patient through the iDoctor app or similar. Two-way status synchronization (canceled in the aggregator = canceled in DCH, and vice versa). Receiving PDF files and structured data (JSON/XML) with analysis results from laboratories linked to the patient's IIN. Expected technical tasks: Backend (Node.js): Development of a Webhooks system for instant acceptance of incoming requests from aggregators. Database (PostgreSQL): Adding mapping tables for external IDs of doctors and services (from iDoctor) with internal IDs of the DCH system. Acceptance criteria: The entry through the aggregator appears in the DCH calendar with a delay of no more than 1 second. Overlapping records at the same time is not possible (the system locks a slot in all aggregators if it is occupied locally). The test results are automatically attached to the patient's EQ. Integrations: iDoctor API, API of partner laboratories (Olympus, Invivo, etc.).

Amina Agzamova