Why YouEDC

YouEDC is an EDC like any other. Just a little more.

Everything you expect from an EDC is here: eCRF, queries, SDV, signatures, the audit trail. On top of it, 11 things a typical old-school EDC does not have. Each already works in the portal, and each says where to find it.

  • Demo studies with data right after sign-in
  • Russian and English
  • Your data belongs to you
7sections in one portal: Capture, Studio, Safety, Sites, Trials, Supply, Biostat
1database: no transfers between systems, no manual reconciliations
2,300+automated tests pass before every build
11things a typical old-school EDC does not have
The name

First You, then EDC

The name has two words, and their order is not an accident. The person comes first: the one who enters the data, the one who checks it, and the one the data is about. The tool comes second. A good, precise, validated one, but a tool.

  • For youThe physician, the data manager, the statistician and the patient each have their own EDC. Every action is an explicit button, the menu does not jump.
  • Yours by rightData belongs to the users and can be exported in full at any moment. The audit trail is the memory and the honesty of the system.
  • Grows with youUsers’ remarks, open release articles, new functions in the demo at once. The portal is made by people who care.
A clinical trial is a pact of trust. The EDC is the place where trust becomes data.
The main difference

Five systems and reconciliations between them, or one portal

An old EDC does eCRF only. Everything else lives in separate systems, and data moves between them by exports and manual reconciliations. In YouEDC these are sections of one portal over one database.

A typical old-school EDC

The EDC and several more vendors next to it

EDCeCRF and queries only ePRO vendorits own database, transfer to the EDC IWRSrandomisation and drug supply apart Safety databaseSAE reconciliation by hand eTMF and CTMSdocuments and monitoring apart Excel and SASreports and statistics after the export
exportsmanual reconciliationsseveral contracts

YouEDC

One portal, one database, one audit trail

YouEDC CaptureeCRF, ePRO, eConsent, randomisation, TMF YouEDC StudioDM tools for data from other systems YouEDC Safetypharmacovigilance, E2B, DSUR YouEDC Sitessites and investigators YouEDC Trialsmonitoring, deviations, site payments YouEDC Supplythe drug from the depot to the patient YouEDC Biostatstatistics on live data
no transfersno manual reconciliationsone sign-in
11 reasons

What YouEDC does beyond an ordinary EDC

Short, to the point, and with the place in the portal where you can see it.

1

A study from its protocol

Upload the protocol PDF and get a draft of visits → forms → fields, with quotes and the contradictions found. A protocol amendment is compared with the current set-up.

UsuallyAll of it is built by hand over weeks.

Where: New study from a protocol; eCRF builder → Auto-setup log, Protocol amendments

The auto-setup log: what was set up from the protocol, what to check and where the contradictions are
2

A safe eCRF amendment

A QA environment, UAT with steps made from the design itself and with signatures. Before the release the draft runs over the live data: you see which forms will turn into errors.

UsuallyCRF versions exist, but no impact analysis, and UAT lives in Excel.

Where: eCRF builder → eCRF versions, test environment and UAT

The eCRF draft run over the working data: new errors, what to add, new automatic queries
3

Validation out of the box

The portal writes the package for GAMP 5, Part 11 and Annex 11 itself, the IQ report, a validation kit for every eCRF version and the DVP straight from the checks that run.

UsuallyThe customer writes it, or the vendor does for extra money.

Where: Validation package, DM documents · more on validation

Validation package written from the portal's data
  • GAMP 5 assessment
  • Requirements and traceability
  • Part 11 and Annex 11 compliance
  • Installation IQ report
  • UAT with steps and signatures
  • A kit for every eCRF version
  • DVP from the checks that run
  • Sent to the TMF in one press
ZIP · versions · electronic signatures · SHA-256
4

One portal instead of five systems

Capture, Safety (pharmacovigilance, E2B, DSUR), TMF, Trials (monitoring, CTMS), Supply (drug supply), Biostat.

UsuallyAn old EDC does eCRF only; the rest lives in separate systems and is reconciled by hand. Some vendors have part of these modules too, at extra cost.

Where: the section switch at the top left · the diagram above

One database one audit trail
eCRFePROeConsentRandomisationDrug supplyPharmacovigilanceE2BDSUReTMFMonitoringDeviationsSite paymentsCodingCDISCBiostatistics
5

Randomisation with a simulator

Minimisation and blocks, a run of the scheme on invented patients before the start (balance and predictability), emergency unblinding.

UsuallyNo randomisation of its own, a separate IWRS is needed. And where there is one, there is no simulator.

Where: Capture → Randomisation

Why the patient got this arm: the minimisation by factors
6 What we grow fastest

