Cloud-Based Closed Loop Referral System
Overview
Settle Signals
Market intelligence for public sector sales teams
RFP Hunter shows what is open. Settle shows what is forming.
Settle pieces together buyer signals, budgets, contract activity, and the sources your team already monitors. See why an opportunity fits and what to do before the RFP posts.
SUMMARY
KEY REQUIREMENTS
CONTRACT DURATION
TIMELINE
RFP released: June 29th, 2026
RFP all-comers kick off webinar: July 13th, 2026
Vendor questions due: July 17th, 2026
Vendor questions responses published: July 31st, 2026
Proposals due: August 14th, 2026
Vendor presentations: August - September 2026
Vendor of choice notified: Q3/Q4 2026
Implementation project begins: Q4 2026
Project go-live: July 22nd, 2027
QUESTION DEADLINE
CONTACTS
Primary procurement contact — name, title, email, and phone
Additional decision-makers and their departments
Issuing Agency
Contexture
DESCRIPTION
The solicitation seeks a vendor to implement, host, and operate a cloud-based Closed Loop Referral System (CLRS). The selected provider must deliver an implementation plan that accommodates both single-vendor and multi-vendor execution, as well as configure the system in alignment with community-specific workflows. The solution is required to support Single Sign-On (SSO) and include a comprehensive, interactive, real-time resource directory where each service supplier can update their own service-related information.
Integration capabilities are essential, with expectations for connectivity to Electronic Health Records (EHRs), Health Information Exchanges (HIEs), 211 systems, Community-Based Organization (CBO) platforms, and other partner systems, provided such integration complies with contractual, operational, technical, and legal requirements. The system will incorporate Master Patient Index (MPI) identity integration, and ensure robust data mapping, validation, migration testing, and reconciliation processes.
Key requirements include maintaining identity and consent across systems, validating workflows across platforms, and developing a coordinated go-live strategy. The system must enforce data provenance, auditability, and consistency, ensure continuity of unique identifiers and MPI-linked identities, support cross-platform identity reconciliation, and preserve existing patient and client consent throughout all integrated environments.
Similar RFPs
Frequently asked questions
- When is the submission deadline?
- Submissions are due August 14, 2026. Questions must be submitted by July 17, 2026.
- Who issued this RFP?
- It was issued by Contexture. The work is located in Arizona, United States.
- Who is a good fit for this opportunity?
- Proven experience developing and operating cloud-based referral or case management systems
- Expertise in integration with EHRs, HIEs, and related healthcare data systems
- Demonstrated ability to manage large-scale system implementations in the healthcare or social services sector
- Familiarity with identity management, consent management, and data validation protocols
- Capability to support both single-vendor and multi-vendor deployment scenarios
Analysis generated by Settle AI from the source RFP.
RFP Hunter shows what is open. Settle shows what is forming.
Settle pieces together buyer signals, budgets, contract activity, and the sources your team already monitors. See why an opportunity fits and what to do before the RFP posts.