The verification layer underneath your closed-loop referral program.
CommonLight ingests resource data from many sources, classifies every facility by service urgency, validates each field against that classification, and delivers HSDS v3.0 compliant records to your workflows through an API.
How the platform works.
CommonLight sits between the sources where resource data lives and the workflows that consume it. Three stages in between: ingest, verify, deliver.
Native schema, currently live across nine endpoints.
Tiered validation by service urgency.
HSDS-compliant payloads, partner-scoped endpoints.
Stricter validation where it matters most.
Not every record needs the same level of scrutiny. A crisis hotline phone number that fails a referral has different consequences than a support group meeting time. CommonLight classifies every facility by the urgency of its most critical service, then applies validation methods to each field based on that classification.
Tier classification feeds a validation matrix. A phone number at a T1 crisis center receives human review. A description at a T4 support group receives automated approval. Every field on every record gets the validation method appropriate to what is at stake if the record is wrong.
Every record carries a score. Programs decide the threshold.
The Resource Confidence Score combines four dimensions into one per-record number: completeness, validity, freshness, and provenance. The score is exposed in the API and sortable at query time.
Closed-loop programs can require a minimum confidence score for any record they act on. Records that fall below threshold are flagged, not deleted. Programs see what is borderline, what is fresh, and what needs re-verification.
How records flow.
Same four stages used across the platform — ingest, validate, verify, deliver.
- 01
Ingest
211 directories, public records, partner data, primary outreach. Source and timestamp stamped on every record.
- 02
Validate
Schema enforcement against HSDS v3.0. Duplicate resolution at the Org and Facility levels.
- 03
Verify
Tiered methodology applied based on facility urgency and field importance. Tier transitions logged.
- 04
Deliver
REST API with HSDS-compliant payloads. Webhook-based diffs. Partner-scoped endpoints.
Wherever your workflow needs it.
Verified records flow into your existing systems through the channels you already use.
- 01API and webhook
- 02EHR and CRM integrations
- 03Care coordination platforms
- 04SMS and mobile workflows
- 05Slack and Teams
- 06Email and partner portals
Two ways to dig deeper.
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 →EngineeringDeveloper documentation.
Schema reference, endpoint documentation, and integration patterns. Gated for technical reviewers evaluating fit; access provisioned per organization and use case.
Request developer documentation →
The verified resource layer underneath closed-loop referral programs.