blueSource manual

Secures clinical trial data collection with cryptographic signing and tamper detection, producing verifiable electronic source records.

What this product is and is not

Is: Cryptographic eSource for clinical trials.

Is not: Not a trial management system, not an electronic data capture (EDC) platform on its own, and not a replacement for existing trial infrastructure.

Who uses it

Clinical trial sponsors, CROs, and research integrity teams.

Getting started — the local demo

From the product's own repository:

make demo
make verify-demo

This runs entirely offline against synthetic fixtures and exits non-zero on any mismatch. It does not connect to any production data source.

Screen-by-screen walkthrough

Enrollment intake — source record form Signature verification — the receipt proving cryptographic integrity Audit trail — entry timestamps and signer identity

blueSource Remote monitor detail: a monitor account verifies binding integrity by cryptographic receipt without viewing underlying chart data. — Synthetic study data
Signature verification — a monitor verifies the cryptography, not the chart; values stay withheld and verification still succeeds.

What a receipt proves

A signed receipt proves what blueSource ran and recorded; it does not prove an underlying real-world claim is true. Anyone can check the signature offline with the standalone verifier shipped alongside the product, without installing blueSource itself.

Known gaps, stated plainly

Demo build (v1); no clinical trial deployment or real trial data processed.
Integration with trial EDC platforms is planned but not yet implemented.

FAQ

Does blueSource make the decision for me?

No. Not a trial management system, not an electronic data capture (EDC) platform on its own, and not a replacement for existing trial infrastructure.

Does blueSource replace the system I already use?

No — it is an overlay. Your existing record system, LIMS, or claims platform stays exactly where it is.