eHealth requirements for MIS: what to consider in the interface

Bridge team · November 6, 2026 · 2 min read

What the official requirements say

• MIS connect to the central eHealth database and must pass testing for compliance with technical requirements.
• The list of MIS that passed testing is published on ehealth.gov.ua. The Ministry of Health advises facilities to choose from that list.
• Requirements are updated regularly: in 2026 changes covered security, e-prescriptions, access to patient records in the eHealth registry, registration of foreigners and staff records.
• The Ministry of Health also advises including in the developer contract that the MIS will implement future requirement changes.

What this means for the interface

Technical requirements describe which data and operations the system must support. How a doctor performs them is a design question — and it’s where MIS most often waste a doctor’s time.

• An appointment as clear steps: from reason for visit to signing, with a clear progress bar.
• The patient card always at hand, so doctors don’t switch between tabs.
• Checks before submission: the system warns about a mismatched diagnosis or a missing field before eHealth returns an error.
• Templates for frequent referrals and prescriptions.
• A clear qualified e-signature step: what exactly is being signed and what to do if the key can’t be read.
• Human error messages instead of technical eHealth response codes.

How we approach such projects

We start with an audit of existing screens and observing how doctors work, then map the appointment flow and test step-by-step forms on real scenarios. An example is our redesign of the MEDEIR medical information system.

This article is an overview for designers and clients, not legal advice. Always check the current requirements on ehealth.gov.ua.

Sources

• Ministry of Health of Ukraine: how a private facility should choose an MIS (in Ukrainian)
• NHSU updated technical requirements for MIS (Medplatforma, 2026, in Ukrainian)