Ohio configuration preview
About these walkthroughs
These are prototype screens for a proposed Ohio Veterans Navigator for the Ohio Department of Veterans Services (ODVS), in response to RFI SRC0000040307. They are a configuration preview. Nothing shown is live, connected to State, county or federal systems, or endorsed by ODVS. Every person, contact detail, schedule, referral status and figure is fictitious. Real public programs such as VA, OhioMeansJobs, the Veterans Crisis Line and RecoveryRachel appear only as resources, with a source link and a review date. Their schedules and statuses are never invented.
The screens show the full-scope product that RingMD recommends, Path B, the ODVS Accelerated Navigator. It is a separate ODVS platform. One shared set of screens serves all three submitted paths; the Approach page explains what Path A builds new and what Path C defers.
How the walkthroughs map to the RFI
| SOW section | Where it is shown |
|---|---|
| III.1 Intelligent navigation and customer journey engine | Walkthroughs 01, 02 and 05 |
| III.2 Unified statewide resource intelligence database | Walkthroughs 03 and 07 |
| III.3 Adaptive user understanding and flow logic | Walkthroughs 01 and 02 |
| III.4 Matching, recommendation and action engine | Walkthroughs 02, 04 and 06 |
| III.5 A–B Channels, accessibility, governed repository | Walkthroughs 01, 03, 05 and 07 |
| III.5 C–D Vector search, knowledge graph, GraphRAG, agents | Walkthrough 09 |
| III.5 E–F Event stream, integration fabric, identity | Walkthroughs 04, 06, 08 and 10 |
| III.5 G–H Traceability, audit, override, content freshness | Walkthroughs 06, 07 and 09 |
| III.6 Performance, data collection and agency dashboard | Walkthrough 08 |
| III.7 Implementation models; IV.C onboarding | Walkthrough 10 and the Approach page |
What is working, simulated or planned
| Label | Meaning in these screens |
|---|---|
| Working in this preview | The public Navigator, plans, resource records, corrections, referrals, county queue, evidence views, traces and audit are prototype screens built from one set of demo data. |
| Test adapter | OH|ID staff sign-in, the constituent sign-in (a State-approved provider, for example ID.me) and the county referral connection. These stand in for systems that are not connected. |
| Public link | RecoveryRachel, the Veterans Crisis Line, 988, 911, OhioMeansJobs and va.gov. They open as links or local previews. Nothing in the demo calls, texts or submits outside the demo. |
| Planned | Live Power BI refresh, partner and agency data feeds, and SMS, voice and kiosk channels. Each depends on a Phase 0 decision and an ODVS and DAS approval. |
Who is signed in
| Walkthrough | Perspective |
|---|---|
| 01 · Start anonymously, in plain language | Jordan Ellis, transitioning Army service member moving to Franklin County, anonymous, desktop browser, Tuesday 2026-09-29 at 10:02 |
| 02 · A plan that changes with circumstances | Jordan Ellis, anonymous, 10:04 to 10:09 |
| 03 · Trusted resources and how we know | Jordan Ellis, anonymous, after plan version 2 at 10:08; the needs-review example is from Denise Walker's search in Athens County |
| 04 · Save, consent and ask a county office | Jordan Ellis, signing in with a test State-approved sign-in at 10:12, then consenting at 10:13 |
| 05 · Caregivers, rural access and urgent needs | Denise Walker, caregiver in Athens County, on her phone at 09:18; Alex Morgan, veteran in Montgomery County, at 08:47; a controlled safety test at 08:55 |
| 06 · A county office handles the request | Marcus Reed, veterans service officer, Franklin County, signed in with OH|ID (test), 10:40 to 15:40; Tessa Lindqvist, Athens County, for the access test at 15:52 |
| 07 · Keeping resources correct | Carla Nuñez, resource steward, Athens County, and Owen Bishop, resource and policy approver, ODVS, both on OH|ID (test), 09:40 to 11:40; Denise Walker on her phone |
| 08 · ODVS evidence on where people fail to connect | Hannah Cole, performance analyst, ODVS, signed in with OH|ID (test), de-identified data only, 10:30 to 16:00; all figures are synthetic |
| 09 · AI governance and traceability | Owen Bishop, resource and policy approver, ODVS, signed in with OH|ID (test), 2026-09-29 |
| 10 · County onboarding and State control | Renee Kowalski, county onboarding lead, ODVS, and Owen Bishop for the tenant view, both on OH|ID (test); readiness figures are synthetic |
Assumptions behind the screens
Each is a proposed decision to confirm with ODVS and DAS in Phase 0.
| Topic | Proposed decision |
|---|---|
| Hosting and tenancy | Production runs in a separate ODVS tenancy in the State-approved cloud selected with DAS, with its own data, secrets, roles, audit and releases (Paths A and B). The tenant screen shows separation in the demo environment only. No State tenancy has been approved. |
| Identity | General navigation is anonymous. People sign in only to save a plan, share it by consent or request a follow-up, through a State-approved external identity. Staff use OH|ID with MFA, role and county scope, and periodic access review. |
| Consent | Each share names the recipient, purpose, exact fields and duration, and gets a version. Stopping sharing prevents future sharing; it cannot recall records already delivered. |
| County referral workflow | Referrals reach a county office's queue in the Navigator. Where a county keeps its own case system, the connection is agreed per county in Phase 0. A confirmed outcome comes only from the county or partner record. |
| Eligibility | The Navigator shows eligibility indicators only. The agency that runs each benefit makes every eligibility and benefit decision. |
| Resources | ODVS owns the taxonomy and publication policy. County offices and approved organizations steward their records. Changes to controlled fields need a separate approver. Resources outside the vetted list are labeled and routed for review. |
| AI | Only State-approved models are enabled in production. The demo model is marked as needing State review. Crisis presentation and eligibility gates are deterministic rules. The model is not trained on ODVS data without written authorization. |
| Safety | Crisis and emergency information is fixed content that shows without sign-in and without the model. Destinations are reverified before every session. The demo's buttons open previews only. |
| Power BI | The export works with Power BI: fact and dimension tables, certified measures, a data dictionary and lineage. A live Power BI connection with row-level security is planned for the first integration wave. Its timing is set in Phase 0 and it is built during configuration. |
| Figures | All volumes, rates, county counts, referral history and readiness status are synthetic. Readiness means ready for production go-live. Baselines and targets are set in Phase 0. In exports, briefings and published county views, counts under 5 are suppressed under a demo policy; analysts see de-identified journey references. They do not see contact details or conversation text. |
| Channels and languages | The web experience works in any phone or desktop browser. SMS, voice, kiosk and languages beyond English are options decided in Phase 0. |
| Names and real resources | The fictitious organizations are Riverside Career Collaborative, Hillside Access Rides and Southeast Ohio Neighbor Drivers. County office names are generic descriptions. Their hours, phone numbers, accessibility and documents are demo values. Real public resources (OhioMeansJobs, va.gov, the Veterans Crisis Line, RecoveryRachel) are linked and summarized. |
Approach: paths, architecture, governance, stage plan and rollout →
Not shown
Eligibility determinations, benefit applications or claims, appointment booking, county case management beyond the referral, SMS, voice and kiosk screens, languages other than English, a live Power BI report, pricing inside the product.