Classification is done in two steps. The first step is definition: the product's intended use, the medical function declared by the manufacturer and the mode of action are read together; a product carrying a medical purpose enters the device definition. The second step is the rules: a product entering the definition is classified from I to III through a set of rules with criteria such as duration, invasiveness, energy use, body region and diagnostic-therapeutic role; on a rule conflict the highest class governs, and on duration the long-term use priority is essential. The class determines whether the notified body engages, the depth of clinical evaluation in the technical file and the registration-inspection practice. A defensible classification is built with written rationale: the applied rules, the eliminated alternatives and the product's technical nature gathered in one file. Classification is not done once and forgotten; it is reassessed as the product's intended use changes.
Whether a product counts as a medical device, and if so which risk class it falls into, single-handedly determines the product's regulatory fate: the class shapes the depth of the conformity assessment, the notified body requirement, the technical file's content, the clinical evidence expectation and the intensity of oversight. Türkiye applies the European framework for medical devices nationally; the classification discussion therefore runs over the common text of the device definition and the classification rules. Classification is not a technical labelling chore: the wrong class means the wrong conformity route; the wrong route means an invalid CE mark; an invalid mark means a noncompliance with no way back, at customs and in the market. This article explains the device definition, the risk-based classification rules, what the class changes, the borderline products, and how to build a defensible classification file.
Who is this for?
This guide is for every role facing the device definition and class question. Manufacturers and their representatives are the primary owner of classification; they build the decision file. Distributors must understand the class risks of the products in their portfolio, because class affects supply continuity and audit risk. Importers include the classification rationale in the customs file and must learn not to confuse device class with GTİP classification: one is a risk regulation, the other a tariff exercise. Regulatory teams prepare borderline product opinions. Quality units tie class changes into change management. Clinical research teams know how the investigating device's class affects the permit process. Procurement questions the class and document consistency of products from new suppliers. In an audit the question is crisp: by which rule and which rationale did you arrive at this class.
Which products does it cover?
The scope is all products entering, or capable of entering, the device definition: instruments, devices, software and materials for diagnosis, prevention, monitoring, treatment and support. The definition's core is intended use: the medical function the manufacturer declares on the label and in the instructions for use. Accessories are classified in their own right and pass through the rules like devices. Software enters the device definition when it carries a medical purpose; from decision-support systems to imaging software the same assessment runs. The borderline groups are known: general wellness products, sport and lifestyle measuring devices, cosmetic-purpose devices, biocidal products, personal protective equipment and general laboratory equipment. In these products a single phrase, a claim or a marketing sentence can create device status. On the GTİP side devices gather in one position family; but customs classification arises from composition and form, device classification from intended use and risk, and the two decisions must be kept in separate files.
When does it apply?
The classification assessment engages on several triggers. The first classification is made when a new product is prepared for market. When an existing product's intended use, label claim or patient population changes, the class is re-read; this is the most frequently missed step. Software updates can affect classification if they change the device's functional claim. When the device's role within a system changes, for instance a component becoming a standalone product, the assessment is renewed. A similar product classified differently in different markets is a borderline signal and must be resolved with rationale. Findings in inspections and market surveillance can bring the class question back. In import inspection the match between the class information in the document set and the technical file is checked. Commercial marketing texts are classification's silent enemy: a therapy claim added by the sales team can move the product up a class. The short rule: if the claim changes, the class is discussed.
Legal framework and authority
The frame is the European medical device regulation Türkiye applies nationally, and that regulation's classification-rules annex. The rules are built on risk-based logic: duration of use, degree of invasiveness, active-device character, place of use and diagnostic-therapeutic function feed the rules. For IVD products a separate regulation and a separate rule set apply; IVD classification is treated in its own article. The competent authority is TİTCK: it applies the legislation, gives opinions on borderline products, audits classification practice and oversees the conformity assessment processes. Notified bodies are party to the conformity assessment for higher-class products and confirm the classification in their own reviews. On the import side the class information enters the inspection document set. The regulation's current text and guides must be tracked from official sources; rule interpretations are clarified over time through guidance. A classification decision stays defensible as long as it rests on the rules and the product's documented characteristics.
Step-by-step process
- Extract the product's intended use from the manufacturer's documents: the medical function declared in the label, instructions for use and technical sheet.
- Run the device definition test: if the intended use carries a medical function the product enters the definition; write the rationale.
- Assess accessories and software components separately: each takes its own classification.
- Read the rule set systematically: note duration, invasiveness, energy, body region and function criteria one by one.
- Put the applied rule and the result in writing; also note why the unapplied rules do not apply.
- Where rules conflict, take the highest class; show the rationale with a conflict table.
- Determine the class's conformity assessment requirement: is a notified body needed, which evidence deepens.
- Bind the decision to the classification file: product description, rules, rationale, date and approving signature.
- Define the change triggers: when the claim, population or function changes, the file enters re-assessment.
Document checklist
- Product description card: intended use, function, place of use, duration.
- Manufacturer's label and instructions for use declarations, current version.
- Rationale for entering or not entering the device definition.
- Applied classification rules and the rule-to-criteria mapping table.
- Elimination rationale for the unapplied rules.
- Rule conflict assessment and the highest-class decision.
- Class table of accessories and software components.
- Class-driven conformity assessment requirement list.
- Classification decision form: date, signature, annex list.
- GTİP classification note; the file kept separate from device class.
Parties and responsibilities
| Party | Responsibility |
|---|---|
| Manufacturer / Authorised representative | Ownership of the classification decision and building the file |
| Regulatory unit | Rule reading, borderline opinions and rationale writing |
| Notified body | Including the classification in the assessment for high-class products |
| Distributor / importer | Carrying class information into the document set, claim tracking |
| Quality unit | Tying class changes into change management |
| Marketing / sales | Ensuring claim language does not alter the classification |
| TİTCK | Applying the legislation, borderline interpretations and inspection |
The table's critical row is the invisible one: marketing language. A therapy or diagnostic claim added in sales material counts as the manufacturer's declaration and can change the class. A classification check should therefore be added to the marketing approval flow.
Exceptions and edge cases
Borderline cases are classification practice's real exam. The line between a general wellness product and a medical device lies in the claim: the same physical product can be a device when declared to monitor heart health. The distinction between a cosmetic device and a medical device hides in the intended medical function. Personal protective equipment, when it carries a protective purpose, is the subject of different legislation; the difference between medical masks and surgical masks is the known example of this distinction. Biocidal products act by chemical action and are not devices. General-purpose laboratory equipment turns into a device when it carries the claim of producing medical results on medical samples. In software, the boundary between decision support and information presentation is drawn by the weight of the output in the medical decision. For sets and systems, the components must be assessed both individually and as a whole. For products with multi-stage intended uses, the highest-risk purpose governs. In every borderline case the tool is the same: a written analysis of intended use and a reasoned decision.
Common mistakes
The most common mistake is copying the classification from a benchmark product; products that look alike can sit in different classes with different intended uses. The second is deciding class I without reading the rules fully; sterile or measuring class I products are special cases and need care. The third is not assessing the accessory like a device; the accessory takes its own class. The fourth is dropping the software component from the file; purpose-driven software is a device. The fifth is not reflecting the marketing claim into classification; the label is clean but the brochure gives the game away. The sixth is keeping no classification file; the decision exists but not the rationale, and at audit the decision collapses. The seventh is not re-reading the class on product revisions; a small functional change can move the class.
Important notice
This article is general information, not legal or customs advice; for the classification of a specific product, the applicable legislation, guides and where necessary the competent authority's opinion must govern. GTİP codes and product examples in the text are for orientation; the GTİP examples are not binding, and customs classification is made separately from device classification. Legislation and guides can be updated; official sources must be checked before any transaction.
Frequently asked questions
What changes when the class rises?
The depth of the conformity assessment and the notified body's role change. In low classes the manufacturer's own declaration may suffice; in higher classes notified body review, the clinical evidence expectation and the technical file content deepen. Registration-inspection practice also tightens with class; market surveillance follows higher classes more closely. On the import side the class determines the document set's content and the questions asked at inspection. A class rise also affects the status of existing stock: a product marked under the old class, if it does not meet the new class's requirements, has its placing on the market halted.
Does a classification error invalidate the CE?
It does. The CE mark rests on the assumption that the applied conformity assessment route was chosen correctly; if the class is wrong the route is wrong and the mark loses its basis. This does not mean the product is physically defective; it is administratively and regulatorily invalid. The consequences are heavy: blockage at import, withdrawal and correction processes in the market. Classification is therefore done before, and as the foundation of, the conformity assessment. Where doubt exists, one should not proceed without a notified body or competent authority opinion.
Can the same product be in different classes in different countries?
The rule set is shared, but interpretations can diverge; this is common and solvable. The right approach is to find the source of the difference: a different intended-use declaration, a different rule interpretation, or a product version difference. If the difference arises from intended use, each market classifies under its own declaration. If it arises from interpretation, a reasoned analysis is made and, where needed, an authority opinion taken; consistency across markets is preferred. An undocumented difference returns at audit as an unexplained contradiction. If the difference is known, written and reasoned, it is not a problem.
When should the classification file be renewed?
If the trigger table is defined, it renews automatically: when the intended-use declaration changes, when a medical claim is added to the label or instructions, when the patient population or anatomical place of use changes, when software functionality is updated in a way that touches the medical outcome, when the product takes a role in a new system, and when marketing language widens the claim. Renewal works as a step of change management: in the change assessment the classification check is a mandatory row. If nothing changes, the file is reviewed annually and a review record is written; at audit even the answer "unchanged" must have its record.
Official sources
- Medical Device Regulation (EU) 2017/745, EUR-LexTİTCK / Ticaret Bakanlığı · verified 07 Sep 2026
- TİTCK Medical Device Clinical ResearchTİTCK / Ticaret Bakanlığı · verified 07 Sep 2026
- Product Safety and Inspection Communiqué AnnouncementsTİTCK / Ticaret Bakanlığı · verified 07 Sep 2026
Revision history
v1.1 · 07 Sep 2026 — Content import: external full text applied.
v1.0 · 15 Aug 2026 — Initial source-backed publication.