Telemedicine & HealthTech in Uzbekistan: What's Allowed and What Isn't

Telemedicine & HealthTech in Uzbekistan: What's Allowed and What Isn't

The short answer: you *can* launch a HealthTech product in Uzbekistan — but everything hinges on what your product actually does. A platform that helps patients book appointments is a fundamentally different legal entity from a platform where doctors diagnose patients online. Different licensing requirements, different liability exposure, different risk profiles. That distinction is worth mapping out before you write a single line of code.

---

Key Takeaways

• Medical practice requires a license — if your product functionally delivers medical services, you cannot operate without one, even if it all happens inside an app.
• Health data is a special category of personal data, subject to stricter protection requirements under Uzbekistan's personal data legislation.
• AI-powered diagnostics sit in a regulatory grey zone — automated medical outputs have no clear regulatory status yet; both the developer and the clinic partner carry exposure.
• Marketplace ≠ medical organization — a platform model reduces regulatory burden, but doesn't eliminate it.

---

What Counts as "Medical Practice" Under Uzbek Law

Uzbekistan's healthcare legislation defines medical practice as professional activities aimed at disease prevention, diagnosis, treatment, and medical rehabilitation. These are the activities that require a license.

For a HealthTech founder, this translates to a practical test: if a doctor on your platform consults a patient, makes a diagnosis, or prescribes treatment — that is licensed medical practice. The fact that it happens inside a messenger or a mobile app changes nothing. The location of the service shifts; the nature of the service does not.

What does not constitute medical practice on its own:

• A doctor scheduling aggregator (you're organizing bookings, not delivering care)
• General health education content without individual recommendations
• Fitness tracking and biometric monitoring without diagnostic conclusions
• CRM or EHR software sold to clinics (you're working with healthcare organizations, not patients directly)

---

Licensing: Who Needs What

In Uzbekistan, a medical license is issued to a legal entity — a registered medical organization. This means a telemedicine platform where doctors deliver services directly to patients must either hold that license itself or operate through licensed partner clinics that carry the regulatory responsibility.

The second model — the marketplace — is technically simpler to set up, but it demands carefully structured contractual arrangements with clinic partners. The classic mistake: a startup assumes it's "just a platform," while in practice it has absorbed part of the liability for service quality — through its terms of service, payment mechanics, or the marketing claims it makes.

The specific list of licensable medical activities and the requirements for license holders are updated periodically — verify the current rules before you launch.

---

Health Data Privacy: A Higher Standard

Medical information — diagnoses, lab results, medical history — qualifies as a special category of personal data under Uzbekistan's personal data protection framework. Processing it triggers stricter obligations than those applied to ordinary user data.

In practice, this means:

• Explicit, standalone consent for processing health data is required — a checkbox buried at the end of a registration flow won't cut it.
• Data localization: personal data of Uzbekistan citizens must be processed on servers physically located within the country. This directly affects your cloud infrastructure decisions.
• Data minimization: collect only what your product genuinely needs to function. Storing full history "just in case" is both a breach risk and a regulatory one.
• Security: your technical and organizational safeguards need to match the sensitivity of the data you're handling.

---

AI in Medicine: Where Caution Outpaces Speed

AI features in HealthTech — symptom checkers, medical image analysis, predictive analytics — currently occupy a regulatory grey zone. Uzbekistan's legislation has no defined status for "AI as a medical device or software" yet, but the absence of a specific rule doesn't mean the absence of risk.

If your model outputs something a user reasonably interprets as a medical conclusion, liability for health harm can land on you — even without a specific AI statute. General tort law applies. Until the regulatory picture solidifies: document your model's limitations clearly, build mandatory human-in-the-loop review into any clinically significant decision path, and do not position your AI feature as a diagnostic tool.

---

HealthTech Business Model Comparison

---

Your Checklist for This Week

• [ ] Run the "medical test": go through each product feature and ask — is this a medical service or not?
• [ ] Determine whether your business model (marketplace vs. own clinic) requires a license.
• [ ] Audit your consent flows: is there a separate, explicit consent for health data?
• [ ] Verify that your infrastructure meets data localization requirements.
• [ ] Review contracts with clinic partners: is responsibility for service quality clearly allocated?

---

FAQ

Can a doctor consult patients through a Telegram bot without a license?

No. The communication channel doesn't change the nature of the activity. If a doctor is making diagnoses and prescribing treatment, that is licensed medical practice regardless of the medium.

Do we need a license if we're only connecting patients with doctors?

A pure aggregator platform doesn't itself deliver medical services — but this needs to be clearly reflected in your contracts, terms of service, and how the product actually operates. If the platform functionally manages the treatment process, regulators may reclassify the activity.

Can foreign doctors consult patients in Uzbekistan online?

The practice of medicine by foreign specialists carries restrictions. This requires individual analysis depending on your operating model — there's no blanket answer.

Can we store health data on AWS or Google Cloud?

Uzbekistan's data localization requirements for citizens' personal data must be factored into your infrastructure choices. Cloud storage with servers outside the country creates regulatory exposure — verify the current requirements before deploying.

What are the penalties for violating medical licensing rules?

Consequences range from administrative fines to criminal liability, depending on the severity of harm and intent. For a startup, reputational damage typically outweighs the financial penalties.

---

*This article is general information only and does not constitute individual legal advice. Healthcare and personal data legislation changes regularly — all requirements must be verified against current sources as of the date of application.*

---

If you're building a HealthTech product and want to navigate from idea to launch without regulatory surprises — book a consultation. At Pactum, we've structured regulatory frameworks for medical marketplaces, AI diagnostics tools, and B2B SaaS for clinics. We'll help you get the architecture right from day one.