RURequest a demo

Moving from OpenClinica — without silent losses

CRF design from OpenClinica 3.x templates becomes a regular design version. Whatever the format cannot express goes into the migration report.

Request a demoDocumentation
Migration report
vital_signs_v3.xls → draft version 1.0
  • Sections, groups and fields42 fields, 2 repeating groupsMoved
  • Code lists and display conditions6 code lists, 4 conditionsMoved
  • Range checksRun in previewCheck
  • Not expressible in the format1 rule — in the reportAttention

The essentials

What moves over

Forms and sections, groups including repeating ones, typed fields, code lists, display conditions, range checks and calculated fields.

What to check

Skip logic and checks — in terms of the rules engine, by running the form preview. Publishing the version stays a regular managed step.

And back

The module exports a version’s design to OpenClinica 3.x templates — one file per form, with a report of what the format cannot express.

How the move works

  1. 01ExportCRF templates from OpenClinica 3.x (.xls) — one form per file.
  2. 02ImportThe module builds a draft design version and a migration report.
  3. 03ReconcileTogether we compare the result with the source CRF in preview.
  4. 04PublishReview and approval — as for any design version.

Questions

Related regulations

21 CFR Part 11EAEU GCP Rules

How to set it up — in the documentation

Does clinical data move over too?

The module moves the CRF design. Moving data is part of the onboarding project — on your export.

Which OpenClinica versions are supported?

OpenClinica 3.x CRF templates (.xls) — for import and export.

eCRF and form builderForms, visits and checks — no programmer needed.EDC systemThe whole study lifecycle — from design to database lock.Queries and cleaningChecks on save and queries at the value.

See the system on your own scenario

We walk through the full cycle on a demo study and answer your validation and hosting questions.

Request a demo