Build and version eCRF efficiently.
Protocols get amended, and whether that takes an afternoon or six weeks is mostly a question of how well the tool was thought through. MonitoHQ puts eCRF design in the study team's hands, with versioning strict enough to make mid-study change safe.
- Browser-based design
- Versioned forms
- Reusable library
- Edit-check rules
- 01Draft the new version
- 02Add or change edit checks
- 03Map to visits
- 04Review the change set
- 05Publish with a version
- 06Prior data keeps its version
No vendor queue between the decision and the form.
Amendments stop being a six-week errand.
Form design belongs to the people who read the protocol, with versioning strict enough to make mid-study change safe.
Your study team owns the form
Fields, edit checks and visit mapping edited in the browser, not queued behind a change request.
Versioning protects existing data
Data stays bound to the version it was collected under. A form change never re-interprets it.
Rules live beside the fields
Edit checks are built where the field is defined, so validation and form cannot drift apart.
A library, not a precedent
Demographics, AE and con-med forms saved and reused across studies.
Design, validate, map, publish.
Design
Numeric with units and ranges, coded lists, dates, free text, calculated values.
Validate
Attach rules to fields or across them, blocking entry or raising a query.
Map
Assigned to scheduled, conditional and unscheduled visits.
Review
See the change set against the current version before publishing.
Publish
Goes live with a version number. Existing data keeps the version it was collected under.
Form building, without engineering.
Field types
Numeric with units and ranges, coded lists, dates, free text, calculated and derived fields.
Edit-check builder
Range, consistency and cross-form rules defined next to the fields they govern.
Visit mapping
Forms assigned to scheduled, conditional and unscheduled visits in the schedule.
Version control
Every version retained, with what changed and when, and data bound to its version.
Reusable library
Save forms and rule sets and reuse them across studies.
Role-gated publishing
Drafting and publishing a live form are separate permissions.
Common questions
How is this different from the EDC page?
EDC is about capturing and monitoring data once forms exist. This is about building and versioning the forms themselves — field types, edit-check rules, visit mapping and what happens to already-entered data when a form changes. Different people, different week of the study.
Do we need a vendor change request to add a field?
No. Form design is done in the browser by your study team. That is the point: mid-study amendments are common, and routing each one through a vendor queue is what makes them slow.
What happens to existing data when a form is amended?
Forms are versioned. Data entered under an earlier version remains associated with that version, and the change history records what altered and when. Patients are not silently re-interpreted under a new definition.
Can we reuse a library of standard forms?
Yes. Forms and edit-check rules can be saved and reused across studies, so a demographics form or an AE form does not get rebuilt from scratch each time.
Connected in the same platform
Bring a form you had to amend mid-study.
30 minutes with a founder. We'll rebuild it, version it, and show what happens to data already entered under the previous version.