The Opportunity:
Orchestration Works | Ensemble Health Partners
Welcome to Orchestration Works — Ensemble's bold leap into the future of healthcare innovation.
We're building something big. Orchestration Works is a brand-new division designed to move fast, break barriers, and bring cutting-edge technology like AI and automation to life across the healthcare revenue cycle. This is where ideas don't just get tested — they get scaled. Our mission is simple: transform how we work, deliver next-level results for our clients, and lead the industry into tomorrow.
Why Orchestration Works Exists
Healthcare is changing at warp speed. To stay ahead, we're taking R+D out of the lab and putting it into real operations — quickly, intelligently, and boldly. This new division gives us the freedom and focus to experiment, learn, and deploy innovations that make a measurable impact.
What Makes It Different
- A dedicated R+D powerhouse: A 50-person independent team headquartered in Austin, Texas — built to move at startup speed.
- Real autonomy: Independent leadership, resources, and decision-making authority that lets us innovate without friction.
- A laser focus: Revenue Cycle Management innovations powered by automation, AI, and reimagined processes — including work on advanced Administrative and Clinical Reasoning Models.
- A future-ready mindset: We're here to help Ensemble evolve rapidly while protecting what makes us exceptional.
Why It Matters
The future of healthcare isn't waiting — and neither are we. Orchestration Works positions Ensemble to stay ahead of industry shifts, unlock new performance breakthroughs, and deliver smarter, faster, more reliable results for the organizations we serve.
Position Overview
The Epic Architecture Lead is Orchestration Works' Epic authority. Everything OW builds has to work with Epic — and this role owns how. From concept validation through production readiness, the Epic Architecture Lead defines the Epic connection strategy for every initiative in the portfolio: what data moves, how it moves, which interfaces and API connections carry it, and what it takes for an OW solution to operate inside real Epic workflows.
The mandate is intentionally broader than any single Epic application. This role covers Epic overall, advises pods on Epic workflows during validation, and figures out what is needed when the answer
is not documented anywhere. The Epic Architecture Lead works daily with engineering, Applied AI, and Concept Engineering teams, and goes beyond core Epic scope whenever that is what it takes to get an initiative across the gate. This is an individual contributor role reporting to Epic Services but with dedication to Orchestration Works.
What You'll Own
- Epic integration architecture: Define and own the Epic connection approach for every OW build — data integration, interfaces, APIs, and web services — from concept validation through production readiness.
- Data strategy: Determine what Epic data each initiative needs, how it is accessed, and how it stays accurate and reliable as solutions move from shadow validation into production.
- Epic workflow advisory: Advise pods on Epic workflows across applications throughout the 120-day cycle, so solutions are designed around how Epic actually works — not around assumptions about it.
- Sandbox testing and trialing: Own how OW uses Ensemble’s Epic sandbox environment as part of the build cycle — standing up test scenarios, trialing integration patterns and workflows, and proving solutions against realistic Epic conditions before anything moves toward production.
- Cross-functional build partnership: Work hands-on with engineers, AI practitioners, and concept teams every day, translating between Epic architecture and the systems being built on top of it.
- The unmapped problems: When an initiative needs an Epic connection pattern, data path, or answer that does not exist yet, this role finds it, tests it, or builds the case for creating it.
- Standards and handoff: Ensure the Epic integration patterns OW proves out are documented and repeatable, so solutions transition cleanly to Core and to Epic Services at production readiness.
- Interface to Epic Services: Keep OW's Epic work aligned with Ensemble's Epic standards, Standard Operating Models, and upgrade roadmap without duplicating them.
What You Bring
Required
- 10+ years of Epic experience working in a technical capacity, spanning build, integration, and workflow design.
- Epic certification in Cadence, Hospital Billing, or Professional Billing.
- Deep working knowledge of Epic data structures and integration methods — interfaces, APIs, web services, and third-party system connectivity.
- Demonstrated range across Epic applications beyond your certified area, and comfort operating where the answer is not documented.
- A startup mentality: energized by ambiguity, fast cycles, and learning new topics outside core Epic scope.
- Strong communication across technical and operational audiences — engineers, AI teams, operators, and executives.
- Must be inquisitive and demonstrate openness to innovation including AI to explore better processes and ways to alleviate friction and improve patient and client experiences.
- This is a remote position; however, candidates must be willing and able to travel to and work onsite at client, temporary, or corporate office locations as business needs require.
- This position pays between $148,800-223,200 based on experience
Preferred
- Experience in product management, solution design, or operational strategy.
- Revenue cycle operations experience across patient access, billing, or HIM.
- Experience connecting AI or automation solutions to Epic in a production environment.
How We Work at Orchestration Works
- 120 days, three gates: Every initiative moves from intake to deployment-ready in 120 days or less, through three decision gates. Killing a concept at the gate is a legitimate, expected outcome — that is the model working, not breaking.
- Multi-hat, startup-like team: Roles here are broader than their titles. Leaders operate hands-on, pods rotate in and out on initiative cycles, and everyone contributes beyond their lane.
- Validated on real work: Front-line Ensemble teammates use what we build on real workflow before anything is locked. Solutions are designed around validated work, not assumption.
- Built on Core: Same codebase, same CI/CD, same Ensemble engineering bar. OW proves it; Core scales it.
- Co-located in Austin: The dedicated team and active pod members work together in person at the OW office. Candidates must currently reside in the Austin area or be willing to relocate; relocation assistance may be available for eligible candidates.
