Ing. Pablo Pazos Profile picture
Jan 31 5 tweets 3 min read
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.
If you want to know what #openEHR is, first read the specs: specifications.openehr.org If you want a summary: cabolabs.com/blog/article/w… if you need help making sense of the specs, contact people that actually knows what they are talking about @CaboLabs #WeCanHelp @HealthcareData

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Ing. Pablo Pazos

Ing. Pablo Pazos Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @ppazos

Jan 30
Healthcare information has many zoom levels, from microcellular, tissue, organ or DNA data, to international metrics and statistics, and everything in between. When working on healthcare data platforms it's important to know at which level(s) you are working.
That will determine how you design your components, repositories, rules, APIs, etc. and when your processes change between different zoom levels, for instance, aggregating data.
The data zoom level will also determine how data is exchanged and processed. Understanding that will lead you to a better platform architecture, but not understanding at which zoom level you are working, can lead to a messy software architecture.
Read 4 tweets
Jan 29
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…
Read 14 tweets
Oct 13, 2022
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.
Read 6 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(