As Odin Health is solely based in Auckland, New Zealand. Odin's strategy is to expand via a partner-led strategy. We’re specifically looking for partners that will not only resell Odin Health products.
No matter where the patient is located, with the support of 5G, hospitals will provide better services. Odin has foreseen the trends of large hospitals, medical alliances, and regions in the 5G era, and is prepared to embrace the arrival of the "Internet of Everything" era.
After strict review by the New Zealand government, Odin Health's core products (Odin Engine Standard Edition, Odin Engine Cluster Edition, and Odin Cloud-Native Platform) have been awarded the FernMark trademark, a national quality certification in New Zealand!
Odin NeXT uses a cloud-native PaaS layer based on the latest container technology, a microservice-oriented architecture, and high-level resource management to achieve high availability, high concurrency, high performance, and super-high concurrency performance.
On November 20, 2018, at the first HL7 New Zealand FHIR® Connectathon, Odin Health successfully completed the patient care track, provided server-side organization, and passed the Connectathon with high quality. It was the only vendor to achieve this.
Introducing the Odin Engine Cluster Edition Optimization Solution, which is based on the 3rd Gen Intel® Xeon® HCI Platform. This white paper outlines the benefits of using the Odin Engine Cluster Edition and the 3rd Gen Intel® Xeon® HCI Platform for optimizing the health integration platform
Given that applications in healthcare environments tend to stick around for a while (10 to 15 years!), the challenge for the health sector is how to support the old technologies while gradually embracing the new.
The Odin Engine is not your typical Integration Engine or ESB - it goes far beyond that. Our engine combines the best functionality from a variety of integration tools, using the latest state-of-the-art technologies, to create an innovative and unrivaled product.
Both ESBs and Integration Engines are application integration solutions. Why do ESBs and Integration Engines provide different solution "flavors" for Healthcare scenarios?