A single patient record, wherever the patient walks in

The client is a multi-facility hospital group that grew the way most hospital groups grow: by building some sites and acquiring others. Each hospital and clinic arrived with its own electronic health record system, chosen by whoever ran it before, and each kept running it. Patients moved freely between facilities. Their records did not. A patient's history stayed behind at whichever site last treated them, and the version of that patient held at each facility slowly drifted apart.

The cost showed up at every handoff. Clinicians re-captured allergies, medications, and histories on every transfer, and every re-entry was a chance to get something wrong. Leadership had a parallel problem: there was no way to see clinical or operational activity across the group without manually consolidating exports from each system. The group was one organization on paper and several in its data.

Kentro was engaged to fix the data problem at its root. Not another integration layer over broken foundations, but full consolidation: migrate every facility onto a single EHR platform, rebuild clinician workflows around the shared record, expose it through standards-based APIs, and put a patient-facing portal on top. The sequencing was part of the engagement. Consolidation first, then interoperability, then new capability.

The group had grown faster than its systems. Every stage of care depended on which building the patient happened to be standing in, and no facility saw the whole picture.

• Fragmented records: Each facility ran a separate EHR, so a patient's history stayed behind at whichever site last treated them. The same patient existed as a different record in every system that had ever seen them.
• Re-entry at every handoff: Clinicians re-captured allergies, medications, and histories on every transfer between facilities. Every re-entry cost time on the ward and created a fresh opportunity for a dangerous omission.
• No group-wide visibility: Leadership could not see clinical or operational activity across facilities without manually consolidating exports pulled from each system. Group-level questions were answered weeks late, if at all.

Kentro consolidated the group onto a single EHR platform in a deliberate order: the record first, then the standards boundary, then the workflows and patient-facing capability that depend on both. The platform runs as isolated Spring Boot services on Kubernetes, with PostgreSQL as the system of record for the longitudinal patient record and Kafka streaming admissions, transfers, orders, and results across facilities.

• A consolidated clinical repository: Records from every facility were migrated into a single longitudinal patient record. An enterprise master patient index resolves identities across the legacy systems, so duplicate records for the same person collapse into a single chart.
• Standards at the boundary: A FHIR API sits over the repository, with an interface engine translating legacy feeds from lab, pharmacy, and radiology systems. Imaging moves over DICOM. Anything that speaks the standard can integrate without touching the core.
• Workflows rebuilt with clinicians: Order entry, clinical notes, and shift handoffs were redesigned with frontline physicians and nurses from each facility, not imposed from a template. Role-based views give physicians, nurses, and pharmacists the screens their work actually requires.
• A patient portal on the same record: Patients book appointments, read results, and view prescriptions against the same record their clinicians use. Access is authenticated through Keycloak and authorized with SMART on FHIR rather than a bolted-on portal database.
• A migration that never went dark: Each site ran its legacy system and the new platform in parallel, with automated reconciliation proving the records matched before cutover. A strangler fig migration, facility by facility, instead of a big-bang switch. Role-based access with break-glass override and an immutable audit trail on every record view and edit came as part of the platform, not as an afterthought.

The outcomes are operational, and they are the ones clinicians notice first. What changed is what the group's staff stopped doing by hand.

• A shared chart at every facility: A clinician at any site opens the same longitudinal record, with current medications, allergies, and history already in it. The record follows the patient instead of the building.
• Handoffs without blank forms: Transfers between facilities carry the full chart, so intake no longer starts with re-capturing what another clinician already recorded. The error surface that came with every re-entry is gone.
• Patients who self-serve: Results, prescriptions, and appointment booking moved into the portal, replacing phone calls and printed reports. Patients read from the same record their care team writes to.
• Group-wide reporting from live data: Administrators query clinical and operational activity across the whole group directly, and the audit trail behind every record supports regulatory review. The manual consolidation of exports is finished as a practice.