A clinical trial coordinator at a graphite steel workbench reviewing a study binder under a single hard task light, with a monitor glow at her shoulder

Capability Guides

What each trial technology system is
for

Clinical technology gets discussed in acronyms as if everyone already knows what they mean. These guides explain what each core system does, where it fits, and what to check before assuming a platform's version of it will cover your study.

Open the guides Compare platforms on these capabilities

Start here

A guided read, not a brochure

This set walks through the seven capabilities that show up in nearly every modern platform conversation: randomization and trial supply management, the clinical database, operational oversight, outcome assessment, participant consent, document control, and finally how to match a capability to the study you are actually running. Each guide names what the system does, where it sits in the chain, and the questions worth asking before you assume your platform covers it.

Read them in order for the full picture, or jump to the system you are evaluating this quarter. The wording stays plain on purpose — you should be able to hand a guide to a study manager and have it land without translation.

Jump to the seven guides

Guide Randomization and trial supply management Where assignment and the supply chain it triggers live, and why they are rarely equal in depth.
Guide EDC and the clinical database The reconciliation between randomization and enrollment that is invisible until it breaks.
Guide CTMS and operational oversight The study manager's daily view, and what changes when it is bundled rather than bought alone.
Guide eCOA and ePRO Instruments, translation, and how the data lands in your analysis set.
Guide eConsent and participant workflows Comprehension checks, re-consent triggers, and the handoff to randomization.
Guide eTMF and document control Filing, version control, and whether the system reconciles with what sites already file.
Method Matching a capability to a study need A five-workflow discipline that keeps a comparison grounded in the study, not the brochure.

A sealed temperature-controlled trial-supply carton on a graphite steel bench under one hard task light

A sealed kit on the bench — the physical thing every capability ultimately serves

The seven guides

One system at a time, plainly

Each bay below names what a system does, where it sits in the chain, and the specific questions that separate a working implementation from a checkbox feature. Nothing here is a sales claim — it is the reading you would want before a scoped walkthrough.

Guide 1

Randomisation and trial supply

RTSM assigns participants to treatment arms and manages the supply chain that follows. That second half is where most of the complexity lives.

A working RTSM tracks kit allocation, resupply triggers, expiry, quarantine, and temperature excursions, and it enforces unblinding rules for the people allowed to break them.

What to check Live in the demo

Kit allocation, resupply triggers, expiry, quarantine, and temperature-excursion handling in the same walkthrough — not as separate slides.

Common gap

Randomization is a mathematical exercise. Supply management is a logistics one — a platform strong in the first can be average at the second. Ask for both in the demo.

Where it breaks Interface risk

When RTSM and EDC come from different vendors, someone has to own the interface specification, the mapping between randomization and enrollment records, and the reconciliation schedule.

Price it honestly

If you are comparing a suite against separate best-in-class systems, this is the interface to price honestly. Everything downstream depends on it staying correct.

Guide 2

EDC and the clinical database

Electronic data capture holds the clinical database, and RTSM has to reconcile with it. That reconciliation work is invisible until it breaks.

Guide 3

CTMS and operational oversight

A clinical trial management system tracks site activity, enrollment, monitoring visits, and study milestones. It is the operational view a study manager actually lives in, and it is increasingly bundled.

Medrio announced a CTMS in November 2026 as part of a connected platform, which fits a wider consolidation pattern where RTSM, eTMF, EDC, and CTMS are sold together.

For bundling

Fewer handoffs between the RTSM, eTMF, EDC and CTMS systems a study touches, and one vendor to reconcile with when a record moves between them.

Against bundling

A module added late in a portfolio's life may not match a specialist tool's depth. Ask which workflow your study manager will live in daily, then look at that one first.

Worth asking

Instrument libraries, translation management, and how the data lands in your analysis set — the questions that separate a usable eCOA module from a checkbox one.

Where it stands

Suvoda, Signant, and Medrio all carry these capabilities in current platform descriptions. In practice, eCOA is a standard adjacent module rather than a differentiator.

Guide 4

eCOA and ePRO

Electronic clinical outcome assessment covers the instruments that capture what participants and clinicians report. Electronic patient-reported outcomes is the participant-facing part of that.

Guide 5

eConsent and participant workflows

eConsent moves informed consent to a screen, which raises questions a paper process did not. How is comprehension checked? How are re-consents triggered when a protocol changes? How does a signed consent hand off to randomization without duplicate entry?

Medidata's myMedidata illustrates the wider push toward participant-facing layers that combine consent, questionnaires, and visit reminders behind one login. Convenience is genuine. So is the lock-in — a participant-facing module pulls you deeper into that vendor's stack.

Constrain on paper