Biostatistics online, on live data

The statistics count themselves, straight from the study's data as it is now. No waiting for an export, no programs to write, no tables to assemble: open the page and see enrolment, how patients take part, the key variables over the visits, adverse events and time to event, by arm. A PDF report in one press.

UsuallyStatistics are counted outside, after the export, weeks later.
YouEDC Biostat: the tiles, enrolment by month and how the patients take part, by arm
Enrolment and taking part by arm, cumulative.
Kaplan–Meier curves with 95 % CI and adverse events per 100 patient-years
Kaplan–Meier with 95 % CI and AEs per 100 patient-years.
At any momentThe numbers are recounted from the live data each time the page opens.
Your choice of variablesYou choose the key eCRF variables: by visit, change from baseline, by arm.
Data cutsA frozen cut with its SHA-256 for an interim analysis reproduces even years later.
Analysis planEstimands by ICH E9(R1) and a check of the design against the eCRF.
NextAn analysis plan locked before the dataCONSORT and STROBE tablesA dietary supplement study template
7

Coding and CDISC inside

MedDRA and WHODrug under the customer's licence, ATC, ICD, plus SDTM, ADaM, Define-XML and aCRF.

UsuallyThe EDC hands over CSV or ODM, and SDTM and coding are done outside.

Where: Capture → Medical coding; Studio → CDISC: SDTM, ADaM, Define-XML

Dictionaries and standards inside the portal
MedDRAWHODrugATCICD-10SDTMADaMDefine-XMLaCRFCDASHODMSAS XPT
MedDRA and WHODrug are connected under your licence
8

No extra hardware for the patient

ePRO as a PWA works without the internet, sign-in by QR code and PIN. A tablet at the site, a legal representative, reminders by e-mail and SMS, remote consent.

UsuallyNo ePRO at all, or it is a separate product.

Where: Capture → ePRO adherence, Informed consent · more on ePRO

9

Data that arrives by itself

Lab results are read from the laboratory's PDF and from a photo of the form; import from the medical record by FHIR and SEMD, device data, an API.

UsuallyManual entry or an Excel template.

Where: Capture → Lab documents, Health records (FHIR), Device data, API

Checking a lab document: the values from the photo of the form next to the fields
10

DM routine on autopilot

Data analytics (outliers, trends), audit trail review by E6(R3), lock readiness by site, a weekly report to the sponsor and scheduled data delivery to SFTP, bulk DCRs. Plus a DM assistant that runs on a local model only.

UsuallyAll of it is done by hand in Excel.

Where: Studio → Data analytics; Capture → Central monitoring, Audit trail review, Status report, Data deliveries, Data change requests

Data analytics: weekly trends by site Central statistical monitoring: a site against the others
11

Access and protection of 2026

2FA, SSO (SAML/OIDC), field encryption of personal data with AES-256 in the application (152-FZ, GDPR), an inspector role with an end date, access review with a signature, automatic lock of unused accounts.

UsuallyA login, a password and a manual procedure.

Where: Profile; Project settings → Security, Team

Security no third-party services needed
  • 2FA sign-in, required by the admin's choice
  • SSO by SAML and OIDC
  • AES-256-GCM encryption of personal data
  • Inspector and auditor with an access end date
  • Team review with a signature
  • Automatic lock of unused accounts
Comparison

An old EDC and YouEDC on one page

TaskA typical old-school EDCYouEDC
Set up a studyby hand from the protocol, weeksa draft from the protocol PDF, with quotes
Release an eCRF amendmentUAT in Excel, impact unseenQA environment, signed UAT, a run over live data
Validationwritten by the customer or the vendor for moneythe package is written from the portal's data
ePRO, randomisation, safetyseparate vendors and reconciliationssections of one portal
Statisticsafter the export, weeks lateronline, on live data, by arm
SDTM and codingoutside, in separate toolsinside the portal
Lab resultsmanual entryfrom PDF and a photo of the form, FHIR, SEMD
Sponsor report and data transferby hand in Excelon a schedule, by itself
Sign-in and accessa login and a password2FA, SSO, encryption of personal data, access review
Honestly

No exaggeration

We compare with a typical old-school EDC, not with every system on the market.

Others have it too

We have double data entry from paper, but old EDCs have had it for a long time, so it is not on this list. Some vendors have randomisation and ePRO, usually as a separate module.

AI only if you want it

The DM assistant and AI reading of the protocol run only on your installation's local model and are switched on separately. Patients' data never goes to third-party clouds.

Descriptive statistics

YouEDC Biostat shows descriptive statistics of the current data. It does not replace the analysis by the statistical analysis plan and does not prove efficacy.