HealthcareCheck

Dialysis patient navigation that captures KDQOL-36 on cadence, runs SIPAT for transplant candidacy, and closes the loop on transportation.

CMS-required KDQOL-36 + SIPAT-aligned pre-transplant psychosocial workflow + Zarit caregiver burden + transportation closed-loop + 48-hour white-label deploy. Built by a clinician who ran dialysis social work programs and watched the transportation referral fail in real time.

Where the pathway breaks — and how we close it

KDQOL-36 quarterly capture under CMS ESRD QIP

The Kidney Disease Quality of Life Short Form is the CMS-required quality-of-life instrument for the End-Stage Renal Disease Quality Incentive Program. The capture is required; the capture rate at the floor is wide. Forms are printed in clinic, completed inconsistently across the chair time, lost in a binder, transcribed late, and almost never trended longitudinally for the social worker or the medical director.

~40%industry-reported capture rate for paper-administered KDQOL-36 in standard dialysis workflowscite

Cost when unaddressed: An uncaptured KDQOL-36 is a quality-measure exposure. A captured-but-untrended KDQOL-36 is a clinical outcome the social worker cannot act on.

Patient-app KDQOL-36 with quarterly auto-cadence and longitudinal trend

KDQOL-36 is administered on the patient's phone or tablet on a quarterly cadence the clinic configures. The instrument is scored against the published Hays et al normative standards. Results land in the provider dashboard immediately, are trended per patient, and are exportable for ESRD QIP submission. Threshold drops route a dashboard alert to the social worker assigned to that patient.

90%+in-app capture rate observed in comparable digital instrument workflows; quarterly auto-served and longitudinally trendedcite
Before~40%paper-administered KDQOL-36 capturecite
After90%+ + trendedpatient-app capture, quarterly cadence, per-patient longitudinal trend, threshold-drop alert routing
Impact on kdqol-36 quarterly capture under cms esrd qipMethodology →

SIPAT-aligned pre-transplant psychosocial documentation

Transplant candidacy review depends on a psychosocial assessment that touches readiness, social support, psychological stability, and lifestyle. The Stanford Integrated Psychosocial Assessment for Transplantation is the most-cited published instrument for that work. In the dialysis-to-transplant referral pipeline the assessment is most often assembled manually — paper notes, EHR free-text, transcribed conversations — and the candidacy packet that reaches the transplant center is incomplete or inconsistent across patients.

Manual + free-textindustry-default workflow for pre-transplant psychosocial documentation in dialysis-program referral packetscite

Cost when unaddressed: An incomplete SIPAT packet means a delayed transplant evaluation. A delayed evaluation means dialysis chairs filled longer and waitlist time accumulated.

SIPAT-domain digital workflow with caregiver and adherence anchors

The platform administers a SIPAT-aligned instrument set covering the four published domains: patient readiness and illness management, social support system, psychological stability, lifestyle and effects of substance use. Caregiver burden (Zarit Short Form) and adherence anchors are administered alongside on a configurable schedule. The completed packet exports as a structured artifact the social worker reviews before forwarding to the transplant center.

Structured + exportableSIPAT-domain packet generated from app-administered instruments; caregiver burden and adherence trended longitudinallycite
BeforeFree-text + papermanually compiled candidacy packetcite
AfterSIPAT-domain structureddigital instrument set with longitudinal caregiver and adherence anchors
Impact on sipat-aligned pre-transplant psychosocial documentationMethodology →

Transportation barrier detection before the missed dialysis appointment

Transportation is the single most-cited cause of dialysis non-adherence — three appointments per week, lifelong, and a transportation gap shows up first as a missed session. The standard workflow is reactive: the chair is empty, the social worker calls, the pattern is documented after the hospitalization. The screen for transportation either does not run on cadence or runs in a paper packet that is filed without a referral being matched.

Reactiveindustry-default — missed-session phone-tag rather than pre-empted transportation screencite

Cost when unaddressed: A missed dialysis session for a transportation reason is a preventable hospitalization that bills as an emergency. The cost is patient harm and is also program economics.

Transportation SDOH screen + 691K-resource match + 30-day closed-loop tracking

The transportation domain runs on the cadence the clinic configures. A positive screen routes the social worker to the matched community transportation resources for that patient — filtered by accepted insurance and geographic catchment from a 691,000+ verified-resource catalog — and generates an AI-drafted outreach. Every outbound referral generates a FHIR R4 ServiceRequest with a 30-day closure window and a dashboard alert if the patient has not connected within the configured threshold.

