Skip to content

Collaborative Shared Care Record DPIA

This page tracks the published DPIA evidence for the Birmingham, Solihull, Coventry and Warwickshire, Herefordshire and Worcestershire Collaborative Shared Care Record.

Supported Conclusion

The published Collaborative Shared Care Record DPIA says partners procured InterSystems as software/system supplier, cloud hosting provider, and processor. It describes local provider systems connecting through a central Information Exchange and HealthShare environment to create a shared care record.

The Herefordshire and Worcestershire Integrated Care and Wellbeing Record DPIA independently supports the same regional pattern. It says H&W STP procured InterSystems, describes the use of a HealthShare instance shared with Birmingham and Solihull and Coventry and Warwickshire, identifies University Hospitals Birmingham NHS Foundation Trust hosting, and describes data being displayed through Clinical Viewer.

BSMHFT's FOI 052/2025 supplies separate customer contract evidence: InterSystems HealthShare, the same three ICS areas, a £4 million total contract value and an April 2029 end date. Its FOI 0469/2025 also reports Shared Care Record installation in April 2020 and no plans to replace it at the time of the response.

Evidence Status

Confidence is moderate-high for the architecture and processor roles described in the published DPIAs, and high for the supplier, regional scope and contract facts reported by BSMHFT. The FOI responses do not publish the signed service schedules, current hosting configuration, complete live participant list or support model. Those implementation questions remain open. The collaborative Shared Care Record contract must not be treated as proof that every service under the separate older MERIT contract continued unchanged.

Relationship to Local Programme Evidence

Use this page with Birmingham and Solihull Shared Care Record. The ICS page establishes local shared-care-record scope; the DPIAs supply stronger InterSystems supplier, hosting, processor, Information Exchange, HealthShare architecture, UHB hosting, and Clinical Viewer flow evidence.

Follow-up Evidence

  • Signed service schedules or an award notice to reconcile the FOI's April 2029 end date with BCHC's 31 March 2029 retention wording.
  • Current data-sharing agreement and processor list.
  • Live operating model, hosting status, and support arrangements.