Telehealth and patient app software clinicians can trust
Video consults, e-prescriptions, remote monitoring, patient portals, chronic care programmes and AI symptom checkers. Built so the clinician stays in charge and the patient's record stays whole.
What telehealth and patient apps software has to get right
Telehealth software lives between the patient's phone and the clinic's systems. Most problems we see come from that gap: readings that arrive but nobody reviews, prescriptions that leave the consult but stall at the pharmacy, and portals that show results without the context a patient needs.
The builds below close the gap with one record per patient, clinical rules that decide what needs a person now, and audit logs that show who saw what. Some of them are medical devices, so the intended purpose and the risk file are part of the design from day one.
Problems we are asked to fix
The problems teams bring to us, the system that fixes each one and the builds that did it.
Remote patient monitoring platform
Device readings from home patients are not reviewed in time.
Readings sorted by clinical risk, so the care team sees the patients who need a call first, with every review logged.
Video consult platform
Clinics need secure video consults linked to records.
Consults booked, held and documented in one flow, with prescribing guided by the rules for remote care.
E-prescription and delivery console
Prescriptions and delivery are disconnected.
Electronic prescriptions redeemed, checked and released by a pharmacist, then tracked to the patient's door.
Patient portal
Patients phone the clinic for results and appointments.
Results, appointments and messages in one place, with proxy access for family members under clear rules.
AI symptom checker
AI symptom checkers face medical device rules.
Triage logic under clinical governance, with a console to review outputs and a risk file kept with each release.
Chronic care programme app
Chronic care patients drop out of programmes.
A coached programme with a coach console and clear escalation to the patient's doctor when readings or answers call for it.
7 kinds of telehealth and patient apps system we have built
Each one links the product build behind it, counted from our case studies.
Telehealth and patient apps products we built
Waypost - Remote Patient Monitoring Platform with Risk-Sorted Alerts
Designed and built a clickable remote patient monitoring platform for a US cardiology and primary care group: home blood pressure, weight and SpO2 readings from cellular devices, a risk-sorted alert queue for nurses, triage with the practice's protocol on screen, and live progress toward each patient's Medicare RPM billing requirements.
Nadi - Video Consult Platform with Guideline-Aware Prescribing
Designed and built a clickable ops console for an Indian telemedicine provider's video consult platform: a live queue across four specialties, every consult with its guideline evidence and signed e-prescription, refunds within role limits, and prescribing flags raised when a doctor tries a medicine the Telemedicine Practice Guidelines do not allow.
Pistill - E-Rezept Redemption, Pharmacist Release and Home Delivery Console
Designed and built a clickable pharmacy operations console for a pharmacist-owned group in northern Hesse with a mail-order permit: one queue for E-Rezepte from every channel, a validation workbench with substitution and co-payment rules, a pharmacist release step, and a cold-chain board for fridge medicines.
Tavor - Member Portal for an Israeli Health Fund with Family Proxy Access
Designed and built a clickable member portal for an Israeli health fund: one login for a member and the children and parents they look after, referrals and tofes 17 commitments with an honest status, and test results with plain-language explanations, held results and teen confidentiality built in.
Leitstern - AI Symptom Checker with a Clinical Governance Console
Designed and built the clinical governance console for a CE-marked symptom checker that tells people in Austria how urgently to seek care: releases of clinical content, red-flag rules and locked models approved by e-signature against a passing regression run, real-world under-triage tracked from follow-ups, and vigilance deadlines kept in view.
Lysning - Type 2 Diabetes Programme with a Coach Console and GP Escalations
Designed and built a clickable coach console for a Danish type 2 diabetes programme that municipalities buy for their residents: a caseload sorted by risk, rule-based flags with a service standard, a full participant record, and letters to GPs that go through clinical review and MedCom delivery.
The rules involved
The rules this kind of software usually has to follow. Guidance, not legal advice.
- 01
Health data protection
HIPAA in the US, the GDPR's special category rules in the EU, and national health record laws elsewhere.
- 02
Medical device rules
Software that diagnoses, monitors or guides treatment can be a medical device under the EU MDR or FDA rules, which sets its class and duties.
- 03
Telemedicine and prescribing rules
Who may consult and prescribe remotely, for which medicines, and how prescriptions are sent, set by each country's health and pharmacy law.
- 04
Interoperability standards
HL7 FHIR and national e-health standards decide how the app exchanges data with clinics, labs and pharmacies.
- 05
Accessibility
WCAG and laws such as the European Accessibility Act matter more here than almost anywhere, because patients are often unwell or older.
Framework guides
Rules our telehealth and patient apps builds cite most
- WCAG 2.1 AA5
- GDPR3
- ABDM1
- ACC/AHA BP guideline1
- AMPreisV1
- AODA1
- ApBetrO1
- ApoG § 11a1
- Austrian DSG1
Two ways to work with OceanLab
Project build
We design and build the system as one project. It starts with a clickable prototype your team tries before any production code is written. Pay per milestone (outcome-based) or hourly at $30-50/hr, depending on role and seniority.
Embedded engineers
Our engineers join your team on a flexible monthly retainer. Part-time is fine and it runs month to month, with hours that overlap the US, UK and Europe, the Middle East, and Australia and Asia. Outcome-based or $30-50/hr.
Guides and tools
Telehealth and patient apps software questions
Is a telehealth app a medical device?
A video consult or booking app usually is not. Features that interpret readings, triage symptoms or suggest treatment for a patient often are. The intended purpose decides it, so we fix it with your regulatory lead before design.
Can you connect to our EHR?
Yes. We integrate over FHIR where the EHR offers it, and over HL7 v2 or the vendor's own API where it does not, with a mapping layer so each new connection is a mapping, not a rewrite.
How do you keep alerts from overwhelming clinicians?
By sorting on clinical risk instead of time, letting clinicians set thresholds per patient, and logging every review so nothing is missed or reviewed twice.
