PATIENT REGISTRIES

A registry your team can trust, record by record

Define what you hold on every patient once, give each a code instead of a name, and let your team and your patients fill it in over time, with every change recorded.

Start building for free
  1. 01 One data dictionary Every record follows the same fields, types and validation.
  2. 02 Identifiers kept apart Mark direct identifiers and special category data, and give everyone a generated ID to work with.
  3. 03 Every change recorded Who viewed, changed or exported what, and when, in an audit trail nobody can edit.
01

Define the registry

Build the data dictionary: every field you hold on a patient, its type, its validation and whether it identifies someone.
  • Generate a short code or UUID for every record, with your own prefix
  • Mark direct identifiers and special category data so they are kept out of tables and exports
  • Validation stops bad data at entry rather than at analysis
Generated IDs and random groups
02

Enrol with consent

Patients join through an onboarding flow with a consent statement they sign, or your team adds records and collects consent with them.
  • Versioned consent, so every signature is against a frozen copy
  • Optional clauses for future contact or data linkage
  • Patients can see what the registry holds about them and withdraw at any time
Onboarding flows
Join flow · Rare conditions registry Recruiting
  1. 1 About the registry
  2. 2 Eligibility A confirmed diagnosis and living in the UK
  3. 3 Consent
  4. 4 Your details
  5. 5 Clinical history
12 enrolled 3 automatically declined
03

Fill it in over time

Your team completes forms about each record, and patients answer questionnaires that update their record. Records
  • Data entry roles for staff who add data but shouldn’t manage the registry
  • Surveys sent to patients automatically at set points
  • Attach files such as letters or scans to a record

Popular features

Help centre

Common questions

Something else? Ask us or browse the help centre.
Can we remove a patient’s personal data but keep the registry data?
Yes. Erasing a patient’s personal data clears the fields marked as identifying and keeps the rest of the record for research.
Can staff enter data without seeing everything?
Yes. Roles control who can add data, manage participants, export or see the audit trail, and special category data is only exported when an owner or admin includes it.
Where is the data stored?
In London, in the United Kingdom, encrypted at rest and in transit.

Set up your registry for free, and pay when it goes live.

Build for free, pay when you go live. Set the whole project up for free, for as long as it takes. When you go live, pay monthly or yearly by card, or by invoice for each project year or the whole project up front. Academic and non-profit research gets a discount. See other use cases