One platform for every study, from first patient to database lock
- Five modules, one study record
- One audit trail
- AI with human review

Five modules. One study record.
How the pieces fit together
Data comes in
Sites
eCRFs, queries and signatures
EDC
Participants
Consent, diaries and questionnaires
eConsent · eCOA
Source documents
Clinic letters, lab and pathology reports
AI Data Extraction
Labs, devices and EHRs
File imports, FHIR R4 and HL7 v2
Imports & API
One study record
Clean, coded and locked in CDMS
- Review and queries
- Medical coding
- Reconciliation
- Database lock
One audit trail across every step
Data goes out
Analysis-ready exports
With metadata, for your statisticians
REST API
For your own systems and dashboards
Audit trail
Every change, exportable for inspection
Shared by every module
One data model
Every module writes to the same study record, so there is nothing to reconcile at lock.
One audit trail
Who changed what, when and why — across forms, consent, questionnaires and AI reviews.
Role-based access
Granular permissions per study, site and role, with single sign-on for your organisation.
Open API & integrations
Connect EHR, lab, IRT, safety and analytics systems instead of re-keying data.
Run it where your data needs to live
Managed cloud
We host, operate and update the platform for you. The quickest way to start, with nothing to install.
Your private cloud
The platform runs in your own cloud account, so study data stays inside the environment you control.
On-premises
For organisations whose data must stay on their own infrastructure, with the same features and governance.
Connects to what you already use
- Health records
- EHR connections over FHIR R4 and HL7 v2
- Labs and devices
- Central lab, device and wearable file imports
- Your systems
- REST API to read and write study data
- Sign-in
- Single sign-on with your organisation's identity provider
- Exports
- Analysis-ready datasets with metadata and the full audit trail
- AI models
- Model-agnostic — every proposal is reviewed by a person before it is saved
From first conversation to first patient
- 1Together
Discover
Walk through your protocol, your sites and the systems the study needs to connect to.
- 2Uplizd Clinax
Configure
Set up your environment, users, single sign-on and integrations.
- 3Study team
Build and test
Build the study in a test environment and run user acceptance testing — or let our team do it.
- 4Sites
Go live
Train sites in a short session and start enrolling participants.
Software, plus the people to run it
Built to the standards your study is held to
Security & privacy
ISO/IEC 27001
Information security management
SOC 2
Trust services criteria
ISO/IEC 27701
Privacy information management
GDPR
EU personal data
HIPAA
US health data
Clinical research practice
21 CFR Part 11
FDA electronic records & signatures
ICH E6(R3)
Good Clinical Practice
EU GMP Annex 11
Computerised systems
GAMP 5
Computerised system assurance
ALCOA+
Data integrity principles
Data standards
CDISC ODM
Study data interchange
HL7 FHIR R4
Health data exchange
Frameworks and standards Uplizd Clinax is built to support. Certification status available on request.
Book a demoFrequently asked questions
Do we have to use all five modules?
No. Start with the module you need today and switch on the others later. They share one data model, so nothing has to be migrated when you add one.
How long does implementation take?
It depends on your study and on how many systems it connects to. We agree a plan with dates in the first conversation, and our services team can take on the build to shorten it.
Where is our data hosted?
In our managed cloud, in your own private cloud, or on-premises. The product and its controls are the same wherever it runs.
How does the AI handle our data?
AI proposes values from source documents, each linked to the passage it came from. Nothing reaches the study record until a qualified reviewer approves it, and every proposal and decision is in the audit trail.
What do sites need to get started?
A modern web browser. Site staff sign in with their own account — or your single sign-on — and see only the studies and sites they work on.
Can we move a running study from another system?
Talk to us about your study. Migration depends on what the current system can export and where the study is in its life.