Comprehension checks, re-consent triggers, and the signing-to-randomization handoff — each with an owner named before the first participant is enrolled.

The trade-off

A participant-facing module is one of the easiest places to slide deeper into a single vendor's stack. Worth naming at the decision table.

What it actually does

Filing, version control, completeness checks, and audit trails. A workflow system the trial master file maintains, rather than a headline trend.

Duplication risk

Ask how the module reconciles with what the site already files. A document control system that duplicates site effort adds work instead of removing it.

Guide 6

eTMF and document control

The trial master file system keeps the study's document record inspection-ready. It appears in modern platform bundles alongside CTMS and EDC, and Medrio names eTMF in its connected suite.

Method

Matching a capability to a study need

Capability checklists are easy to inflate. A more disciplined approach is to write down the five workflows your study cannot survive without, then check how each platform handles those five in a scoped walkthrough.

Everything else is optional by definition. This keeps a comparison grounded in the study rather than the brochure, and it keeps a straightforward trial from paying for adaptive-design machinery it will never use.

01Name the five workflows your study cannot survive without.
02Map each one to the platform's version in a scoped walkthrough.
03Leave the remaining items out of the decision by definition.
04Check the reconciliation cost between whichever systems you pick.

Read side by side

How the same question changes across systems

The same operational question tends to get a different answer depending on which system you are standing in. Read the left column as the RTSM and supply-management side, the right as the wider eClinical suite. Nothing here is a score — it is what the two sides actually do with the same concern.

RTSM side

eClinical side

RTSM and supply

Left column

Assignment Arm assignment and the randomization record the study will reference for every reconciliation downstream.
Supply Kit allocation, resupply triggers, expiry, quarantine, temperature excursions, and unblinding rules.
Interface Owns the interface specification and reconciliation schedule with the clinical database.
Demo check Ask for the logistics half in the same walkthrough as the mathematics half.

eClinical suite

Right column

CTMS Site activity, enrollment, monitoring visits, and study milestones — the study manager's daily view.
EDC Holds the clinical database and the reconciliation records an RTSM assignment has to line up with.
eCOA / ePRO Instruments and participant-facing reporting that land in the analysis set alongside the clinical database.
eTMF Filing, version control, completeness checks, and audit trails for the study record.

The point of reading them side by side is not to pick a winner. It is to see which concerns the two sides actually own, so that when a vendor says "connected platform" you can name the workflow that lands between the systems — and ask who is carrying it.

Compare platforms on these capabilities

Outside this guide set

Not every system is a capability question

Some questions belong to study design or statistical methodology rather than to platform capability. Adaptive-design machinery, Bayesian interim frameworks, and novel endpoint qualification sit outside this guide set — the platform is not the place where those decisions resolve.

This one is a design question, not a platform one.

If your study needs one of those disciplines, the platform comparison here is not the right tool. Bring it to the scoping call and it can be routed to the right place.

A quiet monitor room in a clinical research office at 8am, with morning light entering at a low angle across a graphite steel desk

A monitor room at 8am — where the operational view is read every morning

What teams ask first

Four questions that shape the decision

Which of these capabilities does our study actually need?

Most studies need three to five of the seven. Write the list down before the demo — it keeps a straightforward trial from paying for adaptive-design machinery it will never use.
Check your study complexity
Do we buy a bundle or best-in-class separate systems?

Bundling reduces handoffs and consolidates the vendor relationship. Separates give you deeper tooling per capability if you can own the interface specifications between them.
Compare platforms on these capabilities
How do we tell a strong capability from a checkbox?

Run the five-workflow discipline: name what your study cannot survive without, then watch the platform handle those five in a scoped walkthrough. Everything outside is optional.
Read how we evaluate claims
What does the reconciliation between systems actually cost?

Someone owns the interface specification and the mapping between randomization and enrollment records. That work is real budget even when it does not show up on a slide.
Ask a capability question

About these guides

How we keep them honest

Every guide names what the system does and what it does not. Where a vendor's public platform description says one thing and the operational answer is another, both are written down. Where a capability is a standard adjacent module rather than a differentiator, that is stated plainly.

Sudova Agent is a clinical technology resource for sponsors and clinical operations teams in the United States. If a guide has an error, a gap, or a claim you disagree with, a correction is welcome — write to [email protected] and it will be reviewed. The contact block below is where the rest of the site continues.

Ask a capability question About Sudova Agent

Where to reach us

Cambridge, Massachusetts

Office: 1201 Innovation Drive, Suite 300
Cambridge, MA 02142, USA
Phone: +1-617-555-0184
Email: [email protected]
Hours: Monday–Friday, 9:00 AM – 6:00 PM

Request information

1201 Innovation Drive, Suite 300, Cambridge, MA 02142

What each trial technology system is for