Data & Integration
About Us
Reliable care requires reliable funding. Washington will align dollars with outcomes, equity, and continuity so programs can deliver timely help in every region.
Purpose
Create a shared data backbone that supports closed-loop navigation, shared care plans, and real-time queue health. Use standard interfaces and clear consent so the right people see the right information at the right time.
What success looks like
Seamless handoffs
Referrals, handoffs, and care plans connect across providers without retyping.
Live access metrics
Time to first kept appointment and 7-day follow up visible by region and pathway.
Family portal
Families can see and update their plan through a simple portal or mobile view.
Community-ready
Community and Tribal partners can contribute data without heavy systems or cost.
Public results
Public dashboards show results that are easy to understand.
Today’s gaps
Multiple forms, duplicate entry, and dead-end handoffs.
No simple way to confirm that a referral led to a kept appointment.
Care plans that do not travel across settings or payers.
Fragmented technical standards and slow data sharing agreements.
Limited access for smaller community and Tribal providers.
Six-month targets
Minimum data sets
55% of providers configured (110/200).
Scope: referrals • handoffs • shared care plansStandard consent live
6/10 top languages published.
Plain-talk versions & renewal rulesAPI connections
40% priority endpoints active.
Queue views for teams
9/20 navigation teams live.
Real-time time-to-connection & backlogsTime-to-connection trend
Median days (lower is better)Closed-loop ≤48h trend
% confirmed within 48 hours (higher is better)Core strategies
Build a shared, privacy-first backbone that connects referrals, handoffs, and care plans; makes the queue visible; and includes every partner from day one.
Standardize the essentials
Publish a statewide data dictionary for referrals, handoffs, care plans, and outcomes.
Define unique person, episode, and organization IDs across systems.
Set validation rules so data is complete and useful at the point of entry.
Build lightweight connections first
Use simple, secure APIs and flat file options to include small providers quickly.
Start with event notifications for referral sent, handoff confirmed, and appointment kept.
Add deeper exchange only where it improves decisions or family experience.
Share care plans with consent
Use a single, lightweight plan template that follows the family.
Capture consent once and honor it across settings with role-based access.
Give families a portal view with the ability to update goals and contacts.
Make the queue visible
Standard views that show new referrals, age of items, and stalls by reason.
Weekly huddles use the same views to unblock cases and move people forward.
Region readouts highlight bottlenecks and wins.
Privacy by design
Minimum necessary data, clear purpose statements, and short retention where possible.
Encryption in transit and at rest, with access logs and regular audits.
Simple, fast data sharing agreements that protect rights and enable care.
Include every partner
No-cost submission routes for community and Tribal providers.
Mobile-friendly forms and text-based confirmations for low-tech environments.
Training and office hours for setup, testing, and troubleshooting.
Technical approach
Common data elements
Version control and change logs.
Open APIs
Referrals, handoffs, and care plans.
Event streams
Status changes without full integration.
Provider directory
Hours, modalities, and contact points.
Secure identity & roles
Staff, partner, and family access management.
Measures we will publish
Closed-loop ≤48 hours
68% confirmed within 48h.
Time to first kept appointment
25% faster than baseline.
Median days (lower is better)7-day follow up
57% contact within 7 days.
Referrals with complete MDS
Share of providers on standard interfaces
Family experience
74% “easy to get/share info”.
Top-box %; higher is betterAll measures disaggregated by race, language, disability, geography, and payer.
Equity commitments
Translate consent and notices into top regional languages in plain talk.
Fund community and Tribal partners to design forms and test usability.
Provide low-cost options for connectivity and devices where needed.
Track and close gaps in access to portal features and shared care plans.
30–60–90 day plan
Days 1 to 30
Finalize minimum data sets and data dictionary.
Approve consent model and plain-language versions.
Stand up a sandbox with example payloads and test tools.
Days 31 to 60
Connect two high-volume partners per pilot region through the API or flat files.
Launch queue views for navigation teams and begin weekly unblock huddles.
Train frontline staff on referral and handoff status updates.
Days 61 to 90
Expand connections to school, primary care, and stabilization partners.
Release family portal view for shared care plans in pilots.
Publish the first public data update with measures and lessons.
Governance and roles
Data Lead owns standards, security, and release management.
Integration Lead supports partners, monitors throughput, and resolves errors.
Equity Lead reviews consent, language access, and portal usability.
Regional Coalitions select first connections and run unblock huddles.
Community & Tribal Partners co-design forms and validate experience.
Privacy Officer ensures compliance and responds to concerns.
Risk management
Security incidents mitigated with least-privilege access, audits, and rapid response plans.
Integration delays reduced by offering flat file and API options with clear specs.
Data quality drift managed through validation at entry and routine health checks.
Equity drift countered with translated materials, outreach, and public gap tracking.
What we will not do
Collect data that does not change decisions or improve experience.
Launch pilots without a path to scale and support.
Require expensive technology for participation.
Share information without clear consent or purpose.
Phase gate to reliability
We advance when regions show:
Stable closed-loop rates and improved time to connection.
Shared care plans used across settings with family access.
Majority of high-volume providers connected through standard interfaces.
Community and Tribal partners confirm the data experience is working and worth scaling.
The commitment
Data will serve people. We will connect the system with simple standards, respectful consent, and tools that reduce work. Families will not repeat their story. Providers will see what they need. Leaders will steer with clear measures in public.
