The Crown Prosecution Service (CPS) prosecutes criminal cases that have been investigated by the police and other investigative organisations in England and Wales. It makes its decisions independently of the police and government.
CPS’ are seeking to discover innovative ways to improve their Case Management System (CMS) to save time and improve user experience. As the nature of crime continually evolves, CPS consistently adapts, with digital capability forming the foundational pillar of its response and commitment to enhancing justice.
esynergy partnered with CPS to modernise its infrastructure and make their CMS more efficient. This collaboration aimed to accelerate CPS’s digital transformation and support improving prosecution rates, and reducing case backlogs. The central focus for the project was to find a viable technical solution for seamless connection to the CMS, enabling users to easily review, redact, and search case records.
The project commenced with a discovery phase, where the teams identified the complexities in managing two separate CMS. A crucial step involved rapid prototyping and highly specific user research (UR) to pinpoint issues faced by CMS users and assess if these problems were recurring patterns within CPS. The existing case management process relied on a browser-based CMS application with an Oracle database backend and a Microsoft ASP.NET frontend. Accessing case data and documents within the CMS was previously restricted for third-party applications due to the sensitivity of its production data. Consequently, users had to manually redact and search cases, leading to inefficiency.
The solution, named Casework App, was developed using serverless architecture, leveraging infrastructure-as-code principles and CI/CD processes. In building the Casework App, multiple approaches were explored to interface with the legacy system and connect to the CMS.
Upon realising that direct CMS endpoint connection was impossible, the teams responded innovatively by pivoting and building their own CMS integration called DDEI (Direct Document Extraction and Ingestion). Taking ownership of an internal digital product and its infrastructure marked a first for CPS. The approach revolved around the reuse of API interfaces already exposed by the legacy application. System analysis identified well-structured and stable GraphQL and SOAP APIs integrated into the CMS. To streamline access, a RESTful API was developed to serve as a controlled facade over these existing APIs.