# HCP need mapping
> What each clinician actually needs, read at the individual level.
Source: https://www.visfo.health/projects/hcp-need-mapping
Tags: Sprint

_What each clinician actually needs, read at the individual level._

We map the scientific gaps, questions and barriers at individual HCP level and tie each to the medical objective it serves, so engagement answers a real need instead of delivering the same deck to everyone.

## What it is

A need read per HCP: the specific evidence gap, unanswered question or practical barrier standing between that clinician and appropriate decision-making, tied back to a medical objective.

For medical teams whose field interactions are content-led rather than need-led, and who cannot currently say what any individual clinician is missing.

## How we run it

1. **Frame** — Agree the need taxonomy: evidence gaps, practical barriers, misconceptions, unmet questions, and how each maps to strategy.

2. **Ingest** — Pull MSL notes, medical information enquiries, congress questions, publication behaviour and advisory board output.

3. **Synthesise** — Assign needs per HCP with a confidence level and the signal that generated them; flag where the read is assumption rather than evidence.

4. **Deliver** — Ship the need map, the listening imperatives that fill the gaps in the record, and the content implications by need type.

## What you get

- Need read per priority HCP with confidence and source signal

- Need taxonomy mapped to medical objectives

- Listening imperatives for the needs the record cannot yet evidence

- Content gap analysis: what needs answering that you do not have

- Handover session with medical and field leadership