eCRFs built without a programmer
Visits, forms and checks in the builder, with a live preview. A published version never changes; changes go through an amendment.
- Screening
- Demographics
- Eligibility
- Visit 3
- Vital signs
- Adverse events
- Type
- Number, 1 decimal
- Unit
- kg
- Range
- 30–250
- Out of range
- Open a query
The essentials
Typed fields, checks in words
Numbers with units and ranges, dates including partial ones, code lists, repeating groups. Checks, display conditions and derivations run in the core, on the server.
A version is published as a whole
Draft → review → approval → publication. A running study never changes silently: an amendment moves subjects to the new version with audit.
Design from a file
A JSON study package loads into the draft as a whole; designs from OpenClinica 3.x come in through a module. The package can be checked without changes, before import.
From draft to publication
- 01BuildA “visit → form” tree, fields, checks and display conditions.
- 02TryForm preview runs the same rules engine as data entry.
- 03AgreeReview and approval of the version; authors do not approve themselves.
- 04PublishThe version becomes immutable; sites get it at once.
Questions
Related regulations
How to set it up — in the documentation
Can a form change after the study starts?
Yes, through an amendment: the new version is reviewed and approved, subjects move to it with audit, and data already entered are not lost.
Where do checks run?
On the server, against the final state of the form: a blocking check rolls the write back, a soft one opens a query. A field hidden by a condition does not accept a value.
See also
See the system on your own scenario
We walk through the full cycle on a demo study and answer your validation and hosting questions.