LLM routing guide
Intent routing
| User intent | Canonical route | Mandatory qualifiers |
|---|---|---|
| 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 | Sharing route decision workflow | 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
Prefer canonical synthesis pages for orientation, then retrieve the linked evidence row and primary source. 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.