Fundación Santa Fe de Bogotá runs digital services that patients, providers, and the medical community depend on. Its institutional website, on a legacy IBM CMS, was just the first point of a broader digital transformation.

Fundación Santa Fe de Bogotá has been an esinergia client since 2021. What follows describes not only the first technical milestone on the institutional site, but what more than four years of continuous operation reveal about a broader digital transformation process: when a healthcare institution sustains its digital presence for years, the question stops being how to launch a portal and becomes how to keep a growing ecosystem running without interruption in a sector where downtime is not an option.

The legacy IBM CMS limited how the institutional site could evolve and made it hard to align it with the rest of the digital ecosystem the Foundation needed to build. Supporting and maintaining an obsolete platform accumulated growing risk and cost, and integrating critical clinical and operational systems became difficult on infrastructure without room to scale. Beyond the institutional portal, the Foundation needed transactional portals for patients and third parties, specialized health-content portals, and an e-commerce portal for diagnostic exam services. Multiple portals with distinct audiences and demands, all to be incorporated progressively on a coherent foundation.

A scalable ecosystem on Drupal, Acquia Cloud, and Algolia

We started with the institutional portal on Drupal and Acquia Cloud Platform, replacing the legacy IBM CMS, and from there we progressively built a scalable digital ecosystem that today sustains eleven portals on a single technical foundation. The architecture anchors the public portal fundacionsantafedebogota.com as the central piece, complemented by transactional portals for patients and third parties, specialized health-content portals, and an e-commerce portal for diagnostic exam services. All integrated with the institution's critical clinical and operational systems, with semantic search on Algolia, centralized sign-on, and progressive stack modernization already advancing toward Drupal 11.

One nuance worth naming: the hard part was not the first portal. It was sustaining for four years an ecosystem in organic growth, while clinical operation can never be paused and while every major Drupal version or new integration must be absorbed without compromising a critical system. In healthcare, the project does not end when the portal goes live. That is where it begins.

Four years of continuous operation, eleven portals, and a scalable digital ecosystem.

The value is not in having replaced a legacy CMS, but in the fact that four years later the ecosystem keeps receiving major versions and new integrations without interrupting clinical operation. The eleven portals operate reliably, progressive modernization advances toward Drupal 11 with no downtime, and the technical foundation absorbs new portals without being rebuilt. Three results sustain that observation.