Skip to content

NHS ITK Accreditation

This page tracks InterSystems' NHS Interoperability Toolkit evidence.

Supported Conclusion

InterSystems states on its official standards and certifications page that it was the first company to receive official accreditation for its NHS Interoperability Toolkit implementation and that it continues to support new specifications.

Current IRIS for Health documentation still includes NHS Interoperability Toolkit material and repeats the historical claim that InterSystems received the UK's first fully compliant ITK accreditation in 2010. NHS England Digital's ITK conformance process and catalogue pages describe the current route for submitting evidence, certification spreadsheets, ITK Standard Conformance Certificates, Solution Assurance Conformance Certificates, and catalogue listing. A targeted 2026-06-20 recheck did not find a current public NHS or standards-body row naming InterSystems, HealthShare, Health Connect, or IRIS for Health in the rendered ITK catalogue or public search results.

NHS England Digital's Solution Assurance compliance catalogue is a different route and should not be treated as ITK proof. It explicitly excludes Interoperability Tool Kit Accreditation, even though its rendered rows include The Royal Marsden NHS Foundation Trust RMH PAS with Healthshare as a compliance-catalogue entry.

Evidence Status

Confidence is moderate for the historical/vendor claim and for the NHS conformance-process route. Confidence remains boundary-only for current independent InterSystems ITK status because no current public NHS or standards-body catalogue row or certificate naming InterSystems was found in the 2026-06-20 recheck.

2026-06-20 Current-Source Recheck

Source surface What it supports What it does not support
NHS ITK conformance process Evidence-submission route, certification-spreadsheet requirement, and eligibility for catalogue listing after successful conformance. A current InterSystems row, product/version, certificate type, date, or status.
NHS ITK conformance catalogue Certificate and message-bundle catalogue scope; NHS says the detailed download is historical and will not be updated beyond 31 May 2026. Current InterSystems status from the rendered page or targeted public search.
NHS Solution Assurance compliance catalogue Milestone Achievement Certificate catalogue boundary; includes some Healthshare-named compliance rows. ITK Accreditation, which the page explicitly excludes.
InterSystems standards and IRIS for Health documentation Historical accreditation claim and current product-documentation context for ITK material. Independent current accreditation, live NHS onboarding, or customer deployment proof.

Interpretation

The ITK claim should be kept separate from:

Implementation-Proof Requirements

Use this page as the NHS ITK proof checklist rather than treating the historical accreditation claim as current implementation proof.

Proof layer Required evidence before stronger claim
Current independent status NHS or standards-body register row, certificate, or assurance record naming InterSystems, the product/version, ITK standard, certificate type, date, and status.
Product scope Current InterSystems documentation naming the component that implements the ITK route, such as IRIS for Health, Health Connect, or a packaged partner service.
Technical scope Message profile, transport, payload, endpoint, workflow ID or equivalent route identifier, dependency standards, validation rules, and supported versions.
Testing and assurance Conformance pack, implementation guide, sample payloads, test results, release controls, and regression evidence.
Customer deployment Customer architecture, operational support model, monitoring, incident process, DSA/DPIA where applicable, DCB0129/DCB0160 if patient-care workflow is affected, and go-live/current-status evidence.

Focused ITK Evidence Request Checklist

Use this checklist when asking NHS England, a standards body, InterSystems, a customer, or an implementation partner for evidence. The request should ask for product, certificate, message-bundle, date, and status facts without requesting patient-identifiable information or secrets.

