Home / Projects / FHIR Sepsis Alerts
Case study 06 · Clinical · FHIR · HIPAA

FHIR Sepsis Alerts

FHIR server application with capability-statement generation, built for sepsis alerting.

RoleLead developer
PeriodDec 2025 – 2026
Stack
HL7 v2FHIR R4PythonREST
Data handlingHIPAA · HIPAA

In-network only; minimum-necessary resource exposure.

Problem

Sepsis is time-critical; the signals existed across HL7 feeds, but nothing turned them into a timely, standards-based alert.

Approach

Built a FHIR-facing application that exposes patient and observation resources, generates its own CapabilityStatement, and evaluates sepsis criteria against incoming data to raise alerts.

Architecture

HL7 v2 ingestion → FHIR resource mapping → rules evaluation → alert output; capability statement generated from configuration so integrators can discover what the server supports.

HL7 v2 ingest→FHIR resource mapping→CapabilityStatement→Sepsis rules→Alert output

By the numbers

FHIR R4Standard
Auto CapabilityStatementDiscovery
Sepsis criteriaUse case

Outcome

Standards-based alerting service that positions the hospital for its upcoming Cerner/OCI migration.

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
← PreviousPrivate LLM (air-gapped)
All projects →Back to the index