About this preview
Every screen in these walkthroughs is a prototype with synthetic data: a proposal for how RingMD would run Medi-Cal eligibility review as one accountable workflow, drawn with fictitious people, offices, employers and figures. Nothing here is presented as a live installation.
What you are looking at
Six narrated walkthroughs, one per proof point. Each step shows a prototype screen with a caption (what is on screen) and a note (why it matters). The screens follow the RingMD product's layout and the proposed Care-Cali tenant theme. Where a screen depends on a decision the program has not made yet, the assumption is listed below.
Assumptions, stated as proposed
What is real and what is simulated
Every screen is a static prototype with synthetic people, employers, addresses and figures. Source lookups (Federal Data Services Hub, MEDS, IEVS, CalHEERS, CalSAWS, Truv), rules results and downstream acknowledgments are labelled fixtures returned by simulated adapters. No live system was queried and no enrollment or service authorization was performed.
Agency-approved interfaces, mappings, owners and write permissions are decided in the operating agreement.
Static screens, not a running prototype
This library is captured from static pages, one per state. Buttons and forms depict the proposed workflow; they do not change shared state, and there is no reset or failure control. Playbook acceptance check A10 (reset, working core actions) is therefore not met by this asset; A1 to A9 are shown as depicted behavior.
A working shared-state prototype is the next build once the scope is approved.
Jurisdiction and assisted service
Fresno County appears as the administering county; its offices, units, staff and phone numbers here are fictitious. An assisted-service center operates guided intake, contact updates and the applicant help line. Eligibility actions are recorded only by county roles.
The program confirms the county, the agency and program names, and the solicitation identifier to use.
Applicant experience
The applicant side is a phone browser page opened from a text link, signed in with the phone number on file and a one-time text code. Uploads use the browser file picker or camera. Reminders are text messages and BenefitsCal messages; notifications carry no eligibility detail.
Approved channels, authentication, languages and accessible formats come from the program owner.
Rules, clocks and calculations
Income normalization on screen uses a versioned demonstration rule fixture (MC-INC-2026.3) with its inputs visible. The 45-day clock is shown per application; 90 days applies only when disability or blindness must be established. Official eligibility calculation remains with CalHEERS and CalSAWS.
Production rules, clock exclusions and calendar handling are configured from approved policy.
Notices
Notice templates are demonstration templates labelled 'demo v0.3 · prototype', shown beside a plain-language companion. The companion never replaces or reinterprets the controlled notice.
Production wording, languages, formats and delivery methods require the authorized program owner's specification.
Integrity review
Flags are named by their signal and carry evidence, benign explanations and a next owner. No probability or score appears. A flag alone never approves, denies, discontinues or freezes coverage; the eligibility worker records any processing step separately.
Signal definitions and the review operating model are agreed with the county's program integrity function.
Approval status
This is RingMD's proposed demonstration scope, built from the Care-Cali Workflow document and RingMD's Demo Approval Playbook. The playbook is not yet approved, and the six proof points come from the program's request, not from a published solicitation. The solicitation identifier is unverified.
The approval sheet fixes the scope, the opportunity reference and any edits.
Access to sources
Production access to the Hub, MEDS, IEVS, CalHEERS, CalSAWS or Truv may run only through existing authorized agency interfaces with a permitted purpose. The workspace does not assume direct access to every named source, and source availability is a dependency, not a given.
Permitted access, purpose and source availability are agreed with each agency.
Applicant privacy and household visibility
Maria, as the applicant who filed for the household, sees the status of every member on the application, including Rosa's pending review; Rosa receives her own letters in her own language and format. Phone-number recovery requires an identity check with an agent. Session length and any second factor are not decided.
Household visibility rules and authentication are decided with the program's privacy and security review.
Records and downstream owners
The imaging or case-journal repository, retention and write-back arrangements are not specified. Downstream owners shown (state enrollment broker, state card issuance) and their endpoints are depicted assignments, not agreed operations.
Repository, retention and downstream ownership are confirmed in the operating agreement.
Fixture limits
Extraction values and confidence scores are precomputed; matching and integrity behavior are illustrated, not measured. Queue totals on the supervisor dashboard are stated counts; the 11-row filtered subset is the part that reconciles with its export. Evidence due dates (09-24, 09-26) fall after the application's day 45 (09-21); the clock is shown as it stands and no extension is implied.
Accuracy, false-positive rates and processing times are measured in a pilot, not in this asset.
Deferred from this asset
The two roadmap previews in the playbook (policy-change rehearsal and coverage-continuity watch), live call assistance, evidence reuse and capacity analytics are not shown.
Scheduled after the core scope is approved.
Who is signed in
The top-right corner of every worker, agent and supervisor screen names the signed-in user, their role, and their unit. Applicant phone screens have no header; the caption says they are Maria's. Walkthroughs switch between people as the work moves, and the caption says whose screen it is when the person changes.
| Walkthrough | People whose screens appear |
|---|---|
| 01 · One consolidated workflow | Gloria Sandoval (intake clerk), Priya Venkataraman (assisted service agent), Denise Okonkwo (eligibility worker), Fresno County, 2026-09-14, with the match review from 2026-08-10 |
| 02 · Automated review | Denise Okonkwo, eligibility worker, Fresno County Eligibility Unit 4, 2026-09-14 and 2026-09-16 |
| 03 · Applicant follow-up | Denise Okonkwo (eligibility worker), Maria Lopez (applicant, phone), Priya Venkataraman (assisted service agent), Gloria Sandoval (intake clerk), 2026-09-14 to 2026-09-16 |
| 04 · Possible fraud flags | Denise Okonkwo (eligibility worker) and Marcus Hale (program integrity reviewer), Fresno County, 2026-09-16 |
| 05 · Caseworker action | Denise Okonkwo (eligibility worker), Priya Venkataraman (assisted service agent, blocked action), Maria Lopez (applicant view), 2026-09-14 to 2026-09-18 |
| 06 · Tracking through completion | Denise Okonkwo (eligibility worker) and Raymond Castillo (eligibility supervisor), Fresno County Eligibility Unit 4, 2026-09-16 and 2026-09-18 |