The software healthcare runs on,and the person who keeps it running.

I'm Monish Bista — a software engineer in the United States. For ten years I've built and looked after the enterprise systems that move claims, records, and clinical data between healthcare organizations.

Monish Bista in a navy suit

10 years

building healthcare software

C# / .NET

and SQL Server, daily

HIPAA

compliant environments

SSIS / ETL

high-volume data integration

What I do

Most of my work sits in the unglamorous middle of healthcare IT — the services that have to run tonight, whether or not anyone is watching. A failed nightly job isn't an alert; it's somebody's claim sitting unpaid.

Integrations that hold

EDI, X12, and HL7-era file formats moving between trading partners and internal systems, with the error handling that decides whether anyone sleeps.

Automation over toil

ETL pipelines that used to be spreadsheets, deployments that used to be checklists, reports that used to be somebody's Thursday afternoon.

Systems nobody documented

I tend to become the person who knows how the older applications actually work — and then I write it down so the next person doesn't have to find out the hard way.

Where I've worked

  1. Software Engineer, Wolters Kluwer

    September 2019 – September 2026

    Enterprise applications and APIs end to end, and the primary maintainer for several services that other teams depended on.

  2. Software Engineer, Zelis Healthcare

    June 2015 – September 2019

    Healthcare applications in C#, .NET, and SQL Server, with SSIS pipelines moving high volumes of claims data and automation replacing manual operations work.

  3. IT Intern, Zelis Healthcare, formerly GlobalCare

    June 2013 – June 2015

    EDI testing with trading partners, X12 and HCFA 1500 mapping, and the first scripts I wrote to kill repetitive work.

Full experience  ·  Resume

About

I studied computer science at Kennesaw State and went straight into healthcare software, starting as an intern mapping X12 claim files and staying because the problems kept being interesting. Claims data is messy, the rules change, and every integration has a partner on the other end with their own idea of what a valid file looks like.

I work best on teams where engineers review each other honestly and the documentation is treated as part of the deliverable. I'd rather spend an afternoon making a deployment boring than spend a night fixing an exciting one.

What I work with

Get in touch

Email is the fastest way to reach me. I'm happy to talk about backend work, healthcare integrations, or an old system that needs someone to understand it.

bistamonish@gmail.com LinkedIn GitHub