Community-care patient navigation for veteran programs that closes the CCN loop, screens for MST, tracks moral injury separately from PTSD, and paces suicide prevention in the first thirty days post-deployment.
Structured MST intake + moral-injury care pathway + C-SSRS safety-planning pacing + transportation SDOH closed-loop + CCN referral tracking + 48-hour white-label deploy. Built by a clinician who has watched VA community-care referrals land in inboxes with no structured follow-through.
Where the pathway breaks — and how we close it
CCN referral tracking and closed-loop confirmation
VA Community Care Network referrals to community providers are the federal mechanism for extending veteran care beyond the VA's direct-care footprint. The mechanism generates a referral authorization. It does not generate a closed loop. Community providers receive the authorization, schedule the appointment, render the care — and none of that activity closes back to a structured confirmation in the originating VA record. Coordinators manage the gap with phone calls, fax callbacks, and manual chart notes, all of which create undocumented closure and uncaptured utilization data.
Cost when unaddressed: An open CCN referral is a veteran who may not have made it to the appointment, a program metric that cannot be reported, and a care-coordination gap that becomes visible only after a clinical deterioration.
FHIR R4 ServiceRequest with CCN authorization anchor and 30-day closure window
Every CCN referral authorization generates a FHIR R4 ServiceRequest with the community-provider identifier, the authorization number, a scheduled-appointment write-back pathway, and a status closure window. Coordinators receive a dashboard alert on day ten if acknowledgment has not arrived and a second alert on day twenty-five if closure is not confirmed. A closed loop is defined as a four-condition record: authorization issued, acknowledgment received, appointment confirmed, and closure status updated within thirty days.
Military sexual trauma screening underdetection in community-care settings
Military sexual trauma is a federal mandate — VA screens every enrolled veteran — but the mandate reaches only VA direct-care encounters. Community-care providers receiving CCN referrals are outside the VA screening funnel. MST is underreported by veterans with both male and female military history for reasons of stigma, institutional distrust, and not-knowing-it-counts. A community-care program that does not run a structured MST screen on intake will miss the disclosure that any clinical encounter might be the first chance to surface.
Cost when unaddressed: An undetected MST history is a treatment-planning gap, a trauma-informed-care failure, and a clinical liability at the same time. MST is associated with PTSD, depression, anxiety, substance-use disorder, and suicidal ideation at rates that are substantially elevated above the general veteran population.
Structured MST screening instrument with trauma-informed-care routing at intake
The patient-app intake delivers a structured MST screening item set — aligned with the VA MST screening question and supplementary probes for both sexual harassment and sexual assault during military service — and routes positive screens to a trauma-informed-care pathway flag in the coordinator dashboard. A positive MST flag triggers a structured intake note template for the treating clinician before the first appointment so the clinician does not surface the disclosure in an unstructured first-session context. The MST flag carries through to the CCN referral record and is exportable in the structured packet.
Moral injury care pathway distinct from PTSD
Moral injury — the deep damage from perpetrating, witnessing, or failing to prevent actions that violate deeply held moral beliefs — is clinically distinct from PTSD and responds differently to treatment. PTSD exposure-based protocols that do not differentiate moral injury can produce poor outcomes and early dropout when the presenting clinical picture is moral injury rather than a fear-based response. In standard community-care intake, moral injury is subsumed into the PTSD diagnosis or the veteran does not receive a framework to describe what happened at all. The clinical pathway never branches.
Cost when unaddressed: A veteran receiving PTSD exposure therapy whose primary presentation is moral injury is receiving treatment that the evidence does not support for that clinical picture. Early dropout and treatment non-response are the measurable outcomes.
Moral injury intake screen with Litz/Shay-grounded care-pathway branch
The intake instrument set includes a moral-injury screening module — aligned with Litz et al's moral injury and moral distress framework and Jonathan Shay's moral injury domain distinctions — that flags probable moral injury at intake and routes the coordinator to the appropriate evidence-based care pathway: Adaptive Disclosure Therapy, Spiritual Direction referral, or chaplaincy coordination. The moral-injury flag is independent of the PTSD flag and the two pathways coexist in the clinical record without one subsuming the other.
Suicide prevention pacing in the highest-risk post-deployment window
The first thirty days following separation or return from deployment are the highest-risk window for veteran suicide. The VA/DoD Clinical Practice Guideline for suicide risk management identifies this period as requiring structured risk-stratification and outreach cadence. Community-care providers receiving CCN referrals for newly separating veterans or newly enrolled community-care members often schedule an initial appointment but do not operationalize a structured outreach cadence in the thirty days between enrollment and that first appointment. 83% of individuals who died by suicide had a healthcare contact in the year before their death — most in primary care, not behavioral health — establishing that the window between referral and first clinical contact is where the gap lives.
Cost when unaddressed: A veteran enrolled in community care who does not have a first appointment within fourteen days of referral and does not receive structured outreach in the interim is a veteran in the highest-risk window with no clinical contact. The VA/DoD guideline calls this gap explicitly.
C-SSRS-anchored suicide-risk pacing with structured 30-day post-referral outreach cadence
The platform delivers C-SSRS through the patient app at intake and at the fourteen-day mark in the thirty-day pre-appointment window. A positive C-SSRS — ideation with method or any suicidal behavior — triggers a same-shift safety-planning task and escalated outreach cadence consistent with the VA/DoD CPG and the Stanley/Brown Safety Planning Intervention. Veterans with negative C-SSRS and a scheduled appointment receive a structured check-in message and a lethal-means counseling resource at day seven and day twenty-one. Every outreach attempt is documented as a structured artifact, not a free-text note.
Transportation barrier in rural community-care catchments
Rural veterans face a transportation gap that is both more severe and less visible than the urban equivalent. VA community-care expansion under the MISSION Act was intended to reduce drive time to less than 30 minutes for primary care and 60 minutes for specialty care. The authorization reduces the geographic access barrier on paper; it does not provide a vehicle. Rural community-care providers regularly lose veterans to no-shows driven by transportation failure. The screening for transportation is reactive — a missed appointment triggers a call, not a pre-appointment screen — and the community-resource match for veteran-specific transportation programs (DAV, VFW van programs, Uber Health partnerships) is not embedded in the clinical workflow.
Cost when unaddressed: A missed appointment in a rural community-care setting is harder to reschedule than an urban one. The veteran is already in the highest-utilization window. The program loses the clinical contact and the no-show is documented as administrative attrition, not a transportation failure.
Transportation SDOH screen with veteran-specific resource matching and 30-day closed-loop tracking
The transportation SDOH domain runs on the pre-appointment intake cadence. A positive screen routes the care coordinator to a filtered match against the 691,000+ verified-resource catalog — filtered by veteran-specific transportation programs first (DAV van services, VFW transport, VA Beneficiary Travel Program, Uber Health) before general community resources — and generates an AI-drafted outreach the coordinator reviews before sending. The outbound referral generates a FHIR R4 ServiceRequest with a thirty-day closure window and a dashboard alert if the veteran has not confirmed transportation before the appointment.
VA staff turnover and care-coordination continuity
VA community-care programs and the community providers operating under CCN both face significant staff turnover in care-coordination roles. Social workers, care managers, and intake coordinators change positions. In a workflow built on personal relationships, informal phone-tag protocols, and free-text notes, turnover means care-coordination knowledge lives in the departing coordinator's head rather than in a structured record. A new coordinator inherits no dashboard, no referral status, no outreach history, and no risk stratification. The veteran's navigation continuity resets with every staffing change.
Cost when unaddressed: Turnover is not going to stop. Building a navigation workflow that resets with every transition is a structural problem that requires a structural fix — not a training program.
Role-agnostic dashboard with full referral history and risk-stratification record
Every veteran's referral status, risk stratification, outreach attempt, MST flag, moral-injury pathway, C-SSRS score, and SDOH screening result lives in the dashboard as a structured, searchable record. A new coordinator inheriting a caseload on day one can see every open referral, every pending outreach, every positive screen result, and every documented follow-up without a single phone call to the departing coordinator. The system is role-agnostic — a social worker, a care manager, or a clinical coordinator can pick up where the last person left off because the record is structured, not personal.
Pre-VA eligibility delay and community-care enrollment friction
Veterans separating from service face an eligibility determination window before they can access VA direct care or community-care benefits. The MISSION Act and the Veterans Community Care Program created the community-care pathway to reduce wait times — but the pathway requires an authorization, which requires an enrollment, which requires a determination. A veteran who knows they are eligible for community-care benefits still navigates an eligibility-verification workflow that community-care providers are not equipped to manage. The result is a gap between the veteran's presenting need and the community provider's ability to receive a billable CCN referral.
Cost when unaddressed: A veteran who falls out of the enrollment pipeline before the CCN referral is issued is a veteran who received no care during the highest-risk post-deployment window. The program counts it as a lost lead. The clinical record counts it as no contact.
Streamlined eligibility verification workflow with intake-to-authorization pathway
The platform's intake flow includes a structured eligibility-screening module aligned with the VA Community Care Program criteria: separation date, enrollment status, distance from nearest VA facility, wait-time threshold, and specialty-care need. Veterans who clear the threshold criteria are routed to a coordinator with a pre-populated eligibility summary the coordinator uses to initiate the CCN authorization request. Veterans who need additional eligibility documentation receive a structured checklist in the patient app rather than a verbal instruction from a staff member who may change next week.
Methodology
How we measure
A "completed CCN loop" is the unit of work. HealthcareCheck counts a community-care referral as closed when all four conditions are recorded against a single FHIR R4 ServiceRequest within thirty days of authorization: (a) a ServiceRequest is generated with the community-provider identifier and the CCN authorization number; (b) an acknowledgment is received from the community provider — by electronic write-back, portal confirmation, or documented phone contact with timestamp — within ten days; (c) a scheduled appointment date is confirmed and written back to the ServiceRequest within fourteen days, or a documented patient-outreach attempt is recorded if the veteran cannot be reached; (d) the ServiceRequest status is set to completed, revoked, or entered-in-error within the thirty-day window. Loops exceeding thirty days without a disposition are reported as open and excluded from the closed numerator. A positive C-SSRS is defined as ideation with a method or plan, or any suicidal behavior, at any administration; a positive result triggers a same-shift safety-planning task with documented outreach at twenty-four hours, seventy-two hours, and seven to fourteen days consistent with the VA/DoD Clinical Practice Guideline and the Stanley/Brown Safety Planning Intervention. MST is flagged when one or more MST screening questions yield a positive response; the flag routes to the trauma-informed-care pathway independent of PTSD flag status. Moral injury is flagged when the moral injury intake module identifies a probable moral-injury presentation; the flag is independent of MST and PTSD flags and routes to the Adaptive Disclosure Therapy or chaplaincy coordination pathway. SDOH transportation is flagged when the transportation-domain item yields a positive response; the flag triggers veteran-specific resource matching before general community resources.
What counts
- FHIR R4 ServiceRequest with community-provider identifier and CCN authorization number
- Acknowledgment from community provider within 10 days — electronic, portal, or documented phone contact with timestamp
- Appointment confirmation or documented patient-outreach attempt within 14 days
- Closure status update within 30 days — completed, revoked, or entered-in-error
- C-SSRS administered at intake and at day 14 in the pre-appointment window; positive triggers same-shift SPI + cadenced outreach
- MST screen at intake; positive flag routes to TIC pathway independent of PTSD flag
- Moral injury screen at intake; positive flag routes to Adaptive Disclosure / chaplaincy independent of PTSD pathway
- SDOH transportation domain at pre-appointment intake; positive routes to veteran-specific resource match before general catalog
What doesn't count
- Phone-tag follow-up without a timestamped record — the call without the artifact does not count toward closed-loop
- C-SSRS administered only at the first clinic visit with no pre-appointment digital delivery in the highest-risk window
- MST flag generated only by spontaneous disclosure rather than structured intake screen
- Moral injury presentations subsumed into PTSD diagnostic code without an independent flag and pathway branch
- Transportation referrals to community 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 | vsVA-built tools (VistA/Oracle Health) | vsSalesforce Health Cloud | vsUnite Us | |
|---|---|---|---|---|
| Time-to-deploy for community-care providers | 48 hours (tenant config against live FHIR R4 + Vertex AI + AWS stack) | 6–24 months (VA enterprise build and integration cycle) | 9–18 months (custom Salesforce Health Cloud implementation) | Months (network configuration and onboarding cycle) |
| White-label depth for community-care branding | 100% — patient surface, email, SMS, PDF carry the community provider's brand | VA-branded only — not configurable for community providers | Salesforce-branded or limited customization via Experience Cloud | Unite Us co-branded — vendor surfaces in patient communications |
| MST structured screening at intakecite | Native — MST item set at intake with TIC pathway flag + pre-session clinician note | VA direct-care only — not available to CCN community providers | Not the product | Not the product |
| Moral injury pathway independent from PTSDcite | Native — independent flag and Adaptive Disclosure / chaplaincy pathway branch | VA direct-care specialty programs only — not standard community-care workflow | Possible with custom build — not out of the box | Not the product |
| C-SSRS suicide prevention pacing pre-appointment windowcite | Native — C-SSRS at intake + day 14 + SPI trigger + cadenced outreach + lethal-means resource | VA direct-care only — CCN referral gap is not covered | Possible with clinical workflow configuration — not a default feature | Not the product (social needs referral focus) |
| CCN closed-loop referral trackingcite | FHIR R4 ServiceRequest + authorization anchor + 30-day closure window + dashboard alerts at day 10 and day 25 | VA's CCN Portal tracks authorization status — community provider has limited read-back capability | Possible with Salesforce integration — requires custom development | Social-needs referral loop only; CCN authorization tracking not the product |
| Transportation SDOH with veteran-specific resource matchingcite | Native — pre-appointment SDOH screen + veteran program filter (DAV, VFW, VA Beneficiary Travel) before general catalog + FHIR R4 closed loop | BTRS (Beneficiary Travel) is a separate VA system; no SDOH integration at community-care level | Custom configuration — no veteran-program-first filtering out of the box | Social-needs referral routing — no veteran-specific program prioritization |
| Executed BAA list (subprocessor chain published)cite | Published + weekly-verified — AWS, Vertex AI, pgcrypto, SES all under executed BAAs | VA FISMA ATO covers VA systems — does not extend to community providers' own workflows | Salesforce BAA available; subprocessor chain requires separate HIPAA review | Unite Us BAA available; subprocessor chain less commonly published or verified |
| Built by | LCSW with 14 years across 13 clinical settings — not a tech founder | VA enterprise engineering team | Salesforce professional services and SI partners | Tech founder + healthcare advisors |
Frequently asked questions
- Does this platform meet HIPAA requirements for a VA-affiliated community-care program?
- The platform runs on AWS with executed Business Associate Agreements. Encryption at rest is via pgcrypto; encryption in transit is TLS. Audit logging persists at every state transition aligned with HHS 45 CFR 164.312 technical safeguards. Clinical inference runs on Google Cloud Vertex AI under an executed BAA. The full subprocessor chain — AWS, Vertex AI, the SMS provider, the email provider, the database host — is published on the compliance page and verified on a weekly cadence under the standing HIPAA gate ritual. A mutual BAA is executed with the community-care provider on day one of deployment. VA-affiliated programs under the Community Care Network are covered entities or business associates of covered entities under HIPAA; the BAA chain satisfies both configurations. The platform has never used patient data to train any model. No PHI leaves the BAA-covered infrastructure at any point.
Cited:hhs-2013-hipaa-omnibus-rule, hhs-45-cfr-164-312-technical-safeguards, google-cloud-2024-vertex-ai-baa
- How does the MST screening workflow integrate with the CCN referral record?
- MST screening runs through the patient-app intake before the first community-care appointment. The MST screening item set is aligned with the VA's two-part MST screening question — "While you were in the military, did you ever experience unwanted sexual contact? Were you ever sexually harassed?" — and adds supplementary probes for harassment and assault context consistent with the VA's clinical guidance. A positive response generates a trauma-informed-care pathway flag in the coordinator dashboard. The flag triggers a structured pre-session intake note template so the treating clinician has the disclosure on record before the first appointment rather than surfacing it mid-session without clinical preparation. The MST flag is independent of PTSD and moral-injury flags and is exportable as part of the structured CCN referral packet.
- What is the difference between the moral injury pathway and the PTSD pathway in the platform?
- They are two independent flags in the intake record and two independent care-pathway branches in the coordinator dashboard. The moral injury screening module — aligned with Litz et al's moral injury and moral distress framework and Shay's moral injury domain distinctions — flags a probable moral injury presentation based on the veteran's description of the precipitating event and the nature of the ongoing distress. A positive moral injury flag routes the coordinator to the Adaptive Disclosure Therapy referral pathway, chaplaincy coordination, or spiritual-direction referral — the three evidence-supported pathways for moral injury specifically. The PTSD pathway routes to trauma-focused CBT or Prolonged Exposure as appropriate. The two flags can coexist in the same record. They cannot subsume each other. A veteran can carry both flags and both pathways run concurrently.
- How does the suicide prevention pacing work for newly enrolled community-care veterans?
- C-SSRS is administered through the patient app at intake — before the first community-care appointment — and again at day fourteen in the thirty-day pre-appointment window. A positive C-SSRS at either administration triggers a same-shift safety-planning task, a coordinator-directed outreach, and a cadenced follow-up at twenty-four hours, seventy-two hours, and seven to fourteen days consistent with the VA/DoD Clinical Practice Guideline for Suicide Risk Management and the Stanley/Brown Safety Planning Intervention. Veterans with negative C-SSRS and a scheduled appointment receive a structured check-in message and a lethal-means counseling resource at day seven and day twenty-one. Every outreach attempt is documented as a structured artifact with a timestamp — not a free-text note — so the documentation holds up at audit and survives coordinator turnover. The Stanley 2018 JAMA Psychiatry cohort study across 1,640 suicidal patients at nine emergency departments showed the Safety Planning Intervention plus structured follow-up reduced suicidal behavior by forty-five percent at six months compared with usual care.
Cited:va-dod-2019-suicide-prevention-cpg, stanley-2018-safety-planning-ed-cohort, ahmedani-2014-health-care-contact-suicide, cdc-2024-suicide-mortality
- Does the platform handle the eligibility and CCN authorization workflow for community-care providers?
- The platform includes an eligibility-screening module aligned with the VA Community Care Program criteria: separation date, VA enrollment status, distance from nearest VA facility (less than 30 minutes for primary care, less than 60 minutes for specialty care under MISSION Act standards), access-to-care wait-time threshold, and specialty-care need. Veterans who clear probable-eligibility criteria are routed to a coordinator with a pre-populated eligibility summary the coordinator uses to initiate the CCN authorization request. Veterans who need additional documentation receive a structured checklist in the patient app — not a verbal instruction. The platform does not submit the authorization to VA; it reduces the coordinator's preparation time and reduces the veteran's dropout in the enrollment gap. The actual CCN authorization submission lives in VA's Community Care system; the platform handles the pre-authorization intake, the structured eligibility summary, and the post-authorization closed-loop tracking once the referral is issued.
- How fast can a VA-affiliated community-care program deploy?
- Forty-eight hours to a live tenant subdomain in the standard configuration. The platform runs on an existing FHIR R4 + Vertex AI + AWS pgcrypto stack; a tenant deployment is a configuration job — branding, instrument set selection, CCN referral workflow, MST and moral injury pathway configuration, C-SSRS cadence, SDOH item set, veteran-specific resource catalog filter, BAA execution — not a code-build job. VA-affiliated programs that need EHR integration beyond the FHIR R4 baseline (athenahealth is live; Epic, eClinicalWorks, and the VA's own Cerner-based Oracle Health EHR are reachable through standard FHIR R4 connections) are scoped separately and measured in weeks. The forty-eight-hour clock assumes the BAA is executed on day one and a designated coordinator is available for the configuration session.
Why this exists
Patient navigation should be infrastructure a community-care provider owns — not a VA portal that holds the program's referral and screening data hostage to the next federal IT migration.
I am a Licensed Clinical Social Worker. I have worked in community mental health, forensic assertive community treatment, substance-abuse treatment, dialysis social work, and private practice. I have coordinated care across systems that do not talk to each other and written the safety plan when the system failed to hand off the information the next clinician needed. I have sent referrals and never heard back. I have inherited a caseload from a departing colleague and found a manila folder with a handwritten list of open cases and no status on any of them.
The veteran population carries a specific weight I take seriously. The post-deployment window is not abstract to me. The gaps in MST disclosure, the difference between moral injury and PTSD, the suicide prevention window between enrollment and first appointment — these are not research topics. They are what happens when the system is not built to handle the transition from military to civilian care with the structural specificity that transition requires.
I built HealthcareCheck for community-care programs serving veterans because every program I have walked through faces the same structural problem: the VA issued the referral, the community provider accepted it, and nobody owns the follow-through. The closed loop is the unit of work. The C-SSRS pacing is the unit of safety. The MST flag is the unit of trauma-informed-care integrity. The BAA chain is the unit of trust. We measure all four and we publish all four. Patient navigation should be infrastructure a community-care provider owns — not a VA portal that holds the program's referral and screening data hostage to the next federal IT migration.
Matthew Sexton, LCSWFounder · Mental Wealth Solutions Inc.
Citations
va-dod-2019-suicide-prevention-cpgSeecitations/va-dod-2019-suicide-prevention-cpg.mdxfor primary source, DOI/PMID, and key statistics.ahmedani-2014-health-care-contact-suicideSeecitations/ahmedani-2014-health-care-contact-suicide.mdxfor primary source, DOI/PMID, and key statistics.stanley-2018-safety-planning-ed-cohortSeecitations/stanley-2018-safety-planning-ed-cohort.mdxfor primary source, DOI/PMID, and key statistics.cdc-2024-suicide-mortalitySeecitations/cdc-2024-suicide-mortality.mdxfor primary source, DOI/PMID, and key statistics.baker-2021-closed-loop-tobacco-quitlineSeecitations/baker-2021-closed-loop-tobacco-quitline.mdxfor primary source, DOI/PMID, and key statistics.olson-2025-closed-loop-referral-experienceSeecitations/olson-2025-closed-loop-referral-experience.mdxfor primary source, DOI/PMID, and key statistics.healthy-people-2030-sdohSeecitations/healthy-people-2030-sdoh.mdxfor primary source, DOI/PMID, and key statistics.hhs-2013-hipaa-omnibus-ruleSeecitations/hhs-2013-hipaa-omnibus-rule.mdxfor primary source, DOI/PMID, and key statistics.hhs-45-cfr-164-312-technical-safeguardsSeecitations/hhs-45-cfr-164-312-technical-safeguards.mdxfor primary source, DOI/PMID, and key statistics.google-cloud-2024-vertex-ai-baaSeecitations/google-cloud-2024-vertex-ai-baa.mdxfor primary source, DOI/PMID, and key statistics.posner-2011-cssrs-validationSeecitations/posner-2011-cssrs-validation.mdxfor primary source, DOI/PMID, and key statistics.tjc-2016-sea-56-suicideSeecitations/tjc-2016-sea-56-suicide.mdxfor primary source, DOI/PMID, and key statistics.national-academies-2019-integrating-sdohSeecitations/national-academies-2019-integrating-sdoh.mdxfor primary source, DOI/PMID, and key statistics.cms-2024-sdoh-screening-measureSeecitations/cms-2024-sdoh-screening-measure.mdxfor primary source, DOI/PMID, and key statistics.de-marchis-2019-sdoh-screening-acceptabilitySeecitations/de-marchis-2019-sdoh-screening-acceptability.mdxfor primary source, DOI/PMID, and key statistics.