You are absolutely right. Yesterday I where in a meeting with two national stakeholders for data specification regarding patient with drug/alcohol problems. The problem we as a vendor and our customers and users face is that they ask for almost the same thing. And they can not agree. That's when they ask if we, as a vendor, can map between the terms.
I said no. I said you have to agree about the meaning of your data. Then, maybe, we can do the mapping. Or even better: there will be no mapping and we can reuse data inside the EHR and between different organisations. The base of semantic interoperability is in a firm core definition of what the data is about. Then the software can let magic things happen. Bj?rn N?ss Product Manager DIPS ASA Mobil +47 93 43 29 10<tel:+47%2093%2043%2029%2010> -------- Opprinnelig melding -------- Fra: Thomas Beale <thomas.beale at oceaninformatics.com> Dato: 31.08.2013 10.12 (GMT+01:00) Til: openehr-technical at lists.openehr.org Emne: Re: openEHR-technical Digest, Vol 18, Issue 50 On 30/08/2013 17:42, William Goossen wrote: Semantic interoperability is absolutely compromised when for the same clinical concept variants of archetypes are created. If justified for internal system development , the moment exchange with another system requires harmonizing on datapoint to datapoint level. I have done about 2000 in perinatology 800 in stroke care 1250 in youth care 100 in nursing oncology 20 in reuma, 400 in general nursing 250 in diabetes care 200 in GP care 100 in cardiology. In the past 13 years. The inconsistencies for the same data element in the various domains are BIG, without clinical justifiable reasons. That same situation exists if you have locally / vendor specific arechetypes . The same situation exists if you have local, regionally and nationally competing HL7 messages, CDAs, FHIR specs, CCDs, DICOM-SR, NCI BRIDG models, and all the rest. That is the situation today. Archetype technology doesn't solve the problem of organisations not collaborating, it just gives much better technical support and capability for building semantic specifications of content and creating software and UI from them. The sociological problem still needs work. That's why identification, governance, and networks of cooperation are important. Still, we didn't get nowhere. Now everyone seems to agree on how systolic BP should be represented :) - thomas -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130831/1db1f698/attachment.html>
