Patient and public entry
Use the hosted medical landing to explain visits, records, billing help, and next-step guidance before someone ever signs into the runtime.
Medical operations vertical
Give patient/public entry, intake teams, schedulers, care coordinators, patient-support staff, clinicians, and operating leads one shared view of what is arriving, what needs scheduling, what is blocked in referral flow, and what follow-up still needs action.
A config-first promoted vertical pack built on the shared generated dashboard, list, calendar, board, and workflow hosts rather than on a one-off medical app shell.
Audience-led public entry
Use the hosted medical landing to explain visits, records, billing help, and next-step guidance before someone ever signs into the runtime.
Show how registration readiness, arrivals, waitlist recovery, and first-touch routing stay visible from the first operational lane.
Carry doctors, nurses, care coordinators, and referral managers through one explainable scheduling and follow-up rhythm instead of split portals.
Keep staffing, revenue, quality, and connector-health posture tied back to the same medical story rather than hidden in separate admin marketing.
Multiple audiences, one operational picture
Track incoming requests, registration completeness, and triage readiness before the case stalls.
See appointment pressure, availability gaps, and next-bookable work in one schedule-first operating flow.
Move referrals, escalation, and handoff continuity through one explainable workflow and board posture.
Monitor due follow-up, missed touchpoints, and downstream workload before continuity breaks.
Shared medical starter capabilities
See intake readiness, scheduling pressure, referral throughput, care coordination posture, and follow-up workload together.
Run intake review and registration completeness from the shared premium list runtime.
Coordinate appointments and time-based care commitments through the shared scheduling surface.
Move referrals and care handoffs through shared board and workflow primitives instead of a second case app.
Broader medical continuity story
Frame booking, reminder recovery, virtual visit readiness, and remote follow-through as part of the same public and operator journey.
Extend the story into medication, diagnostics, and result escalation without opening a second vertical runtime.
Show how admissions, transfers, discharge blockers, and multi-location load belong in the same hosted medical narrative.
Keep claims, denials, statements, and payer follow-up connected to the patient and operator story instead of hidden behind a finance-only page.
Let operating leads trace quality indicators, staffing pressure, and credential posture from the same vertical landing language.
Bring EMR, lab, imaging, and billing connector visibility into the public story without reviving the stale interoperability control-plane ask.
Continuity without a bespoke stack
Start with one intake lane that keeps registration, readiness, and urgency visible from the beginning.
Move from request to appointment without losing referral and follow-up meaning between teams.
Keep referral movement, coordination work, and escalations on one shared workflow trail.
Turn missed or due continuity signals into the next outreach or care action from the same workspace.
Promoted vertical pack on shared authority.
The vertical is promoted as a governed shared pack, so the same landing/runtime, navigation, and generated workspace seams can keep expanding into richer medical depth later. Preview and publication already live on the shared Config Studio authority before runtime launch, while the public story can keep growing at medical.stbm.app without another microsite stack.