Healthcare and lab software integration is my specialist area. If you need two clinical systems talking to each other reliably, this is the work I do most.
What I build:
- HL7 v2 interfaces: ORM (orders), ORU (results), ADT, ACK handling, message parsing, mapping and validation
- EMR / EHR integrations: order entry, results delivery, billing and demographics sync
- LIS / laboratory system integrations: lab ordering, result routing, requisition handling
- Webhook receivers and REST APIs for modern clinical platforms that have moved past raw HL7
- Interface engine work: retries, delivery logging, idempotency, dead-letter handling and replay of failed messages
- Per-client onboarding: field mapping templates, configuration tables, multi-tenant database setup
- Debugging existing interfaces that fail intermittently: duplicate keys, race conditions, malformed segments, silent drops
Tech: HL7 v2.x, C#, .NET 8, ASP.NET Core Web API, Azure Functions (isolated worker), Azure Storage Queues, Azure Blob Storage, Azure SQL, MS SQL Server, T-SQL, REST, JSON, XML, API key and token authentication.
Real production experience: HL7 ORM/ORU interfaces connecting an EMR to a laboratory system; a lab ordering webhook integration where I resolved a live race condition; an EMR billing integration where I traced and fixed a duplicate primary key failure; queue-triggered Azure Functions delivering outbound results to an EMR; clinical decision support webhook receivers with archived raw payloads and delivery logs; multi-tenant onboarding across per-client Azure SQL databases.
Why this matters: clinical interfaces fail quietly, and a dropped result is not a cosmetic bug. I build logging, replay and alerting in from the start, so you find out before your client does.
Describe the systems you need connected and I will tell you honestly whether it is a two-week job or a two-month one.