Pre-emptedtransportation gap surfaced before the missed appointment; closed-loop confirmation tracked to 30-day windowcite
BeforeReactivemissed-session phone-tagcite
AfterPre-empted + closed-loopFHIR R4 ServiceRequest with 30-day closure window and dashboard threshold alertcite
Impact on transportation barrier detection before the missed dialysis appointmentMethodology →

Zarit Caregiver Burden measurement on a clinical cadence

Caregiver collapse is a leading-but-invisible driver of dialysis non-adherence and transplant ineligibility. Family caregivers absorb the schedule, the dietary discipline, the medication management, the transportation. The Zarit Burden Interview Short Form is a validated twelve-item instrument with two decades of evidence. In standard dialysis workflows it is not measured until the caregiver has visibly broken down — and by then the data point is a crisis, not a trend.

Rarely measuredindustry-default — Zarit administration triggered by visible caregiver breakdown rather than scheduled cadencecite

Cost when unaddressed: An unmeasured caregiver burden becomes a missed appointment, a medication lapse, a transplant candidacy denial. The intervention point is two to four weeks earlier than the crisis presents.

Zarit Short Form on configurable clinical cadence with threshold pathway

Zarit Burden Short Form is administered to the family caregiver on the clinic-configured cadence. Threshold scores trigger a documented hand-off pathway — caregiver respite, support-group referral, family-systems consult — and the trend is visible to the social worker per patient family unit so the intervention rate is itself measurable.

Trended + threshold-routedZarit administered on cadence; intervention rate quarterly-measurable per patient family unitcite
BeforeCrisis-onlyZarit captured after visible breakdowncite
AfterCadenced + threshold pathwayintervention rate measurable per quarter
Impact on zarit caregiver burden measurement on a clinical cadenceMethodology →

Post-transplant immunosuppression adherence between clinic visits

Graft survival depends on immunosuppression adherence. The check-in for adherence almost always lives at the clinic visit — a snapshot, in a chair, with a clinician across the desk. Between visits the adherence picture is invisible to the program, and a missed-medication pattern that the patient does not report is a graft event the program learns about late.

Visit-only check-insindustry-default — adherence assessed at scheduled clinic visits with limited between-visit signalcite

Cost when unaddressed: Between-visit non-adherence is a graft-loss exposure. Late detection is a transplant program metric and a patient harm at the same time.

Patient-app adherence cadence with caregiver-burden re-assessment

Post-transplant adherence prompts run on the patient app on the program's configured cadence. Caregiver burden is re-assessed alongside on the same schedule because adherence and caregiver capacity track closely. A missed-prompt pattern routes a dashboard alert to the assigned coordinator before the next clinic visit.

Continuous + pairedpatient-app adherence prompts paired with caregiver re-assessment; pattern alerts route before next visitcite
BeforeVisit-onlysnapshot in cliniccite
AfterContinuous + pairedbetween-visit cadence with caregiver-burden anchor
Impact on post-transplant immunosuppression adherence between clinic visitsMethodology →

PHQ-9 depression screening for ESRD with mortality-anchored follow-up

Depression prevalence in dialysis populations is approximately three to five times the general-population baseline. Meta-analyses associate untreated depression in ESRD with elevated mortality risk. PHQ-9 is the standard screen. In the dialysis workflow PHQ-9 is administered inconsistently, the score that signals safety risk is reviewed late, and the follow-up plan that the screen is supposed to trigger is documented narratively rather than structurally.

Inconsistent + delayedindustry-default — PHQ-9 captured but follow-up plan documentation runs through narrative free-text rather than a structured taskcite

Cost when unaddressed: A positive PHQ-9 without a documented follow-up plan is a quality-measure failure and a patient-safety exposure simultaneously.

PHQ-9 cadenced administration with safety-plan trigger and documented follow-up

PHQ-9 is administered on the patient app on the program-configured cadence. A positive screen — score at or above the clinical threshold — opens a structured follow-up task in the dashboard. Item-9 endorsement triggers a safety-planning workflow inline with the screen. Every follow-up is documented as a structured artifact rather than free-text.

Structured follow-uppositive PHQ-9 opens a documented follow-up task; item-9 endorsement triggers safety planningcite
BeforeFree-textnarrative documentation of follow-up plancite
AfterStructured + safety-routedfollow-up task + safety-planning trigger on item-9 endorsementcite
Impact on phq-9 depression screening for esrd with mortality-anchored follow-upMethodology →

