RE: Terminology bindings in openEHR

2016-05-03 Thread Eneimi Allwell-Brown
Thanks, that clears things up a bit. -Original Message- From: "Thomas Beale" Sent: ‎5/‎3/‎2016 2:26 PM To: "openehr-technical@lists.openehr.org" Subject: Re: Terminology bindings in openEHR Some background information from the ADL2 spec may help. This descriptio

Re: Terminology bindings in openEHR

2016-05-03 Thread Thomas Beale
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',

Re: Terminology bindings in openEHR

2016-05-03 Thread ANASTASIOU A .
Hello Eneimi The Data Value entities hold information on which terminology a specific encoded term may be coming from to enforce further data validation. What you describe in your question, involving FHIR, is what happens when you interact with a terminology server (https://en.wikipedia.org/

Terminology bindings in openEHR

2016-05-03 Thread Eneimi Allwell-Brown
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 (at). I think there’s a whole terminology service dedicated to this. But my conf