The EDC is live today — see what ships now
Plugs into the eClinical stack

Live today. Open at the edges.

You integrate once, at the platform boundary — not repeatedly between internal modules. The EDC drops into the stack you already run.

Roadmap module coverage

What we deliver via integration — by module.

Every roadmap module has named, supported partners. Whichever you use, your data lands on the same audit trail and data model as the EDC.

CTMS systems
In build

Site activation, milestones, monitoring visits, and CDSCO submission tracking are delivered through bidirectional integration with your existing CTMS while we build the native module. CTRI registration support lands as part of this milestone.

Your existing CTMSIn-house CRO operations systems
See the CTMS roadmap entry
eTMF systems
In build

Documents and metadata sync with your existing eTMF (or the shared-drive folder you call one); completeness tracking and TMF zone mapping mirror your DIA reference model until the native module ships.

Your existing eTMFShared-drive document roomsIn-house TMF systems
See the ETMF roadmap entry
eConsent platforms
Roadmap

Remote, in-clinic, and hybrid informed consent is delivered through supported eConsent partners — or scanned-paper ICF flows for low-connectivity sites — with signed ICFs on the same audit trail as the EDC.

Established eConsent providersPaper-based ICF flows
See the ECONSENT roadmap entry
ePRO / eCOA platforms
Roadmap

Patient-reported outcomes and clinical assessments flow into the trial data model via integrated ePRO/eCOA platforms — including mobile-first capture for low-bandwidth sites.

Established ePRO / eCOA providers
See the EPRO roadmap entry
RTSM / IWRS systems
Roadmap

Randomization and trial supply management connect via IRT; randomization assignments and kit dispensing are mapped to the volunteer record in the EDC — critical for BA-BE replicate-design studies.

4G ClinicalCenduitIn-house RTSM workflows
See the RTSM roadmap entry
Safety databases
Roadmap

Adverse and serious adverse events captured in the EDC reconcile and hand off cleanly to your safety database via ICH E2B(R3), with India PvPI reporting flows where applicable.

Your existing safety databaseRegulatory reporting gateways
See the SAFETY roadmap entry
Medical coding tools
Roadmap

Verbatim terms can be coded with your existing MedDRA and WHODrug tooling; assignments flow back onto the subject record with full audit history.

MedDRA and WHODrug dictionaries
See the CODING roadmap entry
RBQM and central monitoring tools
Roadmap

Risk signals and central monitoring connect via integrated RBQM tools; queries continue to flow through the EDC's single query workflow.

CluePointsCyntegrityIn-house QMS
See the QUALITY roadmap entry
Getting data out

Leaving is an export, not a project.

Domains build to CDISC SDTM structure from the data as captured, not from a mapping exercise at the end. Statistics gets a clean handoff, and so does anyone who decides to take their study elsewhere.

And every other connection

Plus the data sources, exports, and BI tools every trial needs.

CTRI registration
central labs
Hospital information systems
IRT / IWRS
Safety databases (E2B(R3))
CDISC pipelines
Power BI
Tableau

CDSCO & regulatory

  • CTRI registration (in build)
  • CDSCO Form CT-04 / CT-21 submission packs
  • DCGI / DBT-funded study workflows

Clinical data sources

  • central labs (SRL Diagnostics, Metropolis, Dr. Lal Pathlabs)
  • Hospital information systems via HL7 FHIR
  • Imaging and read-workflow vendors

Analytics & data warehouse

  • CDISC SDTM submission pipelines
  • Power BI, Tableau, Looker
  • Snowflake, BigQuery, Databricks (Mumbai-region)

Need a connection we haven't named?

Our integrations team builds and maintains the connections sponsors and CROs depend on. Tell us your stack and we'll come back with a plan.