An independent architecture review and integration roadmap across four hospital sites — and the conversation it took to get there.
The regional health service operated four hospital campuses and a network of community clinics. Over the previous decade, clinical systems had been procured and implemented on a site-by-site basis. The result was a federation of applications — different pathology systems in different locations, three different patient administration systems, two electronic medical record (EMR) products in use simultaneously — stitched together by interfaces that were poorly documented and impossible to maintain without the institutional knowledge of two long-serving IT staff who were within three years of retirement.
The board had decided that the answer was a single integrated clinical record. The challenge was that nobody inside the organisation had a clear view of how to get there from the current state. Vendors had been invited to present a vision; all of them started from a clean sheet and none of them engaged seriously with the messy reality of how clinical work actually flowed through the existing systems.
We were engaged by the chief information officer to produce an independent current-state architecture assessment, a target architecture, and a credible, funded integration roadmap that the board could adopt. We were explicitly told not to recommend a specific vendor product; we were asked to define what good would look like, and to leave the vendor selection to a subsequent procurement process.
We began by walking the wards. For two weeks, members of our team shadowed clinical staff — nurses, registrars, consultants, pharmacists, allied health — at all four sites to understand how information actually moved through a patient journey. We sat in on handover meetings and observed the gaps. This was not glamorous work but it produced a baseline understanding that no architecture diagram had previously captured.
From there we produced a current-state architecture in plain language: what each system did, where the seams were, where data was being re-keyed, and where single points of failure existed. We mapped this against the patient journey and identified the integrations that, if delivered first, would produce the greatest clinical benefit at the lowest implementation risk.
They were the first people who came in and listened to the nurses before opening a slide deck. The resulting roadmap was not what we had originally imagined, but it is what the clinical staff will actually use. — Chief Information Officer
We defined the target as a unified clinical record presented through a clinician portal, with back-end systems allowed to remain diverse for the medium term. The mistake we explicitly wanted to avoid was a single-vendor rip-and-replace that would have created a five-year implementation horizon and a high probability of clinical workflow disruption. The target we proposed was instead an architecture in which clinical workflows converge even as administrative and operational systems continue to be modernised incrementally.
We built a phased roadmap of five integration releases over thirty months. Each release was sized in capability terms (not vendor terms) and priced against the client's own cost model. We then worked with the chief finance officer to develop the funding submission to the state health department. The submission was successful on the first attempt and secured $4.2 million in capital funding for the first three releases.
The first integration release went live eight months after the engagement finished. It consolidated pathology results across all four campuses into a single clinical view. The second release is now in user acceptance testing and will unify medication administration across the network. The board has formally adopted the target architecture as the basis for all future clinical procurement decisions.
The trap in clinical systems work is to assume that the right answer is always a single vendor and a multi-year implementation. Sometimes it is. Often it is not. The right architecture is the one that solves the most pressing clinical problems at an acceptable cost and risk, while leaving a sensible path to the longer-term vision. We have learned to keep the vision ambitious and the roadmap conservative.
If you are wrestling with fragmented systems, an upcoming procurement or a clinical safety case that needs independent review, we are happy to have a confidential conversation about what an engagement might look like.