Who it's for
Your coordinators experience a stale listing as a wasted call. The person they're helping experiences it as another dead end. Your organization experiences it as information that's hard to keep straight. Here is how CommonLight helps each kind of team.
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.
Community organizations and networks
Better information for the referrals your staff make every day. Your team keeps its relationships and its judgment; the listings they start from get checked and re-checked.
A governed resource layer your referral program can review at the record level.
Each listing shows when and how it was checked, so your program can set a minimum confidence level for the records it uses.
- →Setting minimum confidence thresholds for the records your workflows use
- →Showing when and how each listing was checked
Accurate, dated information behind your referrals.
DHCS's closed-loop referral requirements took effect July 1, 2025, and DHCS began actively monitoring compliance on July 1, 2026. Closing the loop depends on your referral workflows, your community partners, and your reporting. CommonLight addresses one input: accurate, dated information about the programs referrals go to. We do not track referrals, and using CommonLight does not by itself meet DHCS requirements.
- →Checked, dated listings for the programs your referrals go to
- →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 which listings were checked, and when
In practice: CommonLight completed a pilot with Douglas County, Colorado, working alongside the County's Human Services, Community Services, and Information Technology teams on its existing resource dataset. The pilot demonstrated an approach that improved the accuracy and completeness of the County's Social Services Resource Locator data while reducing the manual effort required to maintain it.
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 listings once, in HSDS v3.0, and delivers updates through supported connections.
- →Reducing duplicate directory maintenance across member organizations
- →Enabling members to focus capacity on direct service rather than data hygiene
Care-navigation and referral platforms
Better information for the experience you already provide. Your platform handles the referral; CommonLight supplies and re-checks the listings behind it.
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 checks and re-checks the listings those workflow tools start from. The people downstream feel the difference.
Care coordinatorsspend less of their day calling numbers that no longer work. The listing they start from shows when and how it was checked.
Community health workersYour best community health worker keeps her own list, because she's learned which numbers to trust. That knowledge shouldn't have to live in one person's notebook.
Contact center operatorsspend less time apologizing to callers for numbers that don't work.
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 answerEach listing records its current tier, the method used, and the date it was checked.
- 02Standards
Will the data flow into our existing referral platform without translation loss?
CommonLight answerRecords follow the HSDS v3.0 schema.
- 03Confidence
Can our program set minimum thresholds for the records we act on?
CommonLight answerEach listing carries a confidence level. Partners can set a minimum for the records their workflows use.
- 04Cadence
How often is the data verified, and how do we know when it changes?
CommonLight answerListings are checked again on a schedule, more often for urgent services.
Is your organization listed?
We check the information, we don't grade your program. The confidence level shows how sure we are about the details, not how good your services are. If something about your listing is wrong, write to hello@wearecommonlight.com.
Where to go from here.
Start with the resource list you use today.
We review the resource list you use today and show you which listings look solid, which look out of date, and where information is incomplete.
Talk with us →ComplianceCA DHCS scoping call.
DHCS has actively monitored closed-loop referral compliance since July 2026. We help with the resource-listing side of that work.
Talk with us →Fit conversationTalk to our team.
A fit conversation. We'll tell you whether your use case is something we can support today, on the roadmap, or out of scope.
Talk with us →