Reply's role: the app packager and the app monitoring
Reply contributed to Ambiti8n with 2 components that work behind the scenes, nevertheless crucial for the entire project. The components, the App Packager and the App Monitoring, help to deliver and monitor the Clinical App so that it can be easily deployed and no issues can impact the clinician's work.
"One Helm chart. Eight infrastructures. Same deployment."
App Packager
Reply's App Packager prepares the clinical application developed by Result so that it can be installed and run within Telecom Italia's infrastructure.
In simple terms, our component packages all the elements needed to deploy the application in a consistent and reliable way, using open standards - like Helm charts - which make the process easier to repeat, scale and manage across different Kubernetes environments.
App Packager's goal is to automate the packaging process to streamline the installation of the clinical application over different providers. It's invisible to the end user, the doctor, but its existence removes the need to package and prepare the application manually, limiting mistakes and wasting time.
App Monitoring
App Monitoring allows us to identify possible issues in the software infrastructure at an early stage, before they affect the work of healthcare professionals.
This component directly communicates with Result's Data Pipeline, collecting logs from a component of the clinical application that performs inference over health datasets.
The information collected is displayed in a dedicated dashboard, giving technicians a clear view of the component's status.
Main challenge
The main challenge was managing a complex environment made up of several different interoperable components and systems, with different maturity levels across partners. Furthermore, all the elements had to be securely connected and made to work together in a consistent way.
We dealt with this challenge by conducting an assessment on components' status and agreeing to adopt ICRA (IPCEI-CIS Reference Architecture) as a shared language across the 8 companies – a key step towards achieving interoperability, one of the project's core goals.
Using this common language, we started the integration phase coordinating it through weekly architecture and status meetings to ensure constant alignment and up-to-date communication.
We also hosted dedicated meetings with Telecom Italia and Result's partners to deepen our understanding of the integration and focus our efforts on the shared goal.
Goal orientation and teamwork have been the key to the project's success. This ability to bring together technologies and teams with different maturity levels reflects an approach Reply has refined over years of managing complex, multi-stakeholder projects across industries - combining technical governance with structured coordination practices.
Beyond the solution
The solution we developed all together within the Ambiti8n project, this federated AI system for clinical sleep apnea detection - makes it possible to have a clean, intuitive view of patient signals without letting sensitive patient information leave the hospital.
Beneath the solution, there is a complex architecture including AI, Kubernetes clusters, monitoring, and EU-compliant data controls. All this complexity is completely transparent to the clinician, specifically for what concerns Reply's contributions, and this is the achievement of the project: creating a complex solution that is useful, intuitive and powerful for the end user, simplifying user experience.
This is only the first step towards a new evolution, expanding the current solution in the same sector or applying it to new industries.