Birmingham and West Midlands Validation
This page extends the initial vendor-only Birmingham and West Midlands evidence with NHS, customer, local-programme, FOI, and standards sources.
What Is Now Externally Supported
| Area | Supported conclusion | Confidence and limits |
|---|---|---|
| Birmingham and Solihull Shared Care Record | The local programme brings together records across GP, secondary care, mental health, community, radiology, pathology, maternity, social care, ambulance, and NHS 111 contexts. | High for local programme scope; does not name InterSystems supplier by itself. |
| Collaborative Shared Care Record DPIA | Published DPIAs say partners procured InterSystems, describe a HealthShare environment/shared instance across BSOL, Coventry and Warwickshire, and Herefordshire and Worcestershire, identify UHB hosting, and describe Clinical Viewer display. | Moderate-high for architecture and processor role; verify final contract and current operating status before procurement use. |
| BCHC Shared Care Record Privacy Notice | BCHC states data shared under the BSOL CCC agreement is retained in the Shared Care Record until the InterSystems contract ends on 31 March 2029. | High for BCHC privacy/retention statement; not a full supplier contract. |
| National Record Locator West Midlands References | NHS England Digital's 2024 NRL change history names InterSystems sites, including Birmingham and Solihull ICB, as live with International Patient Summary PDF pointers and first-of-type direct consumer activity. | High for NRL roadmap statement; does not describe the full local shared-care-record implementation. |
| DSIC HealthShare Compliance Map | Current public Birmingham / West Midlands artefact-pack status covers DSA/DPIA signals, DCB0129/DCB0160 absence, supplier responsibilities, GP Connect/MESH/ITK3 onboarding gaps, WMCA DSCR support, current Medicus integration signalling, and national NHS GP Connect / Medicus status evidence. | Moderate-high for partial artefact-pack evidence; boundary for final signed local legal, safety, onboarding, and operating artefacts. |
| GP Connect InterSystems Supplier Progress | NHS supplier-progress and GP Connect service/DPIA material support Medicus national GP Connect context, including supplier-progress rows, Patient Facing APIs live with Medicus, Access Document FoT-ready status for Medicus, and the GP Connect DPIA naming Medicus as a new NHS market entrant for GPs. | High for NHS national GP Connect evidence; not proof of the West Midlands HealthShare deployment route. |
| Royal Orthopaedic Hospital EPR | ROH selected InterSystems as EPR partner on 23 October 2025 and later stated on 13 March 2026 that it had signed a contract with InterSystems UKI for a new EPR system. | High for selection and contract statements; go-live and outcome evidence still needed. |
| MERIT mental health shared record | BSMHFT FOI material states the MERIT system was provided by Intersystem and lists an Intersystems HSSF Contract for MERIT from 01/04/2021 to 31/03/2026. Black Country Healthcare FOI material separately lists MERIT as an InterSystems integrated care system and says there were no replacement plans as of 2023. | Moderate-high for supplier/contract existence; post-31 March 2026 status and outcomes still need validation. |
| West Midlands cancer registry / eMDT | InterSystems says West Midlands cancer registry data was being integrated into HealthShare with UHB leading; Birmingham and Solihull ICS separately lists a West Midlands Cancer Alliance eMDT project. | Moderate: the local source validates the eMDT context, but an NHS/customer source explicitly naming HealthShare for the cancer registry project is still needed. |
| HL7 UK West Midlands OIDs | HL7 UK lists OIDs for InterSystems connectivity from Cerner HIE to InterSystems HealthShare West Midlands and for InterSystems Care Community - Birmingham and Solihull CCG. | High for OID existence; not evidence of current operational status. |
Practical Interpretation
The Birmingham / West Midlands evidence is now separated into independent evidence strands. The regional overview should be used as a routing page; detailed interpretation belongs on the linked pages.
There is now a stronger layered picture:
- Local programme scope is supported by Birmingham and Solihull ICS.
- Supplier/processor and HealthShare architecture are supported by published Collaborative Shared Care Record and H&W ICWR DPIAs, including a shared regional HealthShare instance and UHB hosting trail.
- A current Birmingham Community Healthcare privacy notice names the InterSystems contract end date as 31 March 2029 in relation to Shared Care Record retention.
- National Record Locator change history independently names InterSystems with Birmingham and Solihull ICB in 2024.
- Public Birmingham / Coventry / WMCA and trade/vendor sources now support a partial current artefact-pack reading around DSA-sensitive-information statements, DSCR/GP Connect support, and Medicus GP-system integration into the West Midlands Shared Care Record, but not the final signed DSA, current full DPIA, DCB0129/DCB0160, endpoint/certificate, MESH mailbox, or supplier-responsibility artefacts.
- Official NHS England GP Connect material supports Medicus nationally: supplier-progress rows are visible, the GP Connect service page says Patient Facing APIs are live with Medicus and Access Document is FoT ready for Medicus, and the GP Connect DPIA names Medicus as a new NHS market entrant for GPs. This strengthens the Medicus evidence base but does not officially confirm the West Midlands HealthShare integration route.
- ROH's InterSystems EPR selection and contract are confirmed from ROH's own site.
- BSMHFT and Black Country Healthcare FOI records strengthen the MERIT supplier, contract, cross-trust integration, and no-replacement-plans trail through 2023/2026-era source limits.
The 2026-06-19 follow-up search did not find an official West Midlands NHS/customer source confirming the Medicus-to-HealthShare deployment route, final signed local DSA, current local DPIA, DCB0129/DCB0160 pack, endpoint/certificate setup, MESH mailbox setup, or supplier-responsibility matrix. It also did not find stronger public UHB/West Midlands Cancer Alliance evidence naming HealthShare, post-31 March 2026 MERIT continuity evidence, or ROH implementation/go-live updates beyond contract signature and contract-award evidence. Those gaps remain open rather than inferred from adjacent regional or national evidence.
Official Source Search Status: Medicus / West Midlands
| Target | Official evidence found | Current status | Still needed |
|---|---|---|---|
| Medicus national GP Connect status | NHS supplier progress and GP Connect service/DPIA pages identify Medicus in national GP Connect context. | Supported nationally. | None for national GP Connect status; recheck after NHS page edits. |
| Medicus connected into West Midlands Shared Care Record | Current public claim comes from HTN and InterSystems UKI social material, not an official West Midlands NHS/customer page. | Not officially confirmed locally. | Official ICB/customer page, programme update, deployment note, or board paper naming Medicus, HealthShare, the route, and go-live scope. |
| GP Connect, MESH, or ITK3 route used by the West Midlands Medicus integration | NHS evidence supports GP Connect/MESH/ITK3 service context and supplier-progress cells, but no local route artefact was found. | Boundary. | Local onboarding pack, use-case approval, endpoint/certificate evidence, MESH mailbox, workflow IDs, and test artefacts. |
| DSA / NDSA | Birmingham/Coventry pages support DSA-sensitive-information and local data-sharing context; NHS GP Connect page points to the NDSA for GP Connect data-sharing requirements. | Partial. | Signed local DSA, NDSA adoption evidence, controller/joint-controller matrix, processor terms, and route-specific access policy. |
| DPIA | NHS GP Connect DPIA names Medicus nationally; regional DPIAs describe HealthShare/Information Exchange and InterSystems roles historically. | Partial. | Current local DPIA or addendum covering the Medicus / West Midlands route. |
| DCB0129/DCB0160 | No public official local safety artefact was found for the Medicus / West Midlands HealthShare route. | Missing public evidence. | Supplier DCB0129, deployment DCB0160, hazard log, clinical safety officer ownership, residual-risk acceptance, and change-control evidence. |
Validation Pages
- Birmingham and Solihull Shared Care Record
- Collaborative Shared Care Record DPIA
- BCHC Shared Care Record Privacy Notice
- National Record Locator West Midlands References
- HL7 UK West Midlands OIDs
- West Midlands Cancer Registry and eMDT
- MERIT Mental Health Crisis-Care Sharing
- Royal Orthopaedic Hospital EPR
Remaining Gaps
- Confirm current live status, data coverage, and user adoption for the Birmingham and Solihull Shared Care Record.
- Find the final public contract award or procurement notice for the Collaborative Shared Care Record where available.
- Obtain official current Medicus integration architecture and local GP Connect/MESH/ITK3 onboarding artefacts for the West Midlands Shared Care Record.
- Validate the West Midlands cancer registry / eMDT HealthShare claim against UHB, West Midlands Cancer Alliance, or another NHS/customer page.
- Confirm whether MERIT continued, changed supplier, or was replaced after the contract end date of 31 March 2026.
- Track ROH implementation milestones, go-live date, clinical-safety approvals, and post-implementation outcomes.