Sai Medapati|

Billing, collections, receipts, claims, settlements, credit bills, advances, and payer mapping all touch the same transaction — across patients, payers, departments, facilities, and corporate entities. A rounding error or a mis-mapped payer is not a display bug; it is a reconciliation problem someone has to unpick by hand.

Owned these workflows end-to-end rather than by module, so the finance team could trace any figure back to the event that produced it. Optimised for auditability over convenience — more write-once records, fewer in-place edits.

ERP, LIS, CRM, analytics, government and partner systems each expect their own payloads, auth, and delivery guarantees. ABHA, SAP, Oracle, NetSuite, Zoho, Tally, LeadSquared, Business Central — every one a different contract, and every one able to be down when yours is not.

REST and webhook flows built with retries, reconciliation paths, operational logging, and failure visibility as first-class features rather than afterthoughts. The premise: partner outages are normal, so the system has to make them visible and recoverable instead of silent.

A hospital platform does not get a maintenance window because it is inconvenient. Production debugging, MongoDB and MySQL analysis, integration triage, and incident coordination are the actual job once a release lands.

Led and mentored a 6–9 person cross-functional team through UAT, rollout planning, and post-go-live stabilisation — and wrote the architecture notes, SOPs, and implementation guidance that let other people handle incidents without me.