The verified resource layer your referral program assumes exists.
The continuously verified knowledge graph of community resources HIEs, MCOs, and public health agencies build closed-loop referral programs on top of.
If your closed-loop referral program depends on a resource directory that nobody has audited, that audit is the project we run.
A scoped audit of your current 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.
Closed-loop referral programs don't fail at the workflow. They fail at the data underneath.
Most teams scoping a closed-loop referral program assume the resource directory is the easy part. It is the part that breaks the implementation.
Records arrive scattered across 211 lists, county directories, MCO files, and CBO spreadsheets. No Org → Facility → Service hierarchy. No provenance. No way to answer when a record was last verified, by whom, or against what source. Every record looks equally trustworthy on paper, and none of them are.
The referral didn't fail because the workflow tool failed. It failed because the record it acted on was wrong, stale, or structurally incompatible with closed-loop reporting.
That is the layer we operate on.
Data infrastructure for community resources.
The layer your referral platform, MCO operations team, or public health system reads from. Not a workflow tool — the records the workflow acts on, made real, current, and structurally sound.
Tiered verification.
Every facility is classified by the urgency of its most critical service. T1 covers immediate-response services like crisis hotlines; T4 covers routine services like support groups. The classification determines how strictly each field gets validated — the most consequential fields on the most urgent records receive human review; the least consequential fields on routine records receive automated approval. A wrong phone number at a crisis center has different consequences than a wrong description on a support group listing. The validation reflects that.
Resource Confidence Score.
Every record scored across completeness, validity, freshness, and provenance. Exposed in the API and sortable at query time. Set minimum thresholds; stop treating every entry as equally trustworthy.
Native, not retrofitted.
Built on HSDS v3.0 from the schema up. Org, Facility, and Service hierarchies preserved end to end. Live across nine endpoints. Payloads flow into existing referral pipes without translation loss.
Verification on cadence.
Verified on a defined cadence, not scraped once and stored. Diff reports surface what changed, when, and against which source — scoped to the geographies and categories the SOW defines.
The pipeline, in four stages.
- 01
Ingest
211 directories, public records, partner data, primary outreach. Source and timestamp stamped on every record.
- 02
Validate
HSDS v3.0 schema enforcement. Structural integrity checks. Duplicates resolved at the Org and Facility levels.
- 03
Verify
Tiered methodology applied by record class, freshness, and the confidence target. Every tier transition is logged.
- 04
Deliver
REST API with HSDS-compliant payloads. Webhook diffs. Partner-scoped endpoints, access controls per SOW.
Built for the teams running closed-loop programs.
Health information exchanges.
A verified resource layer your closed-loop programs can govern, audit, and trust at the record level. Confidence, provenance, and tier metadata flow into your existing reporting.
Medicaid managed care organizations.
Defensible compliance with closed-loop mandates, including CA DHCS effective July 1, 2025. Every referral target carries provenance and a confidence score that holds up under audit.
County and state public health agencies.
One trusted source across programs. Replaces parallel spreadsheet directories with a single governed graph.
CIE and CBO networks.
A shared substrate so member organizations stop maintaining the same records in parallel. Update once, propagate everywhere.
What changes when the data layer holds up.
When the records underneath your referral program are sound, the program runs differently.
Implementations stop slipping at the data hand-off. Compliance reviewers can trace any referral target back to a verification record with a date, a source, and a method. Closed-loop reporting reflects what actually happened in the field, not what the directory claimed was true. Conversations with your workflow vendor stop being about why referrals are failing and start being about how to scale what is working.
The data layer rarely gets credit when things go well. It almost always gets blamed when they don't. We make sure it holds up to the diligence the program will eventually face.
For programs operating under CA DHCS, HEDIS-related quality measures, or any state-level closed-loop mandate, this is the layer auditors will eventually examine. We make sure that examination goes well.
We are not a referral application.
CommonLight sits underneath the tools your team already uses. We don't compete with workflow vendors. We strengthen the records they depend on.
- →Case management and navigation
- →Closed-loop referral tracking
- →User interface and workflow logic
- →Reporting and analytics surfaces
- →End-user experience
- →The verified resource graph
- →Tiered verification methodology
- →Per-record confidence scoring
- →HSDS v3.0 schema fidelity
- →Continuous verification cadence
Your team picks the workflow. We make sure the records it acts on are real.
Scoping a CA DHCS closed-loop deployment for the 2025 mandate? The resource layer is where most implementations get stuck. Talk to us before you sign.
Built for the diligence buyers actually run.
- HSDS v3.0 · live across nine endpoints
- 211 HSIS taxonomy alignment
- HIPAA-aligned architecture
- Security review packet on request
- NinePatch
- Additional partners on request
Where to go from here.
Network Integrity Report.
Request a report →A scoped audit of your existing resource directory. We run your data against the HSDS v3.0 schema, our T1 — T4 verification rubric, and the fields closed-loop reporting actually requires. The report tells you what is sound, what is stale, what is structurally incompatible, and where the gaps will show up at audit time.
Most teams come back to us with a directory that looks fine on the surface and breaks under examination. The report makes that examination concrete before the implementation does.
Talk to our team.
Thirty minutes. We'll tell you whether your use case is something we can support today, on the roadmap, or out of scope.
Email partners →ComplianceCA DHCS scoping call.
Scoping a closed-loop deployment for the 2025 mandate? Talk to us before you sign.
Scope the layer →PilotPilot inquiry.
For teams ready to scope a deployment. Includes the SOW template and the data exchange checklist.
Start pilot scoping →
The verified resource layer underneath closed-loop referral programs.