Prison releasees reentering society need more than a good job. Stable housing and access to healthcare are equally critical for reentry success, and strong community support can ease the transition and reduce recidivism. Unfortunately, the justice, housing, workforce, and healthcare systems often operate in silos, and most jurisdictions lack the necessary technical infrastructure to unify critical systems.
As a result, many previously incarcerated individuals lack access to the services they need and struggle to successfully reintegrate. New and emerging technologies show promise for helping jurisdictions break down existing silos and better serve those trying to navigate the transition from incarceration to community life. Today’s scalable cloud architecture leverages application programming interface (API)-driven integration, entity-based data models, and standardized exchange frameworks to overcome longstanding barriers to data integration and enable secure, scalable cross-agency coordination within the criminal justice ecosystem.
Exceptional cross-sector coordination is essential for creating positive reentry outcomes. It delivers better outcomes than single-service interventions because reentry challenges are multidimensional and interdependent. Addressing one domain in isolation shifts the risk to other domains rather than resolving it.
There are several reasons for this shift. First, numerous interacting needs shape reentry outcomes. For instance, people leaving incarceration may secure employment, but without stable housing or behavioral health support, they are unlikely to have positive reentry outcomes. Success in one area during reentry depends on achieving success in other adjacent areas.
Single-service interventions also create fragmented information environments in which each agency holds partial data. For example, probation departments track compliance statuses, healthcare providers understand treatment and/or mental health needs, while housing agencies recognize placement constraints, but none of that information is shared between agencies. This disconnect creates an environment where decisions are often made based on incomplete or outdated information.
Cloud architecture that includes features such as interoperable platforms, shared data standards, and event-driven coordination layers has emerged as a powerful approach for coordinating across sectors within the justice reentry services system.
One example is the Open Justice Broker Consortium (OJB). This recently formed nonprofit membership organization consists of government agencies and jurisdictions that are “dedicated to improving justice information sharing through the reuse of low-cost, standards-based integration software.” With the OJB platform, users can access integrated justice technology, develop and share ideas and information, and access expertise and implementation assistance.
One method to promote cross-sector collaboration within a jurisdiction is to implement a cloud platform that focuses on building communities or experiences as part of an experience cloud. During an experience cloud implementation, external participants gain access to a specific portion of the application that is accessible only to them and an internal team. For instance, external housing representatives receive limited, secure access to customer relationship management (CRM) systems for referrals of customers with housing needs through a community or partner portal license, which is less expensive than a full license.
Administrators can then configure the system to ensure that proper permissions are assigned. Once partners have access, they can view referrals, act reliably, and collaborate to obtain additional information. This approach ensures that all communications are consolidated in a single platform, reducing the chances of procedural delays in processing reentry workflows.
To confirm that their cloud system is working optimally, agencies can track several variables, including cross-domain outcomes, system-level indicators, and coordination quality. For cross-domain outcome metrics, it is best to focus on end-state stability through the Stability Composite Index rather than service activity. This index measures the percentage of individuals who are stably housed, employed (or in training), and engaged in healthcare and behavioral health services simultaneously.
Agencies can also track cross-domain effectiveness by monitoring sustained outcomes. This includes conducting 90-, 180-, and 365-day housing retention check-ins and 30-, 60-, 90-, and 180-day employment retention follow-ups.
Integrated service delivery can improve process performance across agencies and is measured by monitoring:
Keeping abreast of these indicators enables agencies to see whether the system is functioning as a coordinated network. It’s also crucial for agencies to track cohorts by following individuals from pre-release through reentry milestones in addition to measuring the training and education sessions attended and certificates earned.
A significant obstacle agencies encounter is legacy systems. Most reentry organizations rely on systems like SharePoint or Crystal Reports and on traditional communication methods such as phone calls, emails, and Portable Document Format (PDF) files for information distribution. As a result, it is difficult to manage data reporting, avoid expensive duplication, and maintain synchronicity with client records. This approach lacks a secure interface or data backups, has limited ability to track client progress, and requires extensive employee hours to gather the necessary data to meet grant and funder reporting requirements.
Moving away from legacy systems involves migrating historical information into the CRM and is accomplished through a customized data migration strategy. The strategy needs to account for the agency’s individual needs and protect essential data relationships.
To further optimize success, organizations can provide extensive hands-on training to all staff and clearly define access levels and roles. They can also schedule a dedicated pilot period to test the new system in a live environment and identify any deficiencies.
Security is critical to the ultimate success of scalable cloud architecture, which means enabling role-based permissions, encryption, secured automated data backups, audit tracking, and multi-factor authentication (MFA) for most scenarios. There are a few exceptions for enabling MFA. For example, when vocational trainers, job counselors, or career advisors visit a correctional facility to meet with individuals approaching release or to conduct cohort sessions, they are not allowed to bring mobile devices into the facility. In this case, agencies can establish specific permissions that allow staff to temporarily access the system without MFA. Solutions include using a token-based system or Internet Protocol (IP) whitelisting, where specific IP ranges are preconfigured into the CRM to ensure safe access.
Recent research demonstrates that coordinated ecosystems that integrate corrections, housing, healthcare, employment, behavioral health, and community support services deliver the most effective results. Scalable cloud architecture overcomes data silos and facilitates more unified service delivery through shared infrastructure and standardized data practices. By adding encryption, role-based access control, and IP restrictions to their platforms, jurisdictions can also guarantee that the unified services meet compliance standards and protect data privacy and operational integrity, creating a true win-win scenario.
Srinivasu Kavala is the business intelligence lead for Housing Works Inc. and has 17 years of experience in the IT and software industries, specializing in engineering, management, and consultations. He has extensive experience in cloud computing technologies and related integrations, and has worked with major clients across insurance, banking, healthcare, public service, and non-profit domains. Srinivasu holds a bachelor’s degree in technology in electronics and communication engineering. Reach him at kavala.srinivasu@gmail.com.
Disclaimer: The author is completely responsible for the content of this article. The opinions expressed are their own and do not represent IEEE’s position nor that of the Computer Society nor its Leadership.