| Introduce the concepts |
Foundations overview, records, systems, information and work, governance, assurance and procurement, then digital health landscape |
Assume no shared clinical/digital terminology; build definitions in order, then apply them to capabilities and assurance. Use the generic GP patient before the Defence application |
| Define the programme |
Programme scope, operating model, architecture, national interfaces |
Supplier agnostic; public evidence, proposal and discovery separate |
| Prepare a programme decision |
Decision brief, project status and discovery register |
Focus on the wider case for change, outcomes and strategic direction. Keep public findings, proposals and open questions distinct. The owner rejected detailed referral development as the next priority; do not reintroduce it without new direction |
| Explain the subject |
Foundations, Defence context, primary record, model, flows, governance and project status |
Follow the overview reading path; use detailed references for the question being answered |
| Check record-role consistency |
Foundation definitions, information and work, terms and the relevant Human and portable concept pages |
GP source role plus PRC role; community/hospital source accounts; contributions under applicable NHS conventions; primarily read-only DShCR separate from clinical authoring, PRC filing and responsibility |
| Develop shared-record capabilities |
Architecture, system concepts, flows, governance and terms |
Connected, longitudinal overview with fuller source-record access; coverage/currency/permissions remain explicit. IntP two-way exchange and core clinical information for source-system CDSS; source authority/reconciliation remain TBC. HPD profiles and EMPI matching/shared demographics stay distinct from clinical records and patient administration. Continuity, forms and patient-facing options remain TBC. 212, 220 |
| Explain Defence healthcare and military medicine |
Programme terminology, primary record, Defence context and governance |
Wider Armed Forces/civilian scope; occupational health-led qualifies military medicine. Preserve public-source scope, occupational/command boundaries and dated history. 221 |
| Develop the broad concept |
NHS reference model, terms, legal framework |
NHS England baseline, material devolved differences, public primary sources only |
| Specify information exchange |
Correspondence, mechanisms, ADT |
Exact profiles, versions, identity, acknowledgements and clinical tasks |
| Explain Defence mechanisms |
Public mechanism map |
Dated local evidence, announcement versus delivery, explicit unknowns |
| Assess GP IT procurement |
Framework, Lot 1, Lot 2, Lot 3, DSIC, TIF and terms; portable concept in knowledge/concepts/gp-it-procurement.md |
Notice stage, lot scope, buyer eligibility, effective requirement versions, MUST/MAY epics and capability-specific evidence |
| Research a claim |
Source register and relevant concept |
Validation queue and Graphify |
| Write new original English prose |
Manifest roles.authoring_policy path, or AUTHORING.md fallback; the relevant source and intended reader task |
DenchCo ASD-STE100-inspired 80% house style, protected text, stricter local policy, and material exceptions; no computed score or compliance claim |
| Maintain the Wiki |
Manifest, agent guide, and change log |
Design and runtime contracts |
| Prepare a development response |
Manifest capability, canonical Human Wiki URL, and captured response draft |
Markdown/HTML/plain-GFM link forms; --managed-live exact service identity and route HTTP; host pre-send hook for an uncaptured response |
| Select follow-up work |
Current goal and project status |
Failed or unrun checks and unparked validation items |
| Propose a reusable Standard change |
Tracked proposal workflow, verified originating commit/JJ phase, and immutable Standard pin |
Marker matches, affected contract, licence/browser evidence, fixture, migration impact, payload/form digest, upstream registry, and adoption authority |