Protect patient access and throughput.
Faster coordination around scheduling, referrals, documentation, and billing helps patients move through the system with fewer avoidable delays.
OpenNash
Prepared for
Munson Healthcare · July 2026
A working hypothesis for Munson Healthcare operations and back-office teams
Give Munson Healthcare's care teams back the hours they lose to scheduling, registration, and back-office follow-up.
Munson Healthcare runs nine hospitals and dozens of clinics across northern Michigan, and its public postings lean heavily on patient access, scheduling, imaging and lab coordination, revenue cycle, and health-information work. OpenNash would take one of those administrative workflows — the repeated registration, documentation, and follow-up that surrounds the care team — and turn it into a reviewed, source-linked workflow in 14 days. To be clear, this is the back-office and coordination work around care, not clinical care, diagnosis, or medical decisions, which stay entirely with your staff.
OpenNash builds custom 24/7 AI agents for customer support, back-office, and operational work. We automate workflows end to end inside the systems your team already uses: secure, auditable, and human-reviewed where it matters.
Engineers who build AI agents that work.
Start with the Zero to Agent guide, then bring one real Munson Healthcare workflow we can map in plain English.
Read Zero to Agent
Built by engineers from GoogleMetaSnowflakeDatabricks
Business thesis
Munson Healthcare makes money when care moves smoothly and patients get the right help sooner.
As northern Michigan's largest health system, Munson's work depends on patient access, scheduling, documentation, billing, and care-team coordination. OpenNash focuses only on the administrative and clinical-support work around the care team — scheduling, registration, revenue cycle, records, and follow-up — not clinical care, diagnosis, or medical decisions, which stay entirely with clinicians. Within that lane, it helps staff prepare the context around repeated administrative exceptions while keeping human review in control.
Munson Healthcare reportsReduce administrative drag.
AI agents can gather chart, message, claim, and scheduling context before staff spend time rebuilding the same packet by hand.
Give care teams cleaner handoffs.
Reviewed packets help nurses, techs, coordinators, and revenue teams handle more work without burying them in follow-up.
What OpenNash is
Reliable, auditable AI workflows for the work that actually runs the business.
We study how your best humans solve hard work, replicate the skill, and build AI agents that automate the repetitive parts while keeping people in control of exceptions, approvals, and judgment calls.
M.01
Time to production: 4-8 weeks
We do the workflow audit, build the agent, connect the tools, write evals, and launch against real operating cases.
M.02
14-day no-charge pilot
Forward-deployed engineers embed with your team, watch the best operators work, and prove one workflow before you commit.
M.03
Built on your software
APIs, CRMs, data warehouses, dashboards, spreadsheets, inboxes, browser-only portals, and legacy systems.
M.04
U.S.-based, on site if useful
We will fly to you, work with the people doing the work, and price the pilot risk so you do not have to.
Zero to Agent
We teach the basics, then build inside your real work.
Step 01
Learn
We explain the pieces in plain English: models, tools, context, approvals, evals, and why reliable agents need more than a prompt.
Step 02
Build
We connect to the tools that finish the work today and replicate the process against real test cases before automation.
Step 03
Launch
Human-in-the-loop review, monitoring, audit logs, recovery paths, and automated tests keep the agent reliable in production.
Evaluations are the difference between a demo and a production workflow. We write test cases for incomplete requests, unusual documents, portal errors, approval paths, and edge cases so the agent can fail safely, ask for help, and improve from real reviewer feedback.
Research snapshot
Where Munson Healthcare appears to be adding people
Munson's visible hiring clusters around general operations and coordination, clinical-support roles that surround the care team, and lab and diagnostic support — the kind of administrative work where context has to move cleanly between people and systems. Read it as a public-data hypothesis, not a staffing plan, until an operator confirms the real workflow.
Open roles reviewed
562
From careers.munsonhealthcare.org and related public postings.
Largest work pattern
283
Clinical or care team support
To a working pilot workflow
14 days
No charge. On-site if useful. Staff approve everything.
562 open roles pulled from careers.munsonhealthcare.org · July 6, 2026
Three problems worth solving
Three problems worth solving.
PATIENT ACCESS & COORDINATION
The scheduling and registration work around every visit should be measured, not manual.
Munson Healthcare is hiring across patient access and coordination, including Patient Access Representative, Sr Scheduler, and Patient Care Coordinator. These roles run the registration, scheduling, and record handoffs that move a patient through a visit — work that today lives in phone calls, portals, and paper.
Our point of view
OpenNash can gather the scheduling, authorization, and prior-record context from existing systems, draft the next administrative step, and show staff exactly why — while every clinical call stays with the care team.
Less manual coordination and a clearer view of where administrative work gets stuck.
“Patient Access Representative”
CLINICAL OR CARE TEAM SUPPORT
The paperwork around clinical handoffs should be prepared before it reaches the care team.
Munson Healthcare has 189 visible open roles in this pattern, including Registered Nurse - Pre/Post Operative / Pre-Admission Testing, Licensed Pharmacy Technician - Nights, and Licensed Pharmacy Technician. Around each of these sits referral, pre-admission, scheduling, and documentation work that has to be assembled by hand today.
Our point of view
OpenNash can assemble referral, scheduling, pre-admission, and documentation context, then route a draft for human review — the care team still makes every clinical decision.
Less repetitive documentation and cleaner handoffs around patient-facing work.
“Registered Nurse - Pre/Post Operative / Pre-Admission Testing”
LAB AND DIAGNOSTIC SUPPORT
Lab and diagnostic teams lose time turning orders and results into next steps.
Munson Healthcare has 23 visible open roles in this pattern, including Phlebotomy Technician I, OR & Anesthesia Technician II - Weekends Only - Traverse City, MI, and Medical Lab Scientist/ Medical Technician. These teams spend real time moving specimen, order, and result context between systems and people.
Our point of view
OpenNash can turn orders, specimen tracking, result routing, and scheduling notes into reviewed next-step packets, so techs spend less time chasing context — never interpreting results or making a clinical call.
Faster turnaround on routine coordination and fewer dropped handoffs.
“Phlebotomy Technician I”
How OpenNash would help
Turn one administrative exception into a reviewed, source-linked workflow.
The first pilot should make the messy handoff visible, reviewable, and measurable without replacing the systems staff already use.
- The workflow stays inside the tools staff already use.
- Every recommendation links back to source context.
- The pilot measures whether the workflow is worth expanding.
How the first 14 days run
One workflow, live in two weeks, measured honestly.
First workflow we would test
Munson Healthcare patient-access and back-office exception workflow
Day 1
Watch the work
Sit with the team that owns the workflow and record the decision points, source systems, exceptions, and approval rules.
Day 3
Map the packet
Define what context the reviewer needs, what OpenNash drafts, and what must stay human-approved.
Day 8
Run live examples
Turn real requests into source-linked packets inside a small review workflow.
Day 14
Measure honestly
Review cycle time, approval rate, edits, rework, and the exceptions that should stay manual.
No charge for the pilot. U.S.-based team — we fly to you. OpenNash connects to the systems your teams already use; nothing is replaced. Every draft, summary, and routing decision lands in a simple review flow where your staff approve, edit, or reject it, with a link back to the source and an audit trail of every action.
Structured role evidence
All 562 Munson Healthcare roles on this page, searchable.
Search by title, location, work pattern, or how OpenNash would help. This is the full role list behind the hypothesis above, not a curated sample.
562 of 562 roles shown
| Role | Work Pattern | Location | OpenNash Fit | Source |
|---|
No roles match that search.
Pulled from Munson Healthcare public postings on July 6, 2026 · every source link goes to the original posting where available.
The ask
Show us one real workflow from this week.
We will map where an AI agent can help, what should stay human-approved, and what test cases would prove it works.