Skip to main content
Download free report
Softblues
Softblues

Healthcare · AI business automation

A medical trainee with a good research idea can wait 12 to 18 months to publish it. Most never do.

AI-powered clinical research platform

The path from a research question to a published paper runs through statistics most clinicians were never taught, datasets they cannot query, and months they do not have between rotations. About 74% of medical students say they lack the statistical skills, and most research projects never reach publication. We automated the whole workflow: nine specialised AI agents that take a plain-English question to a publication-ready analysis in weeks, with no code to write.

Built for medical traineesHealthcareClinical researchMulti-agent · live in beta
Book a case walkthrough
12–18 months → weeks
From research question to publication-ready
A medical trainee turning a research question into a finished paper through an automated analysis pipeline

A $53bn field with a publication problem

Medical research runs on people trained to treat patients, not to run statistics. The data is not the bottleneck. Public databases like the CDC's NHANES hold decades of population health data ready to analyse. The process that turns that data into a finished study is what's broken.

$53B

Healthcare analytics market in 2024, projected to more than triple by the mid-2030s

Source: Market.us, 2024

~70%

Of medical student research projects never reach peer-reviewed publication

Source: Systematic review and meta-analysis (PMC)

74%

Of medical students cite lack of statistical skills as a top barrier to research

Source: Barriers to undergraduate medical research, PMC (74.2%)

Idea to paper

Six stages between a question and a publication

Every published study runs through the same stages. A clinician without a data team is blocked at almost every one.

1. Research question development
Typical timeDays to weeks
Where it stalls71.4% struggle to choose a topic
2. IRB approval (where needed)
Typical time2–4 months
Where it stallsCommittee schedules
3. Data collection and access
Typical timeDays to 6 months
Where it stallsDatabase complexity
4. Statistical analysis
Typical time2–8 weeks
Where it stalls74.2% lack the skills
5. Writing and review
Typical time2–4 weeks
Where it stallsClinical duties compete
6. Journal submission and review
Typical time4–12+ months
Where it stallsPeer-review cycles

Sources: barriers to undergraduate medical research, PMC (statistical skills 74.2%, topic selection 71.4%); medical-research publication rates, systematic review and meta-analysis.

The opportunity

The data is ready. The process isn't.

Public datasets like NHANES, NHIS and MEPS hold decades of population health data, free to use. The barrier is everything between a question and a result: choosing the right statistical test, writing the SQL to pull the data, weighting the sample correctly, and producing code a reviewer will trust.

Take that off a clinician's plate and a study that took a year can take weeks. That was the brief: automate the whole workflow without lowering the bar a journal sets.

The data was never the problem. The work to turn it into a study was.

The hard part

Why this is hard to automate

Automating research is not a chatbot on top of a database. Each step carries real methodological weight, and the output has to survive peer review.

Four walls in the way

01

Statistical method complexity

The platform has to pick the right test for the data and the question, identify confounders, weight complex survey designs and check the sample is large enough. Get it wrong and the study is worthless.

02

Authoritative data, made usable

Datasets like NHANES cannot be queried without SQL, survey-weighting knowledge and codebook navigation. The agents had to map plain questions onto real variables and pull the data correctly.

03

Methodology and reproducibility

Outputs have to follow PEO and PICO structures and meet journal standards like STROBE and CONSORT, with a complete audit trail and reproducible code.

04

Built for non-technical users

The people using it are clinicians, not data scientists. The interface had to take a plain-English question and explain its statistical choices, not assume training the user does not have.

The build

Built agent by agent, straight to production

We skipped the throwaway prototype. Each of the nine agents was designed, tested against real research scenarios and integrated before the next went in, so the platform shipped as production-quality software from the start.

The orchestration runs on Claude Sonnet over LangChain, with each agent owning one decision in the workflow, from reading the question to validating the final output.

How it works

Nine agents, one orchestrator

