Epic 278 Integration Build

I need a developer who already understands how Epic handles the X12 278 prior-authorization workflow and can turn that knowledge into a working software component. The goal is to accept, transform, and submit 278 requests directly from our Epic instance, then parse and surface the corresponding responses for our care-management team without disrupting existing clinical workflows. You will be writing production-ready code, not a proof-of-concept, so familiarity with Epic Bridges, Chronicles, and Interconnect—as well as the X12 standard itself—is essential. Epic test environments and credentials are ready; you will have access to our sandbox and an internal SME for clarifications. Deliverables will be: • A deployable 278 interface (preferably in Cloverleaf, Mirth, or an Epic-approved alternative) • Configuration scripts or installation guide for our Dev, Test, and Prod environments • Unit and integration tests that can run in an automated pipeline • Brief technical documentation that shows message mapping, error handling, and rollback strategy Additionally: They use Tapestry for UM, while enrollment and claims are still processed through IDX. They already have an outbound 278 from Epic to IDX but now need to establish new outbound 278 integrations to six delegated health plans for the CMS-0057 requirement. The engagement is primarily to take those six payer integrations through build/configuration, payer-specific requirements and companion guides, testing, defect resolution, and production readiness. They're targeting completion around mid-November.