Request item Ask for Minimum acceptable evidence
Product and version Exact supplier name, product/component name, product version or release, packaging name if different, and whether the route is IRIS for Health, Health Connect, HealthShare, or a partner-wrapped service. Dated register row, certificate, assurance record, vendor/customer statement, or product-documentation reference naming the product/version.
Certificate or register status Certificate type, certificate/reference number, issuing body, issue date, expiry/withdrawal/supersession date where applicable, and current status. NHS or standards-body record preferred; otherwise a customer-approved certificate copy or supplier evidence pack that can be independently matched to the NHS route.
ITK standard and message bundle ITK standard version, message bundle, message/profile name, workflow or interaction name, transport route, payload format, dependency standards, and any workflow ID or route identifier that can be disclosed. Catalogue row, certificate annex, conformance spreadsheet, implementation guide, or test pack naming the bundle/profile and supported version.
Scope and supplier role Whether InterSystems is supplier, middleware provider, sender, receiver, hosting provider, implementation partner, or platform supplier; identify any customer, system, or deployment scope if approved for disclosure. Supplier-responsibility matrix, assurance record, deployment architecture, or customer-approved implementation summary.
Assurance and test artefacts Completed certification spreadsheet, conformance pack, sample payloads, validation rules, test result summary, release/change-control evidence, and regression approach. Evidence pack or summary showing test status, date, product/version, and message/profile scope.
Current operational use Whether the capability is currently live, retired, migrated, pilot-only, historical, or superseded; include date last confirmed and support owner. Customer-approved go-live/current-status statement, service-management record, procurement/contract evidence, or programme assurance note.
Local deployment artefacts DSA/DPIA where applicable, DCB0129/DCB0160 ownership if patient-care workflow is affected, endpoint/mailbox/certificate ownership where applicable, monitoring, incident, and support model. Deployment pack or customer-approved summary that identifies role split and governance artefacts without exposing sensitive operational details.

If the answer is that no current row exists, record that explicitly with the responding organisation, response date, search scope, and whether the status is not listed, historical only, superseded, not publicly disclosable, or unknown.

Supplier / Customer Evidence Request Template

Use this as the starting request text for InterSystems, a customer organisation, an implementation partner, NHS England, or a standards-body contact. Adapt the bracketed fields before sending.

Subject: Evidence request - NHS ITK conformance / accreditation status for [product or deployment]

We are compiling an evidence-backed assurance record for [project / deployment / due-diligence context]. Please provide any non-patient-identifiable evidence you can share about the current NHS Interoperability Toolkit (ITK) conformance or accreditation status for:

- Supplier / organisation: [InterSystems / customer / partner]
- Product or component: [IRIS for Health / Health Connect / HealthShare / partner-wrapped service]
- Product version or release: [version if known]
- Deployment or customer scope: [deployment name if approved for disclosure]

Specifically, please confirm:

1. Whether there is a current NHS or standards-body register row, certificate, assurance record, or other conformance artefact naming this product/component.
2. The certificate type, reference number if available, issuing body, issue date, expiry/supersession/withdrawal status, and current status.
3. The ITK standard version, message bundle, message/profile name, workflow or interaction name, transport route, payload format, and dependency standards in scope.
4. The supplier role: supplier, middleware provider, sender, receiver, hosting provider, implementation partner, platform supplier, or another role.
5. Whether the capability is live, pilot-only, historical, retired, migrated, superseded, not listed, not publicly disclosable, or unknown.
6. Whether a conformance spreadsheet, test pack, implementation guide, sample payload set, validation summary, or release/change-control evidence can be shared.
7. Whether customer deployment artefacts exist for the route, such as a customer-approved architecture summary, supplier responsibility matrix, DSA/DPIA, DCB0129/DCB0160 ownership, endpoint/mailbox/certificate ownership, monitoring, incident, or support model.

Please do not include patient-identifiable information, credentials, secrets, endpoint certificates, private keys, or operational details that should not be disclosed. If a full artefact cannot be shared, a dated summary confirming the fields above is still useful. If no current record exists, please state the search scope and whether the correct status is not listed, historical only, superseded, not publicly disclosable, or unknown.

Remaining Follow-up Evidence

  • Current NHS or standards-body record naming the InterSystems ITK implementation and its accreditation status.
  • Manual acquisition or official confirmation of any detailed catalogue spreadsheet row if the public download cannot be reliably retrieved from the rendered page.
  • Customer-side evidence where ITK support is part of a named UK deployment.