Pipeline: a plain-English research question flows through a Claude Sonnet orchestrator and nine specialised agents, querying BigQuery and NHANES, into a publication-ready report with an audit trail
  1. 1

    Research query

    Reads a plain-English research question, detects its PEO/PICO structure and extracts the intent.

  2. 2

    Feasibility

    Checks the question against the available data: variable coverage, dataset fit and sample-size estimation.

  3. 3

    Variable identification

    Maps the study to the dataset codebook and suggests custom variables where they are needed.

  4. 4

    Data extraction

    Generates the SQL, queries BigQuery and applies the correct survey weighting, with no manual querying.

  5. 5

    Statistical method

    Selects the right tests, identifies confounders and builds the analysis plan.

  6. 6

    Code generation

    Produces reproducible, documented Python and R analysis code.

  7. 7

    Context resolution

    Handles multi-turn refinement, holding the whole study in context as the researcher iterates.

  8. 8

    Report generation

    Compiles the methods section, results tables and publication-ready formatting.

  9. 9

    Validation

    Runs quality and statistical-accuracy checks on every output before it reaches the researcher.

See it in action

From a question to a finished analysis

The researcher's journey, in four screens: explore the data, shape a question, define the cohort, then run the analysis.

01

Database exploration

Database exploration: browsing and categorising variables across national health datasets
Browse variables across national health datasets (NHANES, NHIS, MEPS) and mark the ones relevant to the study.
02

Research question generation

Research question generation from selected variables
Turn selected variables into research questions, generated automatically or written by hand.
03

Define the cohort

Defining the study cohort with population, exposure and outcome variables
Variables are assembled into population, exposure and outcome groups for the chosen question.
04

Primary analyses

Primary analyses with descriptive and univariable statistics
Descriptive and univariable analysis surfaces the first associations between the variables.

Built with

Cloud

Google Cloud PlatformCloud RunCloud SQLPub/Sub

AI / ML

Claude SonnetLangChain (multi-agent orchestration)RAG

Data

BigQueryNHANES / NHIS / MEPS public datasets

Analysis

PythonPandasScikit-learnMatplotlib

Application

ReactTypeScriptFastAPIREST API

Security

IAMVPCEncryption at rest and in transit

Results

What it delivers

12–18 mo → weeks

From question to publication-ready analysis

9

Specialised agents, one workflow

0

Lines of SQL or code the researcher writes

100%

Reproducible, journal-aligned audit trail

Live, in beta

The platform is live with beta testers running real research questions. We are supporting users, watching how they work, and refining the agents on real-world queries.

Access widened

Medical students and early-career clinicians can run dataset-scale research without a statistician or a data team behind them.

Where else this works

The platform is built for clinical research. The method behind it is general: split an expert workflow into specialised agents, wire them to authoritative data, and keep the human in charge of the judgement.

Frequently asked questions

An automation of the whole clinical-research workflow. What used to be a six-stage manual process, from choosing a method and accessing the data through to running the statistics and writing up to publication standard, now runs as one pipeline of nine specialised AI agents. A researcher asks a question in plain English and gets back a publication-ready analysis with reproducible code.

It automates the slow stages: statistical method selection, querying public datasets through BigQuery with the right survey weighting, generating the analysis code, and drafting the methods and results. The researcher describes what they want to study; the agents do the data and statistical work that used to take months of specialist time.

No. The pipeline handles the SQL, the method selection and the code. The researcher works in plain English, and the platform explains its statistical choices as it goes, so the output is rigorous without assuming training the user does not have.

Every analysis follows PEO/PICO structure and journal reporting standards such as STROBE and CONSORT, with confounder handling and correct survey weighting. A validation agent runs quality and accuracy checks, and every study carries a fully reproducible audit trail and code.

Nine specialised agents orchestrated by Claude Sonnet over LangChain, querying public datasets (NHANES, NHIS, MEPS) through BigQuery on Google Cloud, with a Python analysis stack and a React front end.

No. The same method, splitting an expert workflow into specialised agents wired to authoritative data with a human in charge, applies to any field where rigorous analysis is gated behind scarce expertise.

Ready to turn an expert workflow into a platform?

If your field gates good work behind scarce expertise, that is what we automate. Book a walkthrough of this build, or a discovery call on your own process.

Anthropic Partner Network member50+ AI ProjectsGoogle Cloud PartnerTop-5 UK AI Firm
Success Stories

Explore Other Projects

Discover more AI solutions delivering measurable results across industries