Appearance
Mobile App
The Medipal mobile app is the patient-facing companion to the Medipal platform. Patients use it to answer the questionnaires their healthcare provider has scheduled for them, on their own phone, at the times the care team has chosen.
What the app does
| Capability | What it means for the patient |
|---|---|
| Paired to an organisation | The app connects to the Medipal instance of the organisation that invited the patient. One phone can be paired with several organisations at the same time. |
| Scheduled questionnaires | Questionnaires appear on the home screen when their access window opens and disappear when it closes. Spontaneous questionnaires can be answered at any time. |
| Offline-first | Questionnaires and their rendering engines are stored on the device. Answers given without a connection are queued and sent automatically when the phone is online. |
| Reminders | Local reminders are derived from the schedule so the patient is told when a questionnaire is due, even when the app is closed. |
| Same rendering as the web | The app uses the same questionnaire engine as the web application, so a questionnaire looks and behaves identically on every channel. |
| Consent | Consent documents published by the organisation are shown at pairing time, and enrollment-specific terms are shown before the first answer. |
| Multi-language | The app interface is available in ten languages. Each questionnaire can be answered in any language the author has provided. |
| Accessibility | Text zoom, high-contrast mode and light, dark or system theme are available in Settings. |
| Records | The Records screen lists the organisations the device is paired with, each enrollment and its status, and the policies the patient accepted. |
Platforms
The app is published for iOS and Android. It is built once and distributed through the public app stores; organisations do not need their own build. When a patient pairs the app with an organisation, the app learns where that organisation's instance lives and talks to it directly from then on.
Feature updates to questionnaire rendering and to the app's own screens can be delivered without a new store release. See Live Updates.
How a patient gets started
- A clinician creates an enrollment in the web application and generates an invite for the patient (a QR code or a link). See Patients & Devices.
- The patient installs the app from the store and opens the invite. See Pairing & Sign-in.
- The patient reviews and accepts the consent documents.
- The app downloads the questionnaires and schedules, and reminders are set up.
- When a questionnaire becomes available, the patient answers it; answers are sent immediately or as soon as the phone is back online. See Offline & Sync.
Screens at a glance
| Screen | Purpose |
|---|---|
| Home | Questionnaires that are available now or coming up, with the time until the next window opens. |
| Records | Paired organisations, enrollments and their status, accepted policies, and a place to paste an invite code. |
| Settings | Language, theme, accessibility, privacy policy, terms of service and information about the app. |
A demo questionnaire is available on the Home screen before pairing so a patient can see how answering works.
Related pages
- Scheduling & Enrollments — how clinicians define when questionnaires are available.
- Questionnaire Engine — how questionnaires are rendered on every channel.
- Troubleshooting — common problems and their fixes.