eCRF design · ISO 14155 · medical device investigations

Best practices for eCRF design in medical device studies

Every data point that supports the safety and performance of a device passes through the eCRF before it is analyzed, reported and submitted. A well-designed form improves data quality, lightens the load on sites and shortens the path to database lock. A poor one produces inconsistent data, frustrated investigators and avoidable delay.

Protocol-drivenInvestigator usabilityIntelligent edit checksConditional logicDevice-specific fields
Electronic case report form design for medical device clinical investigations
From protocol to a validated form
1
Protocol & endpoints
2
Form inventory
3
Draft eCRF
4
Edit checks & logic
5
User acceptance testing
6
Deployment
The protocol drives the form. Every field on the eCRF should trace back to an objective, an endpoint, a safety requirement or a regulatory obligation.
Trusted by medical device teams running clinical investigations in Europe
TerumoMeril Life SciencesNihon KohdenVygonColoplastRegenLabAsahi InteccMolnlyckeTerumoMeril Life SciencesNihon KohdenVygonColoplastRegenLabAsahi InteccMolnlycke
Who manages your clinical data

The team that designs and tests your forms

EUCROF Platinum Award 2026
EUCROF Platinum Award 2026xShare Open Call for Clinical Research, co-funded by the European Union
Sebastien Meier Piantanida

Sébastien Meier Piantanida

Chief Data Officer
Biometrics & Data Systems

30yrs

in clinical data systems, biometrics and statistical reporting

  • Owns data management, biostatistics and EDC architecture across Eclevar studies
  • Vendor-independent on EDC platforms: see data management and eCRF platforms
  • Takes studies from database build to lock and analysis with biostatistics
LinkedIn
Jimmy Andrew Hayek

Jimmy Andrew Hayek

Head of Quality & Compliance
ISO 14155 & data integrity

10+yrs

in quality systems and inspection readiness for device studies

  • Holds the ALCOA+ line: attributable, contemporaneous, traceable data
  • Runs quality control on database validation and lock documentation
  • Prepares studies for audit and inspection under ISO 14155
LinkedIn
Dr Mark Da Costa

Dr Mark Da Costa

Chief Operating Officer · former TÜV SÜD Senior Reviewer

Former reviewer atTUV SUD
25+yrs

in device evaluation and Notified Body review

  • Assessed 400+ medical devices in Europe
  • Brings the reviewer perspective to every dataset we release
  • Oversees delivery across the full evidence program
LinkedIn
The stakes

Your database is only as good as your form

Investigators, study coordinators and research nurses interact with the eCRF throughout the study. Usability is not a nicety here, it is a direct input to data quality.

What good design delivers

  • Higher data accuracy and fewer transcription errors
  • Less missing data because the form makes completion obvious
  • Simpler investigator workflows and shorter training
  • Lower monitoring effort
  • Fewer queries, and better ones
  • A faster path to database lock

What the eCRF captures in a device study

  • Demographics, medical history, eligibility criteria
  • Device information, clinical assessments, follow-up visits
  • Adverse events and concomitant medications
  • Laboratory and imaging assessments
  • Device deficiencies and protocol deviations

Form design is one workstream inside clinical data management, and it is settled in the data management plan before the database is built.

Principles

Start with the protocol, design for the end user

The protocol drives the form, never the other way round. Then the form is shaped around the people who have to complete it forty times.

Every field earns its place

Each field traces to a study objective, an endpoint, safety monitoring, an analysis or a regulatory report. Collecting data because it might be useful later burdens sites and creates error opportunities.

Design for the person filling it in

Logical grouping, consistent layouts, clear labels and instructions, minimal scrolling, simple navigation, familiar clinical terminology.

Keep forms simple

Divide information into logical sections, separate forms per visit or assessment, no duplicate entry. Too much on one page is the most common design mistake.

Use standardized terminology

Align with the protocol, clinical practice, regulatory guidance and controlled vocabularies. Cardiac disorder, not heart issue. Consistency is what makes coding and analysis possible.

Make mandatory fields truly necessary

Require only what is essential for safety, eligibility, primary endpoints or regulatory reporting. Making everything mandatory encourages inaccurate entries just to proceed.

Avoid duplicate collection

Store date of birth and derive age. Two fields representing the same information will eventually disagree, and someone will have to reconcile them.

European delivery

The same form, seen from every site in the study

A form that works in one country is not automatically a form that works across the study. Language versions, readability and regional ethics review of the screens are planned before the database is frozen.

SITE-LEVEL DATA CAPTURE - EUROPE SITE-LEVEL DATA CAPTURE · EUROPE NOUKDEFRITES At the siteForms and instructions in the workinglanguage of the investigatorWatch: coordinator turnover mid-studyFranceFrench site documents, CNIL wordingWatch: readability of patient-facing screensNordics & UKEnglish master forms accepted, strongelectronic source availabilityWatch: source data access for remote reviewGermany & AustriaGerman screens expected at site levelWatch: dual-language edit check messagesSwitzerland, Italy & SpainThree language regions in one country;regional ethics review of the formsWatch: ePRO translations and validation

