About this preview
Every screen in these walkthroughs is a Missouri configuration preview: a prototype of how RingMD would be configured for the Missouri Rural Health Transformation Program, drawn with fictitious people, sites, payers, and numbers. Nothing here is presented as a live installation.
What you are looking at
Ten narrated walkthroughs, one per State demonstration question. 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 Missouri tenant theme. Where a screen depends on a decision the program has not made yet, the assumption is listed below.
Assumptions, stated as proposed
Patient experience
The patient side is a browser web app opened from an SMS link. Adding it to the phone's home screen is optional. There is no app-store download in this preview. Readings from the cuff arrive through the hub whether or not the patient opens the app.
Confirm with the program which patient devices and languages the web app must support.
Sign-in for patients
Patients sign in with a one-time code sent by SMS to the phone number recorded at enrollment. Failed-code and lost-phone paths route to the clinic. Session length and any second factor are still to be defined.
Authentication details are decided with the program's security review.
Device kits
Kits shown are a Bluetooth blood pressure cuff with a 4G cellular hub, a cellular scale, and a validated CGM feed. They are supplied through RingMD's device vendor partners. The RFI states that the State funds licensing first and providers assume subscriptions later; who buys the kits, their connectivity plan, replacements, and return shipping is not decided. Those costs are in the rough order of magnitude estimate, not in this demo.
Who buys, ships, and replaces kits is an open program decision, costed in the ROM.
Hub telemetry and store-and-forward
Hub signal, battery, last sync, and queued readings come from the device vendor's hub and cloud. RingMD receives them through the vendor's integration and displays them. Store-and-forward during an outage is hub behaviour; RingMD shows the readings with their original measurement times once they arrive.
Available telemetry depends on the vendor chosen.
Billing boundary
RingMD assembles a claim support packet per patient and per month (coverage review, service lines with evidence, reading calendar, time ledger, signed notes, consents, exclusions, reviewer) and exports it. The practice's billing system assigns codes, submits claims, and posts payments. Reading-day and time rules are configured per payer and service period; the MO HealthNet maternal rule is shown as awaiting verification.
Payer rules are confirmed with MO HealthNet and each commercial payer before go-live.
Telehealth peripherals
Exam cameras that present as USB video devices and digital stethoscopes that present as USB or Bluetooth audio stream through the browser after pairing and permission. PTZ control, ultrasound, and SDK-only devices are integrations, not shown.
Cart make and peripheral list are chosen with each hospital.
Who is signed in
The top-right corner of every screen names the signed-in user, their role, and their site. 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 · Maternal RPM, end to end | Amara Whitfield, 29, postpartum hypertension pathway, Prairie Bend Family Health |
| 02 · Data types and reporting | Amara Whitfield and Kelsey Trammell; site and program dashboards |
| 03 · Clinical rules configuration | Postpartum hypertension pathway, edited by the clinical lead |
| 04 · Rural usability and connectivity | Rosa Delgado (no smartphone, Spanish), Kelsey Trammell (limited broadband) |
| 05 · EHR integration and reporting | Site admin at Prairie Bend Family Health; state program admin |
| 06 · Operations and reimbursement | Dana Okafor, RN monitor; Corey Maddox, billing specialist and site admin |
| 07 · Rural hospital consult, end to end | Dr. Samuel Whitaker, ED physician, and Nia Thompson, RN, cart operator, at Cedar Fork Community Hospital; Dr. Elena Castellanos, tele-neurology, Riverbend Regional Specialist Hub |
| 08 · Specialist routing | Tasha Reyes, clinical operations; the Emergent stroke request |
| 09 · Clinical collaboration | Dr. Castellanos consulting on Walter Jennings with the Cedar Fork ED team |
| 10 · Performance and reimbursement | Tasha Reyes, clinical operations; the Missouri RHTP program office |