Mobile Applications as Medical Devices in Serbia (2026 Guide)

Is Your App a Medical Device — and Why Does It Matter?

This guide was prepared by Petar Kilibarda and Miomir Stojković, attorneys at Stojković Attorneys, with experience in regulatory matters concerning medical devices and digital health solutions.

Digital health is evolving rapidly. At the same time, a key legal question arises, particularly for companies entering the Serbian market: does your product qualify as a mobile app medical device in Serbia?

The answer has direct and practical implications for your business, including:

• the ability to lawfully place your product on the market
• the scope of regulatory obligations
• development and commercialization costs
• legal risks, including potential prohibition from market placement

In practice, incorrect legal classification often leads to significant consequences, particularly at the stage of market entry or business scaling.

In this guide, we explain how mobile applications are legally classified in Serbia, based on the applicable Law on Medical Devices, and how to identify regulatory obligations at an early stage.

Mobile App Medical Device Serbia: When Does an App Qualify?

In the context of mobile app medical device Serbia regulation, the starting point for the legal classification of mobile applications is the definition of a medical device under the applicable Serbian Law on Medical Devices.

The law explicitly provides that software may qualify as a medical device, provided that it is intended by the manufacturer for specific medical purposes.

In practice, this means that a mobile application falls within the medical device regime if it meets two key criteria:

1. It Has a Medical Purpose (Intended Purpose)

The software must be intended for one or more of the following:

• diagnosis of disease
• prevention or monitoring of health conditions
• prediction or prognosis of disease
• treatment or alleviation of symptoms
• processing and interpretation of medical data

These functions correspond to legally recognized diagnostic, therapeutic, and related medical purposes.

2. Its Primary Mode of Action Is Not Pharmacological, Immunological, or Metabolic

Unlike medicinal products, a medical device (including software) does not achieve its primary intended purpose through biological interaction with the human body.

Instead, its function is technical or informational.

In the case of software, this typically includes:

• data analysis
• generation of outputs or recommendations
• support for decision-making

How This Definition Applies to Mobile Applications

This distinction is particularly important in the context of mobile app medical device Serbia regulation, where functionality and intended use are decisive. In practice, the key factor is not the technology itself, but how the application is designed and presented.

In other words, it is not decisive whether the product is:

• a mobile application
• a web platform
• or an AI-based system

What matters is:

• what the application does
• how it is used
• and for what purpose it is intended by the manufacturer

As a result, two technically similar applications may have completely different legal classifications.

The Importance of the Manufacturer’s Intended Purpose

The law emphasizes that intended purpose is determined based on:

• product labeling
• instructions for use
• promotional materials

This means that legal classification depends not only on functionality, but also on how the product is presented to the market.

In practice, this element is often decisive in determining whether an application will be treated as:

• unregulated software, or
• a medical device subject to full regulatory requirements

Accordingly, a mobile application will be considered a medical device if:

• it has a clearly defined medical purpose, and
• it achieves that purpose through data processing or support for medical decision-making

These two criteria form the basis for further regulatory analysis.

When a Mobile Application Is — and Is Not — a Medical Device

After understanding the legal definition, the next step is its application in real-world scenarios. In practice, the boundary between a medical device and standard software is often not obvious.

For that reason, it is useful to look at typical examples.

When a Mobile Application Is — and Is Not — a Medical Device

When a Mobile Application Qualifies as a Medical Device

In many cases, a product will qualify as a mobile app medical device in Serbia when its functionality goes beyond general informational use.

This is typically the case when the application:

• analyzes medical data (e.g., laboratory results, ECG data, vital parameters)
• provides recommendations for treatment or further medical action
• assesses the risk of disease or predicts the development of a condition
• supports healthcare professionals in making diagnostic or therapeutic decisions

In such cases, the application has a direct or indirect impact on the user’s health, which is the key factor for its classification as a medical device.

When a Mobile Application Is Not a Medical Device

Conversely, an application will not be considered a medical device if it lacks a medical purpose within the meaning of the law.

This typically applies to applications that:

• track general wellness without medical interpretation (e.g., step counters, calorie tracking)
• function as reminders or organizational tools (without providing recommendations)
• provide general educational information about health
• allow users to record personal data without analysis or conclusions

In these scenarios, the application does not influence diagnosis, treatment, or medical decision-making, and therefore falls within the category of wellness or lifestyle software.

Grey Area: When Classification Depends on Specific Features

Most practical challenges arise in the grey area between these two categories.

Typical examples include:

• therapy tracking applications that also provide recommendations
• AI-based tools that “only suggest” but influence user behavior
• platforms combining educational content with data analysis

In such cases, legal classification depends on:

• the scope of functionality
• how the product is presented
• the actual impact on the user or healthcare professional

Even minor changes in functionality or wording (e.g., “information” vs. “recommendation”) can lead to a different regulatory outcome.

Key Takeaway

The boundary between a medical device and standard software is not determined by the technology itself, but by its function and intended purpose.

For that reason, a careful legal assessment is essential in each individual case, ideally before the product is placed on the market.