BAA chain defensibility on a PHI-touching dialysis psychosocial workflow

Dialysis programs operate inside the HIPAA technical safeguard rule and inside CMS-aligned audit pathways. A psychosocial-screening workflow that runs across a hosting provider, a database, an AI inference layer, an SMS provider, and an email provider needs an executed Business Associate Agreement at every PHI-touching subprocessor — not just at the clinic-vendor boundary. Standard procurement asks for a vendor BAA and stops. The subprocessor chain is opaque to the program.

Vendor BAA onlyindustry-default — clinic-vendor BAA executed; subprocessor chain less commonly documented or publishedcite

Cost when unaddressed: An undocumented subprocessor BAA is the audit finding the program does not want during an OCR review or a CMS validation. Tier-4 willful-neglect penalty exposure is not theoretical.

Published, weekly-verified BAA chain with subprocessor list

The Business Associate Agreement chain is published to the compliance page with named subprocessors: AWS for hosting and pgcrypto encryption at rest, Google Cloud Vertex AI for clinical inference, the SMS provider, the email provider, the database host. The chain is verified on a weekly cadence under the same HIPAA gate ritual that runs across every program in the deployment.

Published + verified weeklyexecuted BAA chain visible on compliance page, weekly verification cadencecite
BeforeOpaquesubprocessor chain undocumentedcite
AfterPublishedweekly-verified subprocessor BAA listcite
Impact on baa chain defensibility on a phi-touching dialysis psychosocial workflowMethodology →

Methodology

How we measure

A KDQOL-36 capture counts when the instrument is delivered on the configured quarterly cadence, completed by the patient or completed-by-proxy with documented reason, scored against the Hays et al normative standards, and stored in the patient record with a timestamp. A closed-loop referral counts when four conditions are met: (1) a FHIR R4 ServiceRequest issued with a destination identifier and a clinical reason; (2) an electronic acknowledgment from the destination community-based organization or transplant center within 7 days; (3) a scheduled appointment write-back from the destination within 14 days OR a documented patient-outreach attempt with timestamped follow-up if the destination cannot confirm; (4) a closure status update — completed, declined, lost-to-follow-up — within 30 days of issuance. A SIPAT packet counts when all four published SIPAT domains have at least one current instrument or structured documentation captured within the program-configured candidacy window.

What counts

  • FHIR R4 ServiceRequest issued with destination, clinical reason, and program identifier
  • Electronic acknowledgment from receiving CBO or transplant center within 7 days
  • Scheduled appointment write-back within 14 days OR documented patient-outreach attempt with timestamp
  • Closure status update — completed, declined, lost-to-follow-up — within 30 days of issuance
  • KDQOL-36 administered on configured quarterly cadence, scored to Hays et al normative standards
  • SIPAT packet covering all four published domains within candidacy window
  • Zarit Short Form on configured cadence; threshold pathway documented per patient family unit
  • Audit log entry persisted at every state transition with HHS 45 CFR 164.312 alignment

What doesn't count

  • Phone-tag confirmations without timestamped follow-up — the call without the artifact does not count
  • Verbal-only KDQOL-36 capture without scored, stored result
  • Free-text-only follow-up documentation that cannot be queried as a structured task
  • Referrals routed to community-based organizations outside the executed BAA chain
  • Closures recorded after the 30-day window without a documented patient-outreach attempt during the window

How we compare

Sourced from primary citations — not vendor marketing claims.

UsHealthcareCheck (dialysis)vsUnite UsvsFindhelpvsCustom build
Time-to-deploy48 hours (tenant config against live FHIR R4 + Vertex AI + AWS stack)Months (vendor onboarding cycle)Weeks (network configuration)9–18 months (build + HIPAA review)
KDQOL-36 administration on CMS ESRD QIP cadenceciteNative — patient app, quarterly cadence, scored to Hays et al, trended longitudinallyNot the product (referral routing focus)Not the product (resource directory focus)Possible — but you build it
SIPAT-aligned pre-transplant psychosocial workflowciteNative — four-domain digital instrument set + caregiver and adherence anchors + structured packet exportNot the productNot the productPossible — but you build it
Zarit Caregiver Burden cadenced administrationciteNative — clinic-configured cadence + threshold pathway + intervention-rate trendNot the productNot the productPossible — but you build it
Closed-loop referral measurement (transportation + SDOH)citeFHIR R4 ServiceRequest + 30-day closure window + threshold dashboard alertNetwork-mediated; closure depends on partner integration depthSearch + connect; closure depends on partner reportingPossible — but you build it
PHQ-9 with safety-planning trigger on item-9 endorsementciteNative — structured follow-up task + inline safety-plan workflowNot the productNot the productPossible — but you build it
FHIR R4 native EHR integrationciteYes — every artifact is FHIR R4; athenahealth live, eClinicalWorks dev, Epic + NextGen reachablePartial / network-dependentPartial / network-dependentPossible — but you build it
Executed BAA chain (subprocessor list)citePublished + weekly-verifiedVendor BAA available; subprocessor chain less commonly documentedVendor BAA available; subprocessor chain less commonly documentedYour responsibility to assemble
Patient data ownership / portabilityProgram owns; FHIR R4 export on exit; no trainingNetwork-mediatedDirectory-mediatedProgram owns (you built it)
Built byLCSW with dialysis social work background — fourteen years across thirteen clinical settingsTech founder + healthcare advisorsTech founder + healthcare advisorsYour in-house team

