Principia Health Sciences / est. 2020 / Cary, NC

Research reimagined: one governed record, from real-world data to submission-grade evidence.

Principia builds CuRE — Collaborative Research Ecosystems — so research organizations run the entire evidence pipeline on one governed record. Data maps to OMOP once, then flows into analytics, safety, quality, TMF, and regulatory outputs without rebuilding the dataset for every question.

Study startup
Weeks, not months
Studies stand up on data that already flows into the record
Signal to analysis
Same day
A new safety or quality signal becomes analysis without a data project
Validation
Built in
21 CFR 11 · EMA Annex 11 · audit evidence as a byproduct of the work
Procurement
One agreement
Start with a single app — the whole suite entitled from day one

Why CuRE is different

What the platform changes for you

Not another EDC with a data lake bolted on. CuRE removes research handoffs instead of automating them — so the win shows up as questions you could not ask before, fewer steps, faster evidence, validation built in, and lower cost.

New questions

Ask what siloed systems cannot answer.

Cross-modal questions are native: link manufacturing, shipping, biomarkers, ePRO adherence, and EHR history to clinical outcomes without building a one-off dataset for each question.

Fewer steps

Map once. Stop re-keying everything.

Data maps to OMOP a single time and every product reads from it — no re-entry between capture, analytics, TMF, and publishing, and far fewer queries, reconciliation passes, and decks assembled by hand.

Faster time to evidence

Studies start on data that already exists.

Because patient data flows continuously into one governed record, studies stand up in weeks and a new safety or quality signal becomes analysis the same day — not after a months-long data-engineering project.

Validation built in

No separate validation project.

21 CFR Part 11 / Annex 11 audit trails, source lineage, AI logs, and validation evidence are captured as the platform runs — so GxP readiness is a byproduct of the work, not a separately-budgeted project bolted on at the end.

Lower cost

One platform instead of a vendor stack.

One data model and one validation story replace per-vendor licenses, integration projects, and re-validation cycles — a fraction of the cost of assembling the same capabilities from point solutions.

02 / Platform overview

One platform. Every product.
One governed record.

At the heart of CuRE is one governed OMOP record. The suite reads the way evidence flows: collected at sites and from patients, governed into one record, operated and monitored, analyzed, submitted, and carried into portfolio and market-access decisions. Every product appears once, in the stage where it does its work.

One governed record across every product · OMOP CDM v5.4 Explore the full platform

03 / Benefits of integration

Questions disconnected systems cannot answer.

Integration is not just a cleaner architecture diagram. It changes the questions a research organization can ask, because operational work, clinical evidence, safety, quality, and regulatory outputs all point back to the same governed record.

Read the whitepaper
Question 01

Which sites create downstream safety, quality, and data-cleaning burden after adjusting for patient acuity?

EDC, operations, safety, RBQM, EHR, and outcomes resolve to one governed record.

Site quality is measured by total evidence burden, not just enrollment speed.

Question 02

Do manufacturing delays, shipment excursions, or late dosing change response, relapse, or adverse-event patterns?

Supply, chain-of-custody, clinical outcomes, and safety data stay linked.

Operational variance becomes clinical insight.

Question 03

Which protocol criteria drive screen failures, slow enrollment, deviations, and poor real-world generalizability?

Protocol operations, EHR eligibility, site execution, and longitudinal outcomes can be queried together.

Design studies around patients who actually exist and sites that can execute.

Question 04

Are physician-facing CDS alerts changing enrollment, adherence, safety reporting, or outcomes?

EHR workflow, study operations, care-team activity, and patient outcomes share context.

Measure whether point-of-care engagement changes the study, not just clicks.

Question 05

Which sites should we approach next based on eligible-patient volume, execution quality, and outcome history?

Site capability profiles come from governed evidence, not self-reported feasibility PDFs.

Feasibility from evidence, not surveys.

Question 06

Which label, submission, or registration changes are supported by live safety, outcomes, and operational evidence?

Regulatory lifecycle records remain connected to the evidence and analyses behind them.

