
ISO 13485 Design Controls for Software Teams
ISO 13485 design controls for software teams: clause 7.3 stages, traceability, agile sprint mapping, tools and the FDA QMSR.
Types of HealthTech software, the rules that apply and how to build it well.

HealthTech software covers any software used to deliver, manage or pay for healthcare, from electronic health records and telehealth apps to remote monitoring platforms and AI tools. Building it is different from building ordinary business software because of patient safety, privacy law, interoperability rules and, for some products, medical device regulation. This guide covers the main types of HealthTech software, the rules that apply and how good HealthTech products are built. For custom development services, see custom HealthTech software development.
| Type | Examples | Typical users |
|---|---|---|
| Clinical systems | EHRs, specialty clinical systems, clinical decision support | Clinicians, care teams |
| Patient-facing apps | Portals, telehealth, symptom checkers, digital therapeutics | Patients and caregivers |
| Remote monitoring | Connected devices, monitoring dashboards, alerting | Care teams, patients at home |
| Operations | Scheduling, staffing, capacity, supply chain | Operations and management |
| Revenue cycle | Eligibility, coding, claims, denials | Billing and finance teams |
| Data and analytics | Data platforms, population health, reporting | Analysts, quality teams, leaders |
| Post-acute and home care | Home health and hospice platforms, caregiver scheduling, EVV | Agencies and field staff |
AI is now built into many HealthTech products: documentation support, message triage, coding assistance, scheduling and risk prediction. It needs the same discipline as the rest of the product plus validation, monitoring and clear human oversight. See regulatory compliance for AI in medical devices and healthcare interoperability solutions. Teams building HealthTech products can see our approach on the AI implementation support page.
HealthTech software spans clinical, patient-facing, monitoring, operations, revenue cycle, data and home care systems. It must meet HIPAA, interoperability and information blocking rules, and some functions are regulated as medical devices. Build it with clinical input, early regulatory assessment, security by design, FHIR-based interoperability, quality processes and monitoring after launch.
If you are building HealthTech software, book a consultation with Ekipa's HealthTech engineers.
Software used to deliver, manage or pay for healthcare, such as EHRs, telehealth, remote monitoring, operations and revenue cycle tools.
Some is. Whether a function is a medical device depends on its intended use; many administrative tools are not.
It applies when the software handles protected health information for covered entities or business associates.
An HL7 standard for exchanging health data through modern APIs.
Patient safety, privacy law, interoperability requirements and, for some products, medical device regulation.

ISO 13485 design controls for software teams: clause 7.3 stages, traceability, agile sprint mapping, tools and the FDA QMSR.

EU MDR Rule 11 explained: how Annex VIII classifies medical device software as Class I, IIa, IIb or III, with MDCG 2019-11 Rev.1 guidance.

SaMD classification FDA explained: IMDRF risk categories, FDA device classes, 510(k), De Novo and PMA routes, and CDS exclusions for healthtech teams.
Connect with our team to explore how AI expertise can transform your business.