Healthcare Business Analyst (AI & Automation)
Provident HealthCare ManagementHealthcare 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 technical team intact
ββββββββββββββββββββ
π οΈ REQUIRED β WHAT WE SCREEN ON
β Ability to build a quantified business case: current-state cost, projected benefit, and the rationale for where it sits in the queue
β Working command of the insurance authorization cycle end to end
β Professional swim-lane and field-level data flow diagrams (draw.io, Visio, or equivalent)
β Ability to read API documentation, JSON payloads, and data schemas β you do not need to write code
β UAT design and facilitation with non-technical users across multiple functions
β HIPAA Privacy and Security Rules, and the handling requirements that follow from them
β EMR or health information systems experience in a clinical or operational context
β Microsoft 365 fluency β Teams, SharePoint, Word, Excel, Visio or PowerPoint
β You already use AI tools to produce documentation and diagrams faster than you did two years ago
ββββββββββββββββββββ
π‘ PREFERRED β WHAT BREAKS A TIE
Behavioral health, mental health, or SUD treatment settings Β· Familiarity with AI and LLM concepts, enough to judge whether an extraction output is operationally accurate and not merely plausible Β· Experience across multiple back-office functions in healthcare, ideally RCM plus HR, finance, or compliance Β· Agile sprint work alongside developers or data engineers Β· FHIR R4 and payer API integration Β· CBAP or PMI-PBA Β· SDLC documentation depth (SRS, SDS, STS, Run Book) Β· Revenue cycle, healthcare finance, or back-office process improvement background
ββββββββββββββββββββ
π© HOW TO APPLY
Apply directly through LinkedIn, or email us. Either works β we read both.
Send two things:
1οΈβ£ Your resume, weighted toward healthcare operations and back-office process work across multiple functions.
2οΈβ£ A cover note, three to five sentences: (a) which back-office business functions you have mapped and documented, and (b) one business case you built that actually led to a decision β what you measured, what you recommended, and what happened next.
We read the cover note first. π
If you want the documents you write to show up in how someone's grandmother is cared for on an ordinary Tuesday, this is that job.
βοΈ vmuchnik@providenthcc.com and afeinstein@providenthcc.com
Subject line: Healthcare Business Analyst β [Your Name]
Equal Opportunity Employer Β· Fully Remote Β· Compensation is set by market and shared before your first interview
- #HealthcareBusinessAnalyst #BusinessAnalyst #HealthcareAI #RevenueCycle #BehavioralHealth #SkilledNursing #HIPAA #ProcessImprovement #UtilizationReview #RemoteJobs #Hiring