Quick Answer
- Custom telehealth platform cost in Ireland: EUR 40,000 to 120,000 (add EUR 10,000 to 25,000 if any diagnostic feature triggers EU Medical Device Regulation review)
- Build timeline: 8 to 16 weeks depending on scope
- Core compliance layers: HIQA information governance standards, GDPR Article 9 rules for health data, Data Protection Commission registration
- HSE integration reality in 2026: the National Shared Care Record is still a restricted beta, and the National Electronic Health Record is still in supplier procurement, so build to the standard, not to a live API that doesn’t exist yet
- Ireland’s eHealth maturity score sits at 11%, against a 79% EU average, which is exactly why private providers are moving first
- ISO 27001:2022 certification of your development partner is now a real filter for HSE-adjacent and insurer-facing platforms
The HSE Health App passed 125,000 registrations and more than 210,000 downloads within its first year, and by mid-2026 it was picking up nearly 1,000 new downloads a day (Source: gov.ie, January 2026; HSE newsroom, June 2026). At the same time, the Department of Health approved €263 million for HSE digital projects in 2026, including a dedicated Virtual Care Programme and a new Telehealth Centre of Excellence (Source: Pulse+IT, 24 February 2026). Providers who build now, to the standards the public system is converging toward, are positioned to plug in later rather than rebuild.
That timing matters because Ireland is starting from a very low base. The country’s eHealth maturity score was measured at just 11% in 2023, up from 0% the year before, against an EU average of 79%, making Ireland the lowest-ranked EU member state for citizen access to electronic health records (Source: Houses of the Oireachtas Research Matters, citing European Commission Digital Decade benchmarking). Private telehealth platforms aren’t waiting for the public system to catch up. They’re building the bridge themselves, and the smart ones are building it to HIQA’s information governance standards from day one.
Why Are Irish Providers Investing in Telehealth Right Now?
Government funding and existing commercial traction are both pointing the same direction in 2026.
On the government side, the Digital for Care Capital Plan 2026 set aside €2.7 million specifically for the Virtual Care Programme, targeting 100 virtual care beds per health region within two years, procurement of a national remote health monitoring platform, and virtual care hubs in every region (Source: Pulse+IT). The virtual care rollout had already reached 12 islands by February 2026, a clear signal that remote-first delivery is a genuine government priority, not a pilot project gathering dust (Source: Pulse+IT).
On the commercial side, demand is already proven. Webdoctor, founded in 2013, has delivered over 100,000 patient consultations and now runs a sister platform, NuaHealth, for clinics wanting their own virtual care setup (Source: Silicon Republic). Vhi partners with VideoDoc for member video appointments, Irish Life Health runs its own Digital Doctor service, and HealthHero provides employer-backed digital GP access across several Irish workplace benefit schemes. That’s a market with a decade of validated demand and room for specialty-specific, employer-backed, and HSE-adjacent platforms that none of the generalist players currently cover well.
What Compliance Standards Does Telehealth Software Need to Meet in Ireland?
Any platform handling patient data in Ireland sits under several overlapping layers, and missing one is the single most common reason a build gets delayed at launch.
HIQA’s National Standards for Information Management in Health and Social Care, published in 2024, set out four principles every information system should meet: a rights-based approach, safety and wellbeing, responsiveness, and accountability (Source: HIQA). These standards were built specifically with digital health and telehealth adoption in mind, so a platform’s data architecture should be mapped against them before a single screen gets designed, not after.
The Data Protection Commission treats health data as special category data under Article 9 of the GDPR. That means a platform needs an Article 9(2) lawful basis, most commonly explicit consent for private platforms, in addition to the ordinary Article 6 basis every data processing activity requires (Source: Data Protection Commission). If the platform will ever support research use of patient data, the Data Protection Act 2018 (Section 36(2)) Health Research Regulations add a further layer.
The Patient Safety (Notifiable Incidents and Open Disclosure) Act 2023 expanded HIQA’s monitoring functions to private hospitals and other prescribed health services, which is relevant if the platform supports actual clinical service delivery rather than pure scheduling and admin.
Two EU-wide frameworks round this out. The Medical Device Regulation applies only if the software performs a diagnostic, triage, or clinical decision-support function, so a plain booking-and-video platform sits outside its scope, while a symptom-checker or scoring tool can pull it in without anyone intending that. The European Health Data Space Regulation phases in implementation deadlines between 2026 and 2030. Design your data model with that timeline in mind now, rather than retrofitting it later.
How Does HSE Integration Actually Work in 2026?
This is where most first-time builders in this space overreach, so it’s worth being precise.
The HSE’s Health Identifiers Service, including the Individual Health Identifier, provides common data codes that support integration across the HSE and the wider Irish health sector, maintained by the HSE’s Office of the Chief Information Officer (Source: PSB Data Catalogue). The National Shared Care Record went live as a Release 1 beta in November 2025, bringing together patient information from multiple providers into a single view for a limited group of trained, approved healthcare staff. It has already been assessed against HIQA’s information management standards and meets them, and the HSE Data Protection Office consulted the Data Protection Commission throughout the DPIA process (Source: HSE NSCR Data Protection Impact Assessment).
The National Electronic Health Record programme, meanwhile, is still mid-procurement. The government approved the preliminary business case in April 2025 and gave the go-ahead to shortlist EPR suppliers in 2026. HSE chief executive Bernard Gloster has described it as the largest digital transformation project in the organisation’s history, with private hospitals eventually needing to build bidirectional interfaces once the programme matures (Source: Computer Weekly, 2026).
Need a straight answer on what your specific platform can and can’t connect to right now?
Sigosoft runs a free 30-minute HSE-readiness call where we map your planned data flows against what’s actually live versus what’s still in procurement, so you’re scoping against reality, not a vendor’s roadmap slide.
The practical path in 2026 is to build to HIQA’s information governance standards from the start, structure your data using FHIR-compatible models, and design your architecture so onboarding to NSCR or the national EHR is a configuration exercise later, not a rebuild. Assuming direct API access to either system today is the single biggest scoping mistake we see.
What Core Modules Should a Telehealth Platform Include?
A platform built for the Irish market in 2026 typically needs five layers working together.
The patient app covers registration with verified identity (MyGovID-equivalent verification where relevant), appointment booking, video consultation, secure messaging, e-prescription requests, symptom intake forms, and payment processing.
The clinician portal handles multi-provider scheduling, patient history views, structured clinical note templates, e-prescribing integration, and referral generation, whether that’s GP to consultant or GP to diagnostics.
The video and communication layer typically runs on WebRTC or a managed provider like Twilio or Daily.co for HD video with screen sharing, plus secure in-app messaging and SMS or push notification reminders.
Compliance and governance needs consent capture with a full audit trail for Article 9 processing, DPIA-ready documentation of every data flow, incident and complaints logging aligned to HIQA’s notifiable incident requirements, and clear data retention and deletion controls.
Admin and analytics should support multi-clinic management, utilisation and no-show reporting, and billing workflows that account for insurer reimbursement paths through Vhi, Irish Life Health, or Laya where relevant.
What’s a Realistic Technology Stack?
Next.js or React for the patient and clinician web portals, Flutter or React Native for the patient mobile app across iOS and Android, Node.js or NestJS for the backend, and PostgreSQL for the database. Hosting needs to sit on AWS or Azure’s EU region, ideally Ireland-resident, which isn’t optional given GDPR and HIQA data residency expectations. Twilio or Daily.co covers video, Stripe or an Irish payment processor handles consultation fees, and a FHIR-compatible data model layer keeps future NSCR or national EHR integration a configuration task rather than an architecture rebuild.
What Does the Compliance Layer Actually Cost?
This is the part most cost estimates skip, and it’s usually 15 to 20% of the total build.
GDPR and DPC compliance work, meaning DPIA documentation, consent flow design, data processing agreements with subprocessors like your cloud host, video vendor, and SMS provider, and full audit trail implementation, typically adds €8,000 to €18,000 to a build. HIQA alignment, covering information governance mapping and incident logging structures, adds a further €5,000 to €10,000. If the platform will ever include a diagnostic or triage feature, factor in €10,000 to €25,000 for Medical Device Regulation classification review alone, before the additional software work that a Class IIa or IIb classification would trigger. Flagging this early lets a client scope their MVP to avoid triggering MDR requirements they never budgeted for.
Cost Breakdown by Component
| Component | EUR Cost |
| UI/UX design (patient and clinician) | €7,000 to €14,000 |
| Patient mobile app (iOS and Android) | €14,000 to €24,000 |
| Clinician web portal | €16,000 to €30,000 |
| Video consultation integration | €8,000 to €16,000 |
| GDPR and DPC compliance layer | €8,000 to €18,000 |
| HIQA information governance alignment | €5,000 to €10,000 |
| QA and security testing | €6,000 to €12,000 |
| Total | €64,000 to €124,000 |
Add €10,000 to €25,000 if any Medical Device Regulation-triggering feature is in scope.
Is It Cheaper to Build Custom or License an Existing Platform?
Published pricing gives a useful benchmark here. Webdoctor consultations start from around €30, and Irish online GP pricing has historically clustered between €20 and €36 per consultation (Source: Webdoctor.ie). For a provider running consistent volume, say 500 or more consultations a month, white-label platform fees plus per-consultation processing costs can run past €20,000 to €30,000 a year, and that’s before the provider owns any of the underlying patient relationship or data architecture.
Custom development at €64,000 to €124,000 breaks even against typical white-label fees somewhere between two and four years, and the provider keeps full data ownership, which matters more every year as EHDS data-portability rules phase in through 2026 to 2030. For an early-stage service still validating demand, though, a white-label or licensed platform is still the sensible place to start. Build custom once you know your service model and patient volume are real.
Common Mistakes Providers Make
Assuming HSE systems are open for integration today
The National Shared Care Record is still a restricted beta limited to trained, approved users, and the national EHR is still in supplier procurement. Treat both as roadmap items, not live APIs.
Treating GDPR consent as a checkbox
Health data is special category data under Article 9. Skipping a documented Article 9(2) basis alongside the Article 6 basis is one of the most common and most expensive oversights we see in healthcare builds.
Hosting outside the EU or EEA
It adds GDPR transfer complexity for no real benefit, given EU-region hosting is widely available and no more expensive.
Adding diagnostic-sounding features without checking MDR exposure
A symptom checker or a triage scoring tool can classify your software as a medical device even when that was never the intention.
Skipping the DPIA
Health data processing is inherently high-risk under GDPR. Build the Data Protection Impact Assessment into the architecture stage, not the pre-launch checklist.
Ignoring HIQA’s information governance principles in the data model
Retrofitting audit trails and incident logging after launch costs far more than designing them in from the start.
Realistic Timeline
An MVP covering video consultation, booking, the patient app, and a basic compliance layer typically takes 14 to 16 weeks. A full platform with a clinician portal, e-prescribing workflow, insurer billing support, and complete GDPR and HIQA documentation runs 18 to 22 weeks.
Frequently Asked Questions
Does my telehealth app need to integrate with the HSE?
Not necessarily. Most private platforms operate independently of HSE systems today. What matters is building to HIQA’s information governance standards so integration with the National Shared Care Record or national EHR is a quick configuration step, not a rebuild, once those systems open more broadly to external providers.
What does the Data Protection Commission require for health data specifically?
Health data is special category data under GDPR Article 9. You need an Article 9(2) lawful basis, usually explicit consent for private platforms, alongside the standard Article 6 basis, plus a Data Protection Impact Assessment covering how the data is collected, stored, and shared.
Will my platform need Medical Device Regulation approval?
Only if it performs a diagnostic, triage, or clinical decision-support function. A booking and video consultation platform sits outside MDR scope. Adding a symptom checker or automated scoring tool can bring you into Class I or Class IIa territory, so it’s worth a classification review before you build that feature.
How does HIQA relate to a private telehealth platform that isn’t HSE-run?
HIQA’s National Standards for Information Management in Health and Social Care apply to health and social care information handling broadly, not just HSE-run services. Building to these standards from the start makes future audits, insurer partnerships, and HSE integration far smoother.
What’s the difference between the National Shared Care Record and the National Electronic Health Record?
The National Shared Care Record is a live system, currently in a restricted Release 1 beta since November 2025, that gives approved healthcare staff a combined view of patient information from multiple providers. The National Electronic Health Record is a separate, much larger programme still in supplier procurement in 2026, intended to eventually cover hospitals, GP, and community records nationally.
Can offshore developers deliver HIQA and GDPR-compliant healthcare software for the Irish market?
Yes, provided the team has direct experience with EU healthcare compliance frameworks. Sigosoft has built compliance-driven healthcare software for over 10 years and holds ISO 27001:2022 certification, which addresses the information security expectations built into HIQA’s standards.
Is it cheaper to license an existing telehealth platform or build custom?
It depends on your volume and timeline. Under roughly two years of operation, licensing or white-labelling is usually cheaper. Past three to four years, especially at 500 or more consultations a month, custom development tends to break even and gives you full ownership of patient data and architecture.
Want a straight cost estimate for your specific service model, whether that’s GP-led, insurer-backed, or specialty-focused? Send Sigosoft your current patient volume and consultation type, and we’ll return a scoped estimate within 48 hours, benchmarked against what HIQA and the DPC will actually expect at launch.
