CuRE / Research automation for health science

Collaborative, integrated, governed, real-world and affordable research automation

CuRE is designed to take the routine work of health research off people's hands, from registry follow-up to regulatory evidence, for foundations, registries, sites, sponsors and CROs. People keep the decisions, and every data owner keeps control

01 / Platform overview

Greater than the sum of its apps

CuRE is a family of apps built together on one governed record. Data comes in from sites, patients and outside systems once, and every app after it reads the same record, through to the submission and the market

  1. 01

    Collect

    Sites, patients and outside systems feed one record

  2. 02

    Govern

    Consent, agreements and AI checked where the data lives

  3. 03

    Operate

    Studies, supply and the research network

  4. 04

    Analyze & monitor

    Cohorts, safety and quality on the same record

  5. 05

    Submit

    From the TMF to the label, tied to the evidence

  6. 06

    Lifecycle

    Portfolio and market access on the same evidence

Underneath every stage: one governed record · OMOP CDM v5.4 Explore the full platform

Work the platform is designed to take off your hands

  • Issuing approved data access
  • Feasibility counts across centres
  • Returning data to centres
  • Pre-filling registry forms
  • Loading CRO data files
  • SDTM and define.xml generation
  • Audit trails
  • Binding signatures to content
  • Consent checks before release
  • Registry follow-up collection
  • Mapping terms to OMOP
  • EHR lab data intake
  • Report number checking
  • Monitor access to source data
  • Trial-match screening lists

02 / Who CuRE is for

What's in it for you?

One network, a different return for every role in it. Pick yours

Where the data comes from

Disease Associations

Your patients said yes to research. Not to everything

Every centre that joins, for any reason, makes your next count more complete, and every partner meets the same enforced terms. Centres supply the data, partners need it, and the foundation keeps the terms

The disease foundation page →
Academic Medical Centers

You send the data out all year. This time it comes back

The site is where the network's data comes from. On CuRE the exchange runs both ways: you supply the records sponsors need, and you get back clean data, fewer re-typed values and shorter monitor-visit days

Read more →
Providers & Health Systems

Bedside evidence, paid for with participation

Health systems supply the data research needs. On CuRE that supply buys something back: decision support, clean data and enrollment, instead of another abstraction burden

Read more →

Who answers for it

Data Standards & Biometrics

Write the study once. Stop reconciling it four times

Your standards library and your study build are meant to be the same governed object, so a design change propagates instead of being re-keyed

Read more →
Regulatory Affairs

The report says 412. The analysis says 411. You find out first

What you submit stays traceable to how it was produced, without the export, reformat and reconcile loop between clinical and regulatory systems

Read more →
Quality & Safety Leaders

Stop closing CAPAs on a promise

Monitoring signals, safety cases and CAPAs share one lineage, so "how did you respond, and did it work?" has one answer instead of three exports

Read more →

Who puts it to work

Emerging Biotech

Your CRO has a data team. You have Friday

When the CRO itself runs on CuRE, the files stop: you read the same live views it works from, and its own working data stays private

Read more →
CGT & Rare Disease Sponsors

Lot 4471 failed stability. Who got it, at every site?

Small populations make every patient count. Registries and treating centres on the same network are designed to bring the comparators and follow-up one sponsor could never collect alone

The cell-therapy page →
Large Pharma — Observational Teams

Keep your tools. Change what sits underneath them

Each registry, foundation and health system that joins adds records you can count under its own rules, without a new data-sharing negotiation for every question

The real-world evidence page →
CROs

Different sponsors. Separate systems. Possibly the same subject

Sponsor visibility stops being a threat and becomes a service: sponsors read the same views you work from, and the benchmarks behind your risk thresholds sharpen with every organization that joins

Read more →

03 / Why CuRE is different

Spot the difference

Most research software is built for one buyer and one step, then wired to the next. CuRE is built the other way round

Built as one, not bolted together

The usual way
An EDC, a safety database, a CTMS and an analytics warehouse from different vendors, joined by integration projects and reconciled by hand
With CuRE
Every app built together on one OMOP record, so a value entered once is designed to reach every app that needs it
Explore the platform →

Care and research on one record

