Stuck Access File Diagnosis.

Why is a pricing and reimbursement file for a specialty product stuck past the window the client committed to: a gap in the dossier, a payer or agency queue, a change in the rules, or a stakeholder disagreement?

The diagnosis restates the delay in measurable terms first: how long, past which commitment, and at which step. It then tests each explanation against the file’s record.

The delay as a measurement. The diagnosis states the committed window, the date the file was lodged, the current step and how many days the file is over. EU rules require a price decision within 90 days of a complete application and a decision on inclusion within a further 90 days, or within 180 days when the two are handled together, so the overshoot is measured against a statutory frame as well as the client’s commitment.^{1Council of the European Communities. Council Directive 89/105/EEC of 21 December 1988 relating to the transparency of measures regulating the prices of medicinal products for human use and their inclusion in the scope of national health insurance systems.}

The clock tells you which explanation to suspect. When information is requested, the clock is suspended and restarts when it arrives. A file that has sat in clock-stop looks different from a file that has sat in a queue. The diagnosis looks for the dates that separate them.^{1Council of the European Communities. Council Directive 89/105/EEC of 21 December 1988 relating to the transparency of measures regulating the prices of medicinal products for human use and their inclusion in the scope of national health insurance systems.}

Evidence that fits every explanation is set aside. A late file fits all four explanations, so the fact of delay settles nothing. The matrix weighs the evidence that fits some explanations and not others.^{4Heuer, R. J. Jr. Psychology of Intelligence Analysis, chapter 8: Analysis of Competing Hypotheses. Center for the Study of Intelligence, CIA, 1999.}

How it could be wrong. The diagnosis names the assumption the likely cause depends on and the observation that would break it, for example a request for information that the file does not show.

The diagnosis states the assumptions its likely cause rests on and sets what would break each one. Examples for this problem:

• The file’s record shows every request and response, including informal ones.
• The client’s committed window was realistic when it was set.
• The rules that applied when the file was lodged are the rules that apply now.

The decision practice behind the memo itself is on the template page.

Any date the file does not show, any explanation the evidence cannot yet exclude, and any step where the cause rests on one person’s account.

1. The problem as stated
2. What is actually happening
3. Competing explanations
4. The likely cause
5. What would confirm it
6. Where the effect concentrates
7. What to rule out

1. [1] Council of the European Communities. Council Directive 89/105/EEC of 21 December 1988 relating to the transparency of measures regulating the prices of medicinal products for human use and their inclusion in the scope of national health insurance systems. Check the national rules that implement it.
2. [2] Gemeinsamer Bundesausschuss (Federal Joint Committee). Benefit assessment of medicinal products. English page. Read in full on 9 October 2026.
3. [3] European Parliament and Council. Regulation (EU) 2021/2282 on health technology assessment. Application dates for medicinal products: 12 January 2025, 13 January 2028 and 13 January 2030. The phase-in dates are as given in the European Commission’s factsheet and EUR-Lex summaries; the regulation’s text was not read in full for this page.
4. [4] Heuer, R. J. Jr. Psychology of Intelligence Analysis, chapter 8: Analysis of Competing Hypotheses. Center for the Study of Intelligence, CIA, 1999.

Links checked 9 October 2026

These are the sources the template drew on. None of their authors or issuers has reviewed it.