GP Connect InterSystems Supplier Progress
This page records the current NHS GP Connect supplier-progress evidence that names InterSystems products. It is a precision page for InterSystems GP Connect Evidence Boundary, not a full product-conformance statement.
Source Snapshot
The NHS GP Connect supplier progress page tracks provider and consumer supplier progress by GP Connect capability and was edited on 5 June 2026. Current NHS service/API pages separately confirm the broader GP Connect service context, Access Record Structured status/version, Send Document messaging pattern, National Data Sharing Arrangement context, and national Medicus status/DPIA context.
The public page is useful, but it is column-sensitive. A 2026-06-19 structural HTML table parse resolves the previous rendered-text ambiguity: InterSystems IRIS For Health (Middleware) maps only to Send Document (Send) v2.0.1, while the source-spelled InterSytems Healthshare Access Record: Structured consumer row maps to Medications v1.2.6, Allergies v1.2.6, Immunisations v1.5.0, and Uncategorised v1.5.0; the other HealthShare Access Record: Structured cells, including Access document, are blank in the parsed table.
Structured HTML Capture (2026-06-19)
The table capture found four relevant NHS supplier-progress tables. It confirms both InterSystems rows and the adjacent Medicus rows that matter for the current West Midlands / Medicus interpretation.
| NHS table | Source row label | Parsed capability cells | Interpretation |
|---|---|---|---|
| Consumer supplier progress | InterSystems / IRIS For Health (Middleware) |
Access Record: HTML blank; Appointment Management blank; Send Document (Send) v2.0.1; Update Record blank. |
Strong NHS-published evidence that IRIS for Health (Middleware) appears as a consumer-side Send Document route at v2.0.1. |
| Access Record: Structured supplier capabilities | InterSytems / Healthshare |
Medications v1.2.6; Allergies v1.2.6; Immunisations v1.5.0; Uncategorised v1.5.0; Consultations, Problems, Investigations, Referral (Outbound), Diary entries, and Access document blank. |
Stronger than row-level evidence: the exact Access Record: Structured sections are now mapped, while the source typo and blank cells should be preserved as boundaries. |
Medicus is also visible in NHS GP Connect sources and is relevant because current Birmingham / West Midlands public reporting says Medicus GP systems have been connected into the West Midlands Shared Care Record. The service-status and DPIA material add national NHS evidence: Patient Facing APIs are live with Medicus, Access Document is FoT ready for Medicus, several Access Record: Structured sections are FoT ready for Medicus, and the GP Connect DPIA names Medicus as a new NHS market entrant for GPs.
| NHS table | Source row label | Parsed capability cells | Interpretation |
|---|---|---|---|
| GP patient record system suppliers | Medicus / Medicus |
Access Record: HTML full roll-out approved; Appointment Management full roll-out approved; Send Document (Receive) full roll-out approved; Update Record to be confirmed. | Strong NHS-published provider-side progress signal for Medicus, not InterSystems. |
| Access Record: Structured provider capabilities | Medicus / Medicus |
Medications, Allergies, Immunisations, Consultations, Problems, Investigations, Referral (Outbound), Diary Entries, and Uncategorised FoT ready; Access document development. | Strong NHS-published structured-provider progress signal for Medicus. |
| Consumer supplier progress | Medicus Health Limited / Medicus v1 |
Access Record: HTML v0.74; Appointment Management v1.27; Send Document (Send) v1.3.2; Update Record blank. |
Strong NHS-published consumer-side progress signal for Medicus. |
InterSystems Rows
| NHS section | Row label | What the wiki can say | What not to over-read |
|---|---|---|---|
| Consumer supplier progress | InterSystems IRIS For Health (Middleware) |
The row appears in the NHS consumer-supplier table. The parsed table maps the only populated InterSystems cell to Send Document (Send) v2.0.1. |
This row is not evidence of Access Record HTML, Appointment Management, or Update Record support; those cells are blank in the parsed table. |
| Access Record: Structured supplier capabilities | InterSytems Healthshare in the NHS-rendered row label, normalised here as InterSystems HealthShare |
The row appears in the NHS Access Record: Structured supplier-capabilities section. The parsed row maps HealthShare to Medications v1.2.6, Allergies v1.2.6, Immunisations v1.5.0, and Uncategorised v1.5.0. |
The source misspells InterSystems as InterSytems; Consultations, Problems, Investigations, Referral (Outbound), Diary entries, and Access document are blank and should not be claimed. |
Evidence Boundary
This page strengthens the GP Connect evidence set because it moves beyond dated vendor statements and records current NHS-published supplier-progress rows with exact parsed capability cells and current NHS service/DPIA context. It does not prove live local deployment, full capability coverage, or InterSystems product configuration in any named customer environment.
The capability context remains important. NHS's current Access Record Structured page is the authoritative API/service context for ARS version and status, while Send Document is a production messaging route using MESH, ITK3, HL7 FHIR STU3 payloads, and workflow ID GPFED_CONSULT_REPORT. Those service facts do not prove local InterSystems onboarding, mailbox operations, endpoint certificates, clinical safety, or customer deployment.
Evidence Request Pack
This request pack applies only when the NHS supplier-progress rows are being relied on as assurance evidence for InterSystems IRIS for Health (Middleware), InterSystems HealthShare, GP Connect Send Document, or GP Connect Access Record: Structured. The appropriate evidence is supplier, NHS standards-owner, or customer-approved material. Patient-identifiable records, credentials, private keys, endpoint certificates, and non-disclosable operational details are out of scope.
| Request area | Ask for | Why it matters |
|---|---|---|
| Supplier-progress record | Current NHS supplier-progress extract, row label, supplier legal name, product/component name, product version or build, GP Connect capability, capability version, row status, page edit date, and any supersession or withdrawal note. | Confirms whether the 5 June 2026 parsed rows remain current and prevents the source-spelled InterSytems Healthshare row or blank cells being normalised into broader product claims. |
| Validation and test scope | GP Connect assurance or validation summary for IRIS for Health Send Document (Send) v2.0.1 and HealthShare Access Record: Structured Medications, Allergies, Immunisations, and Uncategorised sections; include test method, payload/profile scope, environment, assessment date, and standards-owner role. |
Shows what the NHS row actually assessed instead of treating supplier-progress presence as complete product conformance. |
| Exclusions and caveats | Explicit blank cells, unsupported GP Connect capabilities, unsupported Access Record: Structured sections, source spelling caveats, First of Type or rollout-stage constraints if relevant, and any third-party or customer prerequisites. | Keeps Send Document, Access Record: Structured, Access Document, Appointment Management, Update Record, and patient-facing API claims separate. |
| Component coverage | Whether IRIS for Health, HealthShare, Health Connect, Clinical Viewer, a partner system, or customer-hosted integration component was assessed directly, indirectly, or only as supporting infrastructure. | Prevents a GP Connect row for one product/component becoming a HealthShare-family or InterSystems-wide claim. |
| Adjacent standards | Separately evidenced MESH, ITK3, HL7 FHIR STU3, workflow ID, National Data Sharing Arrangement, DCB0129/DCB0160, DSIC, and security/onboarding artefacts tied to the same product/version or customer route. | Distinguishes NHS service context from independent proof that a named InterSystems deployment is onboarded and assured. |
| Deployment artefacts | Customer-approved architecture, consumer/provider role split, use-case approval, DSA/NDSA adoption, DPIA reference, DCB0129/DCB0160 responsibility split, endpoint/mailbox/certificate ownership at a non-secret summary level, monitoring/support model, go-live date, and current-status statement. | Converts supplier-progress evidence into deployment-specific assurance without exposing sensitive implementation detail. |
For current use, the safest wording is:
- NHS supplier-progress material edited 5 June 2026 names InterSystems IRIS for Health (Middleware) in consumer supplier progress and InterSystems HealthShare in Access Record: Structured supplier capabilities.
- The parsed IRIS for Health row maps to Send Document (Send)
v2.0.1; current Send Document service context is production MESH / ITK3 / FHIR STU3 messaging. - The parsed HealthShare Access Record: Structured row maps to Medications
v1.2.6, Allergiesv1.2.6, Immunisationsv1.5.0, and Uncategorisedv1.5.0; other structured sections and Access document are blank. - Official NHS service/DPIA pages strengthen national Medicus context, but they do not confirm the West Midlands HealthShare route, local onboarding artefacts, DSA/NDSA adoption, DPIA addendum, or DCB0129/DCB0160 evidence.
Related Pages
- InterSystems GP Connect Evidence Boundary
- GP Connect Deep Dive
- GP Connect Send Document
- GP Connect Access Record: Structured Capability
- Health Connect
- HealthShare
- Standards and Interoperability Evidence Domain
Remaining Follow-up Evidence
- Current GP Connect-specific InterSystems technical documentation showing how Health Connect or HealthShare implements the relevant capabilities.
- Supplier, standards-owner, or customer-approved response to the evidence request pack above.
- Customer-side deployment evidence for any named InterSystems-backed GP Connect use, including the use-case, safety, information-governance, and operating-model artefacts.
- Recheck the NHS supplier-progress page after any edit later than 5 June 2026.