Türkiye's rare-disease ecosystem has acquired an institutional state architecture over the past six years. Two reports — the Rare Lives and Rare Diseases Workshop 2026 and the Summit 2026 final reports — lay out its stones one by one: from the Directorate to the National Action Plan, from the Rare Disease Data System to e-Nabız integration and the ICD coding gap. This article maps Türkiye's rare-disease state architecture in full, addressing what each structure solves — and what it does not — together with the company perspective.
Building blocks: a chronology of founding
The architecture advanced on three parallel tracks. The administrative track: on 10 January 2020, the Directorate of Autism, Intellectual Disabilities and Rare Diseases was established within the Ministry of Health — the counterpart of patient organisations and a strategic unit planning health, education and social services together. The legislative track: in March 2020, two Parliamentary Research Commission reports were finalised — No. 199 (hard-to-treat diseases such as ALS, SMA, DMD and MS) and No. 200 (developmental disorders such as Down syndrome and autism). The coincidence of the Directorate's founding with Parliament's comprehensive field research sharpened the road map. The planning track: the Rare Diseases Action Plan — the first official document adopting the 1/2000 threshold — runs in parallel with the Second Autism Action Plan. This simultaneity is proof that the field grew on civil-society demand and that the state's response institutionalised.
The data problem: the ICD gap and non-mandatory recording
The reports' most concrete technical finding: current ICD coding cannot form specific diagnostic groups for rare diseases. Rare diseases are mostly buried in general ICD categories, complicating both clinical management and epidemiological counting. To close the gap, the Rare Disease Data System was established in 2022; but two structural obstacles are identified: data entry is below desired levels due to physician workload, and rare-disease records are not within a mandatory entry tied to reimbursement systems. The contrast is striking: records tied to reimbursement processes (prescriptions, billing) are kept regularly, while no mechanism encourages or obliges rare-disease-specific data entry. Remedies proposed include appointing data officers, developing registry systems and e-Nabız integration.
Functional classification: a Türkiye-specific coding proposal
One of the workshop's original proposals is to move beyond ICD insufficiency through a functional classification model: categorising diseases as preventable / treatable / preventable-treatable / undiagnosed patient group. The classification serves two purposes. First, resource management: tracking a disease with 1/2,000 prevalence and a case seen once in a million under the same operational plan strains the system; the legislator's prioritisation of treatable areas channels the constrained budget towards the highest clinical benefit. Second, prevention strategy: expanding screening programmes for "preventable" diseases — especially premarital carrier screening in Türkiye's demography of high consanguineous marriage — reduces both individual-health and public-finance burdens. For companies, the classification signals the priority lane in which their product will be assessed.
Coordination: the 34% cry and the Coordination Centre model
34% of Summit participants named inter-institutional coordination as the field's greatest deficit — ahead of technical, medical and financial constraints. The report reads this as the absence of a "top governance and alignment mechanism" and stresses that the leap will come not from singular moves but from an institutional governance reform. The workshop's concrete proposal is a Coordination Centre structure managing every stage from diagnosis to education, employment and social life. The field evidence is in the report: university centres have become the focus of direct patient applications (email, personal requests) in place of their policy-production purpose — centres trying to fill the referral vacuum lose sight of their core mission. The coordination-centre model carries that load into an institutional frame.
Digital and AI: a means, not an end
That data/digital infrastructure received only 4% in the survey is meaningful: for participants, digitalisation is not a "goal" but the instrument for reaching coordination and diagnosis targets. Leading digital agenda items in the reports: analysis of data in a wider pool through e-Nabız integration; national data standards (USVS work) and their technical implementation; artificial intelligence offering physicians "collective experience" by analysing large data pools; and the expectation that digital support will be among the most effective tools to minimise the diagnostic odyssey. A further notable finding is the 2021 Genetic Data Sharing Circular framing data sharing — data governance is part of the architecture's legal backbone.
The NGO ecosystem: the Federation's founding role
The architecture's third leg is civil society. The Rare Diseases Federation, organiser of the workshop and summit series, is the field's seated representative; in the reports' language, NGOs carry the process "where relevant ministries, NGOs and service institutions gathered around one table". The growth of the association and federation network breaks the ownerlessness connotation of "orphan"; in the report's words, these individuals are no longer alone in crowds. From the company perspective, the NGO ecosystem is the natural partner for patient-need mapping, awareness programmes and advisory-board processes — though collaborations must be designed within promotion-law and transparency principles.
What it means for companies: three takeaways
- National registry = data mine: as the Data System and e-Nabız integration mature, local prevalence and patient-flow data become accessible. Companies building relationships today with data officers, reference centres and the Directorate are constructing tomorrow's reimbursement file now. In rare-disease files, "Turkish data" is worth more than any imported assumption.
- Category-based strategy: the preventable/treatable split signals where resources will flow. In treatable groups early diagnosis will be the priority investment; in preventable groups, screening and awareness programmes — public and corporate collaboration areas — will grow. Carry your product's place in the functional category into your file language.
- Be a stakeholder in coordination: advisory work bridging reference centres, NGOs and the Directorate produces both visibility and access advantage. The survey's message is clear: the deficit is not resources but alignment; every contribution feeding alignment earns a place in the system's memory.
The institutional recommendation list from the reports
- Carrying the rare-disease definition and prevalence threshold into binding legislation.
- Integrating national registries into reimbursement processes, making them mandatory; appointing data officers.
- Authorising reference (excellence) centres by disease group, with TÜSEB accreditation.
- Shortening diagnosis times through specialised centres; expanding screening programmes.
- Establishing the Coordination Centre architecture; managing all stages from a single centre.
- Developing a Türkiye-specific functional ICD classification.
- Running national prevalence studies reflecting regional differences with methodological integrity.
How the data system should work: design principles
The problem the reports expose (voluntary, sparse data entry) is solvable only with sound design principles. Principle 1 — embed entry in the payment flow: if registration becomes a mandatory step of the reimbursement application, it is not extra work for the physician but part of existing work; "no registration, no billing" is the shared backbone of international registry practice. Principle 2 — minimum data set: the smallest meaningful field set for diagnosis, treatment, response and follow-up per disease group; bloated forms kill entry. Principle 3 — enter once, use many: the registry integrated with e-Nabız and hospital systems; the physician should never write the same data twice. Principle 4 — feedback loop: centres entering data should receive reports showing their own performance and the national picture; data flowing only "upward" depresses motivation. Principle 5 — quality indicators: missing-data rate, entry delay, follow-up loss — the system measuring its own health. Principle 6 — participation incentives: appointing data officers, training, and linking accreditation criteria to data quality. Companies should adopt these principles for their own registry investments too: putting sponsored registries on the same standard raises the standing of the data with the payer.
e-Nabız and USVS: integration practice
Two components of the national digital infrastructure stand out. e-Nabız: the integrated record of individual health data; the reports foresee integration for "analysis of rare-disease data in a wider pool". In practice this means diagnosis codes, laboratory and imaging history and medication use can be combined at patient level — a powerful ground for epidemiological measurement and drug-safety surveillance. USVS (national health data standards): the data-dictionary and format standards work, described in the reports as the infrastructure implementing those standards technically. Standards' existence means data from different institutions and centres can be combined — proliferating registries make sense only under a single standard. For companies, integration practice translates to this: when local data studies (expert opinion, registries) are designed to these standards, the data becomes comparable and verifiable against institutional systems — directly raising the standing of local evidence in the file.
Triple collaboration models: NGO-company-institution
The table drawn by the reports has three actors, and collaboration runs in four formats. (1) Policy studies: joint reports, road maps and action plans with specialty societies and the federation — the company's role being data and technical support, under independence and transparency principles. (2) Registry and data projects: naturalistic registry studies run with centres and NGOs, feeding the national system under the payer's oversight. (3) Awareness and education programmes: content support in physician and public education, within promotion-law boundaries. (4) Early-access and payment pilots: model agreements where payer and company meet on the NGO's map of patient need. The shared success conditions of these models are three: role clarity (who brings what), transparency (relations and contributions disclosed) and continuity (structured partnership, not one-off projects). The Summit process is the living example of meeting these conditions.
A measurement frame: how to track infrastructure development
To measure progress on the definition-data-coordination axes, the recommended indicator set: Definition axis: the prevalence threshold's legislative status (present/absent; in which document), the size of the defined disease list. Data axis: number of actively registering centres, annual registration volume, minimum-data-set completion rate, number of national prevalence studies. Coordination axis: number of authorised reference centres and disease-group coverage, establishment of the coordination mechanism, the NGO's place in official consultation processes. Access axis: the trend in diagnosis times (downward movement from the 6-7 year baseline), waiting time to treatment. A company tracking these indicators annually builds its rare-disease strategy on measurement, not assumption; the same set is also the board of the common language with institutions and NGOs.
Frequently asked questions: rare-disease infrastructure
- Under which ministry is the Directorate? Within the Ministry of Health, established 10 January 2020; the official counterpart of patient organisations.
- What does the Rare Disease Data System do? The national system established in 2022 to collect rare-disease diagnoses; its completeness is limited because entry is not mandatory.
- Why are ICD codes insufficient? Most rare diseases lack specific ICD codes; hence weakened counting, follow-up and research.
- Is the Action Plan binding? It has strategic-plan character; the debate over regulatory-level binding force is central to the reports.
- Which problem does the coordination centre solve? Managing all stages from diagnosis to education under one roof; preventing centres from drowning in patient load and families from getting lost in the system.
- How is e-Nabız used in rare diseases? Integration is targeted for integrated analysis of diagnosis, laboratory and medication data; access and governance rules are maturing.
- How does the company contribute to data systems? By building sponsored registries to the standards and supplying data in NGO-centre projects — under payer oversight.
- What is TÜSEB's role? In the reports it is positioned as the ecosystem's science base, with accreditation of excellence centres and analytical capacity.
International comparison: Türkiye's place
Three country experiences guide the comparison of rare-disease state architecture. France is among the first-generation examples with its national rare-disease plans (Plan National Maladies Rares); its reference-centre networks (BMRM) and patient registries support plan-period evaluation. Italy stands out with a national rare-disease network and registry infrastructure (RNMR) despite regional health systems; AIFA's payment mechanisms interlock with data. The European Union combines expertise pools by disease group through the cross-border ERN model, supporting member-state infrastructures. Türkiye's architecture is not the same age as these experiences but starts with two advantages: a strong digital backbone (e-Nabız) and an NGO ecosystem mature enough to set the table. The open area has been solved similarly in all three: the sequence definition → data → centre network → coordination. The reports' recommendation list is precisely the Turkish version of that sequence; company strategy should be timed to it as well.
Step by step: the company's rare-disease data strategy
The company's data strategy, parallel to infrastructure development, is built in six steps. Step 1 — Portfolio scan: which products sit in rare/ultra-rare indications; which data gaps block access. Step 2 — Source map: for each indication, existing sources (centre registries, NGO data, publications, e-Nabız potential) with reliability assessment. Step 3 — Prioritisation: which data investment returns fastest for which product (closest to file delivery). Step 4 — Investment decision: focus groups, registry sponsorship, publication programmes — each with defined evidence output and calendar. Step 5 — Participation and governance: protocols with NGOs and centres; payer oversight, ethical consent and transparency principles. Step 6 — Continuity: turning evidence generation into corporate capability — annual data plan, internal reporting and structured flow into files. The company that builds this strategy catches infrastructure developments (the data system, e-Nabız integration) prepared; the one that does not tries to adapt from scratch at every new regulation.
An NGO collaboration protocol: the transparency frame
In rare diseases, NGO collaborations are a company's most valuable and most sensitive asset; they must run by protocol. We recommend a five-article transparency frame. Article 1 — Purpose definition: the collaboration's subject (awareness, education, data, advisory) written and bounded; no scope creep. Article 2 — Independence: no interference in the NGO's institutional decisions; independent-committee approval of scientific content. Article 3 — Disclosure: declaration of the company's financial and non-financial contribution in corporate publications and, where required, NGO channels. Article 4 — Promotion boundary: no product name/indication promotion in joint content; the principle of disease-level information. Article 5 — Data and confidentiality: the source, purpose of use and KVKK/GDPR frame of shared data; third-party transfer conditions. The frame sits at the intersection of promotion law, KVKK/GDPR and industry codes; a collaboration compliant with all three endures. An NGO's credibility with the payer carries the standing of the company's data too — which is why the protocol is not a legal formality but a strategic investment.
Sources and key takeaways
Core sources: the Workshop 2026 and Summit 2026 final reports (legislation, data and coordination sessions); the Rare Diseases Action Plan; Parliamentary Commission reports (No. 199 and 200); Directorate announcements; e-Nabız and USVS documentation; the ERN model. Recommended monitoring: Directorate and TÜSEB announcements, the Federation agenda, e-Nabız integration news. Our key takeaways: (1) the architecture gained a strong skeleton in six years; the open ground is alignment across definition-data-coordination; (2) the data system works only when entry is embedded in payment flows (obligation + minimum set + integration); (3) functional classification (preventable/treatable) signals resource direction; (4) in the NGO-company-payer triangle the transparency protocol is a strategic investment; (5) the company data strategy should be the capability that anticipates infrastructure developments.
Conclusion
Türkiye's rare-disease architecture has gained a strong skeleton in six years — directorate, plan, parliamentary reports, data system and NGO network; yet the reports' shared finding is that the skeleton must be equipped with a coordination muscle. Every step on the three axes of definition, data and coordination directly affects companies' evidence production and access strategy. Sources: the Workshop 2026 and Summit 2026 final reports. For health data management and advisory-board organisation, see our Health Data and Information Management service and reach out.