Skip to content
DT Nova

Hospital mobile apps: types, rules and how to build them

Hospital mobile apps fall into two families: apps for patients, which handle appointments, check-in, wayfinding, results and messages, and apps for staff, which handle rosters, secure messaging, tasks and bedside access to the record. Both have to connect to clinical systems, protect sensitive data and, in some cases, meet medical device rules. This guide explains the common types, the standards and regulations that shape them, and what to settle before building one, with sources from the regulators themselves.

The short version

  • Start from one job for one group of users, such as patients checking in or nurses receiving tasks, not from a list of everything a hospital app could do.
  • Decide early whether any feature is a medical device; it changes the whole project.
  • Integrate through standard interfaces, preferably HL7 FHIR, rather than copying data into the app.
  • Store as little as possible on the phone, host in the hospital's control and log every access.
  • Design for stressed, tired and unwell people: large text, plain words, few steps.

Types of hospital mobile apps

TypeTypical featuresMain systems behind it
Patient accessAppointments, reminders, check-in, questionnaires, letters and resultsPatient administration, electronic health record
WayfindingIndoor maps, routes to a department, parkingBuilding data, appointment location
Treatment companionPreparation instructions, recovery plans, symptom diaries, messages with the care teamCare pathways, record, messaging
Staff communicationSecure messaging, alerts, on-call lists, escalationDirectory, rosters, alarm systems
Staff work toolsTask lists, checklists, bed management, bedside documentationElectronic health record, bed and task systems
Rosters and shiftsDuty rosters, swaps, leave, on-call availabilityWorkforce and payroll systems
Remote monitoringReadings from home devices, alerts to the care teamDevices, record; often a medical device

Each row is a different product with different users, data and risks. Hospitals that try to put all of them in one app usually end up with an app that does none of them well. A clear first scope, such as patient check-in and wayfinding, or staff rosters and messaging, delivers value sooner and makes later additions easier.

When an app becomes a medical device

This is the question that decides the rest of the project. In the United States, the FDA's page on device software functions and mobile medical applications (read 11 November 2026) explains that the agency applies the same risk-based approach to device software as to other devices. It focuses its oversight on software that presents a greater risk to patients if it does not work as intended, such as apps that diagnose heart rhythm abnormalities. For some low-risk software that meets the device definition, such as tools that help patients self-manage a condition without specific treatment suggestions, it exercises enforcement discretion. The underlying guidance, Policy for Device Software Functions and Mobile Medical Applications, was first issued in 2013 and last updated in 2022.

In the EU, software intended for medical purposes falls under the Medical Device Regulation (EU) 2017/745. Its classification rule for software, Rule 11 in Annex VIII, places software that provides information used for diagnostic or therapeutic decisions in class IIa at least, and higher where a wrong decision could cause serious deterioration of health or death. The Medical Device Coordination Group's guidance MDCG 2019-11 explains how manufacturers qualify and classify software.

In practice: booking, wayfinding, rosters and general messaging are not medical devices. A dose calculator, an early warning score that prompts clinical action or a remote monitoring app with alerts probably is. If a feature might qualify, the hospital's regulatory team or a notified body confirms it before development, because a device needs a quality management system, clinical evaluation and documentation from the first line of code. See medical device software development for how we work inside a manufacturer's quality system.

Integration: FHIR and the patient record

A hospital app is only as useful as its connection to clinical systems. HL7 FHIR, described by HL7 as a standard for health care data exchange, is the common route today. Its current published version is R5. FHIR defines resources such as Patient, Appointment, Observation and Encounter, exchanged over web interfaces, and most modern electronic health record systems offer FHIR interfaces next to older HL7 version 2 messages.

Good integration follows a few rules. The app reads and writes only the resources it needs. It uses the user's own identity and permissions, typically through the record system's authorisation server, rather than a shared service account. It does not keep a second copy of the record. And every access is logged where the hospital's audit tools can see it.

The European Health Data Space