Practical Legal Test: How to Determine the Status of Your App

After understanding the legal definition and typical examples, the practical question arises: how can you quickly and reliably determine whether your mobile application qualifies as a medical device? So, this framework is widely used to determine whether a product falls under mobile app medical device Serbia rules.

In regulatory practice, the answer comes down to a small number of key questions.

1. Does the Application Have a Medical Purpose?

The first and most important question relates to the intended purpose of the product.

You should assess whether the application is designed for:

• diagnosis, monitoring, or prediction of disease
• treatment or alleviation of symptoms
• processing and interpretation of medical data

If the answer is yes, this is a strong indicator that the application falls within the medical device framework.

In particular, the decisive factor is how the manufacturer defines and presents the intended purpose in documentation and market communication.

2. Does the Application Influence Medical Decision-Making?

The second question relates to the practical effect of the application.

You should consider whether the application:

• provides specific recommendations or conclusions
• guides the user toward certain actions or treatment decisions
• influences decisions made by healthcare professionals or patients

If such influence exists, even indirectly, it is a key factor supporting classification as a medical device.

By contrast, applications that only display data without interpretation or recommendations will generally not meet this criterion.

3. Does the Application Process Medical Data in a Way That Generates Conclusions?

The third question focuses on how data is processed.

A critical distinction must be made between:

• simple display or transmission of data, and
• analysis that produces new conclusions or assessments

An application that analyzes data and generates outputs (such as risk scores, classifications, or recommendations) crosses the threshold into the regulated domain.

How to Apply This Test in Practice

If the answer is “yes” to one or more of these questions, there is a high likelihood that the application qualifies as a medical device.

In such cases, it is advisable to:

• conduct a detailed legal assessment
• define a regulatory strategy (classification, conformity assessment, registration)
• align documentation and product positioning

Important Note

This test serves as a practical tool for initial assessment.

However, the final classification always depends on the specific circumstances, including the product’s functionality, technical documentation, and actual use.

That said, in many cases, a structured set of the right questions is sufficient to identify the regulatory status of the product.

Common Mistakes and Legal Risks in Practice

In the field of digital health, the legal classification of products is often underestimated at the early stages of development. However, it is precisely at this stage that mistakes occur, which can later lead to significant regulatory and commercial consequences.

Based on practical experience working with various types of medical devices, including software and mobile applications, the following issues are among the most common.

Mispositioning a Product as a “Wellness” Solution

One of the most frequent mistakes is attempting to present an application as a wellness or lifestyle product, even though its functionality has a medical character.

This typically occurs when the application:

• analyzes health or biometric data
• provides recommendations to the user
• influences decisions related to health

In such cases, formal positioning does not change the legal nature of the product.

Regulators will assess the product based on its actual functionality and intended purpose, in line with the applicable Law on Medical Devices.

Reliance on Disclaimers and Wording

Another common approach is attempting to avoid regulatory classification through statements such as:

• “this application does not provide medical advice”
• “the information is for educational purposes only”

However, if the functionality of the application suggests otherwise, such disclaimers are not decisive.

In practice, the substance and real-world effect of the application prevail over formal wording.

Underestimating the Impact of AI and Algorithms

Applications that rely on algorithms or artificial intelligence present particular challenges.

Although often described as tools that “only assist,” in reality they may:

• generate conclusions
• influence user behavior
• guide decision-making

As a result, they may cross the threshold into the medical device category, even when this was not the developer’s initial intention.

Failing to Identify the Right Regulatory Timing

Another common mistake is postponing legal assessment until a late stage of development or immediately before market entry.

At that point, the need for:

• additional documentation
• conformity assessment procedures
• changes to product functionality

can significantly delay or complicate commercialization.

Ignoring Differences Between Markets

Products developed for other jurisdictions are often introduced into the Serbian market without proper analysis of local regulatory requirements.

Although there is a high degree of alignment with European standards, in practice it is still necessary to:

• complete local registration steps
• adapt documentation
• understand the role and expectations of the national regulator

Key Takeaway

The most significant legal risks related to mobile applications do not arise from the complexity of the regulations themselves, but from incorrect assumptions made during the early stages of product development.

For that reason, a timely and well-structured legal assessment is essential for:

• avoiding regulatory obstacles
• planning product development efficiently
• ensuring a smooth and compliant market entry

What If Your Application Is a Medical Device: Regulatory Steps in Serbia

If your product is classified as a mobile app medical device in Serbia, a structured regulatory process must be followed. So, once it is established that a mobile application qualifies as a medical device, the next step is to understand the regulatory pathway required for its lawful placement on the Serbian market.

This process is governed by the applicable Law on Medical Devices and involves several interconnected steps.

1. Classification of the Medical Device

The first step is to determine the risk class of the product.

Classification depends on:

• the intended purpose of the product
• the manner of use
• the potential impact on the user’s health

For software, classification typically depends on:

• whether the application influences medical decision-making
• the significance of those decisions for patient health

This step is critical, as it determines the applicable regulatory pathway.

