Methodist Hub — Feedback & Scoping

How this works: fill in what you can, then tap Copy answers or Email answers at the bottom. Questions with a green number are the ones that most change how (and what) we build — please prioritize those.

The ones that change everything

1Which electronic health record (EHR) do you use?

This single answer drives the entire patient-data side — appointments, insurance/coverage, cost estimates, and "navigate me to my appointment." It determines how we connect (SMART-on-FHIR) and what's possible.

2For wayfinding — do you need a live "blue-dot" at launch, or is "pick your starting point" acceptable first?

Pick-your-start ships fast with zero hardware. A live blue-dot ("you are here" that moves) needs Bluetooth beacons or a Wi-Fi survey of your buildings — a bigger Phase 2.

Pick-your-start is fine to launch — add blue-dot later Live blue-dot is a must-have from day one Not sure — want your recommendation

3Can you provide floor plans, and how big is the campus?

We build the route map from your floor plans (CAD or PDF). Scale tells us the effort.

We have CAD/architectural floor plans We only have PDF / printed maps We have existing Bluetooth beacons or strong Wi-Fi coverage

4Patient data & privacy — how far do you want to go, and who handles compliance?

Showing insurance/appointments means handling PHI. That requires a Business Associate Agreement (BAA) and hardened, HIPAA-grade hosting. We can also launch a fast, PHI-free version first (hub + wayfinding + general helper) with none of that overhead.

Start PHI-free (hub + wayfinding + general AI), add patient data later We want patient data (insurance, appointments) in the first release Not sure — walk us through the trade-off

The patient data, specifically

5Which patient information should the app show? (pick any)

Each one is a separate FHIR data type and may need its own approval.

Insurance / coverage on file Upcoming appointments (+ "navigate me there") Estimated visit cost / copay Care team & provider info Visit prep / instructions Test results / records Bill pay Secure messaging with the care team

6Do patients already use a portal like Methodist My Care today?

If yes, patients can sign in with their existing credentials — we don't create a second login, and you keep the system of record.

The hub & the helper

7What links & departments belong in the hub?

We drafted a starter set (portal, pharmacy, billing, cafeteria, visitor info, telehealth, find-a-doctor). Tell us the real ones, including phone numbers.

8What should the AI helper be able to do — and where are its limits?

It can answer questions, give directions, and (signed in) read a visit. It will not diagnose or triage. Confirm the boundaries and any must-have skills.

Find departments & give directions Hours, parking, visitor policy, FAQs Look up the patient's own appointment / coverage (signed in) Start pre-registration / forms Hand off to a human / call the right desk Multiple languages

Important: should it ever answer clinical/symptom questions, or always redirect those to a nurse line? (We recommend redirect.)

Fit, scale & logistics

9Is this one hospital or a system / multiple campuses?

10Do you use any wayfinding or visitor app today?

e.g. Gozio, an Epic-embedded map, kiosks, or nothing. Move off it, or complement it?

11Branding — logo, colors, and the right name.

We themed the demo in a clinical blue/teal and called it the “Methodist Hub — Wayfinding & Care Companion.” Change anything.

12Timeline — when would you like patients using this?

Open floor

13What did we get wrong, and what's on your wish list?

Anything in the demo that misses the mark, plus features you'd love that we didn't show.

14Who's filling this out?

Copied — paste it into an email or message to us.