SalesDemo
A WORKING DEMO · SYNTHETIC DATA · RESEARCH USE ONLY

The molecular baseline pattern program, end to end.

Every step of the operational chain, running: intake and consent, order creation, the draw, processing and aliquoting, manifest and shipment, lab receipt and accession, result upload — with role-based access at every point and a complete chain of custody behind it. Eight roles, one seeded dataset, nothing hypothetical. Walk it in any order.

Intake & consentdraw & processingmanifest & shipmentlab receipt & result

Pick any role and start anywhere. Nothing you do here touches a live system, and every value in it is invented.
Read the two-minute user guide →

What this demonstrates

Four things carry the weight. Every state change is attributable, every custody step is recorded, access is scoped to the role doing the work, and consent gates the whole chain rather than sitting beside it.

01
Research Use OnlyAn investigational molecular research program studying patterns in serum. Clinician-mediated, independent of standard care, and never a diagnosis. Individual results are not returned. The system is built around that constraint rather than apologising for it — the discipline is what makes the findings worth anything.
02
Role-based accessEight roles across clinic, processing lab and oversight. Each one sees exactly what its work requires and nothing else. The boundaries are real: switch roles and watch what disappears.
03
Chain of custodyDraw tube through cryovial, manifest line, shipment, receipt and accession — every hop recorded with actor, role, time and cause. One tube becomes several aliquots and the record follows all of them.
04
Consent, enforcedProgress blocks on unsigned consent and halts on withdrawal. The trail shows where it stopped and why. Consent here is a gate the workflow cannot route around, not a document filed after the fact.

How the chain works

Four stages, eight roles, one continuous record. Each stage hands off to the next with the custody trail intact — and the demo lets you enter at any of them.

Stage 1
Intake and consentA participant is enrolled and the consent is captured. Consent can be signed in person or handed to the participant’s own phone, which is what the prospect app in this demo shows. Nothing downstream moves until it is signed, and the order is created only once it has been.Roles: Intake Specialist, Clinic Admin
Stage 2
Draw and processingThe draw tube is scanned against the order, spun, and the serum transferred into barcoded cryovials. The tube itself does not travel — the aliquots do, and each carries its own identity from this point on.Roles: Clinic Lab Tech
Stage 3
Manifest and shipmentAliquots are assembled into a manifest and shipped. The manifest is de-identified by design: barcodes and quantities, no participant identity travelling with the box.Roles: Lab Ops
Stage 4
Receipt, accession and resultThe receiving lab confirms what arrived against what was sent, accessions what it accepts, rejects what fails inspection, and uploads the result. Rejection is part of the demo, not an edge case hidden from it.Roles: Lab Admin, Lab Tech, Clinician
Running alongside all four: the Compliance view, where the whole chain can be read back in one place.

Eight roles, one chain

Access is scoped to the work. Every role below is enterable in the demo, and you can return to the picker and change roles at any point.

RoleLine
Intake SpecialistEnrols the participant, captures consent, creates the order
Clinic AdminClinic-level oversight; deferrals and consent withdrawal
Clinic Lab TechScans the draw tube, spins it, aliquots into cryovials
Lab OpsBuilds the manifest and ships it
Lab AdminReceives, accessions, and rejects what fails inspection
Lab TechUploads the result
ClinicianOrder status and the population view
ComplianceReads the audit trail and the full chain of custody

Walk the demo

The console is the main surface: pick a role, walk its part of the chain, and come back to the picker whenever you want. The prospect app is here for one purpose — mobile consent signing. The console issues a QR; the phone signs it.

PHONE-FIRST · THE PARTICIPANT-FACING VIEW

Open the prospect app

What a participant sees on their own device. In this demo it does one job: consent signing. Scan the QR the console issues, read the statements, and sign on the phone. In the live portal that signature returns to the clinic’s record as it happens — here the two surfaces run independently, so what you see is the participant’s side of the handoff.

Open the app →
On a phone? You'll go straight in.
DESKTOP · STAFF-FACING · THE MAIN DEMO SURFACE

Open the Program Portal

The staff surface, and where most of the demo lives. Enrol a participant, capture consent, create the order, scan the draw tube, spin and aliquot it, build the manifest, ship it, receive and accession it, upload the result — then open the Compliance view and read the whole chain back.

Open the Console →
Desktop-first workstation. Start with any role; the picker is always one click away.

What is real here, and what is not

Real

The workflow, the role boundaries, the custody record, the consent gates, and the screens themselves. This is the software, not a mock-up of it. Every rule you run into is a rule the system actually enforces.

Not real

Every participant, value, result, clinic and staff member in it. All invented, all fixed — everyone who opens this demo sees the same dataset. Nothing here connects to a live system in either direction, and nothing you do is recorded anywhere but your own session.

Refresh the page and the demo returns to its starting state. Nothing you do can break it for the next person.
A sales demo. Every value, result and person in it is synthetic and illustrative.
Research Use Only. This is a research initiative — not a screening or diagnostic test. It does not return individual results and is not used to diagnose, treat, or direct anyone’s medical care. Its purpose is to advance research toward possible future approaches to earlier detection.
User guide · Terms of use · Privacy notice
Powered by Person Health