Validation queue
These items do not prevent a qualified explanatory wiki. They prevent treating the proposed model as an approved implementation. The retained implementation dependencies are parked; new programme-definition questions are open for discovery.
The 16 October expansion uses public primary sources only. Earlier local decision and approval items remain implementation dependencies, not requests for private operational material. The broader reference questions are developed through published evidence; undocumented mechanisms remain unknown.
| ID | Gap | State | Next bounded action | blocked_by |
reopen_when |
last_checked |
|---|---|---|---|---|---|---|
| VAL-001 | Historical programme timetable | historical / superseded as architecture driver | Retain attribution only; assess any later public announcement on its own scope | No current public baseline established | A relevant new public announcement requires baseline reassessment | 2026-10-20 |
| VAL-002 | Exact GP Connect participation route | parked | Obtain service-owner confirmation for the intended supplier, cohort, purpose and product | Current service notices restrict new onboarding; Defence route not established | An assured supplier and service owner confirm the route | 2026-10-14 |
| VAL-003 | Current DPHC organisation and responsibility map | parked | Validate current medical, dental, occupational, mental-health and rehabilitation responsibilities | No complete current organisation chart supplied | Authoritative current structure becomes available | 2026-10-14 |
| VAL-004 | Record selection and clinical task ownership | parked | Agree one referral/result pathway, including redaction, pending tasks, review and escalation | Local clinical and governance decisions required | Named pathway owners provide an approved workflow | 2026-10-14 |
| VAL-005 | Defence-specific legal applicability and cross-border care | parked | Map purposes, legal roles, lawful basis and nation-specific arrangements for one selected flow | England reference material is not a complete Defence legal assessment | Approved intended use and applicable agreements are available | 2026-10-14 |
| VAL-006 | Later position on recruitment-related GP Connect use | parked | Check for a formal decision changing the dated NDG advice | No later public reversal established | Service-owner or NDG evidence changes the position | 2026-10-14 |
| VAL-007 | Approved access and sharing rules across military clinical services | parked | Validate one purpose/role/data/action matrix, including treatment, occupational assessment, sensitive detail and command outputs | Public scope and training descriptions do not define local access authority or approved workflows | Named clinical and governance owners provide current service policies and an intended use | 2026-10-14 |
| VAL-008 | Deployed continuity during connectivity loss | parked | Validate one handover and delayed-record reconciliation pathway, including provenance, pending actions and conflict handling | Forward concept does not establish delivered offline capability or an approved technical design | An operational pathway owner supplies the agreed clinical and technical design | 2026-10-14 |
| VAL-009 | Public Defence interface specifications, including ADT | parked | Map an available public specification to its sender, receiver, event/profile version and response/recovery rules | Local inspections describe workflows but not complete wire contracts | A public MOD, NHS, regulator or approved standards publication identifies the actual interface | 2026-10-16 |
| VAL-010 | Current national-service transition and availability | parked | Reconcile NEMS migration, pathology API availability and relevant receiving products against their dated service notices | Deprecation, development and production status differ; replacement use-case coverage is not fully established | A public migration guide, production release or corrected service notice changes an applicable route | 2026-10-16 |
| VAL-011 | Correspondence and territorial coverage across Defence | parked | Extend the type-to-route matrix only where a public source establishes actual service, nation, standard and workflow | Public evidence does not cover every clinical service, specialty or devolved boundary | New public guidance or inspection evidence identifies an uncovered correspondence route and scope | 2026-10-16 |
| VAL-012 | Final DPC tender, capability definitions and relevant participation | parked | Read the UK4 notice and accessible capability attachment; reconcile dates, call-off terminology, applicable capability versions, lot conditions, MOD scope and named supplier evidence | UK3 is indicative; attachment access failed and structured EOI field conflicts with no-response text | Public UK4, amended notice, accessible attachment or named award changes the evidence | 2026-10-17 |
See the evidence matrix for the supported statements and the project updates for historical direction. The maintenance guide explains how to reconcile new evidence. Parked rows do not authorise recurring checks or additional external actions.
Programme-definition discovery — 20 October 2026
The following questions remain open. They are not requests for private operational data or claims that approval can be obtained through public research alone. Research can establish public constraints; formal programme and pathway decisions remain separate.
| ID | Discovery question | Evidence or decision needed | blocked_by |
reopen_when |
last_checked |
|---|---|---|---|---|---|
| CT-01 | Which problem set and strategic direction should the coalition agree? | Evolving public evidence, assumptions, risk register and decision record | Programme definition not agreed | Definition workshop or new public evidence | 2026-10-20 |
| CT-02 | Who owns each pathway and handover? | Responsibility and cover model, including external partners | Proposed roles only | Pathway defined with accountable roles | 2026-10-20 |
| CT-03 | Which information enters the primarily read-only DShCR, and how is it accessed or retained? | Content coverage, provenance, correction rules and evaluated storage options; any separate forms need explicit source-record responsibilities | Coverage and storage decisions remain open after the owner clarification | Content scope and continuity options can be compared | 2026-10-22 |
| CT-04 | What does safe disconnected work require in each setting? | Minimum dataset, permitted cache, expiry, recovery, reconciliation and safety criteria | Setting-specific requirements missing | Scenario evidence and applicable sharing rules available | 2026-10-20 |
| CT-05 | What can Defence consume/contribute through England SPR? | Final law, technical contracts, participation and operation-specific conditions | Proposed law and incomplete service contract | Enacted/commenced provisions or published service contract | 2026-10-20 |
| CT-06 | Which Scottish functions support external Defence use? | CHI approval route, current technical scope and permitted content | Demographics qualifications need reconciliation | Current service-specific external guidance | 2026-10-20 |
| CT-07 | What is Wales's latest ICR scope and participation offer? | Later programme decisions and published interfaces, separate from NDR services | February minutes do not establish October stage | Later dated public decision or specification | 2026-10-20 |
| CT-08 | What are Northern Ireland's external operations? | Function-level access, primary-care boundary and migration coverage | FAQ combines read-only and transaction wording | Current operational guidance resolves scope | 2026-10-20 |
| CT-09 | How do regional connections evolve with national services? | Region-specific contracts, coverage and transition rules | No uniform regional contract | Applicable current regional guidance | 2026-10-20 |
| CT-10 | How are identity and corrections reconciled across nations? | Namespace, match, merge/unmerge, correction and recipient rules | Complete cross-boundary contract missing | Published profiles and synthetic scenario tests | 2026-10-20 |
| CT-11 | Which separate-purpose uses are permitted? | Treatment, assessment, command and secondary-use decisions with data minimisation | Public direct-care rules are insufficient | Intended use and applicable public authority clarified | 2026-10-20 |
| CT-12 | What differs for overseas, allied and contracted care? | Public jurisdiction, standards, restrictions and handover evidence | UK source increment is incomplete | A representative partner pathway is researched | 2026-10-20 |
| CT-13 | How will value and safety be assessed? | Outcome baselines, measures, trade-offs and acceptance criteria | No measured programme baseline | Discovery evidence enables comparison | 2026-10-20 |
| CT-14 | Which policy and organisational changes are needed? | Current-to-future responsibility and policy assessment | Target operating model remains proposed | Evidence demonstrates a needed change | 2026-10-20 |
The internal architecture, operating model and national interface map set the current hypotheses. Supplier-specific market questions from release v1.0.0 are retired from the future definition; their history remains preserved. This queue does not authorise recurring checks or external messages.
Shared-record and platform discovery
The 22 October 2026 owner clarification establishes capability direction, not a completed design. The DShCR is primarily a read-only overview, closely coupled with the IntP. Source systems retain their accounts. The EMPI's shared demographic profile is a critical requirement. The following work develops those requirements without asking the owner to select software internals prematurely. 212
| ID | Focus | Next bounded action | blocked_by |
reopen_when |
last_checked |
|---|---|---|---|---|---|
| SR-01 | PRC contributions and DShCR coverage | Map applicable NHS content standards to PRC correspondence; define the contiguous, longitudinal overview and authorised access to complete contributing records, with work state, provenance and freshness | Source coverage, permissions, content scope and applicable standards are not yet mapped comprehensively | Public standards can be assessed against a defined information category | 2026-10-23 |
| SR-02 | Continuity and capture | Compare retained information, consultation capture and reconciliation with source systems against stated failure scenarios; define source-record responsibility for captured information | Outage scope, retention, recovery objectives and forms uses remain open | Failure scenarios and candidate capture needs are defined | 2026-10-23 |
| SR-03 | Patient-facing services | Explore viewing, patient contribution and self-management features; define attribution, review and return flows through the IntP | Feature scope and incorporation rules remain open | A bounded feature set is ready for assessment | 2026-10-22 |
| SR-04 | HPD and access profiles | Define profile and organisation/facility lifecycle, permissions, broad care relationships, break-glass and oversight; assess service discovery with controlled location disclosure | Administrative visibility, access matrix and location policy remain open | Intended user functions and disclosure conditions are defined | 2026-10-22 |
| SR-05 | EMPI identity and shared demographics | Specify identifier linkage, demographic sources, conflict resolution, merge/unmerge and correction propagation | The required functions are agreed; source authority and implementation rules are unknown | Sources and identity-maintenance requirements can be compared | 2026-10-22 |
| SR-06 | Exchange, processing and integrity | Define two-way IntP exchange with independent source systems, including conditions, medications, vaccinations and allergies for specialist-system CDSS; specify EMPI/HPD context, identifiers, retries, corrections and recovery | Content authority, currency, reconciliation and processing responsibilities remain open; no automatic overwrite or global clinical source hierarchy selected | A bounded information category and exchange contract are ready for evaluation | 2026-10-23 |
Public references for continuity, PHRs, identifiers, provenance and hashes are registered separately. They support option assessment and do not select Defence products, topology or standards versions. 213, 214, 215, 216, 217, 218
The wider healthcare operating-model introduction remains parked at the owner's request. blocked_by: owner scope hold. reopen_when: the owner explicitly returns to that expansion. last_checked: 2026-10-22. Existing programme scope remains; this content revision focuses on technology.