The Research Bottleneck

A manifesto on automating the wrong kind of hard work in medical research

The real bottleneck in medical research is not ideas. Not patient numbers. Not diagnoses. Not work hours.

It is the mechanical labor. The data entry. The copy-pasting. The hundred thousand keystrokes between you and your results.

The arithmetic of dread

You know the feeling. You open that Excel file. Fifty-plus columns. Eight hundred patients. Every row empty, waiting for you.

800 patients × 50 columns × 2–3 keystrokes each = ~100,000 keystrokes
…and that is before you even open the EHR.

How many clicks to open a patient file? To find the lab results? To verify units match your dataset schema? How many days until the conference deadline? Should you delegate half to a colleague and spend hours reconciling inconsistencies later?

This system evolved from the era of handwritten patient notes. It was designed for paper charts and filing cabinets. We carried it into the digital age unchanged. That has to stop.

The privacy gate

Medical records are personal. They are protected under HIPAA, KVKK, GDPR — whatever your jurisdiction calls its patient data protection law. This is not optional and not negotiable.

But this is not an obstacle to automation. It is a design constraint.

Anonymization can be automated. Not by sending data to big AI companies’ cloud models. By small, fast models running locally on your own machine — or your hospital’s machine. These are cheap, proven solutions. They are simply not yet widely implemented.

No automated system catches everything on its own — that is why the human review step is built in. You verify the output before it moves forward. That is part of the design, not a limitation.

Once data is properly de-identified, the entire downstream pipeline opens up.

The key insight

You are not asking the LLM to do medicine. You are asking it to do what it is good at — write code, move data, search text — in service of your clinical judgment.

LLMs are not deterministic. Nobody claims they are. But the code they write is. A Python script that runs a Cox regression gives the same result every time. The LLM is the architect. The machine is the calculator. You are the scientist.

Manually entering data into each cell of a massive dataset is neither efficient nor safe. Humans are prone to errors. Tested, deterministic systems are not. And LLM agents can build those systems — personalized to your specific research needs.

Core principles:
Human clinicians think — machines do repetitive work.
Privacy first: local model, no cloud, no exceptions.
Every automated step must be inspectable and reversible.
Tools should serve your workflow, not engineers’ assumptions.

The pipeline

The entire research workflow, from raw records to manuscript, can be restructured:

  1. 01
    Extract raw text Pull patient files from the EHR — discharge summaries, lab reports, imaging reports. OCR and text parsing only. No LLM. No cloud. Just the raw documents.
  2. 02
    Anonymize Local de-identification on the raw text. Small model, runs on your machine. No data leaves the hospital. HIPAA/KVKK/GDPR-compliant by design. This is the gate.
  3. 03
    Structure Now that data is safe, parse it into structured fields — NLP, extraction templates, deterministic mappings. The smart processing happens after anonymization, not before.
  4. 04
    Validate Unit conversion, range checks, deduplication. Rule-based. No LLM needed.
  5. 05
    Analyze Agent-written statistical scripts — scipy, lifelines, statsmodels — that run identically every time. You review the code before it runs.
  6. 06
    Interpret Debate results with an agent that has biostatistics knowledge. Iterate. Get new angles. Identify what additional data would strengthen the study.
  7. 07
    Review literature Systematic search with citation verification. Do not accept any author at their word. Find gaps. Challenge historical assumptions. Re-analyze if needed.
  8. 08
    Write Agent-assisted manuscript drafting from your results and your outline. You own the science.

Every step has a human checkpoint. The agent handles the hundred thousand keystrokes. You handle the thinking.

· · ·

Why this matters now

The technology for every step of this pipeline exists today. Local language models, structured extraction, automated statistics, literature search APIs, citation verification. None of this is speculative.

What has been missing is implementation from the right direction. Most tools in this space are built by engineers guessing what doctors need. They optimize for the wrong things. They miss the workflow. They do not understand which steps actually consume your days.

When a clinician builds the tool, the priorities are different. The interface matches how you actually think about your data. The constraints reflect real regulatory requirements, not hypothetical ones. The output is what you actually need for the conference submission, not a demo for investors.

The second-order effects

When you remove the mechanical load, something else happens.

You stop cutting corners. You do not skip the extra analysis because it means another week of data entry. You do not settle for a smaller cohort because the extraction is too tedious.

Your mind is clearer. You spot gaps in the literature that nobody had the bandwidth to look for. You find outdated claims in foundational papers. You re-analyze. You fix collective mistakes faster.

You do more research. Better research.

· · ·

The time is now. Not in five years. Not when the models get better. Now.

We build tools that preserve privacy, eliminate drudgery, and put clinician judgment front and center. Human thinking belongs to humans. Mechanical work belongs to machines.