Cross-Deck Evidence Carry-Over
This page controls how InterSystems sibling wiki evidence is used in this Defence Medical Command (DMedC) NHS App wiki.
The DMedC Source Register currently includes InterSystems sibling wiki entries as local cross-deck synthesis, not as primary sources. Claims can be promoted only when the underlying primary evidence is carried over or separately registered.
Carry-Over Checklist
| Check | Requirement | Why it matters |
|---|---|---|
| Sibling source path | Identify the InterSystems sibling wiki page and source ID. | Keeps the cross-deck reading traceable. |
| Primary source | Identify the underlying MOD, NHS, NHS England Digital, supplier, regulator, FOI, standards, or implementation source. | Prevents local synthesis from becoming unsupported primary evidence. |
| DMedC source ID | Add or reuse a DMedC Source Register ID for the primary source. | Keeps all claims traceable inside this wiki. |
| Claim type | Classify as product positioning, programme role, architecture component, interface route, implementation status, NHS App feature availability, or cohort behaviour. | Prevents product fit from becoming patient-facing availability. |
| Scope limit | State what the source does not prove. | Maintains evidence-boundary language. |
| Freshness tier | Apply Source Freshness. | Keeps time-sensitive programme and supplier evidence current. |
| Decision impact | Identify which Guidance Decision Model row could change. | Ties evidence carry-over to guidance decisions. |
Current Cross-Deck Ledger
| Sibling evidence | Claim type | Current use | Carry-over status |
|---|---|---|---|
| InterSystems sibling wiki Programme CORTISONE / UK Defence Healthcare page | Cross-deck synthesis | Helps interpret Programme CORTISONE, HealthShare, Health Connect / Integration Platform, Enterprise Master Patient Index (EMPI), and supplier-role evidence. | Secondary synthesis only; primary source IDs required before promoting claims. |
| InterSystems sibling wiki HealthShare Unified Care Record (UCR) page | Cross-deck synthesis / product positioning | Helps frame HealthShare UCR as a possible shared-care / longitudinal-record component. | Secondary synthesis only; use primary InterSystems / MOD evidence for claims. |
| InterSystems sibling wiki Health Connect page | Cross-deck synthesis / product positioning | Helps frame Health Connect as an integration-engine candidate relevant to CORTISONE. | Secondary synthesis only; current DMedC evidence does not prove it is the named CORTISONE Integration Platform component. |
| InterSystems sibling wiki Programme CORTISONE / UK Defence Healthcare page, carrying over MOD performance-row evidence | Supplier / programme-role evidence | Strengthens the CORTISONE IP / EMPI and InterSystems supplier-role evidence base. | Primary evidence carried over; still not NHS App publication, GP-provider role, cohort coverage, or feature-test evidence. |
| InterSystems sibling wiki Programme CORTISONE / UK Defence Healthcare page, carrying over Contracts Finder OCDS evidence | Procurement / licence-package evidence | Supports InterSystems HealthShare / IRIS for Health licence-package tracking for IP&EMPI and Defence Medical Services (DMS)-IX FY25-30. | Primary evidence carried over; licence evidence is not implementation-status or patient-facing availability evidence. |
| InterSystems sibling wiki InterSystems GP Connect Evidence Boundary page, carrying over NHS supplier-progress evidence | Supplier-progress / GP Connect evidence | Records NHS-published InterSystems GP Connect supplier-progress touchpoints for IRIS For Health middleware and Healthshare. | Primary evidence carried over; not Defence Primary Healthcare (DPHC) / CORTISONE deployment, GP Connect PFS enablement, or NHS App feature availability evidence. |
Work Package 4 Route-Layer Binding
Use this binding when updating the Evidence Work Packages CORTISONE route map. A carried-over source can support a layer without proving the next layer.
| Work Package 4 route layer | Direct use in this wiki | Do not infer |
|---|---|---|
| Programme layer; component-role orientation | Secondary synthesis for Programme CORTISONE, HealthShare, Health Connect / Integration Platform, EMPI, and supplier-role framing. | Primary evidence, production deployment, NHS App publication, or patient-facing availability. |
| Component role | HealthShare Unified Care Record product positioning as a possible shared-care / longitudinal-record component. | CORTISONE source-system coverage, GP-provider role, GP Connect PFS enablement, or NHS App publication. |
| Component role; integration-layer candidate | Health Connect product positioning as a possible healthcare integration-engine analogue. | That Health Connect is the named CORTISONE Integration Platform, or that it receives Defence Medical Information Capability Programme (DMICP) / DPHC feeds. |
| Programme layer; component role; identity layer | Primary carried-over evidence for Programme CORTISONE IP / EMPI and InterSystems supplier-role tracking. | NHS App publication, DPHC cohort coverage, GP-provider role, or feature-test results. |
| Component role; procurement / licence layer | Primary carried-over evidence for InterSystems HealthShare / IRIS for Health licence-package tracking for IP&EMPI and DMS-IX FY25-30. | Live deployment status, patient-facing route, Interface Mechanism 1 (IM1) / GP Connect enablement, or feature availability. |
| NHS-facing route gate | Primary carried-over NHS supplier-progress evidence for InterSystems GP Connect supplier-progress touchpoints. | DPHC / CORTISONE deployment, GP Connect Patient Facing API enablement, NHS App exposure, or cohort availability. |
Promotion Rules
- Do not promote cross-deck evidence to NHS App feature availability without direct primary evidence.
- Do not infer GP-provider role, GP Connect Patient Facing API use, IM1 pairing, NHS App publication, or DPHC cohort coverage from product fit alone.
- Do not keep cycling on unavailable DPHC practice-level evidence when the active implementation hypothesis is CORTISONE / InterSystems enablement. Record the DPHC practice-level absence as a boundary, then test the CORTISONE component, source-system, NHS-facing route, assurance, and cohort gates.
- When a primary source is carried over, update Source Register, Evidence Matrix, NHS App Adoption and Implementation, and Guidance Decision Model together.
- Keep InterSystems product and vendor claims separate from MOD/NHS implementation claims.