Where the pathway breaks — and how we close it
Multi-call sales motion replaces clinical fit
Every patient-navigation vendor sells the same way: SDR call, qualification script, sales engineer hand-off, junior account executive who books a follow-up call. Three call layers later, the people who understand the workflow have been replaced by the people who understand the contract. Clinical directors lose two months in qualification rituals before the first useful conversation.
Cost when unaddressed: Eighteen-month vendor cycles waste clinical-director time. The signature on the contract arrives long after the operational urgency has passed.
First call is the call
The 30-minute discovery call is with Matthew Sexton, LCSW, NATC directly — founder, architect, and practicing clinician. Vertical fit, BAA scope, white-label requirements, engagement terms, and go-live timeline are scoped in one sitting. No SDR, no qualification scripts, no sales engineer hand-off, no junior AE booking the next call.
Tenant-specific BAA negotiation drags every deploy
Most patient-navigation vendors require new tenants to negotiate cloud-vendor BAAs from scratch. The Vertex AI BAA, the AWS BAA, the database-vendor BAA — each is a separate paperwork cycle. Two of three weeks of every deploy go to BAA paperwork that does not produce a single clinical workflow.
Cost when unaddressed: Every tenant repeats the same legal review. The BAA paperwork outpaces the clinical workflow. Patients are not enrolled until the lawyers finish.
Inherited BAA chain at provisioning
Mental Wealth Solutions operates under one executed Vertex AI BAA + one executed AWS BAA + one RDS Postgres database with pgcrypto encryption at rest. Every tenant inherits the full BAA chain at provisioning. No tenant-specific BAA negotiation with cloud vendors. PHI never leaves BAA-covered infrastructure.
Forked-CSS white-label is a six-week design sprint
Most vendors deliver white-labeling as a forked CSS bundle — every tenant gets a separate stylesheet branch, every brand change is a code deploy, every typo is a six-week ticket queue. The white-label promise becomes a maintenance liability that the vendor charges to the tenant on month thirteen.
Cost when unaddressed: Tenants pay for re-branding three times — at deploy, at refresh, at vendor renewal. Brand drift between deploys is the rule, not the exception.
White-label as configuration, not code branch
Tenant brand — logo, color palette, vanity domain, copy variants — lives as configuration data, not as forked CSS. The same UI renders three brand skins from three configuration rows. Branding intake at hour 4 of the 48-hour clock is a form, not a design sprint.
Quality-measure capture stitched manually at quarter-end
CCBHC, FQHC, dialysis, and transplant programs already use the screening instruments — C-SSRS, PHQ-9, SDOH 10-domain, UDS, KDQOL-36, SIPAT. The instrument is not the gap. The gap is the closure-of-loop tracking that makes a referral or a screening score actionable. Most programs capture the data manually across three systems and stitch the report together at quarter-end.
Cost when unaddressed: Quarter-end is the discovery moment for missing referral closures. By then the patient has been lost for ninety days.
Closed-loop referral as default
Every HealthcareCheck tenant gets closed-loop referral capture out of the box — referral creation, completion confirmation, follow-up automation, audit trail. CMS quality measures and HRSA UDS reporting plug into the same data structure. No tenant builds it themselves.
Crisis routing is opt-in vendor add-on
Most patient-navigation vendors treat crisis safety as an add-on module. PHQ-9 item 9 fires positive — and the vendor charges for the safety-planning workflow. C-SSRS captures suicidal ideation — and the escalation path is a phone number on a paper handout. Stanley & Brown 2018 demonstrated that safety planning plus structured 24-72 hour follow-up reduced subsequent self-harm roughly 45 percent versus usual care. That outcome is the baseline, not the upsell.
988 + Stanley-Brown safety planning baseline
Every PHI-touching surface ships with 988 single-tap, Stanley-Brown safety planning embedded in the workflow, escalation paths to LCSW backstop coverage, and audit-logged crisis-event triggers. Tenants do not opt into crisis safety — they opt out only via documented program-specific exception.
Pre-deploy HIPAA gate is a one-time audit
Most vendors run a HIPAA gate at deploy and never run it again. Six months later the encryption-at-rest configuration has drifted. Audit-log integrity has not been verified. Backup posture has not been tested. The next discovery moment is the breach notification.
Cost when unaddressed: Configuration drift is the silent failure mode. Vendors discover the gap at the post-incident review, not in advance.
Weekly HIPAA gate ritual
Pre-deploy HIPAA gate runs every Wednesday across all PHI-touching tenants — BAA inventory check, technical-safeguard automated test suite (current baseline 43 PASS / 0 WARN / 0 FAIL), encryption-at-rest verification, audit-log integrity check, BCP/DR posture verification per 45 CFR 164.312. Failure on any gate blocks Thursday production deploys for that tenant.
Methodology
How we measure
The 48-hour HealthcareCheck deploy clock is decomposed into seven discrete checkpoints — discovery call complete (hour 0), tenant BAA addendum executed (hour 2), branding intake captured (hour 4), DNS provisioned with Vercel SSL auto-provisioned (hour 8), tenant turn-up with database row + pgcrypto encryption keys (hour 16), tenant admin walkthrough + quality-measure dashboard configuration (hour 24), and patient enrollment ready (hour 48). The clock is measured wall-clock from BAA execution to first patient enrollment, not engineering hours. TransplantCheck deploys (2-4 weeks) reflect SIPAT and KDQOL-36 calibration to the receiving program's clinical thresholds per the Maldonado 2012 instrument and the Chen 2016 dialysis-cohort validation. EAPCheck deploys (1-3 weeks) reflect HRIS feed schema variance across employers. CoachesCheck deploys (1 week) reflect bespoke quote scoping. Industry baselines reference ONC 2024 HTI-1 Final Rule procurement timelines and FDA 2022 software-medical-device guidance.
What counts
- HealthcareCheck white-label tenants on 48-hour clock from BAA execution
- TransplantCheck program deploys on 2-4 week clock for SIPAT + KDQOL-36 calibration
- EAPCheck B2B2C deploys on 1-3 week clock for HRIS feed schema configuration
- CoachesCheck bespoke deploys on 1 week clock from quote signature
- Wednesday weekly HIPAA gate covers all live PHI-touching tenants
What doesn't count
- Custom EHR integration work scoped beyond FHIR R4 / HL7v2 baseline (timeline scoped during discovery)
- Vanity-domain DNS provisioned by tenant on tenant's own registrar (DNS hand-off scoped at hour 4)
- Third-party billing or e-prescribing integrations requiring separate vendor BAAs (scoped during discovery)
- Bring-your-own-LLM requests (gated by partner BAA execution — not on 48-hour path)
- Crisis-routing opt-out exceptions (documented program-specific exception only)
How we compare
Sourced from primary citations — not vendor marketing claims.
| Us Mental Wealth Solutions | vs Unite Us / Findhelp | vs Generic CCBHC vendor | vs Hospital EHR module | |
|---|---|---|---|---|
| First-call decision-maker | Founder LCSW, 30-min discovery, scoped engagement same call | SDR + sales engineer hand-off, 3+ calls | AE + product manager, 4+ calls | Vendor relationship manager, internal procurement queue |
| White-label deploy timeline cite | 48 hours for HealthcareCheck tenants | 6-9 months | 3-6 months | 9-18 months |
| BAA chain inherited at provisioning cite | Vertex AI + AWS + RDS pgcrypto — inherited day one | Tenant-specific BAA negotiation | Tenant-specific BAA negotiation | Inherited from hospital — depends on facility |
| Closed-loop referral as default cite | Out of the box — referral, confirmation, follow-up, audit | Referral capture only — closure manual | Variable — depends on add-on modules | EHR-dependent — usually no automated closure |
| Crisis routing default cite | 988 + Stanley-Brown safety planning + LCSW backstop on every PHI surface | Add-on module | Phone number handout | Inherited from hospital protocol |
| HIPAA gate cadence cite | Weekly — 43 PASS / 0 WARN / 0 FAIL baseline | Annual | Annual | Hospital-cycle dependent |
| Founder credibility | Built and operated by Matthew Sexton, LCSW — practicing clinician | Vendor sales team | Vendor sales team | EHR vendor — no clinician at the table |
Frequently asked questions
- How long does a tenant take to deploy?
- White-label HealthcareCheck tenants deploy in 48 hours from BAA execution — DNS at hour 8, tenant row turn-up at hour 16, admin onboarding at hour 24, first patient enrollment at hour 48. Other verticals deploy on the timeline scoped during the discovery call: TransplantCheck takes 2-4 weeks because SIPAT and KDQOL-36 instrument calibration must be tuned to the receiving program's clinical thresholds; EAPCheck takes 1-3 weeks because HRIS feed schemas vary across employers; CoachesCheck takes 1 week after the bespoke quote is signed. Industry norm for comparable patient-navigation infrastructure runs six to nine months — the 48-hour clock is the architecture, not a sales claim.
Cited: onc-2024-hti-1-final-rule , google-cloud-2024-vertex-ai-baa , maldonado-2012-sipat-validation
- What happens on the 30-minute discovery call?
- The call covers five things in sequence: technical fit (does your vertical match a deployable HealthcareCheck tenant or does it need bespoke scoping), BAA scope (which BAA-covered infrastructure your tenant inherits, what your existing BAAs cover, where the gaps sit), white-label requirements (logo, color palette, vanity domain, copy variants, mobile app brand if applicable), engagement terms (founding-customer LOI for HealthcareCheck tenants or scoped statement of work for bespoke verticals), and go-live timeline (the 48-hour clock for white-label or the calibrated timeline for transplant/EAP/coaching). The call is with Matthew Sexton, LCSW directly. No SDR, no qualification scripts, no sales engineer hand-off, no junior account executive who books a follow-up call to talk to the actual decision-maker.
- Do I need an existing BAA with my cloud provider?
- No. The platform operates under executed BAAs with Google Cloud (Vertex AI for the Gemini model family that powers patient-navigation AI) and Amazon Web Services (for compute, RDS Postgres database with pgcrypto encryption at rest, and S3 storage for audit logs and document vault). Your tenant inherits the full BAA chain from day one — there is no tenant-specific BAA negotiation with cloud vendors and no waiting period for paperwork to clear before patients can be enrolled. PHI never leaves BAA-covered infrastructure. If your organization already has BAAs with other vendors (your EHR, your e-prescribing platform, your billing clearinghouse), those BAAs are scoped to your existing data flows; the HealthcareCheck tenant operates as an additional BAA-covered system that interoperates with your stack via FHIR R4 and HL7v2 exchanges.
Cited: google-cloud-2024-vertex-ai-baa , aws-2024-hipaa-eligible-services , hhs-45-cfr-164-312-technical-safeguards
- Can I bring my own LLM provider?
- Not today. Production runs Google Gemini exclusively under the executed Vertex AI BAA — no Anthropic, no OpenAI, no Bedrock multi-model, no Azure OpenAI. Bring-your-own-LLM is on the roadmap and gated by partner BAA execution; until a vendor-specific BAA lands, that vendor cannot touch PHI on this platform. The model selection question matters less than most prospective tenants assume: closed-loop referral capture, quality-measure reporting, and audit-log integrity all run on database and application logic rather than on LLM inference. The LLM layer handles patient-facing conversational navigation and clinical-decision-support summarization, both of which are outcome-equivalent across the major frontier models for the populations served.
- What if I am a coach or a non-clinical practice?
- Coaching practices are quoted bespoke under the CoachesCheck vertical. Every coaching engagement carries different scope (single-coach side practice vs multi-coach group practice vs corporate coaching contract), different liability profile (coaches are not licensed clinicians, so the engagement always includes LCSW backstop coverage as a liability shield against the predictable risk of a client decompensating mid-engagement), and different white-label requirements. Quotes are scoped during the 30-minute discovery call. There is no published coaching tier and no self-serve coaching checkout — every coaching tenant is configured and priced individually because the unit economics of a coaching practice differ materially from the unit economics of a CCBHC, an FQHC, or a transplant program.
Cited: icf-2020-code-of-ethics , apa-2018-coaching-vs-psychotherapy-distinction
- How is crisis safety handled across all tenants?
- Crisis routing is always-on across every PHI-touching surface. PHQ-9 item 9 thresholds and C-SSRS suicidal-ideation flags trigger Stanley-Brown safety planning embedded in the workflow with 24-72 hour clinical follow-up. Stanley & Brown 2018 demonstrated that safety planning plus structured follow-up reduced subsequent self-harm by roughly 45 percent versus usual care. 988 single-tap and after-hours warm-line lookup are present at every patient touchpoint. LCSW backstop coverage handles escalation paths for coaches, EAP utilization spikes, and transplant pre-listing crisis events. Tenants do not opt into crisis safety — they opt out only via documented program-specific exception with executive sign-off.
Cited: stanley-2018-safety-planning-ed-cohort , brown-2005-safety-plan-cohort
Why this exists
The first call is the call. The 48-hour deploy is the architecture, not a sales claim.
Every patient-navigation platform I have ever evaluated — Unite Us, Findhelp, the custom-built CCBHC referral systems, the generic EAP vendors — sells the same way. SDR call, qualification script, sales engineer hand-off, three-week procurement cycle, six-to-nine-month deploy, and a vendor relationship that holds your data hostage at the end. That sales motion is the failure, not the implementation. By the time a clinical director has been routed through three call layers, the people who actually understand the workflow have been replaced by the people who understand the contract.
I built Mental Wealth Solutions to run the engagement the way a clinical referral runs: direct, scoped, and outcome-anchored. The first call is the call. I am the founder, the LCSW behind the clinical frameworks, and the architect of the platform. I will tell you in 30 minutes whether your vertical fits the 48-hour HealthcareCheck path, fits the bespoke TransplantCheck or EAPCheck or CoachesCheck path, or does not fit at all. If it does not fit, I will tell you what does — even if it is a competitor.
The 48-hour HealthcareCheck deploy is not a marketing claim. It is a consequence of building tenant-first infrastructure under BAA before vendor, gate before ship, patient before product. The same discipline that makes a closed-loop referral complete in seven days makes a tenant turn-up complete in two. Matthew Sexton, LCSW, PLLC — the clinical practice — is itself the first HealthcareCheck tenant in production. If the platform cannot run my own clinical practice cleanly, I will not sell it to anyone else's. The PLLC pays for every line of code that ships, every BAA the vendors execute, every weekly Wednesday HIPAA gate that runs against production. That is the discipline of a practitioner who pays for the platform with the same clinical fees that fund his own family. Buyers feel that discipline on the first call.
Matthew Sexton, LCSW Founder · Mental Wealth Solutions Inc.
Citations
- (2024). HIPAA Compliance on Google Cloud — Business Associate Agreement and Covered Services. Google Cloud.
Source
- Google Cloud offers Business Associate Agreement (BAA) coverage for Vertex AI services including Gemini API (text-bison, gemini-pro, gemini-1.5-pro, gemini-1.5-flash) — establishing HIPAA-compliant LLM infrastructure for covered entities and business associates.
- BAA-covered Vertex AI services include: Gemini API for text generation, Embeddings API, Vector Search, Vertex AI Pipelines, Vertex AI Workbench, AutoML, Model Registry, Model Monitoring, and Endpoints — comprehensive ML/AI infrastructure for HIPAA-regulated workflows.
- Established the BAA-covered LLM cloud infrastructure baseline that enables HIPAA-compliant deployment of large-language-model clinical applications without requiring on-premise model hosting — key infrastructure enabling cloud-native HIPAA AI architecture.
“Google Cloud Vertex AI BAA coverage includes the full Gemini API family plus Embeddings, Vector Search, AutoML, and Model Endpoints — establishing the BAA-covered LLM cloud infrastructure baseline for HIPAA-compliant clinical AI deployment.”
- (2024). HIPAA Eligible Services Reference. Amazon Web Services.
Source
- AWS HIPAA Eligible Services Reference documents the comprehensive list of AWS services covered under the AWS BAA — currently 175+ services including EC2, RDS, S3, KMS, Lambda, Bedrock, SageMaker, CloudWatch Logs, Systems Manager, and Aurora.
- Critical HIPAA-architecture services for healthcare workloads: RDS (encrypted PostgreSQL/MySQL with pgcrypto), S3 with SSE-KMS encryption, Bedrock for LLM inference (BAA-covered foundation models), Systems Manager Session Manager (CloudTrail-logged session-data S3 archival), and CloudWatch Logs for audit trail.
- Established the AWS BAA-covered services baseline enabling HIPAA-compliant cloud-native architecture for healthcare workloads — key infrastructure enabling HIPAA-compliant deployment without requiring on-premise hosting or self-hosted security infrastructure.
“AWS HIPAA Eligible Services covers 175+ services under BAA including RDS, S3, Bedrock, SageMaker, and Systems Manager Session Manager — establishing the AWS BAA-covered services baseline for HIPAA-compliant cloud-native healthcare architecture.”
- (2013). HIPAA Security Rule — Technical Safeguards (45 CFR § 164.312). Code of Federal Regulations, Title 45 — Public Welfare.
Source
- Mandates access control, audit controls, integrity controls, person-or-entity authentication, and transmission security as technical safeguards for ePHI.
- Encryption and decryption are addressable specifications under access control and transmission security — required unless an alternative measure is documented as equally protective.
- Audit controls require hardware, software, and procedural mechanisms to record and examine activity in systems containing or using ePHI.
“A covered entity or business associate must implement technical policies and procedures for electronic information systems that maintain electronic protected health information to allow access only to those persons or software programs that have been granted access rights.”
- (2024). NIST Special Publication 800-66 Revision 2 — Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule. National Institute of Standards and Technology.
Source
- NIST SP 800-66 Rev. 2 (February 2024) provides authoritative implementation guidance for HIPAA Security Rule technical, administrative, and physical safeguards — referenced by HHS OCR as definitive HIPAA Security Rule implementation reference.
- Establishes detailed technical-safeguards implementation guidance: access control, audit controls, integrity controls, person/entity authentication, transmission security, and encryption — with cross-references to NIST Cybersecurity Framework and NIST SP 800-53 security controls.
- Anchored the federally-recognized HIPAA Security Rule implementation framework — covered entities and business associates following NIST SP 800-66 implementation guidance establish a defensible technical-safeguards posture.
“NIST SP 800-66 Rev. 2 provides authoritative HIPAA Security Rule implementation guidance — referenced by HHS OCR as definitive technical-safeguards implementation reference, anchoring federally-recognized HIPAA security architecture.”
- (2013). Modifications to the HIPAA Privacy, Security, Enforcement, and Breach Notification Rules — Omnibus Rule. HHS Office for Civil Rights.
Source
- HHS HIPAA Omnibus Rule (effective March 2013) implementing HITECH Act provisions — established business-associate direct liability for HIPAA violations, expanded breach notification requirements, and updated marketing/fundraising restrictions.
- Established that business associates (including health-IT vendors and cloud-service providers handling ePHI) are directly liable for HIPAA Security Rule and Breach Notification Rule violations — extending HIPAA enforcement to the entire ePHI handling chain rather than only covered entities.
- Anchored the modern HIPAA enforcement framework: covered entities and business associates each carry direct compliance obligations, with Business Associate Agreements (BAAs) as the contractual instrument establishing the compliance chain.
“The 2013 HIPAA Omnibus Rule established business-associate direct liability for HIPAA violations — extending enforcement to the entire ePHI handling chain with Business Associate Agreements as the contractual compliance instrument.”
- (2025). CCBHC Quality Measure Set and Reporting Requirements. U.S. Department of Health and Human Services / CMS.
Source
- CMS-defined quality measure set required for CCBHC participation in the Medicaid Section 223 demonstration and state-option Medicaid CCBHC programs.
- Required measures include depression remission at 12 months, follow-up after hospitalization for mental illness (FUH), screening for clinical depression and follow-up plan, and adherence to antipsychotic medications for schizophrenia.
- Quality-measure performance directly drives CCBHC prospective payment system rate cells and continued certification eligibility.
“CMS quality-measure performance directly drives CCBHC payment rate cells and certification eligibility, making measurement-based care reporting infrastructure a financial as well as clinical requirement.”
- (2024). Uniform Data System Modernization Initiative: Patient-Level Submission Specifications. U.S. Department of Health and Human Services / HRSA.
Source
- HRSA initiative transitioning Section 330 health center reporting from aggregate UDS submission to patient-level UDS+ data submission specifications.
- Patient-level reporting enables more granular quality-measure attribution, longitudinal patient-cohort analysis, and SDOH-domain stratification across the federally funded health center network.
- Establishes the federal data-infrastructure trajectory anchoring next-generation UDS reporting expectations for FQHCs, FQHC look-alikes, and Section 330 grantees.
“HRSA's UDS Modernization Initiative transitions federally funded health centers from aggregate to patient-level reporting, enabling granular quality-measure attribution and SDOH-domain stratification across the Health Center Program.”
- (2024). Health Center Program Uniform Data System (UDS) Data: 2023 Annual Snapshot. U.S. Department of Health and Human Services / HRSA.
Source
- HRSA Health Center Program served approximately 31 million patients across 1,400+ federally funded community health centers and FQHC look-alikes in calendar year 2023.
- Roughly 90% of health center patients have incomes at or below 200% of the federal poverty level and 23% are uninsured, anchoring the safety-net role of the Section 330 program.
- Behavioral health visits at FQHCs grew faster than medical visits over the past decade, reflecting the expansion of integrated behavioral health and SDOH-aware service models.
“HRSA-funded health centers serve 31 million patients annually, with 90 percent at or below 200 percent of the federal poverty level — the largest safety-net primary care infrastructure in the United States.”
- (2024). Health Data, Technology, and Interoperability — Certification Program Updates, Algorithm Transparency, and Information Sharing (HTI-1) Final Rule. HHS ONC.
Source
- ONC HTI-1 Final Rule (January 2024) establishes the first federal regulatory framework for AI/algorithm transparency in certified health IT — including 'Decision Support Interventions' (DSI) certification criteria for predictive AI/machine-learning models embedded in EHRs.
- DSI certification requires source attribute disclosure for predictive models, intervention risk management practices, and feedback mechanism for end users — establishing the baseline transparency requirements for AI-enabled clinical decision support.
- Anchored the regulatory baseline for AI in certified health IT — vendors offering AI/ML-enabled clinical decision support to ONC-certified EHRs must satisfy DSI transparency and risk-management requirements as of January 1, 2025 effective date.
“ONC HTI-1 Final Rule establishes the first federal regulatory framework for AI/algorithm transparency in certified health IT — DSI certification requires source attribute disclosure, intervention risk management, and end-user feedback mechanisms for predictive AI/ML models.”
- (2022). Clinical Decision Support Software — Guidance for Industry and Food and Drug Administration Staff. U.S. Food and Drug Administration.
Source
- FDA Clinical Decision Support Software guidance (September 2022) clarifies which CDS software functions qualify as medical devices subject to FDA regulation under the 21st Century Cures Act.
- FDA-regulated CDS includes software that: provides diagnostic/treatment recommendations not based on transparent rationale clinicians can independently review, processes medical images/signals/patterns, or provides time-critical decisions where clinicians cannot independently review rationale — requiring premarket FDA review.
- Anchored the FDA medical-device regulatory boundary for clinical AI software — AI/ML systems providing autonomous diagnostic/treatment recommendations cross into FDA-regulated medical-device territory, while non-autonomous reference/educational tools remain non-device.
“FDA's CDS Software guidance clarifies the medical-device regulatory boundary for clinical AI — autonomous diagnostic/treatment recommendation systems cross into FDA-regulated medical-device territory, while non-autonomous reference tools remain non-device.”
- (2018). Comparison of the Safety Planning Intervention with follow-up vs usual care of suicidal patients treated in the emergency department. JAMA Psychiatry.
doi:10.1001/jamapsychiatry.2018.1776
- Cohort comparison study of 1,640 suicidal patients across 9 emergency departments comparing the Safety Planning Intervention plus structured follow-up phone outreach with usual care.
- Intervention arm showed a 45% reduction in suicidal behaviors over 6 months compared with the usual-care comparison group.
- Engagement in outpatient mental-health treatment was approximately twice as high in the intervention arm relative to usual care.
“The Safety Planning Intervention combined with structured telephone follow-up was associated with a substantial reduction in suicidal behavior and increased outpatient treatment engagement among emergency-department patients.”
- (2005). Cognitive therapy for the prevention of suicide attempts: a randomized controlled trial. JAMA.
doi:10.1001/jama.294.5.563
- Randomized controlled trial of 120 adults presenting to an urban emergency department after a suicide attempt, comparing 10-session cognitive therapy plus enhanced usual care versus enhanced usual care alone.
- Cognitive therapy reduced repeat suicide attempts by 50% over an 18-month follow-up window (24% reintervention vs 41% usual care, hazard ratio 0.51).
- Anchored the evidence base for brief structured suicide-prevention interventions including the Stanley-Brown Safety Planning Intervention now embedded in CCBHC and ED protocols.
“A brief 10-session cognitive intervention focused on suicide-attempt cognitions cut the rate of repeat suicide attempts in half across an 18-month follow-up window, establishing the evidence base for the structured safety-planning paradigm.”
- (2012). The Stanford Integrated Psychosocial Assessment for Transplantation (SIPAT): a new tool for the psychosocial evaluation of pretransplant candidates. Psychosomatics.
doi:10.1016/j.psym.2011.12.012
- SIPAT incorporates 18 risk items across patient readiness, social support, psychological stability, and lifestyle/effect of substance use.
- Inter-rater reliability among trained raters reached intraclass correlation coefficients above 0.85.
- Higher SIPAT scores at evaluation correlated with worse psychosocial outcomes after transplantation.
“SIPAT provides a standardized psychosocial assessment that minimizes inter-rater variability and operationalizes the previously subjective transplant candidacy decision.”
- (2016). Cross-cultural adaptation and validation of the Chinese version of the Kidney Disease Quality of Life-36 (KDQOL-36). Health and Quality of Life Outcomes.
doi:10.1186/s12955-016-0539-y
- Cross-cultural adaptation and validation of the KDQOL-36 in a Mandarin-speaking population of dialysis patients in Taiwan.
- Internal consistency reliability across the burden, symptoms, and effects-of-kidney-disease subscales exceeded a Cronbach alpha of 0.80.
- Confirms the international applicability of the KDQOL-36 as the standard ESRD-specific health-related quality-of-life instrument required for CMS quality reporting in U.S. dialysis facilities.
“The Chinese version of the Kidney Disease Quality of Life-36 demonstrates acceptable reliability and validity for use in dialysis patients, supporting its cross-cultural applicability for ESRD-specific quality-of-life assessment.”
- (2020). ICF Code of Ethics. International Coaching Federation.
Source
- ICF Code of Ethics establishes professional conduct standards for ICF-credentialed coaches across four sections: Responsibility to Clients, Responsibility to Practice and Performance, Responsibility to Professionalism, and Responsibility to Society.
- Section 4.4 explicitly requires coaches to refer clients to other professionals when issues exceed coaching scope — including mental health concerns requiring clinical intervention — but the Code does NOT require any clinical license, mental-health training, or scope-of-practice credentialing for coaches themselves.
- Established the only widely-adopted coaching profession ethics framework, but with no licensing-board enforcement mechanism — violations result only in ICF membership/credential revocation, not legal consequences.
“ICF Code of Ethics Section 4.4 requires coaches to refer clients to other professionals when issues exceed coaching scope — but the Code does NOT require any clinical license or mental-health training for coaches themselves, leaving scope-judgment to individual coach discretion without licensing-board enforcement.”
- (2018). Society of Consulting Psychology — Distinctions between coaching and psychotherapy. American Psychological Association.
Source
- APA Society of Consulting Psychology guidance distinguishes coaching (focused on present/future goal-attainment in non-clinical populations) from psychotherapy (focused on diagnosis and treatment of mental-health conditions in clinical populations).
- Established scope-of-practice boundary: coaching addresses non-clinical performance/goal-attainment concerns; psychotherapy addresses DSM-diagnosable mental-health conditions requiring licensed clinical intervention.
- Anchored the professional consensus that coaches encountering signs of clinical-mental-health concerns (depression, anxiety disorders, trauma, suicidality) MUST refer to licensed mental-health professionals — coach scope ends where clinical scope begins.
“APA Society of Consulting Psychology established the scope-of-practice boundary — coaching addresses non-clinical performance/goal-attainment concerns, psychotherapy addresses DSM-diagnosable mental-health conditions requiring licensed clinical intervention.”