Compliance documentation for closed-loop referrals must prove three things: that a referral was sent, that the receiving party acknowledged and acted on it, and that the individual reached a documented outcome. Funders and regulators are no longer satisfied with service counts. They want evidence of follow-through for each referred individual, with timestamps, status history, and a closure reason on file.
Use this checklist to confirm your program’s funder readiness before the next reporting cycle:
- Structured referral ID assigned at initiation (not a free-text note)
- Individual identifier that links screening, referral, and outcome records
- Referral need domain captured in a coded field (housing, food, transportation, etc.)
- Referring and receiving organization/staff IDs recorded at each handoff
- Timestamps for send, acknowledgment, service start, and closure
- Status-change history with actor ID and timestamp at every transition
- Closure reason documented for every closed referral
- Consent flag confirming the individual agreed to the referral
- Demographic fields (REALD/SOGI where required) for stratification reporting
The Oregon Health Authority (OHA) explicitly recommends moving away from free-text documentation toward structured fields in EHRs and Community Information Exchanges (CIEs) to support automated reporting. WellCheck’s EquiLoop platform is built around this exact data model.
Key Takeaways
Funder-ready compliance documentation requires structured referral records, a resolved status for every individual at period close, and a scheduled export that reports individuals served, not referral counts.
| Point | Details |
|---|---|
| Structured fields are required | Free-text notes cannot be queried; every required field must be coded and captured at initiation. |
| “Pending” must be resolved | Unresolved pending statuses at period close create audit exposure; document a next action or carry forward with a reason. |
| Report individuals, not referrals | Closed-loop completion rate uses individuals with confirmed service as the numerator, not raw referral counts. |
| Validate before you submit | Run a pre-submission check for missing fields, stalled statuses, and demographic completeness at least five days before the deadline. |
| WellCheck EquiLoop | EquiLoop implements this data model, status taxonomy, escalation logic, and scheduled exports for community health programs. |
Table of Contents
- What does your compliance documentation actually need to capture?
- Which referral statuses do funders expect, and how do you resolve “pending”?
- Who owns each step in the referral workflow?
- How should you store and export referral data for an audit?
- What metrics and report formats do funders actually expect?
- How do you get funder-ready in 8–12 weeks?
- What training and SOPs keep your documentation audit-ready?
- What governance failures break compliance documentation?
- WellCheck EquiLoop: Built for This Workflow
- Sources
What does your compliance documentation actually need to capture?
Every referral record in a funder-ready system requires a defined set of structured fields. Free-text notes may supplement a record, but they cannot substitute for coded, queryable data. When an auditor or funder runs a report, they pull structured fields. Anything living only in a notes column is invisible to that query.
The OHA FAQ confirms that referrals documented in structured data fields (such as a referral order in an EHR) enable automated queries for reporting, while free-text entries require manual chart review and introduce completeness gaps.
| Field | Type | Why It Matters for Compliance |
|---|---|---|
| Referral ID | System-generated unique key | Links all status changes to one referral event |
| Individual ID | Coded identifier | Connects screening, referral, and outcome records |
| Screening date | Date | Establishes the timeline baseline |
| Need domain | Controlled vocabulary | Enables stratification by social need category |
| Referring org/staff ID | Coded | Documents accountability at initiation |
| Receiving org/staff ID | Coded | Documents accountability at acceptance |
| Referral modality | Coded (electronic/phone/in-person) | Required for interoperability reporting |
| Send timestamp | DateTime | Starts the timeliness clock |
| Acknowledge timestamp | DateTime | Confirms receipt; required for CLR metrics |
| Service start date | Date | Proves delivery, not just referral |
| Closure date + reason | Date + controlled vocabulary | Completes the closed loop |
| Status-change history | Actor ID + timestamp + status | Immutable audit trail |
| Consent flag | Boolean | Required for data-sharing compliance |
| REALD/SOGI fields | Coded demographic | Required for equity stratification |
Pro Tip: When your EHR lacks one or more of these fields, build a crosswalk to a minimal intermediary CSV export schema. Map each EHR field to its canonical compliance equivalent, document the mapping, and validate it before each reporting submission. That crosswalk becomes part of your policy and procedure documentation.
Which referral statuses do funders expect, and how do you resolve “pending”?
A compact, standardized status taxonomy prevents the most common audit failure: referrals that age in an ambiguous state. The OHA Social Needs Service Coordination Report Guidance specifies that final referral statuses must be recorded as of the reporting period end, and any pending statuses must be updated in a future quarter once resolved.
Required status categories:
- Sent — referral transmitted; awaiting acknowledgment
- Acknowledged/In review — receiving party confirmed receipt
- Accepted — receiving party confirmed they will serve the individual
- Rejected — receiving party cannot serve; reason documented
- Service started — first service contact confirmed
- Service delivered — service completed
- Unable to reach — outreach attempted; individual not contacted
- Member declined — individual opted out after referral
- Pending/Needs client action — awaiting individual response or documentation
- Closed — referral resolved with a documented outcome reason
Map any vendor or EHR status labels to these canonical categories before building your export schema. Mismatched labels are a common source of funder confusion during review.
Escalation cadence: automated alerts should fire at 7, 14, and 30 days for referrals that have not advanced past “Sent” or “Pending.” At 7 days, the assigned care coordinator receives the alert. At 14 days, the CBO contact is notified. At 30 days, the program manager reviews the referral in a weekly exceptions queue and documents a next action or closure reason.
Pro Tip: Treat “Pending” as a monitored state with a hard deadline. If a referral remains pending at the close of a reporting period, carry it forward with a documented reason and a scheduled next action. An unresolved pending status at period close is an audit exposure, not a neutral placeholder.
Who owns each step in the referral workflow?
Consistent documentation depends on clear role assignments at every handoff. The workflow below maps responsibilities from screening through closure.
- Screening — MA or clinician administers SDoH screen; records results in structured fields; flags identified needs.
- Referral initiation — Referring care coordinator creates the referral record, assigns need domain, selects receiving organization, and sets send timestamp.
- Send and acknowledgment — Platform or staff transmits referral; receiving CBO staff acknowledges within 1 business day per SFHP closed-loop referral standards.
- Care navigation/outreach — Navigator or CHW contacts the individual, documents outreach attempts, and updates status.
- Service start — Receiving CBO staff records service start date and attaches confirmation (authorization, RTF receipt, or service record).
- Closure — Care coordinator or CBO staff records closure date and reason; program manager reviews for completeness.
- Reporting — Program manager runs scheduled export; validates completeness; submits to funder.
Routine documentation tasks by cadence:
- Weekly: Program manager reviews exceptions queue (unresolved pending, no-acknowledgment alerts); care coordinators update status on all active referrals.
- Monthly: Reconciliation report comparing referrals sent vs. acknowledged vs. closed; data steward flags missing fields.
- Quarterly: Full export validated against funder schema; demographic completeness checked; OHA SNSC submission prepared within 45 calendar days of quarter-end.
How should you store and export referral data for an audit?
Storage and export architecture determines whether your program can answer a funder’s question in hours or days. The OHA playbook recommends CIE platforms and EHR integration to automate reporting and reduce manual chart review.
Practical options, in order of audit reliability:
- Native EHR structured fields with a referral module — highest reliability when fields map directly to the required data model.
- CIE platform (such as a statewide or regional health information exchange) — supports automated status updates and RTF returns from CBOs.
- Vendor API — enables real-time status sync between the referring organization and the receiving CBO.
- Scheduled CSV/RTF exports — acceptable when structured correctly; require a canonical export schema and a validation step before submission.
- Intermediary population-health tables — useful for aggregating data across multiple EHRs or partner systems.
All exports must meet HIPAA security requirements: secure SFTP or API token authentication, encryption in transit and at rest, and access logging. The audit trail itself must be immutable: timestamps, actor IDs, and status-change history cannot be edited after the fact.
Pro Tip: Schedule a validation script to run automatically before each reporting submission. The script should flag any record missing a required field, any referral with no status update in 30 days, and any demographic field with a null value. Fix those records before the export reaches the funder.
What metrics and report formats do funders actually expect?
The core metric funders use is the closed-loop completion rate: the share of referred individuals who received at least one service within a defined time window (commonly 30 days). The unit of measure is individuals, not referrals. Reporting raw referral counts instead of individual-level linkage is one of the most common reasons programs receive funder pushback.
| Metric | Definition |
|---|---|
| Closed-loop completion rate | Individuals with confirmed service ÷ individuals referred |
| Median time to acknowledgment | Median days from send timestamp to acknowledge timestamp |
| % acknowledged within 1 business day | Share of referrals acknowledged within 1 business day |
| % with service started within 30 days | Share of referred individuals with a service start date within 30 days |
| Data completeness rate | Share of required fields populated across all referral records |
A sample quarterly report should include: total individuals screened, total referred, counts by status (Sent, Accepted, Service delivered, Closed, Pending), timeliness distribution (0–7 days, 8–14 days, 15–30 days, 30+ days), and demographic stratification by REALD/SOGI fields. OHA requires quarterly SNSC submissions within 45 calendar days of quarter-end, with final statuses as of the reporting period close.
In one rural health hub deployment with a multi-partner ecosystem, EquiLoop supported 22,682 individuals screened, 45,458 services delivered, and a 93.9% closed-loop completion rate.*
Rural health hub deployment with a multi-partner ecosystem. Includes both clinical and social services referrals.
How do you get funder-ready in 8–12 weeks?
A phased approach keeps the project scoped and prevents the common failure of building too much before validating data quality.
- Phase 0 (Week 1): Discovery. Map your partner network, document current referral fields, identify reporting requirements from each funder, and inventory existing EHR or platform capabilities.
- Phase 1 (Weeks 2–4): Configure. Add or map structured fields, build the canonical export schema, configure status taxonomy, and establish data-sharing agreements with CBO partners.
- Phase 2 (Weeks 5–7): Pilot. Run live referrals through the new workflow; identify missing fields and data quality gaps; adjust escalation rules.
- Phase 3 (Weeks 8–9): Validate. Run the validation script against a full sample; confirm demographic completeness; schedule automated exports.
- Phase 4 (Weeks 10–12): Submit and monitor. Submit the first reporting cycle; document any exceptions; establish the ongoing reconciliation cadence.
Minimum staffing: a part-time program manager (0.2–0.5 FTE) to own the project, an IT or integration lead for EHR field mapping and API configuration, and one or two care coordinators for reconciliation during the pilot phase.
Artifacts to produce before go-live: canonical export schema, status taxonomy mapping document, automated validation rules, scheduled export configuration, and role-specific SOPs.
What training and SOPs keep your documentation audit-ready?
Documentation accuracy degrades without structured training and written procedures. Role-based SOPs should cover: how to record a referral in the system of record, rules for updating status at each handoff, when and how to escalate a stalled referral, how to attach supporting evidence (authorization, RTF receipt, service confirmation), and how to run and interpret a reconciliation report.
Training plan components:
- Onboarding module for all staff who touch referral records (MAs, CHWs, care coordinators, CBO partners).
- Role-specific modules covering the exact fields and status transitions each role is responsible for.
- Quarterly refreshers tied to reporting cycle reviews; update content when the status taxonomy or export schema changes.
- Completion tracking maintained in a training log; required before staff are granted edit access to referral records.
WellCheck’s Workforce Development Academy provides a white-labeled LMS for CHW, navigator, and care-coordination workforce training and credentialing, with completion tracking built in.
Pro Tip: Tie competency checks to data quality KPIs. If a staff member’s referral records show a missing-field rate above your threshold, require a targeted refresher before they resume full documentation access. This creates a direct feedback loop between training and data quality.
What governance failures break compliance documentation?
Most audit exposures trace back to three governance gaps: no designated data steward, no pre-submission validation, and no process for resolving pending statuses before period close.
Governance requirements:
- Designate a data steward responsible for the status taxonomy, export schema, and change approvals.
- Weekly exceptions queue reviewed by the program manager; every stalled referral gets a documented next action.
- Monthly reconciliation comparing referrals sent vs. closed; flag mismatched timestamps and missing closure reasons.
- Quarterly audit of demographic completeness and data completeness rate before submission.
Common red flags that trigger funder pushback:
- Referral counts reported instead of individual-level linkage metrics
- Free-text-only referrals with no structured fields
- Unresolved “Pending” statuses at period close with no documented reason
- Missing consent flags or closure reasons
- Demographic fields with high null rates that prevent required stratification
- Status-change history absent or editable after the fact
Pro Tip: Run a pre-submission validation report that checks every required field, flags referrals with no status update in the current period, and counts unresolved pending statuses. Share that report with your data steward and program manager at least five business days before the submission deadline.
WellCheck EquiLoop: Built for This Workflow
If your program is building this infrastructure from scratch, or retrofitting it onto a system that was never designed for closed-loop accountability, EquiLoop addresses the specific gaps this playbook describes.
EquiLoop implements the minimum data model, status taxonomy, automated escalation alerts, and scheduled funder-ready exports described above. It is configured around your existing partner network and reporting requirements, not a generic template. The EquiLoop workflow covers SDoH screening through referral closure, with immutable status-change history and demographic fields built into every record. For workforce readiness, the Workforce Development Academy provides role-based training modules with completion tracking.
In a rural health hub deployment with a multi-partner ecosystem, WellCheck supported 22,682 individuals screened, 45,458 services delivered, and a 93.9% closed-loop completion rate.*
Rural health hub deployment with a multi-partner ecosystem. Includes both clinical and social services referrals.
Schedule a 30-minute demo at Calendly to walk through how EquiLoop maps to your funder’s reporting schema.
Sources
The following documents shaped this playbook and are the primary references program leaders should consult when validating local reporting requirements.
- Closed Loop Referral Q&A (SFHP)
- SDOH Screening and Referral Metric: Learning Collaborative Playbook (OHA, 2025)
- Health-Related Social Needs EPT Rubric (PopHealth Learning Center, 2026)
