Available with limitations

Connect research data without losing provenance.

Moving data in from another system is only useful if you can say where each value came from and who was allowed to send it. ValidTrials can import some structured files, including a FHIR bundle for the real-world module, and can export CDISC-shaped packages from a freeze. A standard on this page is a format the code knows. It is not a certified connector and it is not a live feed from a named hospital system.

What this capability does

FHIR bundles

A bundle can be ingested with the source identifier hashed. Names are not stored.

CDISC-shaped export

SDTM- and ADaM-shaped files can be built from a freeze. They are not a CDISC CORE or Pinnacle 21 result.

ODM

A form can be imported from ODM. That is not a full ODM exchange with every vendor.

APIs

A scoped key can read what its scope allows. It cannot ask for platform administration or the audit log.

Webhooks

A public HTTPS address can be stored. Private and link-local addresses are refused. Delivery to an outside system was not demonstrated as a finished loop.

No named EHR

A hospital interface is a project, not a logo on this page.

How it works

Agree the contract

What is sent, and under whose authority, is written down.

Map

A person maps fields. The software does not guess a clinical meaning.

Load

The import stores provenance.

Reconcile

A person compares counts.

Connected modules and services

Questions

Is FHIR R4 support a certified interface?

No. The ingest accepts a bundle and hashes the patient id.

Do you connect to Veeva, Medidata, Oracle, Castor or Medrio?

No live connection is claimed.

Available with limitations means the described software behavior exists. A professional service is work a person does under a separate scope. Nothing here is a certification.

See the workflow on your protocol.

The conversation is about your study design and what the software can and cannot do today.