What Next: Suggestions and Decisions
This is the working record of follow-up suggestions that have not been pursued, have been combined, or are already covered. It explains why a suggestion matters and what useful result would finish it. A suggestion is an option for choosing work, not an instruction to start it or a claim that evidence exists.
Reconciled: 1 October 2026. The initial record covers the two suggestions questioned by the user, the urgent-care follow-ups in this conversation, and related work already recorded in the wiki. It is not an exhaustive reconstruction of every historical chat. Imported wiki priorities are labelled as such rather than presented as recovered quotations.
The Two Suggestions Explained
“Resolve the matrix’s devolved GP API gaps using supplier interface documentation.” In plain English: if we want software to read a GP record, write information back or book an appointment in Scotland, Wales or Northern Ireland, check the documentation for that particular connection. A record viewer does not establish a software interface with the same capabilities. This matters for a real integration choice, but “resolve the gaps” was too broad and implied that public documentation could answer everything. WN-001 is parked until a specific nation, supplier and operation need a decision. The existing “unverified” cells are valid conclusions, not a demand to research indefinitely.
“Extend the four-nation adapter model with the newly documented registration and identity routes.” An adapter model describes how a common application would connect to each nation's different services. The identity and registration facts are already in the country pages and matrix. The remaining useful improvement is to explain, in one place, how looking up a patient, signing a person in, changing GP registration and transferring a record differ. WN-002 is a bounded explanation task, partly covered already; it does not establish or build new connections.
These findings come from reconciling the matrix, four-nation model, country pages and existing interface gaps. No new supplier-interface validation was performed for this register.
How This Fits the Wiki
| Question | Canonical home |
|---|---|
| What was suggested, why, and should it still be pursued? | This register; stable WN identifiers and decisions |
| What evidence is missing, and what source or response could settle it? | Evidence Validation Queue |
| Which broad research gaps matter? | Further Research Priorities |
| What is currently known and how does it work? | Existing topic, country and model pages |
| What supports the claims? | Source Register and Evidence Matrix |
| What work was completed? | Research Log, with a short closure link retained here |
Statuses: Suggested = executable but not selected; Needs scope = too broad to start usefully; Parked = a specific decision, source or response is needed; In progress = selected and started; Completed = the stated result exists and has been checked; Merged = another WN item owns the work; Retired = no remaining value, with a reason. Partial coverage is explained in the entry; it does not mean the whole item is complete.
Working Register
The 1 October reconciliation puts the Executive Summary before the Matrix, followed by the Landscape, and aligns their reading routes, existing interface qualifications and review controls. The subsequent Current Med IS pass repeats the same six service annotations in the summary and adds the network row, with paired highlight checks. The later row-separation correction gives diagnostic ordering and professional/patient viewing independent rows. These changes extend WN-007’s partial editorial coverage without completing its other passes or the worked identity example. WN-008 (closure: reconcile deployment priorities), WN-002 (synthesis: explain identity versus registration) and WN-006 (breadth: compare urgent mental-health pathways) remain executable, unselected options; this pass does not authorise them.
The order groups related work; it is not an automatic priority ranking. The current shortlist offers one closure, one synthesis and one breadth pass. Each can be selected independently.
| ID | Plain-English outcome | Status / relevance | Where the work belongs |
|---|---|---|---|
| WN-001 | Establish whether one named devolved GP software connection is available | Parked — relevant to an actual integration choice | Matrix, country page and existing interface gap |
| WN-002 | Explain patient identity, login and GP registration as separate steps | Suggested; partly covered — synthesis shortlist | Existing four-nation model |
| WN-003 | Compare urgent-care routing across the UK | Completed — retain as a closure record | Matrix and four country sections |
| WN-004 | Trace an England 111 report into the GP system | Merged into WN-005 — use as its first worked example | Existing urgent-care model and DSIC detail |
| WN-005 | Explain who receives, accepts and acts on an urgent-care handoff | Suggested — useful workflow explanation | Existing urgent-care adapter section |
| WN-006 | Compare urgent mental-health access and onward handover | Suggested — breadth shortlist | Existing urgent-care matrix and country pages |
| WN-007 | Make existing explanations easier to follow | Needs scope — select one of the six recorded editorial passes | Existing narrative-work queue and affected pages |
| WN-008 | Reconcile older deployment research priorities with the new platform estate | Suggested; partly covered — closure shortlist | Research priorities and platform estate |
| WN-009 | Compare products doing the same job | Needs scope — useful only for a named comparison | Comparative Analysis |
| WN-010 | Explain who operates and supports software versus a managed service | Needs scope — choose one named service pair | Product portfolio and service pages |
| WN-011 | Show record-keeping duties in one everyday example | Suggested — a separate practical synthesis option | Existing healthcare-recording page |
Scope and Completion Decisions
WN-001
Origin: the user's quoted GP API follow-up, 29 September 2026. Decision: narrow and park the blanket task. The matrix already distinguishes record viewing, structured reads, writes, appointments and bulk access; a common supplier does not prove a common interface across nations.
Reopen for a named nation, supplier/product and operation that affects a real connection choice. A bounded pass would check its published national and supplier specifications for supported actions, requester role, authorisation, record coverage and onboarding. Finish by recording documented, unsupported or still unverified, with the reason and source date, in the country page and canonical queue. If documentation is unavailable, retain the gap; do not promise to resolve it or send supplier requests without authorisation.
WN-002
Origin: the user's quoted identity/registration follow-up, 29 September 2026. Decision: retain a smaller synthesis task. Country-level identity and registration routes are already documented; generic “extend the model” wording obscured the remaining benefit.
Add one compact worked example and route table to the four-nation model. Distinguish patient identifiers/lookups, patient or staff login, registration application, accepted GP-list change, administrative notification and subsequent record transfer. Reuse the existing country evidence for England PDS/registration services, Scottish CHI/NHSCR, Welsh WDS/PCRM/NHS login and NI HCN/NIDIS transition limits. Finish when a reader can identify which step reads information, which changes registration, and which interface remains unverified, with country links. Do not imply that sharing identity infrastructure imports England's DSIC requirements or proves InterSystems implementation.
WN-003
Origin: the earlier “Add an urgent-care routing comparison…” suggestion, selected by the user. Completed 29 September 2026: five functions were added to the matrix, with country, DSIC, PRSB and adapter detail. See the completed research pass. Residual interface and locality gaps belong to the urgent-care queue; they do not make the functional comparison unfinished.
WN-004
Origin: the subsequent “Trace one England 111→GP report” suggestion. Merged into WN-005 on 29 September 2026. The GP report path is a useful first example for the same workflow explanation; separate tasks would repeat the S33, report-adaptor and receiving-system analysis. Preserve the DSIC receiver requirements as the requirements source.
WN-005
Origin: the subsequent worked urgent-referral example, combined with WN-004. Suggested; the conceptual boundaries already exist. Add one worked sequence in the urgent-care adapter section, starting with England 111 reporting to a GP system. Show sending, delivery acknowledgement, receipt, GP filing/review and failure handling; contrast the informational post-event report with an actionable referral. Show clinical acceptance or booking only where the chosen route actually supports them.
Finish when each step identifies its owner, documented message/operation and what an acknowledgement proves. Link to existing S33 and PRSB detail, label any illustrative step, and leave unverified local workflow explicit. This is an explanation, not evidence of a tested deployment or a universal BaRS flow.
WN-006
Origin: the subsequent urgent mental-health comparison suggestion. Suggested; breadth shortlist. Compare public access, crisis assessment, onward handover and operating scope across the four nations, including the roles of 111 mental-health routes and NI Lifeline where supported. Existing mentions are not a complete comparable pathway.
Finish with a concise extension to the urgent-care matrix and country sections, using current official sources and separating crisis support, clinical referral and emergency response. Do not infer a shared backend or turn locality-specific information into a universal patient-routing rule. No separate page is proposed.
WN-007
Origin: imported from the 16 September content and narrative review, not a recovered chat quotation. Needs scope: select one of its six existing passes—entry points, HealthShare workflow, chronology, readability/evidence links, history/source preservation, or the national-service reading journey. The queue retains their detailed completion criteria.
The user-selected Core Services Executive Summary, completed 30 September 2026, adds a simpler national-services entry point. The same-day browser follow-up gives all five requested topic groups their own sections and places access types in separate right-hand columns per nation, using System, Portal and other relevant labels. The selected 1 October reading-order and synchronisation correction makes the route Summary → Matrix → Landscape, adds a matching DSIC section, reconciles existing interface qualifications and strengthens the explicit review gate. See the reconciliation record. The subsequent Current Med IS alignment repeats the same six dated service annotations, adds a Healthcare network row and checks paired marker placement without colouring the Access columns. The row-separation correction then places separate pathology and imaging ordering rows above their results and distinguishes professional from patient viewing. This is partial editorial coverage, not completion of all six passes or the comparative portal-journey test.
The clinical-data example in Further Research Priorities overlaps the HealthShare workflow pilot: treat these as one pass, preserving terminology and receiving-system steps. WN-005 has a different urgent-care handoff purpose; reuse useful explanation patterns without claiming the two examples prove the same architecture. Finish a selected editorial pass in its existing pages and update the queue and this disposition together; do not mark all six complete from a sample review.
WN-008
Origin: imported from “Current NHS deployment coverage” in Further Research Priorities. Suggested; partly covered: the UK Clinical Platform Estate now supplies a substantial site/function/status/source baseline, so requesting another general deployment inventory would duplicate work.
Reconcile that older priority against the estate and existing customer pages. Produce a bounded list of coverage still missing, distinguish estate inventory from deeper implementation/outcome evidence, and select at most three concrete records for a later source-validation pass. Finish when the priority says exactly what the estate closes and where further evidence would change a conclusion. Keep record-specific gaps in the estate queue; this reconciliation does not require rechecking every deployment.
WN-009
Origin: imported comparable-product priority. Needs scope: name the task, setting and two products before gathering costs or outcome claims. Existing FHIR comparison does not settle integration-engine or EHR suitability. Finish one scoped comparison in Comparative Analysis with comparable functions, source dates and explicit unknowns; do not create another general supplier ranking.
WN-010
Origin: imported software/service-responsibility priority. Needs scope: choose one software-versus-managed-service comparison relevant to a deployment choice. Use service-specific documents to allocate hosting, upgrades, monitoring, recovery and support in the product portfolio and its existing detail pages. Finish with a sourced responsibility comparison; product availability alone does not establish the customer's contract or rollout.
WN-011
Origin: imported everyday record-keeping synthesis priority. Suggested: add a single creating/correcting/sharing/retaining example to UK Healthcare Recording. Finish when the example keeps professional duties, confidentiality, data protection and local safety controls distinct, linking to the existing source layers. Recheck any legal proposition used before publishing the example; this register itself makes no new legal assessment.
Keep Suggestions Useful
Before adding a suggestion, check this register, the research priorities and the relevant queue entry. Reuse its WN identifier if the outcome is the same; merge overlap and record the reason. Capture a plain-English outcome, provenance/date, relevance, current status, existing destination and completion criterion. A recorded suggestion does not authorise external correspondence or start an automation.
Before publishing a response's three “What Next” steps, save or reconcile them here and link to their entries. Choose actionable work rather than a parked item; explain any required scope in plain English. When the user selects work, mark it in progress; after checking the result, retain a short completed/merged/retired disposition and link to the actual output and Research Log. Do not silently delete abandoned suggestions or keep presenting completed work as new.
Detailed missing artefacts, supplier responses and triggers remain in the Evidence Validation Queue. The existing parked West Midlands, DUAA/ICO, supplier-assurance and Defence trails remain there; this page does not reactivate them. Further historical suggestions can be added when their original wording or a durable project record is available, with honest provenance rather than inferred quotations.