Is a Wearable a Medical Device in Korea? Review Intended Use, App Functions and Risk

Key takeaway — Wearable describes how a product is worn. Start by stating who receives which output, what action it supports, and what happens if it is wrong. A watch or patch design does not establish the device class.

What separates medical use from wellness?

Article 2 of Korea's Medical Devices Act defines devices by purposes including diagnosis, treatment and prevention. Article 3 links classification to intended use and potential risk. The MFDS wellness assessment guidance revised in February 2026 likewise considers both intended use and risk.

A low-risk product supporting everyday activities requires a different assessment from a product evaluating disease or guiding clinical management. The guidance is an administrative interpretation resource, not a product approval or blanket exemption. It should not be used to unilaterally relabel a product already licensed, certified or notified as a medical device.

Can the same sensor support different regulatory outcomes?

The following examples help structure a development brief. They are not final classifications of individual products.

Proposed function	First question to resolve
Heart-rate and activity recording during exercise	Does it support only exercise and everyday wellness without medical interpretation?
Analysis of ECG or other signals for a particular disease likelihood	What clinical conclusion is produced, for which patient and user?
Movement tracking during sleep	Is it a lifestyle record or an assessment of a condition such as sleep apnea?
Skin-worn sensor linked to a hospital alert app	Which component analyzes the data, and what clinical decision uses the output?

The 2026 guidance includes a limited example of non-invasive optical sensing that displays blood-pressure or glucose trends as graphs or colors. It must satisfy the stated conditions, including no implantation, medical purpose, medical-device replacement or guidance for specific clinical action. Numeric measurement results and medical screening or diagnosis fall outside that example. Non-invasive sensing alone is insufficient.

How much of the device, app and server should be assessed together?

If the sensor collects data, the app displays it and a server estimates disease likelihood, a hardware manual alone does not show the product's actual use. Draw the flow from collection through transmission and analysis to output and user action. Identify the manufacturer, version and function at each step.

Distinguish storage or transfer from medical interpretation. An app that applies thresholds or presents disease likelihood needs a different description from one that merely moves data. Our SaMD guide addresses the software question; a wearable review must also connect that function to its sensor and combined intended use. Products designated as digital medical and health support devices require a separate check under the Digital Medical Products Act.

What risks should a wearable brief describe?

An everyday-health claim does not remove risk assessment. The guidance considers biocompatibility concerns, invasiveness or implantation, harm if the device fails, detection of critical conditions, and control or modification of a medical device.

Document the body-contact site and duration, adhesives and electrodes, cleaning and reuse, battery and charging conditions, and the displayed state when communication fails. A useful design question is whether the last recorded value remains on screen as if it were current after disconnection. These are assessment questions, not a universal test list. Function and risk determine the evaluation scope. Wireless requirements should also be reviewed separately through the KC and radio-certification guide.

What should go into a device-status review package?

A coherent package is more useful than a sales brochure:

1. An intended-use statement covering the user, setting, purpose and use of results.
2. Hardware structure, sensing principle, contact materials and specifications.
3. App and server functions, representative screens, analysis and alerts.
4. Proposed instructions, packaging and sales-page wording.
5. Consequences of malfunction, connection loss or incorrect output.

The guidance describes a status-review package built around intended use, shape, structure, materials, performance, use method, operating principle and specifications. First establish device status; where it is a device, then develop the item, class and applicable procedure.

What commonly goes wrong before launch?

Typical inconsistencies include calling the product wellness in engineering documents while claiming disease detection on the sales page, importing an overseas classification into Korea unchanged, or adding analysis through an app update while relying on the original assessment. A disclaimer does not reconcile contradictory intended uses.

Compare the assessed version with the actual launch functions, screens and claims. Send the manual, app screenshots and function list through our free pre-review. We can identify the wellness conditions still needing evidence and the functions that require a medical-device assessment.

Official sources checked 28 September 2026: Medical Devices Act, Articles 2 and 3, Act 21263, effective 1 July 2026; MFDS wellness assessment guidance 0091-03, revised February 2026, full attachment reviewed. The examples and package structure are practical review aids, not an official classification of a particular product.