European hospitals should plan for the European Health Data Space Regulation (read 11 November 2026). It was published on 5 March 2025 and entered into force on 26 March 2025. The Commission's timeline sets March 2029 for the exchange of patient summaries and ePrescriptions in all member states, and March 2031 for medical images, laboratory results and hospital discharge reports. It gives people fast, free access to their electronic health data in a standard European format, the right to share it with health professionals and to see who has accessed it. Patient apps built today should use standard formats and access logs that fit that direction.

Data protection and security

Health data is a special category of personal data under the GDPR in the EU, and protected health information under HIPAA in the United States. For a hospital app that means a documented legal basis and purpose for each data item, a data protection impact assessment, data processing agreements with every supplier, and hosting under the hospital's control, in the EU for European hospitals. Apple's App Review Guidelines (read 11 November 2026) add platform rules: apps in healthcare should be submitted by the legal entity that provides the service, health data may not be used for advertising or data mining, and personal health information may not be stored in iCloud.

Technically, the baseline is strong sign-in (for staff, the hospital's single sign-on; for patients, a national e-identity where one exists), minimal data on the device, encryption in transit and at rest, automatic sign-out on shared devices, and audit logs of every view and change.

Designing for patients and staff

Hospital apps are used by people under stress. Patients may be anxious, in pain, elderly or reading in a second language. Staff are interrupted constantly, wear gloves and have seconds, not minutes. That calls for large text and touch targets, plain words instead of clinical shorthand for patients, offline access to what is needed on the ward, notifications that are rare enough to be trusted, and accessibility that meets WCAG. In the EU, public sector hospitals are also bound by the Web Accessibility Directive for their websites and mobile apps.

Build checklist

  • One user group and one job for the first version.
  • Medical device question answered in writing for every feature.
  • Systems to integrate, their interfaces (FHIR, HL7 v2, other) and test environments.
  • Sign-in method for each user group.
  • Data items, legal basis, retention and where each is stored.
  • Data protection impact assessment and processing agreements.
  • Hosting location under the hospital's control.
  • Accessibility level and languages.
  • Store accounts in the hospital's name, or a web app where installation is not needed.
  • Support and maintenance after launch, including yearly iOS and Android updates.

How we help

We build patient and staff apps for healthcare organisations, from the first scope to store release and maintenance (see healthcare mobile app development), with EU hosting and the code in the client's own repository. For staff rosters, see healthcare scheduling software. For repetitive administrative work around the apps, read RPA in healthcare. For video visits and remote care, see telemedicine app development, and for products sold to hospitals as a service, read our healthcare SaaS guide. For record systems and apps that plug into an existing EHR, see EHR software development. For the build itself, see mobile app development and cross-platform apps, and for budgets, how much app development costs.

Questions people ask

What are hospital mobile apps used for?

Two groups of people use them. Patients use them to book and manage appointments, check in, find their way, read results and messages, and prepare for or recover from treatment. Staff use them for rosters, secure messaging, tasks, alerts, checklists and bedside access to parts of the patient record.

Is a hospital app a medical device?

Most are not: appointment booking, wayfinding, rosters and messaging are administrative. An app becomes a medical device when it is intended for diagnosis, monitoring or treatment decisions, such as calculating a dose or flagging a deteriorating patient. Then the EU Medical Device Regulation or FDA device rules apply, and the route is decided before development.

How does a hospital app connect to the patient record?

Through the interfaces the electronic health record system offers, increasingly based on HL7 FHIR. The app reads and writes only the resources it needs, with the user's own login and permissions, and every access is logged.

Can patients use the hospital app without installing it?

Often, yes. Many patient services work well as a web app that opens from a text message or email link, with an installable app for patients who use the service often, such as those in long treatment.

Where should patient data be stored?

In the hospital's own systems and in hosting the hospital controls, in the EU for European hospitals, with as little as possible stored on the phone. Apple's guidelines also prohibit storing personal health information in iCloud.

Sources