Admissions, lab orders, and results all flowed through one interface engine. Days before an EHR cutover, testers sent it a few crafted messages from an ordinary workstation network. The engine accepted every one, and the changes flowed straight into the patient chart.
AT A GLANCE
- Industry: Health system, multiple clinical systems
- Test type: Internal test of an HL7 interface engine before EHR cutover
- Severity: Critical, CVSS 9.1
- Outcome: Every listener locked to approved sources, cutover on schedule
Moving to a new EHR meant rebuilding dozens of HL7 interfaces. The integration team wanted proof that the new engine would trust only the systems it should, before real patient data started moving.
What's Inside the Case Study
- Why the interface engine accepted messages from any internal network segment
- How one crafted message changed a test patient's allergy list and attending physician
- How a fake lab result landed in a test patient's chart
- What a stalled interface queue means for lab, pharmacy, and radiology
- The four fixes that tightened the engine and kept the cutover on schedule