A line of temperature-logged clinical trial kit shippers on a depot bench under flat daylight

Editorial vendor profiles

How five clinical platforms position RTSM

These profiles give a short, factual read on how named vendors frame their RTSM, IRT, and eClinical capabilities — each one built from publicly available product documentation and vendor-published materials.

Reading these profiles

What each profile covers, and what it does not.

Every profile below covers the same ground: what the product is, where RTSM sits inside it, what the vendor emphasizes, and what a buyer should ask before including it on a shortlist. We do not score vendors on this page. Scoring happens against your study's criteria, which we cover on the platform comparison page. Where a vendor's published material makes a claim we cannot trace to a documented feature, we say so rather than repeating it as fact.

Sources

Public product documentation and vendor-published material only.

Scoring

None on this page. Scoring runs against your protocol on the comparison page.

Untraceable claims

Flagged as gaps rather than repeated as fact.

Sealed vendor dossiers

Five platforms, read as they position themselves.

Each profile is a short, factual read — a summary of how the vendor frames its own product, and the questions a buyer should carry into the first call.

01 Integrated

Medidata

Rave platform family — EDC, RTSM, and study management

Medidata shows up repeatedly in RTSM comparison guides, usually through the Rave platform family. The company is known for EDC, RTSM, and study management delivered as combinations inside one product line, and it is commonly positioned for enterprise-scale clinical operations.

For a buyer, the question is not whether Medidata can run RTSM — it clearly can. The question is whether the breadth of the platform is a benefit or a commitment for your organization, and whether the specific RTSM module is the most configurable option in the running. If you already run Rave studies, the integration argument is strong. If not, weigh the whole platform relationship, not the module.

Ask before shortlisting

  • How much of the platform is required to use the RTSM module in production?
  • Which supply algorithms ship natively, and which need configuration work billed separately?
02 Modular

Veeva RTSM

Modular randomization and trial supply management, connected to Veeva EDC and eCOA

Veeva RTSM is presented as a modular randomization and trial supply management solution that connects with Veeva EDC and Veeva eCOA. Published market summaries describe emergency unblinding and configurable supply algorithms, which puts the core RTSM functionality in line with specialist vendors.

The interesting design choice is the modular framing. It lets a sponsor adopt RTSM without taking the full Veeva clinical data stack at once, then add EDC or eCOA if that becomes the right move. The tradeoff is the one that comes with any modular approach: the value of the integration is highest for teams already on Veeva systems.

Ask before shortlisting

  • Which integrations are native to the RTSM module and which run through interfaces?
  • What does a sponsor on a non-Veeva EDC actually gain from the modular setup?
03 Suite-native

Viedoc RTSM

Built inside the Viedoc eClinical suite rather than sold standalone

Viedoc RTSM is built natively into the Viedoc eClinical suite rather than sold as a standalone product. Vendor materials describe support for both static and dynamic randomization and real-time kit management, and the suite is positioned as avoiding a separate IWRS or IVRS login in some use cases.

That last point sounds small and is not. Site coordinators who work in one application for EDC and randomization make fewer data entry mistakes, and every reconciliation report that does not need to run is time back on the study. For teams not already on Viedoc, the suite's coverage of downstream systems is the question to answer first.

Ask before shortlisting

  • Which downstream systems does the suite actually cover today vs. roadmap?
  • If we are not on Viedoc, what does the suite integration buy us that a specialist RTSM does not?
04 Operations

Almac Trial Coordinator

Fully integrated eClinical platform inside Almac's clinical technologies offering

Almac Trial Coordinator is described as a fully integrated eClinical platform and sits inside Almac's clinical technologies offering. The vendor markets it as a way to simplify and unify clinical trial operations, which places it in the clinical supply chain and study coordination conversation rather than the standalone RTSM market.

That positioning is worth noting at evaluation time. A platform that covers trial operations broadly will usually have a broader support relationship and a different commercial shape than a specialist RTSM. The buyer's question is which functions are natively built and which are delivered through partners, because that affects both support depth and how quickly changes move.

Ask before shortlisting

  • Which trial operations functions are built by Almac and which come through partners?
  • What does the commercial shape look like across a multi-year study vs. a standalone RTSM contract?
05 Study mgmt

Trial Interactive

Connected eClinical platform with study-management support across the study lifecycle

Trial Interactive provides a connected eClinical platform with study-management support that runs from site identification through study closeout. The company's positioning includes site collaboration and remote monitoring, which puts it in the broader clinical technology space rather than in RTSM specifically.

