Patient app

For patients the app bundles what is otherwise spread across phone, paper and email: appointments, reminders, treatment plan, documents before the visit, messages to the practice. For the team that means fewer calls about routine questions and fewer missed appointments.

The second side matters: a panel for the practice team where requests arrive sorted and content is maintained. Without that tool you create one more channel that someone has to look after on top.

Health data is a special category of personal data. Concrete technical decisions follow from that: storage in the EU, encryption in transit and at rest, a role model that shows each person only their own patients, and a log of every access.

Consent is collected per purpose and can be withdrawn in the app. Push notifications carry no medical content — the lock screen only says there is something new. We conclude the necessary data processing agreements with you and your providers.

The most important question comes first: what is the app for? If it organises appointments, communication and information, it is generally not a medical device. If it evaluates data to support diagnosis or therapy, it can fall under the Medical Device Regulation — with consequences for documentation, risk management and schedule.

We are a development agency, not a certification body. So we clarify the classification early with you and, where needed, your regulatory adviser, and build so that the required documentation runs alongside from the start.

A first scope with appointments, reminders and messages is a manageable project. Each connection to existing systems adds effort.

• Interfaces to the practice or hospital information system — not every one offers an open API
• Video consultation, payments or prescription requests
• Multiple languages and accessibility: large type, screen readers, plain language
• Number of locations and roles