Frequently asked questions

Is KDQOL-36 administration included for ESRD QIP submission?
Yes. The CMS-required Kidney Disease Quality of Life Short Form is administered through the patient app on the quarterly cadence the program configures. Results are scored against the Hays et al normative standards, trended per patient longitudinally, surfaced to the social worker and the medical director, and exportable for ESRD Quality Incentive Program submission. Threshold drops route a dashboard alert to the assigned social worker.

Cited:hays-1994-kdqol-validation

How does the platform handle pre-transplant psychosocial documentation for transplant candidacy review?
The platform administers a SIPAT-aligned instrument set covering the four published Stanford Integrated Psychosocial Assessment for Transplantation domains: patient readiness and illness management, social support system, psychological stability, lifestyle and effects of substance use. Caregiver burden via the Zarit Short Form and adherence anchors are administered on a configurable schedule alongside SIPAT. The completed candidacy packet exports as a structured artifact the social worker reviews before forwarding to the transplant center.

Cited:maldonado-2012-sipat-validation, bedard-2001-zarit-short-form

How is the transportation referral closed-loop tracked?
The transportation SDOH domain runs on the configured cadence. A positive screen triggers an insurance-aware and geography-aware match against the 691,000+ verified community-resource catalog; the match generates an AI-drafted outreach the coordinator reviews before sending. The outbound referral creates a FHIR R4 ServiceRequest with a destination identifier; status updates close the loop within 30 days or a dashboard alert routes if the patient has not connected within the configured threshold. Closed loop is defined as a four-condition rule documented on the methodology block.

Cited:baker-2021-closed-loop-tobacco, griva-2014-non-adherence-dialysis

What instrument set runs alongside KDQOL-36 and SIPAT?
PHQ-9 with safety-planning trigger on item-9 endorsement, Zarit Burden Short Form on the family caregiver, WEMWBS for positive mental well-being, ISEL-12 for perceived social support, and SDOH screening across the federal domains organized in Healthy People 2030 with the transportation domain anchored for dialysis non-adherence. Every instrument is patient-app administered, scored against the published validation standards, and trended longitudinally per patient.

Cited:kroenke-2001-phq9-validation, odphp-2030-sdoh-framework

Does the platform meet HIPAA technical safeguards for a PHI-touching dialysis workflow?
The platform runs on AWS with executed Business Associate Agreements, encryption at rest via pgcrypto and in transit via TLS, audit logging persisted at every state transition aligned with HHS 45 CFR 164.312 technical safeguards, role-based access, and rate limiting on every endpoint as baseline infrastructure. Clinical inference runs on Google Cloud Vertex AI under an executed BAA. The full subprocessor chain is published on the compliance page and verified on a weekly cadence under the standing HIPAA gate ritual.

Cited:hhs-45-cfr-164-312-technical-safeguards, hhs-2013-omnibus-rule-baa-requirements, ocr-2024-hipaa-enforcement-statistics

How does the platform integrate with the dialysis program's EHR and operational systems?
Every artifact is FHIR R4. athenahealth runs on a live FHIR R4 connection today; eClinicalWorks integration is in active development; Epic and NextGen are reachable through standard FHIR R4 calls. Programs that do not run a FHIR-native EHR can use the dashboard as the primary surface and export structured artifacts on a configured schedule. Tenant subdomain configuration runs against an existing FHIR R4 + Vertex AI + AWS pgcrypto stack — branding, instrument set, KDQOL-36 cadence, SIPAT domain set, transportation catchment, and EHR connection are provisioned through tenant config rather than net-new code.

