Thanks, that clears things up a bit.

-----Original Message-----
From: "Thomas Beale" <thomas.be...@openehr.org>
Sent: ‎5/‎3/‎2016 2:26 PM
To: "openehr-technical@lists.openehr.org" <openehr-technical@lists.openehr.org>
Subject: Re: Terminology bindings in openEHR

Some background information from the ADL2 spec may help. This description 
explains the same semantics as for ADL 1.4. archetypes, except that in ADL 1.4, 
'at' and 'ac' codes are used, whereas ADL2 has 'id', 'at' and 'ac' codes.

With respect to tools, there is not yet a standard openEHR terminology look-up 
tool, and the direction is most likely that openEHR modelling tools will 
integrate with other available tools such as the ones you mention. 

- thomas


On 03/05/2016 12:24, Eneimi Allwell-Brown wrote:

Hi,

Can I get  some insight into how terminology bindings work in openEHR, or how 
they are supposed to work?

It appears openEHR supports multiple terminologies, in addition to its own 
internal coding structure (atxxxx). I think there’s a whole terminology service 
dedicated to this. But my confusion is how to implement the feature.

In the Ocean Template designer as well as the Archetype editor, there are 
features that allow us specify what terminology we want to use and to 
‘manually’ input the codes we want to represent. Some data elements already 
have fixed ‘Valuesets’ (e.g. Regular, Irregular as Coded_text values for the 
‘Regular?’ element in the Pulse archetype).

When I use free online tools to create a FHIR resource for upload to a FHIR 
repository, where ‘CodeableConcepts’ exist the form field has a code/database 
lookup service to LOINC, SNOMED CT, internal FHIR codes etc., so that as I 
enter the first three characters of the concept I want the system presents a 
list of options which I can override if I don’t find what I want. When I select 
the concept I want, the system inputs the correct code as well as the URL of 
the source terminology server. 

I want to imagine openEHR supports this sort of ‘lookup’ to existing 
terminologies, but how do I accomplish this? Otherwise how does it handle 
terminology binding?
_______________________________________________
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Reply via email to