Horizon research dossier · Türkiye · Healthcare and life sciences · reviewed 2026-10-12
Türkiye health technology: a full decision dossier for a defined medical-device, diagnostic or digital-health route
Decision question: Under what evidence conditions should a medical-device, diagnostic, software, health-data, service or distribution proposition advance from Türkiye market research to a bounded commercial or technical proof?
Verified facts
Türkiye maintains a national product-tracking system, has a public reimbursement framework, and is building health-technology and local-production capacity. Those system facts do not establish registration, reimbursement, eligibility, hospital demand or a buyer route for a particular offer.
Horizon view
The market can support disciplined product- and buyer-specific work. The relevant unit is a precise intended use, regulatory classification, local operating role, funded care setting and documented route to acceptance; not a generic claim about the Turkish medtech market.
Commercial implication
Advance only after the proposed product or service, authorised local roles, UTS and other regulatory pathway, Turkish documentation, reimbursement or private-payor logic, procurement route, clinical and digital owners, integration, delivery, payment and post-market responsibilities are evidenced in writing.
Dossier sequence
01
1. Decision scope and non-claim boundary
This dossier is a decision instrument for one defined Türkiye health-technology proposition. It does not assess the whole health market and it does not recommend a distributor, hospital, manufacturer, regulator, technology, tender, investor or transaction. The initial file must specify the product or service, intended purpose, claim, user, care setting, patient or operational population, risk and classification hypothesis, commercial model, clinical outcome sought and commercial reason to stop. A device, in-vitro diagnostic, clinical software, workflow tool, data service, maintenance offer, consumable and consulting engagement have different regulatory, procurement and delivery pathways. National production, innovation or health-system statistics are context only. They do not prove a lawful market placement, a local representative, reimbursement, public-budget availability, data access, hospital interest, technical integration, accepted price or a contract.
02
2. Dated system context and what it cannot establish
The Ministry of Health reported at its May 2026 Medical Device Governance Summit that domestic production represented more than 31 per cent of public medical-device procurement and that the national product-tracking system covered approximately 5.3 million devices. Those statements are useful context for an environment in which local production, traceability and public purchasing are material. They do not say that a foreign product is excluded, that an offer has a local-content advantage, that a named facility has a budget or that a product can be placed on the market. TÜSEB also publishes 2026 research, innovation and local-production activity. Its mandate and programmes demonstrate ecosystem capacity and policy direction, not regulatory clearance or customer demand. Keep official statements, independently reported market estimates and product-specific proof separate; they answer different questions and should never be combined into a generic accessibility claim.
03
3. Product definition, intended use and classification gate
Before contacting buyers or preparing commercial material, write a controlled product statement: exact device, diagnostic, software or service; intended purpose; users; patient group; clinical setting; anticipated claims; interfaces; accessories; consumables; lifecycle; and whether the proposition is a standalone product or part of a combined solution. Determine the applicable Turkish regulatory category and the corresponding evidence requirements with a qualified local regulatory specialist. Türkiye has aligned relevant medical-device rules with EU MDR and IVDR concepts, while Turkish implementation and product-specific documentation still matter. A CE mark or a prior EU deployment is not by itself proof of Turkish classification, registration, language, promotional, import or establishment requirements. If the proposition is software, distinguish administrative workflow from software with a medical intended purpose; if it is AI-enabled, define the decision role and human oversight. No sample, demonstration, clinical claim or quotation should imply that classification or authorisation has been resolved before the responsible evidence owner confirms it.
04
4. Product Tracking System and regulatory-document route
Türkiye operates the Ürün Takip Sistemi (UTS), its national Product Tracking System. Official UTS access and Ministry guidance establish a real system boundary, while SGK material links product tracking to reimbursement administration. They do not disclose a complete product-specific submission file or confirm acceptance. The responsible manufacturer, authorised representative, importer, distributor or other local party must be identified before any process begins, together with their written authority and role. Build a document register for conformity evidence, quality-system documentation, declaration of conformity, technical file, labelling and instructions, device identifiers, certificates, vigilance and post-market material, translations, e-signature/portal requirements and renewal or change-control dates. Record issuer, version, language, product linkage, expiry and open question. A portal account, marketing statement or consultant assertion is not proof of a completed entry. A locally qualified reviewer should confirm the actual UTS sequence and evidence required for the defined product at the intended date of placement.
05
5. Turkish language, labelling, promotion and communication boundary
Product language and marketing are operational as well as regulatory questions. The European Commission language-requirements table identifies Turkish labelling and instructions-for-use requirements under the Turkish medical-device framework, subject to the relevant exceptions and product circumstances. That reference is useful orientation rather than a substitute for local legal confirmation. The project file must identify every customer-facing and professional-facing document: label, IFU, implant card where relevant, declaration, training material, website, brochure, clinical presentation, software interface, adverse-event notice and technical-service record. It must specify the approved Turkish version, translation owner, clinical and regulatory review, version control, distribution channel and withdrawal process. Advertising, comparative claims and patient-facing communication require particular caution. A distributor should not improvise translations or claims. For digital products, user-interface text and support workflows can themselves affect safe use; multilingual capability must be tested in the actual clinical workflow, not assumed from an English demonstration.
06
6. Reimbursement and price-access gate
The Social Security Institution (SGK) administers the national health-insurance system and its published material explains that covered medical devices and payment approaches are determined through the relevant framework and annexes. A June 2026 SGK notice also shows that the Health Implementation Communiqué can be amended. These sources establish that reimbursement is an administered, changing pathway; not a generic market fact. They do not show that a defined product is listed, that its code is matched, that a facility can bill for it, that the reimbursement level supports the offer or that the product will be chosen. For each proposition, separate market placement from reimbursement. Verify current coverage category, code/annex, price basis, application route, evidence expectations, responsible applicant, timing, review status, co-payment or additional-payment relevance, hospital billing implications and change risk. Private-provider, self-pay, research or donor routes may have different logic. No price, forecast or public claim should assume reimbursed access until current written evidence supports it.
07
7. Public procurement versus private-provider route
A product can be technically compliant yet lack a route to purchase. The file must classify the route before outreach: public hospital procurement, central or framework procurement, university/research setting, municipal or other public body, private hospital group, laboratory, distributor-led sale, insurer/payor arrangement, or a narrowly authorised study. The Public Procurement Authority and SGK announced an August 2026 protocol concerning electronic processes for certain foreign medicinal-product procurements; it is evidence of an institutional digital-procurement development, not a medtech tender or a general eligibility rule. Public procurement requires a live, exact notice, scope, procurement authority, eligibility, specification, amendment history, deadline, evaluation, contract and remedy path. A historical request for expression of interest, event, programme or memorandum is not a procurement opportunity. For private routes, identify the buyer, clinical owner, budget holder, evaluator, incumbent, pricing authority, payment terms and acceptance mechanism. Do not offer an informal pilot in the expectation that a policy reference will later become a funded contract.
08
8. Clinical, technical and facility acceptance architecture
Clinical relevance is not the same as a sale. Map the care pathway and accountable roles for the intended setting: facility legal entity, director, clinical lead, biomedical engineering, laboratory or service-unit manager, procurement office, information technology, cybersecurity, data-protection owner, finance, quality and risk function, installer, trainer, maintenance owner and final acceptance authority. Confirm site utilities, physical space, connectivity, workflow, infection-control or safety conditions, consumable supply, calibration, service response and end-of-life arrangements. A national strategy, summit or hospital logo cannot confirm these conditions at a named facility. The acceptance plan should state the baseline problem, technical specification, clinical/use-case criteria, installation and commissioning protocol, user training, performance measures, maintenance plan, incident escalation, warranty, return or removal procedure and the authority that signs acceptance. If one of these owners is unknown, the proposition remains a research case rather than a deployment plan.
09
9. Digital health, data and cybersecurity boundary
Türkiye has substantial digital-health infrastructure, and WHO system material offers useful independent context. It does not confer access to health records, an integration endpoint, patient data, an institutional mandate or a lawful cross-border data route. For any software, diagnostic, platform, AI, remote monitoring or data-enabled service, document the system of record, data categories, controller/processor roles, legal and contractual basis, consent or ethics question, localisation or transfer issue, hosting, user roles, authentication, minimum access, interface, audit logs, retention, deletion, incident response, cyber testing, service continuity and exit plan. Separate aggregate operational data from identifiable patient or clinician data. A sandbox should use authorised synthetic, de-identified or otherwise approved data until the appropriate legal, clinical and information-security checks are complete. A public-sector software procurement example cannot be reused as evidence for access to another system. Never represent an integration as available before its owner confirms the technical and governance conditions in writing.
10
10. Local commercial, import and service-delivery model
The local model must be more specific than “find a distributor.” Establish who is manufacturer, authorised representative, importer, registrant, customs declarant, stock owner, seller, installer, service provider, trainer, vigilance contact, complaint owner, recall contact, warranty obligor and invoice issuer. The role map should include legal identity, authority, country coverage, product scope, technical capability, quality process, storage conditions, spare-parts capacity, response-time commitment, insurance and ability to sign. The U.S. International Trade Administration market guide is a useful external operational reference on UTS, documentation and the distinction between registration and reimbursement; it is not a licence or a substitute for Turkish advice. Import, customs, storage and maintenance questions must be treated as product- and channel-specific. A partner’s general health-sector reputation does not prove it can lawfully sell, service or support a particular device or digital product. Do not grant exclusivity before a bounded route has generated independently reviewable evidence.
11
11. Counterparty, integrity and quality-system diligence
Every proposed representative, importer, distributor, hospital, laboratory, integrator, consultant, service partner and subcontractor requires its own diligence record. Verify legal identity, ownership/control where appropriate, signing authority, registration or licence claims, relevant product and service scope, quality-system documentation, technical staff, training, storage/service capacity, financial/payment ability, tax status, conflicts, sanctions and export-control screening, insurance, cyber posture, adverse-event and complaint capability, references matched to the offer, litigation or regulatory history where available and data-access controls. Record evidence source, confidence, reviewer and expiry date. A public body, global brand, development programme or personal introduction is not a substitute for diligence. A request to use an informal importer, bypass documentation, make unsupported clinical claims, share patient data or offer inducements is a stop signal. Partner diligence should be refreshed at material change, renewal, expansion or before any role involving regulated documentation, product custody, installation, data or money.
12
12. Commercial model, tender economics and payment protection
Price is meaningful only after the buying route and responsibilities are known. The commercial model should distinguish manufacturing price, freight, customs/import cost, registration and translation cost, distributor margin, stock financing, installation, configuration, integration, training, maintenance, warranty, spares, software subscription, cybersecurity support, insurance, tax, tender/bid cost, clinical-support cost, promotional restriction and contingency. Use a base and adverse case for tender delay, reimbursement non-listing, currency movement, payment delay, unsuccessful integration, site-readiness failure, additional support and warranty claim. Label every input as an attributable quotation, counterparty indication, official record or internal planning assumption. Public-procurement budgets and generic market-size estimates are not price evidence. The contract and purchase order must identify currency, tax, invoice and acceptance trigger, payment milestone, security, late-payment remedy, retention, claims limit, indemnity, product-liability allocation, warranty, support scope and termination. A profitable-looking list price can be uneconomic if service, working capital or acceptance responsibility is unpriced.
13
13. Controlled proof design
The first permitted step should answer one material uncertainty: regulatory-gap assessment, non-clinical workflow review, facility readiness assessment, interoperability assessment using approved non-production data, technical demonstration, training design, limited installation study, reimbursement evidence map or commercial diligence exercise. It should not imply unrestricted clinical deployment, broad system access, reimbursement, procurement preference, patient-data processing, distributor appointment or a future award. The written charter must state parties, site or system, product version, authorised use, data boundary, clinical governance, safety and cyber controls, materials, staff, cost allocation, insurance, intellectual-property treatment, performance and acceptance measures, communications restriction, timeline, change control, exit plan and stop condition. A meeting, demonstration, letter of interest or policy reference is not a proof. A successful proof applies only to the named setting and controlled conditions; it cannot be presented as a hospital-group, national-system or market-wide approval.
14
14. Risks and stopping conditions
Key risks include wrong classification or intended-use claim, incomplete UTS or documentary pathway, unsuitable Turkish labelling, unapproved promotion, reimbursement mismatch, tender ineligibility, unclear authority, lack of facility readiness, unsafe or unsupported use, product or data-security failure, unapproved data transfer, insufficient service coverage, local-partner conflict, customs/storage error, uninsurable liability, delayed payment, currency movement, quality-system weakness and reputational misuse of public institutions. For each risk, record source, owner, likelihood, impact, mitigation, residual exposure, review date and explicit stop trigger. Stop or hold before placing a product on the market, issuing a clinical or economic claim, submitting a bid, importing commercial stock, accessing patient or operational data, commencing installation, granting exclusivity, extending credit, naming a public institution or announcing a partnership if the corresponding regulatory, authority, data, quality, financial or contractual evidence is incomplete. A well-documented hold is a valid output of this dossier.
15
15. Final decision gate
Advance only when the exact product/service and intended use, applicable regulatory path, accountable local roles, product-tracking and documentation status, language package, reimbursement or private-payment route, named buyer system, live procurement or private-commercial path, clinical and technical acceptance, data/cyber control, capable delivery structure, counterparty diligence, risk allocation and bounded proof align. The decision record must attach dated facts, Horizon interpretation, unresolved issues, required specialist confirmation, authority matrix, document register, source log, cost cap, pilot charter, risk register, permissible next action and re-review date. It must state go, hold or stop. A go decision authorises only the bounded step described; it does not approve registration, reimbursement, product placement, patient-data processing, tender eligibility, integration, representation, partner appointment, contract or transaction. Reopen the decision whenever the product, claim, regulation, buyer, facility, procurement, data boundary, local party or commercial model changes materially.
What to verify before acting
This completed research dossier is not Turkish medical-device, diagnostic, digital-health, product-safety, reimbursement, public-procurement, health-data, cybersecurity, customs, tax, insurance, clinical, regulatory or legal advice. It does not establish a classification, registration, UTS entry, reimbursement, product placement, tender eligibility, data-access permission, hospital budget, distributor appointment, technical acceptance, payment, contract or transaction.
Current market intelligence
Signals connected to this dossier
2 October 2026
Turkic health ministers adopt a 2026 to 2027 cooperation agenda covering medicines, workforce and digital health
For an authorised health, medtech, pharmaceutical, training or digital-health case, select one country and one use case first. Map the responsible ministry, purchaser, provider, regulator, data owner and clinical owner; identify the relevant product classification, registration, import, standards, language, reimbursement, procurement or private-contract route; confirm data, interoperability, security, consent and cross-border-care boundaries; and document local installation, training, maintenance, vigilance, insurance, invoice, payment and claims ownership. Track the action-plan implementation only through current official records and written authority from the responsible institution.
30 June 2026
Türkiye places medical-technology localisation and strategic cooperation on its health-industry agenda
Build a Türkiye medical-technology file per product or service: intended use and classification; manufacturer, authorised representative and local operator; UTS/quality/evidence position; local design, component, production and test roles; clinical engineering, installation, maintenance and training; data and cybersecurity boundary where relevant; reimbursement, public tender, DMO, private-hospital or distributor route; localisation/technology-transfer structure; price, currency, warranty, liability, insurance, payment and after-sales controls. Confirm the current regulatory and procurement route with the responsible authority and qualified local specialists before presenting a product, local-manufacturing, hospital-access, price or partnership proposition.
22 April 2026
Türkiye updates the electronic-instructions framework for medical devices
For an authorised Türkiye device case, build a documentation-and-market file: exact device and intended use; regulatory classification and UTS position; manufacturer, authorised representative and distributor roles; current labelling and IFU version; language, accessibility and user-interface requirements; electronic access, availability and cybersecurity; quality-system ownership and change control; hospital, pharmacy, distributor or private-provider route; installation, service and training; complaint, vigilance, recall and data records; price, warranty, insurance, payment and contracting. Obtain current specialist and authority confirmation before changing instructions, launching a digital interface, shipping stock, promoting a device or making a compliance statement.
Relationship platforms