DCT Built for hybrid and decentralized trials in the US

See your whole trial. Prove every data point

Decentralized trials spread patient data across EDC, IRT, eCOA, labs, wearables and home visits. SourceParity brings it into one independent view, proves every mismatch, and keeps your data ready for FDA submission and inspection

Read-only by designBuilt for 21 CFR Part 11Rules built for GAMP 5 validationICH E6(R3) sponsor oversightFDA submission-ready dataNo direct patient identifiers
The problem

Decentralized trials multiplied the sources. Reconciliation is still done by hand

12hours

a week per study spent on manual reconciliation

Veeva Clinical Data Industry Research, 2025
97%

of teams reconcile outside their clinical systems

Veeva, 2025
36days

on average from last patient visit to database lock

Tufts CSDD
How it works

One engine checks every source. Three answers come out

EDC subject data
IRT randomization, kits
ePRO and eCOA patient diaries
Central and local labs results, samples
Devices wearables, home visits
SourceParitySourceParityReads exports, read-only. Checks every pair against your protocol rules on every load
Where monitors go

Only the sites where data does not match

Who is ready for lock

Patient by patient, every day

Evidence for inspection

Every finding and decision, ready to export

Where to monitor

Send monitors where the data breaks. Skip the rest

Each month SourceParity names the sites that need a visit and the ones where every source agrees, with the reason for each

  • Sites ranked by open mismatches per subject
  • Late source feeds flagged next to the site
  • Visits saved, counted at your own cost per visit
This month, visit 3 of 12 sites The other 9 reconcile
PL-021
Visit
ES-009
Visit
US-104
Visit
US-101
Remote
DE-013
Remote
9
on-site visits not needed
18 d
monitor days freed
−$27k
at $3,000 per visit
Lock readiness

Lock patients as their data reconciles. Not all at once at the end

See who is clean, who is waiting and exactly what is holding each subject back

  • Every blocker named, with its owner
  • Projected lock date at the current pace
  • Locked records stay sealed; reopening keeps the original

184 subjects

Projected full lock: 12 Dec 2026
Locked 96Ready 31Waiting 57
PL021-101Device vs diary, bed-rest day34 d
PL021-107Kit 40 mg vs dose 20 mg12 d
ES009-204Sample outside visit window5 d
Evidence for inspection

When the inspector asks, the answer is one export

Every finding keeps both readings, the rule, the protocol section, who decided and when. Nothing is overwritten

  • Discrepancy listing for the whole study
  • Machine-readable audit trail
  • Version, lock and change control record

Evidence pack · LXP-301

Release 1.4.0 · rule set RS-2026-03 v3 · frozen 2 Mar 2026
Discrepancy listing, full studyCSV
Audit trail, every decisionJSON
Version, lock and change controlPDF
Data management summaryPDF
sha256 4d81…ef07SEALED
Start without risk

Start with a study you have already closed

Send us a recently locked study. We check it across every source and show what manual reconciliation missed. No risk to a running trial, and a clear answer in weeks

Retrospective audit · example

Closed study · Phase II · 88 subjects

37mismatches missed by manual reconciliation, still in the locked database
IRT vs EDC, kit and dose
11
Central lab vs visit date
9
ePRO vs EDC
8
Touching the primary endpoint
5

Example data

Design partner program

We are onboarding three design partners for early 2027

One closed study checked end to end, a fixed scope agreed upfront and direct access to the team building the system. Your feedback shapes what we build next

PARTNER 1Open
PARTNER 2Open
PARTNER 3Open
Trust

Built for regulated data. From the first line of code

Read-only

We read the exports your systems produce. We never write back to EDC, IRT or lab systems

No patient identities

Subject and site numbers only. Treatment assignment is never shown

Full audit trail

Every load, rule version, finding and decision is recorded and exportable

Validated rules, assessed AI

The rule engine is built for validation under GAMP 5. AI only explains findings, is assessed for fitness for use and never makes a GxP decision

Rules prove. AI explains. A person decides

FAQ

Questions sponsors ask us

Do you need access to our EDC?

No. We work from the exports your EDC, IRT, labs and vendors already produce. Access is read-only and nothing is ever written back to your systems

Where is our data stored, and who can see it?

In the US, on AWS. Only the people you grant access to can see a study, limited by study, site and data type, and every view is logged. We hold no direct patient identifiers, only subject and site numbers

How long does a retrospective audit take?

Usually a few weeks from receiving the exports, depending on the number of sources and the size of the study. You get a report of every mismatch with its evidence

How do you use AI?

The checks are deterministic rules, built to be validated like any GxP software, so every finding can be shown to an inspector. AI explains findings in plain language and suggests next steps. Its output is reviewed by a person, the model version is fixed, and it never changes data or makes decisions

Is the system validated?

We are building the validation package under GAMP 5 and 21 CFR Part 11 from day one, and we share it with our customers. The AI layer is not validated like deterministic software: it is assessed for fitness for its limited, advisory use, with human review of every output

What happens on the 30-minute call?

No slides. You tell us how you reconcile data today, and we show you what we would check first in your study

From first patient to FDA submission, know your data is right

30 minutes. Tell us how you reconcile today, and we'll show you what we would check first

Book a 30-min call30 minutes, no slides: you tell us how you reconcile, we show what we'd check firstinfo@getsourceparity.com