Discover and read the best of Twitter Threads about #openEHR
Most recents (5)
Currently I'm researching two areas of #openEHR CDR implementation: 1. Conformance verification, 2. Performance / High throughput.
For #openEHR conformance verification I'm continuing my work at #HiGHmed in which I designed hundreds of test cases and data sets (archetypes, templates, JSON and XML instances), to verify an openEHR CDR complies with the openEHR specs.
The first implementation of those #openEHR compliance test cases was done in #RobotFramework which is a Python tool, initially tests were really nice to read, but with complexity, the Robot tests started to look messy and were difficult to maintain.
There are some #openEHR marketing materials circulating that states "openEHR is a clinical data persistence standard" which is incorrect and people is getting and forwarding the wrong message.
First the marketing material mixes what is the #openEHR specification with some implementation (won't name names). Second, openEHR specifications don't even mention how to persist clinical data.
In terms of data #openEHR allows/enables long term clinical data management, but allows vendors to implement the persistence of data in any way, paradigm or technology that fits their needs.
Recordé la publicación "Estándares e interoperabilidad en salud electrónica: Requisitos para una gestión sanitaria efectiva y eficiente" de la Comisión Económicapara América Latina y el Caribe (CEPAL) de Naciones Unidas donde hice mención de #openEHR allá por 2011.
Fui coautor junto a Selene Indarte, en ese momento presidenta de SUEIIDISS (HL7 Uruguay), ella escribió desde el punto de vista de la gestión sanitaria y quien les habla desde los estándares y la interoperabilidad.
Creo que la publicación fue muy importante en aquel momento, y para mi que CEPAL me haya dado la oportunidad de escribir con tan pocos años de experiencia en el área, pero con un camino ya recorrido, fue un honor. Aquí la publicación repositorio.cepal.org/handle/11362/3…
In the last couple of weeks I've been studying and testing the #openEHR demographic model which has a lot of potential though it needs some improvements.
First it needs more flexibility to specify roles by setting the identities to optional. Second there is an inconsistency in the languages attribute which is DV_TEXT and a better option would be CODE_PHRASE.
Also, the demographic #openEHR model needs more support by modeling tools, we actually need demographic OPTs to be able to test conformance with the openEHR specs.
Now for a thread celebrating the achievements of the international #openEHR Clinical Modelling Program, its' Editors, & its' community of volunteer reviewers. I'm so proud of these people, these models. Together we've achieved something truly unique & groundbreaking 🌟🌟🌟🌟🌟
1. #openEHR archetype design methodology - a strategic and coordinated approach to data design that proactively deconstructs clinical knowledge & applies scientific rigour and repeatable clinical recording patterns to clinical information model development
2. #openEHR Clinical Knowledge Manager (CKM) tool - our secret weapon! This custom-built unique online tool is the coordinating centre for the Clinical Modelling Program - our library of archetypes, our collaboration portal and our governance hub rolled into one.