Language versions, screen readability and national wording are settled before the database is frozen, because changing a live form costs a validation cycle.

Validation

Edit checks that find real problems

Edit checks improve quality by catching issues at entry. They damage quality when there are so many that investigators stop reading them.

Range checks

Age cannot be negative. Blood pressure and heart rate stay within plausible clinical limits. Device measurements are in the expected unit.

Date validation

Informed consent cannot be dated after the first study visit. Follow-up visits occur after baseline. Implantation precedes explantation.

Logical validation

Pregnancy questions do not appear for male participants. A withdrawal is not followed by scheduled visits.

Cross-form validation

A serious adverse event on one form requires the corresponding safety forms to be completed.

Conditional logic

The adverse event detail section appears only when an event is reported. Irrelevant fields stay hidden, which cuts entry time and errors.

Proportionate checks

Validation intensity follows the importance of the variable, which is the core of risk-based data management.

Distinguish what was typed from what was imported
Distinguish what was typed from what was importedCentral laboratory results, imaging assessments, ePRO responses and device telemetry arrive from other systems. The form should make the difference visible, so traceability survives and nobody enters the same value twice.
Device specifics

The fields a pharmaceutical form does not have

Medical device investigations collect information that has no equivalent in drug studies, and it is the information the MDR traceability requirements care about most.

Design these carefully

  • Device model, serial number, batch or lot number
  • Implantation details and device configuration
  • Software version, including updates during the study
  • Device deficiencies and malfunctions
  • Corrective actions taken
  • Explantation information and device disposition

External sources to plan for

  • Central laboratories and imaging platforms
  • Wearable and connected devices
  • Electronic patient-reported outcomes
  • Device telemetry
  • Randomization systems

Structured capture of these fields is what makes device accountability reconstructible years later, whether for a clinical evaluation report, a device registry or a Notified Body question.

Before deployment

User acceptance testing, with clinical users in the room

Every eCRF undergoes comprehensive user acceptance testing before enrollment. Testing done only by the people who built the form finds only the errors they did not think of twice.

NavigationEdit checksConditional logicVisit schedulesData exportsPermissions & audit trail

Clinical users take part, because the question is not only whether the system behaves correctly but whether it supports the real workflow at a site. This runs alongside clinical monitoring preparation and the wider study start-up.

The mistakes that cost most. Unnecessary data, overly complex forms, excessive mandatory fields, inconsistent terminology, duplicate variables, poor navigation, too many edit checks, insufficient testing, and ignoring investigator feedback. Nearly all of them are difficult and expensive to correct once enrollment has started.

Compliance

Designed so the data stays trustworthy

The form has to support ISO 14155, ICH GCP E6, the EU MDR, FDA expectations and 21 CFR Part 11 where applicable, and it has to make the ALCOA+ principles achievable in practice.

Attributable and contemporaneous

The audit trail records who entered what and when, without the site having to do anything extra.

Legible and original

Entries are unambiguous, and the original value survives every correction.

Accurate and complete

Validation catches the implausible; the form structure makes omissions visible rather than silent.

Consistent, enduring, available

One terminology across forms and visits, exportable in a form biostatistics can analyze years later.

Platform

The form and the system are separate decisions

A good design can be built on most modern platforms, and a weak design will not be saved by an expensive one. Choose the form structure from the protocol, then check the platform can build it without heavy programming. We are vendor-independent, so the recommendation follows the study.

Electronic data capture platform configuration for a device investigation
Coming soon
FAQ

Questions teams ask about form design

What is the difference between an eCRF and an EDC system?

The EDC system is the software platform used to collect and manage clinical data. The eCRF is the electronic form inside that platform where investigators enter study data. Choosing the platform is covered on the EDC selection page.

How many edit checks should a study have?

There is no target number. Each check should identify a discrepancy that someone would act on. A check that generates queries nobody uses costs site goodwill and buys nothing.

Can the eCRF be changed after the study starts?

Yes, but every change means a revalidation cycle, potentially a database migration for data already entered, and retraining at sites. This is why user acceptance testing before enrollment pays for itself.

Who should be involved in eCRF design?

Data management owns the build, clinical operations checks it is usable at site level, biostatistics confirms the data supports the planned analysis, and regulatory checks what has to be reportable. Investigator feedback before freeze is worth more than any of them.

Do you design forms in platforms we already own?

Yes. We are vendor-independent and work in the sponsor platform where one is already in place, or help select one where it is not.

How do you handle patient-reported outcomes and wearable data?

As external sources with their own transfer specification and reconciliation rules, defined in the data management plan. The eCRF makes clear which values were entered at the site and which arrived from another system.

Start the conversation

Want your eCRF reviewed before it goes live?

Send us the protocol and the draft form set. We come back with a design review against the protocol and the analysis plan, the fields that will generate queries, and the device-specific data that is usually missing.

Your documents are reviewed confidentially. An NDA can be put in place before we receive any technical or clinical information. You can also reach the team through the contact page.

Reforming Clinical Evaluation of Medical Devices in Europe