Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
e-Nabiz is Turkey’s national personal health record, aggregating every citizen’s clinical data in one place, and MHRS is the central appointment system that books their care across public providers.

What Are e-Nabiz and MHRS?
Two national platforms carry most of Turkey’s citizen-facing health interaction. e-Nabiz is the personal health record operated by the Ministry of Health, into which hospitals, laboratories, imaging departments, pharmacies, and family practices report, so that a citizen’s clinical history exists in one consolidated place. MHRS is the central appointment system that books consultations across public hospitals and family practices, reachable through the web, a mobile application, and a national telephone line.
For a British reader the closest comparison is the NHS App combined with GP online services, but the architectural difference is substantial and it is the reason the security questions differ.
English health records are federated. A GP practice holds its record, a hospital holds its own, shared care records join some of them regionally, and access is controlled by role within each organisation, with the National Data Opt-Out governing secondary uses and Caldicott Guardians overseeing confidentiality decisions.
e-Nabiz centralises. One account holds a lifetime of prescriptions, diagnoses, laboratory results, imaging reports, and hospital visits. That design makes a genuinely useful thing possible, and it also concentrates risk: compromise of a single citizen account yields their complete medical history, not a fragment of it.
The compensating control is unusual and deserves credit. The patient, not the institution, grants clinical access. A doctor wanting to view the national record generally needs the patient to permit it, through a one-time code or a standing permission the patient manages, and the patient can inspect and revoke those permissions. Compared with the UK, where access control inside an organisation is a professional and contractual matter largely invisible to the patient, this puts a meaningful decision in the data subject’s hands.
Health data is special category personal data under Turkish Personal Data Protection Law No. 6698, with processing conditions narrower than for ordinary personal data, and the Ministry of Health maintains its own regulation on the processing of personal health data covering access, sharing, and retention within the health system. Breach notification follows the KVKK route, to the national authority and to affected individuals.
A UK organisation handling Turkish health data, for example an insurer, an occupational health provider, or a clinical research sponsor, should assume three things. Consent requirements are stricter than a UK team expects, because explicit consent carries more weight in the Turkish regime than it typically does under UK GDPR, where other lawful bases often serve. Transfers abroad run through the mechanisms introduced by Law No. 7499 from 1 June 2024 rather than through UK adequacy thinking. And the Ministry’s own rules apply in addition to general data protection law, so a KVKK-only assessment is incomplete.
The patient-granted access model is the part worth borrowing. Where a system consolidates sensitive records, giving the subject a visible, revocable permission mechanism and an access log they can read does more for trust than any amount of internal policy. The NHS has moved in this direction through the app, and Turkey’s implementation is a usable reference for what it looks like at national scale.
The caution worth borrowing is the opposite one. Consolidation makes the authentication layer the whole security model. If the gateway credential is phishable, everything behind it is phishable too, regardless of how carefully the health platform itself was built. At Privia Security, we test patient-facing applications and the services behind them through our mobile application security services.
The national record is designed so that a clinician generally needs the patient’s permission to view it, granted through a one-time code or a standing authorisation the patient controls and can withdraw. Clinicians retain access to records created within their own institution as part of providing care. The patient can review which permissions they have granted and when the record was accessed.
The NHS App gives patients access to a federated set of records held by different organisations, with access control managed inside each one and governed by professional duties, the National Data Opt-Out, and Caldicott principles. Turkey consolidates clinical data into a single national record and compensates with a patient-granted permission model. One optimises for distributed control, the other for completeness.
Personal Data Protection Law No. 6698 treats health data as special category data with narrower processing conditions, and the Ministry of Health maintains its own regulation on personal health data covering access, sharing, and retention within the health system. Both apply together, so a compliance assessment that considers only the general data protection law will miss sector obligations.
Yes, in a different way. Automated bulk booking of scarce appointment slots denies capacity to patients who need it, and the abuse pattern is the same one retailers see with limited stock. Defences are also the same: behavioural detection of automation, limits per identity, penalties for repeated non-attendance, and monitoring for booking patterns that no human would produce.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.