Healthcare Business Analyst (AI & Automation)

Healthcare Business Analyst (AI & Automation) 🏥 The most expensive thing in healthcare isn't the technology. It's the same date of birth being typed into four different systems by four different people. Nobody went into healthcare to do that. Not the nurse. Not the Executive Director. Not the biller, the HR director, or the person reconciling an invoice at 6pm because the system that should have caught it doesn't talk to the system that created it. Provident Healthcare Consulting operates skilled nursing, behavioral health, and substance use disorder treatment across the Midwest. Our residents and patients are elderly, medically complex, in withdrawal, in crisis, or in early recovery. They meet us at the hardest moment of their year — sometimes the hardest moment of their life. We are building an AI-powered automation platform to take the manual re-entry out of their care. LLM agents. Healthcare interoperability APIs. A Human-in-the-Loop approval layer, because in this environment nothing automated gets to act unwatched. 🤖 And none of it works without someone who understands the operation well enough to tell the engineers the truth about it. That's this role. 🚀 📍 Fully remote · 🌍 We hire across multiple countries · 📋 Contract / contract-to-hire · 👤 Reports to the Chief Technology Officer ━━━━━━━━━━━━━━━━━━━━ 🎯 THE JOB IN ONE SENTENCE You are the bridge between what actually happens and what gets built. You will sit with a utilization review coordinator and watch her work a concurrent review. You will sit with a business office manager and watch her chase an eligibility check. You will sit with HR, with finance, with compliance, with the facility team. Then you will go to the engineers and describe what you saw with enough precision that what they build is the thing that was needed. ✍️ If the translation is off by a little, we ship something clever that nobody uses. If the translation is right, we give hours back to people who would rather spend them on patients. ❤️ ━━━━━━━━━━━━━━━━━━━━ 🔭 WHAT WE'RE NOT DOING We are not automating clinical workflows and calling it a day. 🩺 Utilization review · 💰 Revenue cycle · 👥 Human resources · 📊 Finance · ✅ Compliance · 🔧 Facility operations Half the redundant data entry in a healthcare organization lives in the back office. If you can map a clinical workflow beautifully but can't explain an AP approval chain or an onboarding packet with the same rigor, the automation we build will solve half the problem — and the half it leaves behind is the half that quietly eats the budget. 🔍 This role covers the full operational footprint. All of it. ━━━━━━━━━━━━━━━━━━━━ ⚡ WHAT YOU'LL ACTUALLY DO 🔹 Map current-state workflows end to end — clinical and back-office — through structured stakeholder interviews 🔹 Produce swim-lane diagrams showing role, system, and decision gate at every step 🔹 Document every provider-payer touchpoint: eligibility, prior authorization, concurrent review, reauthorization, denial and appeal 🔹 Find and quantify redundant data entry — staff hours, error rate, compliance exposure 🔹 Build the business case for every automation opportunity, including the cost of doing nothing 🔹 Prioritize every opportunity on a value-vs-complexity matrix that spans all business functions, not just the loudest one 🔹 Turn operational pain points from back-office staff into formal use cases with measurable success criteria 🔹 Define the canonical data model every source must normalize to before it writes to the system of record 🔹 Classify regulated vs. non-regulated data at every step of every flow, and document the consent and handling requirements attached to each 🔹 Author the Software Requirements Specification — functional and non-functional, with scope boundaries drawn explicitly — alongside the Architect and the CTO, and hold traceability from SRS through SDS into test cases 🔹 Pressure-test the Human-in-the-Loop approval design against operational reality — and say so when it doesn't survive contact 🔹 Design and facilitate UAT with clinical and administrative staff, and validate AI extraction accuracy against ground truth 🔹 Present business cases to the CTO and executive leadership in plain language, with the data behind them 🔹 Surface blockers, requirement conflicts, and process changes before they become technical problems — across every function, not just your favorite one ━━━━━━━━━━━━━━━━━━━━ 🧠 THE THREE NON-NEGOTIABLES Everything else is coachable. These three are not. ✅ 1. Three or more years inside a healthcare operation. Not adjacent to one. Not advising one from a deck. You have sat next to the people doing the work and you know what a denial actually costs. ✅ 2. You have authored a formal requirements document that engineers built from. SRS, BRD, or functional spec, with structured use cases and testable acceptance criteria. "Participated in requirements gathering" is not this. ✅ 3. You have mapped and documented at least two back-office business functions — RCM plus at least one of HR, finance, compliance, or facility operations — to the field level, not the flowchart level. ━━━━━━━━━━━━━━━━━━━━ 🗣️ AND ONE THING THAT OUTRANKS ALL OF IT Communication is the primary qualification of this job. You translate between three worlds — clinical operations, back-office business functions, and software engineering — and all three translations have to be accurate. A requirement that reads two ways will get built two ways. ✅ Exceptional written communication — unambiguous requirements, clear business cases, concise executive summaries ✅ Strong facilitation — you can pull precise process detail out of a charge nurse and out of an AP clerk, and you know those are different conversations ✅ You can explain deduplication, LLM extraction, and Human-in-the-Loop to someone in any function without making them feel small ✅ You can carry clinical and back-office constraints back to a technica