EDCdata capture

The trial, running on the model.

The forms, the checks and the visit schedule come out of the study model rather than a vendor ticket queue. And because the model stays live after go-live, the study keeps answering to it: every value, every deviation and every amendment is read against the protocol itself.

Capture04 ideas

Four things that follow from capture knowing the protocol.

01Strange data, immediately Not at the next monitoring visit. A value that is implausible for this subject at this visit is flagged as it is typed — against the ranges this protocol defines, and against what the same subject recorded last time, rather than a generic bound.
02Deviations caught against the clause A visit outside its window, a missed assessment, a dose that does not match the assigned arm. The deviation is raised against the protocol section that established the requirement, so the finding arrives with its authority attached instead of as an opinion.
03An amendment states its own impact An amendment is a diff against the study model, so its consequences are visible before it is accepted: which forms change, which visit windows move, which findings are affected, which sites are touched. It is a review, not a change order.
04Audit as replay The audit trail is not an archive to be exported once at the end. It is a record that can be replayed: who changed what, when, under whose authority, and against which clause — months later, without asking us to explain it.
An AccuraTrials eCRF for vitals and assessment with branching logic and a resolved query in place
eCRF with a resolved query in place Vitals & Assessment
Branching logic configured on a generated form in AccuraTrials Studio
Branching logic on a generated form Accura Studio

Alsothe checklist

And the things an EDC is simply expected to do.

  • Queries — raised by a failed check or by hand, routed, threaded, escalated
  • SDV — form and field level, remote monitoring, complete verification log
  • Double entry — side-by-side adjudication for critical data
  • Locks — readiness check, freeze, sign, lock, export
  • Signatures — credential re-authentication, bound to the record version signed
  • Randomization — stratified, blinded arms, controlled unblinding, kit tracking
  • Coding — MedDRA and WHODrug against controlled terminology
  • Export — PDF, Excel, CSV, ODM XML, with the audit trail attached

FAQthe questions

EDC software questions.

What does EDC stand for?

Electronic data capture: the software a clinical trial uses to collect, validate, store and export study data, replacing paper case report forms with a system that catches errors at the point of entry.

How fast can a study go live?

Days rather than weeks for most studies, because the protocol drafts the build instead of a specification going into a queue. Review and validation still have to pass before activation — that part is not compressible.

Is it built for 21 CFR Part 11?

It is designed around those controls: a tamper-evident audit trail, electronic signatures with credential re-authentication, role-based access control, session management and data-locking workflows. Part 11 compliance is something a sponsor demonstrates for its own system and use, not a certificate a vendor holds — so what we offer is the machinery and the evidence. The section-by-section mapping is public.

Nextthe ask

See the build happen on your protocol.

Thirty minutes on the real platform. Bring a protocol and we will model it live.