The usual way
Trial software stops at the case report form, and real-world data arrives later as a purchased extract
With CuRE
EHR, lab, registry and patient-reported data map once to OMOP beside the study data, so routine care feeds the next study
See the record →

Built for the whole network, not one buyer

The usual way
Software built for the sponsor who pays, with sites and foundations handed a login
With CuRE
Foundations, registries, sites, sponsors and CROs each get something back, and every member makes the network more useful to the rest
See what each member gets →

Data stays with its owner

The usual way
To answer a question across organizations, someone collects everyone's data first
With CuRE
Each centre answers inside its own records, under its own rules, and each data owner approves every use
See the questions →

04 / Benefits of integration

The data stays. The question travels

Each of these crosses a line between systems or between organizations. The records stay where they are, under their owners' rules. The question is what travels

Read the whitepaper

Across organizations

Each organization answers inside its own records, under its own rules

Is the subject in front of us already enrolled in another sponsor's trial?

Identity matching runs across every organization on CuRE, not inside one sponsor's EDC

Visible only across organizations

How many eligible patients sit across forty centres, without anyone collecting a record?

Each centre counts inside its own records under its own rules, and only a privacy-protected total comes back

Feasibility from the records, not a survey

Which community centres see the patients our trials keep missing?

Designed to read each centre's patient mix from its own records, with small cells hidden

Representation before site selection, not after enrollment

Across systems

Chart, CRF, supply chain and study report share one record, so nothing has to be joined

Which adverse events reached the chart but never reached a case report form?

Where a study has an EHR feed, events with no matching CRF record are flagged site by site

Monitoring that sees past the CRF

Did a manufacturing delay or a cold-chain excursion change response or toxicity?

Designed so supply, chain of custody, outcomes and safety stay on one record

Operational variance becomes clinical insight

Does every number in the study report match the number the analysis produced?

Each number in the narrative is checked against the analysis and marked Match, Mismatch or Unverified

Regulatory content stays tied to its evidence

Give and take

Sites supply the data, sponsors need it, and every organization that joins makes every answer better

N-01

Sites supply the data, and get it back

Centres contribute records and download their own patients' data, cleaned and harmonized, instead of waiting for an annual PDF

N-02

Sponsors bring the questions

A feasibility question reaches the records without collecting them, and a sponsor's open trials are designed to surface in each participating site's own workflow

N-03

Foundations keep the terms

The purposes a patient community agreed to travel with the data and are checked before every release, by every partner, at every centre

N-04

CROs see across sponsors

Duplicate subjects and risk benchmarks only exist across organizations, so they sharpen with each one that joins

N-05

Every answer gets better

Each new centre makes the next count more complete for every foundation and sponsor already on the network

05 / The unified record

All roads lead to one record

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, SDTM and CDASH on the way out. The study design is meant to be written once and to drive the CRFs, the SDTM mapping and define.xml, so submission artifacts come from the design instead of being rebuilt beside it

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

06 / See it, then try it

Don't take our word for it

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 today's actions, a portfolio heat map of enrollment, validation and open queries across four studies, and overdue visits by site
CuRE Capture · RWD-native EDC — sandbox preview, synthetic data
CuRE Calculate — cohort characterization with observation time, record counts by clinical domain, sex and age demographics, and the most frequent concepts in each domain
CuRE Calculate · Advanced Analytics — sandbox preview, synthetic data
CuRE Control — study-operations dashboard with an enrollment funnel, forecast versus actual enrollment, overdue subject visits, upcoming milestones and site activity
CuRE Control · CTRMS — sandbox preview, synthetic data
CuRE Cue — treatment-flow Sankey for 108 stage II–III multiple myeloma patients, showing regimen paths across three lines of therapy against the guideline-recommended pathway, with concordance rates
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

08 / How you adopt CuRE

Pay as you grow

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 share one record, so the only integrations are to outside systems such as your EHR

See how adoption works

Talk to Principia

First, do no busywork

Tell us the work your team still does by hand: the re-keying, the chasing, the checking. Foundations, registries, health systems, sponsors and CROs start with one job like that, and grow into the network from it

Direct line
[email protected]
Request a conversation

No newsletters. A human reply within 24 hours