“Would developers and CTOs of EHRs be willing to be honest about their own implementation of openEHR? What were their expectations, and what challenges did they encounter?”
A question posted to the openEHR Discourse forum; and Sebastian Iancu, software architect at CODE24, board member of openEHR Netherlands, and Vice Chair of the openEHR specification committee, stepped up to the plate.
When CODE24 was established in 2011, the company committed to building their system on openEHR specifications, banking on several years of prior experience. The expectation was clear; to create a robust, scalable backend adhering to international standards, enabling swift development and seamless integration with other systems while harnessing shared medical knowledge.
Sebastien’s responses offer a transparent view of the journey, confirming that even though their expectations were met, the journey wasn’t always easy. While some challenges were expected – particularly in implementing a complex standard – others came as a surprise, like integrating non-medical concepts into medical applications. openEHR provided a valuable degree of freedom, while still promoting interoperability. And openEHR helped CODE24 adapt, become agile, and embrace emerging technologies, such as FHIR, but the hope for broader industry adoption progressed more slowly than envisioned…
Check out the full article of Sebastien’s honest appraisal of Code24’s openEHR implementation