What is Medipal

Medipal is a platform for medical questionnaires. Healthcare organisations use it to design questionnaires such as patient-reported outcome measures (PROMs), screening tools and follow-up surveys, deliver them to patients on a schedule, collect the answers on web and mobile, and turn the results into clinical insight.

Each organisation runs its own Medipal instance: a self-contained deployment with its own users, patients, questionnaires and data. Nothing is shared between instances.

Who uses Medipal

Audience	What they do	Start here
Clinicians and study teams	Design questionnaires, enrol patients, follow up on submissions, review results and dashboards	User Guide
Administrators	Manage users, roles and API keys, configure folders, install plugins, store credentials in the vault	Users, Roles & Scopes
Patients	Answer questionnaires on their phone, on time, even without a network connection	Mobile App
Questionnaire developers	Build custom questionnaire engines and question components that render inside the web and mobile apps	Questionnaire Engine
Integrators	Connect Medipal to other systems through the API, webhooks, EHR connectors and plugins	Integrations
Deploying partners	Install and operate a Medipal instance for an organisation	Deploying an Instance

Main capabilities

Capability	Summary
Questionnaire design	Visual designer with sections, many question types, conditional logic, variables, scoring functions, multiple languages, preview and simulation
Versioning	Every change is tracked as a revision; questionnaires are published explicitly and can be forked
Scheduling	Recurring or one-off schedules with access windows, calendar view and per-patient slots
Patient delivery	Patients pair the mobile app once and receive questionnaires automatically; anonymous links cover public surveys
Offline mobile app	Questionnaires are stored on the device, answered offline and synchronised later; reminders arrive as notifications
Questionnaire engines	Rendering is done by versioned engine bundles; organisations can build their own engines and custom question components
Folders and configuration	Questionnaires live in a folder tree; configuration and permissions set on a folder flow down to everything inside it
Workflows	Event-driven automation: react to submissions and other events with conditions, computations, HTTP calls, delays and plugin actions
Webhooks and events	Subscribe external systems to platform events with signed deliveries and automatic retries
Clinical sources (EHR)	Link patients to hospital records through FHIR and view clinical data next to questionnaire results
Analytics	Datasets, charts and dashboards built from submissions and clinical data, with presets for common clinical instruments
Consent documents	Versioned consent texts shown to patients before they take part
AI assistant	An assistant inside the web app that helps design questionnaires, schedules and engine configuration
Access control	Roles made of fine-grained scopes, scoped API keys, single sign-on and multi-factor authentication
Vault	Encrypted storage for credentials and secrets that other features reference by name
Plugins	Server-side plugins add actions to workflows and connect to external services; frontend plugins extend the web app

How the documentation is organised

• Overview explains the moving parts, the core concepts and the security model.
• User Guide walks through the web app feature by feature, from folders to troubleshooting.
• Questionnaire Engine is for developers who build engines and custom question components.
• Mobile App describes the patient experience and how to support it.
• API Server describes the server side in more depth: architecture and request lifecycle, API design, authentication and authorization, the data model, configuration and vault, events, the workflow engine, the plugin runtime, background jobs, database and migrations, the command line interface and observability. The Technology Stack page lists what each part is built with.
• Integrations covers the API, events and webhooks, EHR connectors, server and frontend plugins, and deployment.