Healthcare policy intelligence: which revision applied, and when
An architecture for policy decisions where an apparently correct answer can still be wrong because it rests on the wrong revision, date or authority: a 2025 prototype that resolves the revision in force on the date, and a proposed modernization that reconstructs the source first and reasons over procedure behind deterministic gates.
Federal rules, national coverage policy, regional contractor adoption, state variation; each with its own revisions and effective dates
Problem
A question about coverage can be answered identically across many revisions of a manual and differently in the one that applies. Similarity search ranks the many and buries the one. Applicability also depends on effective date, authority relationships and the revision history of the source.
Covered? Authorized? Payable? Each answer is for this patient, this provider, this place and this date of service. The work is reconstructing the applicable rule and its context, not finding a passage that reads well.

Architecture
The paper sets out the full design and its commercial vision: where policy intelligence turns into operational value, and how the system stays current as policies change.
Policy intelligence is two questions that cannot be separated: which rule applies, and what that rule requires (the actions, conditions, exceptions and timing it imposes). My architecture answers them in a fixed order: reconstruct the source first, then reason over it, then let only verified output through.
| Layer | Stage | Status |
|---|---|---|
| Source truth | Extraction of sections, tables, images and cross-references; before-and-after reconstruction from change markup | Built (2025 prototype) |
| Source truth | Revision graph over a manual's full release history, with content inheritance | Built (2025 prototype) |
| Source truth | Pinned releases, an element ledger and a checked canonical reconstruction | Proposed (Gate A) |
| Context | Resolve the revision in force on the date, then run the vector search inside it | Built; exercised on one section |
| Context | Effective, publication and observation dates; supersession | Proposed (Gate B) |
| Context | Graph and vector search in one store, with the date filter and the similarity search in one query | Proposed |
| Context | Self, parent, ancestor and subtree views of each section | Proposed |
| Procedure | Typed procedure and step objects: actors, triggers, deadlines, forms, exceptions, appeals | Proposed (Gate C) |
| Procedure | Ontology seeded from the manuals' own definitions and acronyms, with is-a and part-of relations | Proposed (Gate B) |
| Verified output | A directed workflow of specialist roles and small models behind deterministic gates | Proposed (Gate D) |
| Verified output | Explicit UNKNOWN or PARTIAL with human review; reproducible as-of answers | Proposed (Gate D) |
| Scope | National coverage policy and regional contractors | After the gates pass |
Decisions
- Canonical first. The reconstructed source and its procedure objects are the record of authority; embeddings and model output only interpret it.
- Resolve the date, then search. The revision in force on the date is resolved before any similarity search, so that a passage from the wrong revision cannot reach the answer. In the 2025 prototype the vector search followed this rule; context expansion and undated questions did not yet, and the modernization closes both, running the date filter and the search in a single graph query.
- Correct means in force on the date. An answer counts as correct only if it cites the revision that governed on the date asked.
- Procedures as structure. Actors, steps, deadlines, forms and exceptions become typed, cited objects, because instructions read as flat text lose their order and conditions.
- Models propose, gates decide. Small models propose extractions and mappings; deterministic checks confirm source, scope and date before anything is used.
- Abstain explicitly. When sources disagree or steps are missing, the system returns UNKNOWN or PARTIAL and routes the question to a person.
What was built
- A working prototype on one manual section across its revisions: extraction of changes, before-and-after reconstruction, tables and links
- A revision index over a manual's full release history, with each section linked to the release that last changed it
- Date-based revision resolution: the prototype selects the latest revision released on or before the date asked and restricts retrieval to it (by release date; effective dates and supersession were designed but not populated)
- Graph context (Neo4j) and vector retrieval (Weaviate) coupled to source citations, answered by a small local model
- Revision identifiers and release dates carried through ingestion, the graph, the vector index and the citations
Proposed modernization
- Canonical reconstruction, effective and observation dates, supersession and an ontology, in sequenced gates with acceptance evidence for each
- Procedure extraction and a controlled workflow of specialist roles and small models, behind deterministic checks
- Graph and vector search consolidated in Neo4j's native vector index, so the date filter and the similarity search run in one query
Verification
The 2025 prototype ran its date-resolution path end to end on real queries; it was not formally evaluated. Planned: evaluation sets of dated questions, with canaries that must fail; an answer counts as correct only if it cites the revision that governed on the date asked. The question-and-answer sets are being built during extraction, with a human in the loop checking accuracy.
Evidence
- VERIFIED — PUBLICPublic account of the architecture (Global Trial Accelerators blog, Oct 2026)source · checked 2026-10-27
- VERIFIED — PRIVATERepository and technical whitepaper (2025)private
- VERIFIED — PRIVATEEvidence audit of the 2025 prototype (Oct 2026)held
- VERIFIED — PUBLICPublic architecture white paper: Health Policy Insight Engine (Nov 2026, PDF)PDF · checked 2026-11-07
Status
In development: a 2025 prototype, and a modernization that is proposed, not deployed.
Independent project: a 2025 prototype on one manual section; the modernization is proposed, not deployed. · updated 2026-11-07