All work

Case study 04

Platform Integration Design


  • Architecture
  • APIs
  • Interoperability

An example of designing an integration strategy to connect multiple legacy systems, with data flows, dependencies, and technical considerations.

Integration Architecture EHR Lab SystemImaging SystemLegacy System Integration Layer API GatewayData Transformation(Mapping)FHIR API Unified Results Platform Web AppMobile AppProvider Portal

The problem

Point-to-point does not scale

Three source systems feed three applications. Connected one by one, that is nine interfaces, each with its own data format, error handling and owner. Every new channel would add three more.

  • Codes do not match between systems, so the same test appears under different names.
  • Results arrive late in some channels because the legacy archive only exports overnight.
  • Failures are silent: when an interface breaks, users find out first.

My approach

Design the flow, then the parts

  1. InventoryListed every system, the data it owns, its volume and how it can share data today.
  2. Target architectureAn integration layer between sources and channels: API gateway, data transformation and mapping, and a standard FHIR API.
  3. Common data modelAgreed one representation of a result and its status, and a mapping table from each source's codes to it.
  4. Non-functional requirementsLatency, security, audit and failure handling, written as testable requirements, not left to the end.
  5. Phasing and dependenciesLab first (highest volume, cleanest interface), imaging second, the legacy archive last.

Sample artifact

Technical considerations

AreaRequirementWhy
LatencyA final result is visible in every channel within 5 minutesClinicians act on results during the visit
StandardsResults exposed through a FHIR APINew channels and partners connect without custom work
Code mappingEvery source code mapped to one standard code; unmapped codes go to a review queueOne test, one name, everywhere
SecurityAccess by role and scope; every view is loggedPatient privacy and audit requirements
Failure handlingAutomatic retry, alert after 3 failures, dashboard of message statusThe team finds problems before users do
Legacy archiveNightly batch until it is retiredEvent support would cost more than the archive's remaining life

Key decisions

Trade-offs I made

  • Hub instead of point-to-point

    Options: keep adding direct interfaces, or build an integration layer.

    Chose the hub. Six connections instead of nine today, and one more (not three) for each new channel.

  • Events where it matters, batch where it does not

    Options: real-time for everything, or match the method to the need.

    Mixed. Lab and imaging results flow as events; the legacy archive stays on a nightly batch until retirement.

  • Lab first

    Options: start with the hardest system, or the one with most value.

    Started with lab. Highest volume and a clean interface, so users saw value early and the team learned on the easier source.

Outcomes

How success is measured

  • 9 to 6Interfaces to maintain
  • < 5 minFrom final result to every channel
  • < 0.5%Results with unmapped codes
  • 0Silent failures: every error alerts the team

Illustrative targets. My role in a design like this is to make sure the architecture serves the user problem, that dependencies are known early, and that the technical requirements are clear enough to test.

Illustrative example. This work sample uses a fictional scenario and synthetic data. It does not contain confidential or proprietary employer information.

Want to talk through how I'd approach your product?

Let's Connect