Built for the teams running closed-loop programs.
Different buyers, same data layer. CommonLight provides the verified resource graph that closed-loop referral programs, Medicaid managed care, public health agencies, and CIE networks all need underneath their workflows.
Who reads from CommonLight.
The teams that benefit most are the ones running referral programs governed by compliance requirements, audit expectations, or contractual obligations to deliver verified care navigation.
A governed resource layer your closed-loop referral program can audit at the record level.
Confidence thresholds, provenance, and tier metadata flow into your existing reporting infrastructure. Every record carries its verification history. Every referral target can be traced back to a source, a method, and a date. Your program governance committee gets the data it needs to set thresholds and the documentation it needs to defend them.
- →Setting minimum confidence thresholds for closed-loop reporting
- →Producing audit-ready provenance documentation per referral
Defensible compliance with closed-loop mandates.
The CA DHCS closed-loop requirement effective July 1, 2025 is the most visible example, but it is not alone. Closed-loop referral expectations are spreading across state Medicaid programs and value-based care contracts. CommonLight gives your operations team a verified resource layer where every referral target carries provenance and a confidence score that holds up under audit.
- →Closed-loop reporting for state Medicaid mandates
- →Member-facing resource navigation with documented data quality
One trusted source across programs.
Public health agencies typically maintain parallel resource directories across programs. Behavioral health has one list. Maternal child health has another. Substance use has a third. CommonLight replaces the parallel spreadsheets with one governed graph that every program can read from, with the records each program needs filtered by service category and geography.
- →Replacing program-specific spreadsheet directories with a shared graph
- →Cross-program reporting on community resource availability
A shared substrate so member organizations stop maintaining the same records in parallel.
Coordinated care networks and CBO consortia spend significant operational capacity keeping the same provider records updated across multiple member systems. CommonLight maintains the records once, in HSDS v3.0, with verification metadata, and propagates updates to every member organization through their existing workflows. Updates flow once. Member orgs stop duplicating effort.
- →Eliminating duplicate directory maintenance across member orgs
- →Enabling members to focus capacity on direct service rather than data hygiene
The frontline teams who feel the difference.
CommonLight does not put a tool in the hands of the people answering the phones, navigating the cases, or doing the home visits. Their workflow tools do that. CommonLight makes sure the records those workflow tools act on are real. The people downstream feel the difference.
Care coordinatorsstop spending their day calling providers who are not actually available. The referral they send through their workflow tool reaches a real organization with a real opening.
Community health workersstop building personal directories of providers they trust because the official directory is unreliable. They start trusting the official directory because it carries verification history they can see.
Contact center operatorsstop apologizing to callers when the third number on the screening list does not work. They start moving callers through their queues at the pace the workflow promised.
The diligence questions the data layer has to answer.
A buyer evaluating a closed-loop referral implementation is going to ask the resource directory questions sooner or later. Better to ask them now.
- 01Provenance
Can we trace any given referral target back to a source, a method, and a date?
CommonLight answerYes. Every record carries verification history exposed in the API.
- 02Standards
Will the data flow into our existing referral platform without translation loss?
CommonLight answerHSDS v3.0 native, currently live across nine endpoints.
- 03Confidence
Can our program set minimum thresholds for the records we act on?
CommonLight answerYes. Resource Confidence Score is exposed per record and sortable at query time.
- 04Cadence
How often is the data verified, and how do we know when it changes?
CommonLight answerContinuous verification on a defined cadence. Diff reports scoped per partner.
Where to go from here.
Network Integrity Report.
A scoped audit of your existing resource directory against HSDS v3.0 and our verification rubric. We tell you what is sound, what is stale, and what will not survive closed-loop reporting.
Request a report →ComplianceCA DHCS scoping call.
Scoping a closed-loop deployment for the 2025 mandate? The resource layer is where most implementations get stuck. Talk to us before you sign.
Schedule a call →Fit conversationTalk to our team.
Thirty-minute fit conversation. We will tell you whether your use case is something we can support today, on the roadmap, or out of scope.
Schedule a call →
The verified resource layer underneath closed-loop referral programs.