That makes it a different kind of shortlist candidate. If you are evaluating RTSM in isolation, Trial Interactive's relevance is mostly in what surrounds the RTSM. If you are assembling the wider operations stack, the study-management and monitoring capabilities are the reason to include it at all.

Ask before shortlisting

  • Which monitoring and site-collaboration functions are native vs. partner-built?
  • Where does the RTSM piece sit inside the wider operations stack?

The release condition

What these profiles do not tell you.

They do not tell you which platform fits your protocol, because nobody can answer that from the outside. They do not score build speed or amendment turnaround, because those numbers are study-specific and vendors rarely publish comparable figures. And they do not repeat vendor claims we cannot trace to published documentation.

What they do is give you a starting map of how each platform is positioned, so your first vendor call starts from a better question than "tell me about your RTSM."

The first call

Four questions to bring to every vendor.

Ask every vendor the same four questions and compare the answers side by side. The answers will tell you more than any feature matrix.

  1. 01

    Build queue length and how it moves

    How long is your current build queue for a study of our complexity, and how does that queue move when demand rises? A moving queue tells you more about delivery capacity than any static estimate.

  2. 02

    A recent amendment, retold honestly

    What is a recent amendment example, and did the study stay live during the change? Ask for the shape of the change and how long the study ran in a temporary state.

  3. 03

    Native vs. interface-based integrations

    Which integrations are native and which are interface-based, and who maintains the interface? Interfaces are fine — the question is who owns the break when one changes.

  4. 04

    Recent study types, with a recent example

    Which study types does your platform handle best, with an example from the last twelve months? The example matters more than the claim — ask what the study actually needed.

Reading the terminology

Older terms, current use.

Vendors still use different names for the same capability. When you compare profiles side by side, translate the vocabulary before you compare the feature.

  • IRT Interactive response technology — the oldest name in the category, still used by vendors who came up through phone-based systems.
  • IWRS Interactive web response system — the web-era abbreviation. Often used interchangeably with RTSM by vendors who also run supply management.
  • IVRS Interactive voice response system — the phone-entry convention. Some sites still describe patient randomisation in these words, whatever the vendor calls it today.
  • RTSM Randomization and trial supply management — the current term, and the one used throughout these profiles when a vendor positions randomization and kit logistics as one module.

Where a vendor's own materials still use IRT, IWRS, or IVRS, the profile keeps that vendor's vocabulary and notes the substitution here.

More in review

Vendors we are reading next.

These profiles are a working set. Coverage grows as vendors appear repeatedly in RTSM comparison discussions and their materials are traceable to published documentation. If a vendor should be here that is not, the contact page is the fastest way to tell us.

  • Platforms currently under review Shortlist stage
  • Coverage update cadence Reviewed as materials change
  • Reader suggestions considered Yes — via contact
Suggest a vendor for review
A clinical operations coordinator's hands working a blinded trial kit carton on a steel bench in a trial supply room
Site-randomisation work, photographed on the coordinator's bench. Trial supply

Questions about this page

What these profiles are, and are not.

Are these profiles sponsored by the vendors?

No. Suvodav Agent is independent and does not take referral fees or sponsorship for vendor coverage. Each profile is built from publicly available product documentation and vendor-published materials. Where a vendor's marketing makes a claim we cannot trace to documented functionality, we note the gap rather than repeat the claim as fact.

Why are only some RTSM vendors profiled?

We cover the platforms that appear repeatedly in RTSM comparison guides and vendor evaluation discussions. That is a working criterion, not a judgement about which platforms are best. If a vendor is missing that should be here, the contact page is the fastest way to tell us, and we will review the material.

Can I use these profiles to make a final platform decision?

Not on their own. The profiles tell you how each vendor positions its product and what to ask next. The final decision depends on your protocol's randomization scheme, your supply rules, your existing EDC and eCOA stack, and how much multi-vendor coordination your team can absorb. The platform comparison page walks through the criteria that actually decide that.

How current is the information in these profiles?

Each profile reflects vendor-published material at the time of writing. Vendor positioning and product scope change, sometimes quickly, so treat the profiles as a starting point for the conversation rather than a permanent record. If you spot a change we have missed, send it in through the contact page and we will review it.

Before the first call

A shortlist starts with a better question.

Read the profiles, take the four questions to every vendor, and compare the answers side by side before you compare feature lists. The platform comparison page walks through the delivery criteria that actually decide a study, and the RTSM and IRT guide covers the terminology you will hear on the call. If a vendor should be profiled that is not here yet, tell us — the review is ongoing, and reader input is the fastest way to grow it.

Released