Telemedicine & Telehealth Platforms
Telemedicine & Telehealth Platforms: Reimbursement, RPM and Cross-Border Licensing (US & EU)
Telemedicine has moved from a peripheral convenience to a core delivery channel for healthcare systems on both sides of the Atlantic. Yet the technology is rarely the hardest part. The obstacles that sink telehealth ventures are regulatory and financial: whether a consultation can be billed at all, who is permitted to deliver it, and what happens when a patient and a clinician sit in different jurisdictions.
This guide examines three structural questions that determine whether a telemedicine platform is commercially viable: reimbursement models, remote patient monitoring (RPM), and cross-border licensing. Each is addressed separately for the United States and the European Union, because the two systems rest on fundamentally different legal architectures.
The Two Regulatory Architectures
The United States operates a largely market-based system in which federal programmes, state regulators, private insurers and professional boards all exert influence. Payment is fragmented across Medicare, Medicaid, commercial payers and employers, and licensure is a state-level competence.
The European Union, by contrast, treats healthcare as a predominantly national responsibility. There is no equivalent of a federal payer, and no single licence to practise across the bloc. EU-level legislation touches telemedicine mainly through data protection, medical device rules, and patient mobility rights rather than through payment or licensure.
Core distinction: In the US, the binding constraint is usually payment. In the EU, the binding constraint is usually licensure and data protection.
Reimbursement Models in the United States
Medicare and the fee-for-service legacy
Medicare has historically reimbursed telehealth under a set of restrictive conditions: the patient had to be located in a rural area, and had to be physically present at an approved "originating site" such as a clinic or hospital rather than at home. These restrictions were substantially relaxed during the COVID-19 public health emergency, expanding coverage to audio-video visits in home settings and broadening the range of eligible practitioners.
The durability of those flexibilities has been a recurring subject of congressional and administrative action, with extensions granted on a rolling basis. Because the position changes, platforms should treat Medicare telehealth policy as a moving target and verify current rules rather than relying on any published summary — including this one.
Commercial payers and employer arrangements
Private insurers set their own telehealth policies. Many now cover synchronous video consultations at parity with in-person visits for behavioural health and primary care, though coverage for asynchronous messaging and store-and-forward modalities varies widely. Employer-sponsored direct-to-consumer arrangements — often delivered through a subscription model rather than fee-for-service — have become a significant channel, particularly for mental health and chronic condition management.
Payment model comparison
| Model | How it works | Implication for platforms |
|---|---|---|
| Fee-for-service | Payment per encounter, coded by CPT/HCPCS | Requires accurate coding and documentation; revenue scales with volume |
| Subscription / cash-pay | Patient or employer pays a recurring fee | Bypasses payer rules but limits reach to those able to pay |
| Value-based / capitated | Payment tied to outcomes or per-member-per-month | Rewards efficiency and remote management over visit volume |
| RPM-specific codes | Separate billing for device supply, setup and monitoring time | Creates a distinct revenue stream independent of consultations |
Reimbursement in the European Union
The EU does not operate a unified reimbursement regime for telemedicine. Coverage is determined by each Member State's health system and, in many countries, by regional authorities or individual sickness funds.
- Statutory systems such as those in France, Germany and the Netherlands have introduced dedicated teleconsultation remuneration, often through negotiated fee schedules with national insurers.
- Tax-funded systems such as those in Spain, Italy and the Nordic countries typically fund telemedicine through provider budgets rather than itemised payments, meaning platforms integrate with public providers instead of billing insurers directly.
- Private supplementary insurance plays a larger role in some markets and may cover teleconsultations where statutory systems do not.
The practical consequence is that a single EU-wide reimbursement strategy is rarely achievable. Platforms generally succeed by partnering with national providers or insurers market by market, or by operating a private-pay model that sidesteps payer negotiation altogether.
Remote Patient Monitoring
Remote patient monitoring describes the collection of physiological data from a patient outside a clinical setting — blood pressure, glucose, weight, oxygen saturation, heart rhythm — transmitted to a clinician for review and longitudinal management.
RPM in the United States
RPM has developed a relatively defined billing identity in the US, with dedicated codes covering device supply, patient setup, and the clinical staff time spent reviewing and acting on transmitted data. This structure has encouraged the emergence of specialised RPM vendors that supply devices and monitoring services to physician practices.
Two cautions apply. First, documentation and consent requirements are substantive; monitoring time must be genuine and recorded. Second, regulators and payers have scrutinised programmes where monitoring generates billing without demonstrable clinical benefit. Sustainable RPM depends on integration into a care plan, not on code optimisation.
RPM in the European Union
EU reimbursement for RPM is far less standardised. Several Member States have piloted or implemented remote monitoring pathways, frequently for specific conditions such as heart failure, chronic obstructive pulmonary disease, or diabetes, and often within integrated care programmes rather than as standalone billable services.
Where reimbursement does exist, it tends to be bundled into broader care or disease-management funding rather than paid per transmission. From a product perspective, this favours platforms that can demonstrate reduced admissions or improved outcomes, since the buyer is often a provider organisation or regional health authority rather than a fee schedule.
Device regulation intersects here. If an RPM platform interprets data, generates alerts based on clinical thresholds, or recommends action, it may qualify as Software as a Medical Device. Transmission alone generally does not.
Cross-Border Licensing
United States: state-by-state licensure
Medical licensure in the US is granted by individual states. The prevailing rule is that the clinician must hold a licence in the state where the patient is physically located at the time of the encounter. A physician licensed in California cannot ordinarily treat a patient sitting in Texas without Texas authorisation.
Several mechanisms soften this:
- Interstate compacts allow expedited licensure across participating states for certain professions.
- Telemedicine-specific registration exists in some states, permitting out-of-state practitioners to consult under defined conditions, sometimes with fee and scope limits.
- Consultation exceptions may permit informal specialist input without full licensure, though these generally do not extend to establishing a treatment relationship.
Operationally, platforms typically enforce licensure matching at the point of scheduling — routing a patient to a clinician authorised in the patient's state. Maintaining an accurate licensure database is a continuous compliance obligation, not a one-time setup task.
European Union: mutual recognition without a single licence
The EU has no pan-European medical licence. Healthcare regulation remains a Member State competence, and a clinician wishing to serve patients in another Member State must generally obtain recognition of qualifications or register with the relevant national authority.
The Cross-Border Healthcare Directive establishes a patient's right to seek healthcare in another Member State and to reimbursement under defined conditions, but it addresses patient mobility rather than creating a clinician passport. Similarly, the Professional Qualifications Directive facilitates recognition of qualifications for establishment and temporary provision of services, yet national regulators retain the ability to impose conditions, language requirements, and registration obligations.
In practice, cross-border teleconsultation within the EU is most workable where a clinician is established in the patient's Member State, or where a specific bilateral or regional arrangement permits otherwise. Platforms serving multiple EU markets typically maintain separate clinician pools per country.
Data Protection: The Overlay That Applies Everywhere
Both markets impose data protection obligations that materially shape platform architecture.
- United States: HIPAA governs protected health information held by covered entities and their business associates. Platforms handling such data usually require a Business Associate Agreement, along with administrative, physical and technical safeguards.
- European Union: The GDPR classifies health data as a special category requiring an explicit lawful basis and additional safeguards. Controllers must satisfy requirements including data minimisation, purpose limitation, and in many cases a Data Protection Impact Assessment. Cross-border transfers require an appropriate transfer mechanism.
Because these regimes differ in structure and terminology, a platform built for one market rarely satisfies the other without deliberate adaptation.
Practical Takeaways for Platform Builders
- Decide your payment route before your feature set. Fee-for-service, subscription, and value-based models demand different product capabilities, documentation standards and integrations.
- Treat licensure as infrastructure. Automated routing based on patient location is a core system, not an administrative afterthought.
- Design RPM around outcomes. Programmes justified by clinical benefit survive scrutiny; those justified by billing codes do not.
- Assess device status early. Determine whether your software is SaMD before you commit to an architecture.
- Plan per-market in the EU. Assume separate reimbursement negotiations, separate clinician registrations, and separate data protection analysis for each Member State you enter.
Conclusion
Telemedicine platforms operate at the intersection of clinical practice, payment policy and jurisdictional law. In the United States, viability hinges on understanding a fragmented and shifting reimbursement landscape alongside strict state licensure rules. In the European Union, the challenge shifts to national licensure, market-by-market funding arrangements, and the GDPR's demanding treatment of health data. Neither market rewards a generic approach. Success comes from designing for the specific regulatory and financial realities of each jurisdiction from the outset.
Frequently Asked Questions
Medicare covers many telehealth services, but coverage has historically been tied to geographic and originating-site restrictions that were temporarily relaxed during the COVID-19 public health emergency. Which services are covered, and whether a patient's home qualifies as an originating site, depends on the rules in force at the time of the encounter. Providers should verify current coverage and payment rules before billing.
Remote patient monitoring is the use of connected devices to collect physiological data from a patient outside a clinical setting and transmit it to a healthcare professional for review and management. Typical applications include blood pressure, blood glucose, weight and heart rhythm monitoring for chronic disease management.
Generally no. Medical licensure in the United States is granted by individual states, and the prevailing principle is that the practitioner must be licensed in the state where the patient is physically located at the time of the encounter. Some states participate in interstate compacts or offer telemedicine-specific registration pathways that create exceptions.
There is no single EU-wide licence to practise medicine. Competence for healthcare regulation rests largely with Member States, so a clinician must generally be recognised or registered in the Member State where they provide services. The Cross-Border Healthcare Directive establishes patient rights to seek care in other Member States, but it does not create a pan-European teleconsultation licence.
It depends on intended use. A platform that merely transmits video and stores records is generally not a medical device. Software that analyses clinical data, calculates dosages, or supports diagnosis may qualify as Software as a Medical Device (SaMD) and fall under FDA or EU MDR requirements.
In the United States, HIPAA governs protected health information handled by covered entities and their business associates. In the European Union, the GDPR governs personal data, including health data, which is treated as a special category requiring a lawful basis and heightened safeguards. Platform vendors commonly need contractual instruments such as a Business Associate Agreement (US) or Data Processing Agreement (EU).
Sources and Further Reading
- Centers for Medicare & Medicaid Services — Telehealth policy and billing resources: cms.gov
- U.S. Department of Health & Human Services — HIPAA rules and guidance: hhs.gov
- Federation of State Medical Boards — resources on state licensure and interstate compacts: fsmb.org
- European Commission — Cross-border healthcare: health.ec.europa.eu
- European Parliament and Council — Regulation (EU) 2017/745 on medical devices: EUR-Lex
- European Parliament and Council — Regulation (EU) 2016/679 (GDPR): EUR-Lex
- U.S. Food and Drug Administration — Software as a Medical Device (SaMD): fda.gov
Disclaimer: This article is for informational purposes only and does not constitute legal, regulatory, or billing advice. Telehealth coverage rules and licensure requirements change frequently. Verify current requirements with the relevant authorities and qualified advisers before relying on any information presented here.
