Mission Control

Real-time patient-flow dashboard fed by the hospital's HL7 ADT stream.

RoleArchitect and developer

PeriodNov 2025 – Dec 2025

Stack

.NETTCP / MLLP listenerHL7 ADTSQL ServerWeb dashboard

Data handlingHIPAA · On-prem

Runs entirely inside the hospital network; identifiers are displayed only to authorised roles.

Problem

Operations and nursing leadership had no live view of admissions, transfers and discharges; census questions were answered by phone calls and stale reports.

Approach

Wrote a .NET service that listens for ADT messages over TCP/MLLP, parses A01/A02/A03/A08 events, and writes a normalised event stream. A web dashboard reads that stream and shows live census, bed movements and alerts.

Architecture

Listener service → parser → SQL Server event tables → dashboard with auto-refresh; designed so additional message types (ORU, ORM) can be added without touching the UI.

HL7 ADT over TCP/MLLP→.NET listener service→Parser · event tables→SQL Server→Live dashboard

By the numbers

ADT A01 / A02 / A03 / A08Message types

Seconds from HL7 to screenLatency

Dec 2025Launched

Outcome

Launched December 2025; gave leadership a single live screen for patient flow and became the base for later alerting work.

What I would tell your team

Ask me how this maps onto your EHR, your interface engine and your security review. I can walk through the data flow, the failure modes we hit at go-live, and what I would do differently the second time.

Talk about a similar system

← PreviousORBIT

Next →North Star