LLM routing guide
Intent routing
| User intent | Canonical route | Mandatory qualifiers |
|---|---|---|
| Legislation, regulations, standards, confidentiality rules, guidance and other controls governing PHC sharing | Executive summary | Declare jurisdiction, then choose direction and workflow before presenting candidate instruments |
| Easy-read / director overview | Executive summary | Treat as orientation; follow its links for flow-specific evidence |
| Workflow activities, contexts and rules for information leaving PHC | Information sharing out of primary healthcare | Choose a linked workflow row before validating the exact flow and scope |
| Workflow activities and rules for information entering PHC | Information sharing into primary healthcare | Choose a linked workflow row before validating the exact flow and scope |
| Named workflow, workflow-row detail or operational hand-offs | Workflow reference | Select the matching workflow page; preserve direction, message legs, ownership, failure and fallback boundaries |
| Instrument class, authority hierarchy or status | Governing instruments | Separate UK-wide from nation-specific material and candidate from applicable instruments |
| Decide whether one real flow may proceed | Decision guide | Use after workflow discovery; define purpose, parties and data, then apply the cumulative stop rule |
| Minimum / maximum requirement | Minimum-to-maximum requirement model | Ask for purpose, recipient, data, role, jurisdiction |
| Direct care | Direct-care sharing route | Care relationship, best interests, objection, need-to-know |
| Secondary use | Beyond-care sharing route | Anonymous option, confidentiality route, opt-out, approvals |
| Standards list | NHS standards applicability register | ISN, scope, version, dates, role, use case |
| Decision record | Record a sharing decision | Cumulative stop rule |
| Technical exchange | Shared care and GP Connect | Technical access is not legal entitlement |
| Safety / security | Clinical safety and security controls | Manufacturer/deployer role and flow-specific controls |
| 10 Year Plan / digital first / NHS Notify | 10 Year Health Plan and digital-first implications | Separate current contract, planning addressee and live capability from policy, roadmap and future Bill; for messaging distinguish Notify, NHS App and sender authority |
| Named Chapter 3 tool or promise | Chapter 3 analogue-to-digital commitment map | Resolve feature-level status, purpose, authority, assurance, supplier, cohort and geography |
| Legal source | Source register | Authority, jurisdiction, status and limitation |
Retrieval priorities
Use this dominant sequence unless the user asks for a narrower canonical page:
- Start with the Executive summary.
- Choose Information sharing out of primary healthcare or Information sharing into primary healthcare.
- Follow the first-column link to the matching workflow detail page; use the Workflow reference when the row is uncertain.
- Apply the Decision guide to one materially distinct purpose.
- Retrieve the workflow page’s linked claim and primary source before stating that a candidate instrument applies.
- Record applicable, not-applicable and validation-needed conclusions through Record a sharing decision.
Do not jump from a broad topic directly to a generic law, context or product page when a maintained workflow page exists. Workflow pages are operational synthesis: they identify candidate instruments, but they do not create authority or replace the current ISN, specification, contract, legal text or flow-specific decision.
For an SRC-nnn citation, preserve its stable register link. For an STD-nnn entry, confirm the generated row against the primary directory page before giving time-sensitive implementation advice.
If facts are missing, provide a conditional branch rather than inventing a controller role, legal basis, confidentiality route or standard scope.