Care Journal

Use case · Pre-launch

Meet your patients before the protocol locks.

Size the population, find where the need is, and test your clinical assumptions against how treatment actually runs. Long before anyone asks you for a dossier.

See what’s in the data →

Why pre-launch RWE

Feasibility gets sharper with a whole history.

Linked records across every provider a person has seen, with the notes intact and the between-visit experience alongside them. Enough depth to plan a programme on.

What you get

Four things you can do before you file.

  1. Size the population that actually exists

    Run your inclusion and exclusion criteria against linked records across every provider a person has seen, in one linked history.

  2. See where treatment is already failing

    Discontinuation, switching, and the stretches where nobody billed for anything. With the reason the person gave, in their words.

  3. Test your endpoints on real people

    Check whether the thing you plan to measure is something patients notice and report, before it becomes the endpoint you defend.

  4. Hand HEOR something they can model on

    Cost-effectiveness inputs, adherence estimates and comparator arms, ready before the pricing conversation starts.

Where teams use it

Seven jobs this does before approval.

  • Feasibility and cohort sizing

    HEOR · Clinical development

  • Unmet need and care-gap mapping

    Medical Affairs

  • Endpoint selection against what patients report

    Clinical development

  • Synthetic comparator arms

    Biostatistics

  • Cost-effectiveness model inputs

    HEOR

  • Subgroup identification for access strategy

    Market Access

  • IRB-ready datasets for external research

    RWE

Have a different question? Send it. We’ll show you what the data can do with it before you spend anything.

Send us the protocol synopsis.

We’ll size the population and show you exactly what the data supports, before you commit to anything.