Regulatory content stays connected to the evidence record.

We have spent years watching outcomes research duct-tape trial tools into shapes they were never designed to hold.

Real-world evidence happens in patient journeys.

P-01

Dense, not cramped.

Clinical research is information-rich. The interface earns space with alignment, tabular data, and hierarchy instead of padding everything into sameness.

P-02

Semantic color does real work.

Teal means automated, amber means attention, sky means information, and magenta marks AI-assisted work. Color carries state.

P-03

Context persists.

Study, site, patient, cohort, and time cursor should follow the user across surfaces, pages, and refreshes.

P-04

Provenance is visible.

Every important value should show whether it was entered, ingested, suggested, reviewed, locked, or overridden.

P-05

AI stays attributable.

AI features should expose confidence, source material, and correction paths instead of hiding authorship behind a magic button.

04 / The unified record

One patient record, stitched from every source.

EHRs, labs, registries, claims, patient apps, and translational data map through open standards into one governed record — FHIR on the way in, OMOP as the analytical backbone, submission-grade SDTM/CDASH on the way out. One governed study-design metadata record — a built-in Metadata Repository — drives the CRFs, SDTM mapping, and define.xml, so submission artifacts are generated from the design rather than hand-rebuilt in parallel.

data flow / sources → standards → governed record → outputs
Sources
EHR / FHIR SMART on FHIR
Lab feeds HL7 · LOINC
Patient PROs Compass
Registries OMOP-mapped
Claims ICD · SNOMED
Translational Cyto
Standards layer
FHIR
EHR connectivity & ingestion
OMOP CDM v5.4
analytical backbone · OHDSI toolkit
SDTM · CDASH · define.xml
generated from the study design
one governed record
Outputs
Cohorts & Briefings Calculate
Signal detection Canary
Quality & KRIs Caliber
Decision support Cue
Randomization & supply Cascade
Study operations Control
standards in · governed record · standards out

05 / See it, then try it

Real software. Try it right now.

No sales call required. CuRE apps ship live, in-browser demos of their real engines — synthetic data, actual logic — on their product pages. Start with the screenshots, run a single engine, or follow one synthetic record through the whole pipeline.

CuRE Capture — investigator dashboard with a portfolio overview and a per-study enrollment, validation, and open-query heatmap
CuRE Capture · RWD-native EDC — sandbox preview, synthetic data
CuRE Calculate — analytics workbench Cohorts view with portfolio metrics, AI-authored cohort narrative, and saved cohorts including a CAR-T grade-≥3 CRS prediction cohort
CuRE Calculate · Advanced Analytics — sandbox preview, synthetic data
CuRE Control — study-operations dashboard with active studies, sites, enrollment, and registries
CuRE Control · CTRMS — sandbox preview, synthetic data
CuRE Cue — clinical decision support showing mSMART guideline risk stratification and inferred transplant eligibility across a 121-patient cohort
CuRE Cue · Clinical Decision Support — sandbox preview, synthetic data
Cross-app journeys thread one synthetic record through the suite, stage by stage Follow the governed record

07 / How you adopt CuRE

One platform. One agreement. Adopt at your pace.

An integrated platform shouldn't mean an all-or-nothing purchase. Sign one enterprise agreement — priced to start at a single app — and grow into the suite on your timeline, with no integration work between CuRE products as you add them.

Start with one app

Priced as one app, with the whole suite entitled from day one — no re-procurement to grow.

See your data across the suite

One governed record, so your data surfaces in every app the moment it lands — explore before you activate.

Activate app-by-app

Turn on regulated and advanced features per app, when you need them. Pay for what you actually run.

Integrations only at the edges

CuRE apps are natively connected; adapters for outside systems — EHRs, safety, eTMF — are already built.

See how adoption works

Talk to Principia

Let's talk about your most difficult clinical trial and RWE challenges.

We engage leading non-profits, health systems, and biopharma organizations on programs ranging from data integration and report automation to full CuRE network buildouts.

Direct line
info@principia.health
Request a conversation

No newsletters. A human reply within 24 hours.