The project health sap started in 2017 with 3 premises: use existing products to set up a first-line service, be in the cloud and rely on data to make decisions.
Sap is a composite company, from before Gartner made them fashionable as the most interesting emerging trend of 2020. From its start to its debut in the press 18 months later, it brought three different brands to the market, tried to include the services of 6 health providers, of which it only incorporated some and it was assembled using 2 clouds, Amazon y Google, instead of one.
The challenge
The vision was clear: an octopus. It was about centralizing in a single point everything that had to do with the clients, so that their experience was coherent and fluid.
The octopus would have multiple legs, corresponding to all the services that could be included in the offer. The legs would be numerous, different from country to country, completely heterogeneous and external to the brain. Also, they would surely be volatile: adding or removing a leg had to be quick.
All the exchanges, all the information had to be analyzed by the data specialists to be able to see what was and what was not, in a cycle of constant and rapid change. The structure of the technology team had to be very light.
The solution
Savia had the focus and advice from the team of Sloop to design an orchestrated architecture of microservices, built on mature modules such as Salesforce o Zuora.
With this architecture, each brand required the services it needed from the components it needed, but the same architecture and the same components were capable of behaving differently depending on the brand, the type of customer… The information is anonymised for its journey to data environments, where the behavior of the system is constantly studied in order to adjust it.
The futuristic vision of Sap it is that of a complex system, capable of aggregating the behavior of its elements, which provides its managers with visibility of what is happening and the ability to correct itself. Anyone's dream.