2. Conformity Assessment

Following classification, a conformity assessment must be carried out to demonstrate compliance with essential requirements.

This includes:

• demonstrating the safety and performance of the product
• preparing technical documentation
• assessing compliance with applicable standards

Depending on the risk class, this process may be conducted by:

• the manufacturer (for lower-risk devices), or
• a notified or authorized conformity assessment body

3. Technical Documentation

The manufacturer is required to prepare and maintain technical documentation covering:

• a description of the product and its functionality
• risk analysis
• clinical or other relevant data
• evidence of compliance with essential requirements

For software, particular attention should be given to:

• the description of algorithms and decision logic
• data processing methods
• change management (updates and version control)

4. Registration and Competent Authority

To place a medical device on the Serbian market, it is necessary to complete the relevant procedure before the Medicines and Medical Devices Agency of Serbia (in Serbian ‘Agencija za lekove i medicinska sredstva Srbije’).

This typically includes:

• entry into the national register of medical devices
• submission of required documentation
• possible recognition of foreign certificates

Without completing this step, the product cannot be lawfully placed on the market.

5. Post-Market Obligations

Regulatory obligations do not end with registration.

The manufacturer must:

• monitor product performance in real-world use
• report incidents and potential risks
• implement corrective actions when necessary

This phase, known as post-market surveillance, is particularly important for software products that are regularly updated.

6. Specific Note for Foreign Manufacturers

If the manufacturer is not established in Serbia, it is necessary to appoint an authorized representative.

This entity:

• acts on behalf of the manufacturer
• participates in regulatory procedures
• assumes part of the responsibility for product compliance

Key Takeaway

The regulatory pathway for mobile applications as medical devices is not a formality, but a structured process requiring both legal and technical alignment.

When properly implemented, it enables:

• lawful market entry
• reduced legal risk
• stable and sustainable business operations

Conclusion

Mobile applications in healthcare operate at the intersection of technology and regulation. Although they may appear to be standard software products, their legal classification depends on their specific function, intended purpose, and impact on the user.

Under the applicable legal framework, the distinction between unregulated software and a medical device is not determined by form, but by substance and effect.

For that reason, early and accurate legal assessment is essential.

It allows for:

• clear definition of the regulatory pathway
• avoidance of delays at market entry
• optimization of development time and costs
• reduction of legal and business risks

In practice, the difference between successful market entry and regulatory complications often comes down to asking the right questions at the right time and correctly interpreting the applicable rules.

Frequently Asked Questions (FAQ)

Does every healthcare mobile app qualify as a medical device?

No. A mobile application is considered a medical device in Serbia only if it has a medical purpose, meaning it is intended for diagnosis, monitoring, treatment, or supporting medical decision-making under the applicable Law on Medical Devices.

Do AI-based applications automatically fall under medical device regulations?

Not automatically. However, if an AI application generates conclusions or recommendations that influence healthcare decisions, it is highly likely to be classified as a medical device.

Is a disclaimer (“this app does not provide medical advice”) sufficient?

No. Regulators assess the actual functionality and real-world use of the application, not just disclaimers or wording in the product description.

Is a therapy tracking app considered a medical device?

It depends. If the app only provides reminders, it is generally not a medical device. However, if it gives recommendations or influences how therapy is applied, it may fall under the medical device regulatory regime.

Is registration in Serbia required if the app already has a CE mark?

In most cases, yes. Even if the application has a CE mark, placing it on the Serbian market requires a procedure before Agencija za lekove i medicinska sredstva Srbije.

When is the right time to perform a legal assessment of the app?

As early as possible. Ideally, the legal assessment should be conducted during the development phase to avoid regulatory issues, delays, and additional costs at the time of market entry.

Can a foreign company place a health app on the Serbian market?

Yes, but typically through a local regulatory process, which may include appointing an authorized representative and completing registration requirements.

How We Can Help

Stojković Attorneys (STATT) have extensive experience working with various types of medical devices, including software and digital health solutions.

In this context, we provide support in:

• legal qualification of your product
• defining a regulatory strategy
• preparation of technical and regulatory documentation
• registration procedures before Agencija za lekove i medicinska sredstva Srbije
• compliance with Serbian and relevant international standards

If you are developing a mobile application or planning to place it on the Serbian market, it is advisable to conduct an initial legal assessment before further investment and commercialization.

For an initial review, a brief description of the product’s functionality and intended purpose is usually sufficient.

Based on this, it is possible to determine:

• whether the application falls under the medical device regulatory regime
• which regulatory steps are required
• how to structure further development and market entry

For additional information or an initial assessment, you can contact us via the contact form on our website, by email at [email protected], or by phone at +381 11 328 19 14.

Authors

This article was prepared by:

Petar Kilibarda – Lead legal advisor at Stojković Attorneys for the healthcare sector, with experience in regulatory matters, including medical devices and pharmaceuticals

Miomir Stojković – Founder and senior attorney, focusing on complex legal and business structures

The content is based on the applicable regulatory framework and practical experience in working with medical devices and digital health solutions.