Cited:hl7-fhir-r4-2019

Founder thesis

Why this exists

Patient navigation should be infrastructure a dialysis program owns — not a vendor relationship that holds the program's psychosocial and transportation data hostage.

— Matthew Sexton, LCSW

I am a Licensed Clinical Social Worker. I worked dialysis social work. I ran the SDOH screening programs. I coordinated the psychosocial evaluations for transplant candidacy. I administered the Zarit Burden Interview to the family caregiver in the chair next to the patient. I wrote the safety plan when PHQ-9 item nine was endorsed at three in the afternoon on a Tuesday during a chair change. I called the transportation provider, and I called again, and I documented the missed appointment in a free-text note that nobody trended.

I built HealthcareCheck for dialysis programs because every program I have walked through tries to solve patient navigation the same two ways and both lose. Build it yourself: nine to eighteen months and a payroll line a medical director cannot defend to the board. Buy a directory tool: thirty days later your transportation referral data is somebody else's product, your KDQOL-36 quarterly capture is still on paper, and your patient is staring at somebody else's logo on a screen.

The closed loop is the unit of work. The KDQOL-36 score on cadence is the unit of accountability. The SIPAT-domain packet is the unit of transplant candidacy. The Zarit threshold trend is the unit of caregiver intervention. The BAA chain is the unit of trust. We measure all five and we publish all five. Patient navigation should be infrastructure a dialysis program owns — not a vendor relationship that holds the program's psychosocial and transportation data hostage. That is the entire pitch.

Matthew Sexton, LCSWFounder · Mental Wealth Solutions Inc.

Citations

  1. usrds-2024-esrd-incidenceSee citations/usrds-2024-esrd-incidence.mdx for primary source, DOI/PMID, and key statistics.
  2. hays-1994-kdqol-validationSee citations/hays-1994-kdqol-validation.mdx for primary source, DOI/PMID, and key statistics.
  3. maldonado-2012-sipat-validationSee citations/maldonado-2012-sipat-validation.mdx for primary source, DOI/PMID, and key statistics.
  4. bedard-2001-zarit-short-formSee citations/bedard-2001-zarit-short-form.mdx for primary source, DOI/PMID, and key statistics.
  5. kroenke-2001-phq9-validationSee citations/kroenke-2001-phq9-validation.mdx for primary source, DOI/PMID, and key statistics.
  6. palmer-2013-prevalence-depression-dialysis-metaSee citations/palmer-2013-prevalence-depression-dialysis-meta.mdx for primary source, DOI/PMID, and key statistics.
  7. chilcot-2018-depression-dialysis-mortalitySee citations/chilcot-2018-depression-dialysis-mortality.mdx for primary source, DOI/PMID, and key statistics.
  8. griva-2014-non-adherence-dialysisSee citations/griva-2014-non-adherence-dialysis.mdx for primary source, DOI/PMID, and key statistics.
  9. chen-2021-immunosuppression-adherence-transplantSee citations/chen-2021-immunosuppression-adherence-transplant.mdx for primary source, DOI/PMID, and key statistics.
  10. jindal-2020-medication-non-adherence-esrdSee citations/jindal-2020-medication-non-adherence-esrd.mdx for primary source, DOI/PMID, and key statistics.
  11. baker-2021-closed-loop-tobaccoSee citations/baker-2021-closed-loop-tobacco.mdx for primary source, DOI/PMID, and key statistics.
  12. hl7-fhir-r4-2019See citations/hl7-fhir-r4-2019.mdx for primary source, DOI/PMID, and key statistics.
  13. hhs-2013-omnibus-rule-baa-requirementsSee citations/hhs-2013-omnibus-rule-baa-requirements.mdx for primary source, DOI/PMID, and key statistics.
  14. hhs-45-cfr-164-312-technical-safeguardsSee citations/hhs-45-cfr-164-312-technical-safeguards.mdx for primary source, DOI/PMID, and key statistics.
  15. ocr-2024-hipaa-enforcement-statisticsSee citations/ocr-2024-hipaa-enforcement-statistics.mdx for primary source, DOI/PMID, and key statistics.
  16. cms-2024-esrd-qip-quality-measuresSee citations/cms-2024-esrd-qip-quality-measures.mdx for primary source, DOI/PMID, and key statistics.
  17. odphp-2030-sdoh-frameworkSee citations/odphp-2030-sdoh-framework.mdx for primary source, DOI/PMID, and key statistics.

Ready to close the gap?