Open platform and open standard

MEDrecord is open in the sense of being transparent. Our API’s use the standard format defined by openEHR and approved by ISO/NEN13606, guaranteeing semantic interoperability; the ability to express the meaning of the data (the how and the why behind data).

Semantic interoperability

For Hospitals:

Complying is expensive: we provide shared clinical models, terminology bindings and data normalization

The doctor in control

Develop your own clinical models and provide them to others
(there are already hundreds available)

Developers

Focus on development, not on the clinical models..;-)

Independent report

Gartner believes that truly effective and sustainable open architectures will need a capability for vendor-neutral data persistence, such as utilizing a common schema or set of openEHR archetypes and rules for managing structured and unstructured data (for example, a VNA, openEHR or IHE XDS repository in combination with services for trust/consent, ecosystem governance and oversight, and reuse of data and processes for secondary purposes, such as research and population health).

Providing open messaging standards (for example, FHIR, HL7) for data exchange in specific use cases will only go so far in meeting the architectural challenges of digital citizen-centric care delivery.

See complete report

The ISO/NEN 13606 and openEHR standard

The openEHR community is based on 15 years research, focussing on engineering design and real-world implementation experience, rather than being created as a formal consensus standard. It has had a significant influence over the development of EHR standards by the three main international eHealth standards organisations: CEN, HL7 and ISO.

Jan-marc Verlinden explaining openEHR: