EMR, HIS and PM talking to each other

Apache Camel routing between the clinical and administrative systems of a healthcare provider whose records were complete in no single place.

Talk to an engineer ServiceNow

Healthcare Client

ServiceNow Practice

July 2023 Published

01 — The challenge

Where it started.

The provider ran an Electronic Medical Record system, a Hospital Information System and a Practice Management system that exchanged nothing. Staff moved data between them by hand.

The clinical cost of that is a patient record that is complete in no single place.

02 — What we built

The work itself.

Apache Camel between three systems. Message routing configured on an open integration framework rather than built as bespoke point-to-point code.

Transformation across formats. Each system’s format mapped in the integration layer, so none of them had to change in order to participate.

Messages moved without people. The manual re-entry step removed rather than accelerated.

03 — Results

What the client has now.

Patient care improved through unified visibility across systems. Efficiency increased and manual effort reduced. Cost saved by using an open-source framework rather than custom development.

The rest of this study

What we built, what it produced, and the stack behind it.

We share the whole write-up — we would just like to know who is reading. One form opens every case study on the site for the next 30 days.

If this is your problem too

Start with a fixed-price pilot.

Two weeks on a real piece of your backlog, priced before we begin. You keep the output whether or not you continue.

Related work

Private cloud · ServiceNow ITSM

Untangling a complex IT environment

Private cloud · Billing integration