Product-to-Patient Explorer
Nine stages from concept to the person who receives the product, and the return path that carries what happens to them back into the design. Most maps of this journey stop at dispatch, which is where the obligation is least finished.
The return path is not the forward path reversed. A complaint, an adverse event or a trend jumps: from the patient to surveillance, from surveillance to the design or the process, and only then forward again through qualification, manufacture and release. Every jump crosses an organisational boundary, and each boundary is where signals are lost — which is why the 7 organisations are given their own reading, each stating what it retains no matter what it delegates. The journey is synthetic and generic across modalities: no specific product’s route is claimed to be typical, and reaching a later stage is never an approval.
Concept and intended use
The product is defined by the problem it claims to solve and the population it claims to serve. Everything downstream is measured against this claim.
Whether the intended use is specific enough to be tested against, or so broad that no evidence can satisfy it.
Scientist, Clinician, Regulatory strategist
Intended-use statement, target product profile — document system
An intended use written to preserve optionality, which later forces the evidence set to cover every option.
That the claim on the label was fixed years before the product existed, and constrains what may be said about it.
The nine stages, end to end
Read the third column down the page: each stage exists to make one decision, and hands the next stage something it cannot proceed without.
| # | Stage | Decision made here | What it hands on | Accountable |
|---|---|---|---|---|
| 01 | Whether the intended use is specific enough to be tested against, or so broad that no evidence can satisfy it. | An intended use narrow enough to be proven | Development | |
| 02 | Whether the design is frozen, and what it costs to change it after that point. | A frozen design with a traceable rationale | Development | |
| 03 | Whether the process is understood well enough to be operated by someone who did not develop it. | A repeatable process with defined parameters | Development to Manufacturing | |
| 04 | Whether qualification proved fitness for the intended use, or only that the equipment ran. | A qualified state, with the conditions that maintain it | Engineering and Quality | |
| 05 | Whether this batch was made within the qualified state, and what to do when it was not. | A batch with a complete, contemporaneous record | Manufacturing | |
| 06 | Whether every deviation and result has been assessed, or only those that were flagged. | A released batch and a decision that can be defended | Quality | |
| 07 | Whether the conditions the product experienced are known, or only assumed. | A product delivered in a known condition | Supply chain | |
| 08 | Whether the product is used as intended, and whether misuse was foreseeable. | An outcome, and a signal about the design | Clinical | |
| 09 | Whether a signal is a complaint, a trend, or a reportable event — and how quickly that is decided. | A change request, or a documented decision not to change | Quality and Regulatory |
Illustrative synthetic journey for interface design. Stage names are generic across modalities; a specific product's route will differ in sequence, terminology and obligation.