OpenNash builds on the systems Munson Healthcare already uses.
No rip and replace. We sit on top of existing ticketing, ERP, CRM, HR, data, document, scheduling, service, plant, branch, fleet, or workflow systems, then turn repetitive work into human-approved queues with source links and audit trails.
open roles reviewed from public career sources
roles with detail text available for mapping
OpenNash-relevant work signal buckets
locations or work areas represented
OpenNash point of view
- Best first queue: patient access, referrals, and revenue-cycle queues.
- Why this should matter: The current evidence sample is small, but pharmacy, radiology, transporter, and care-support titles point to clinical support handoffs.
- Practical pilot: Start with referral, scheduling, prior-auth, or patient-contact work where staff need source-linked drafts and exception routing.
What this means
- Munson Healthcare is an Healthcare system operator. The public hiring signal points to repetitive intake, review, routing, documentation, service, and exception work.
- Northern Michigan health system with patient access, clinical informatics, revenue cycle, care delivery, and support operations.
- OpenNash should not sell another standalone tool. We should connect to the workflows staff already use and make the work easier to review.
- The source list did not expose full job descriptions, so this page treats titles, functions, locations, and official role links as directional evidence.
Hiring signals
Top functions or categories
OpenNash work signals
Where OpenNash fits
Revenue-cycle queues, clinical informatics evidence packs, referral packets, scheduling, patient contact, and documentation support.
Start with one queue where staff are already reviewing documents, messages, exceptions, or handoffs.
Keep the stack. Improve the workflow.
We integrate through APIs, files, inboxes, queues, exports, and human review screens before anyone talks about replacing systems.
Measure weekly.
Track volume, cycle time, rework, approval rate, and exception reasons so the operator can see whether the workflow is worth expanding.
Role evidence
This is a bounded view of public roles available from the official career source route. Search by title, function, location, role evidence, or OpenNash help angle.
| Role | Hiring signal | Role evidence we saw | How OpenNash can help | Source |
|---|