Re: Binding to multiple terminologies / code systems

Dave, the solution to this situation is not yet 100% clear in ADL2 (it is in ADL1.4, as others have described). We are trying to define a cleaner way to represent it in ADL2, but I'm still not clear on the requirements. It appears that the scenario you have is that since SNOMED CT, READ and

RE: Binding to multiple terminologies / code systems

...@lists.openehr.org] On Behalf Of Thomas Beale Sent: Fri 30/10/2015 15:04 To: openehr-technical@lists.openehr.org Subject: Re: Binding to multiple terminologies / code systems Dave, the solution to this situation is not yet 100% clear in ADL2 (it is in ADL1.4, as others have described). We

Re: Binding to multiple terminologies / code systems

On 30/10/2015 16:00, Barnet David (HEALTH AND SOCIAL CARE INFORMATION CENTRE) wrote: Thomas For use (NHS in England) it’s probably at the template level (but it would be good to occasionally specify at the node level). just to be clear on this point, because this is the one I want to

Re: Binding to multiple terminologies / code systems

Hi, Using Archetype Editor I was succeeded to bind a coded text to two terms from different coding systems: ELEMENT[at1054] occurrences matches {0..1} matches {-- New Element name matches { DV_TEXT matches {*} } value matches { DV_CODED_TEXT matches { defining_code

Re: Binding to multiple terminologies / code systems

The answer isn't completely simple. Some background here . If there are bindings defined for snomed_ct, read2 and ctv3 to the ac-code that appears in the archetype definition section, and no further

Re: Binding to multiple terminologies / code systems

Hi Dave, As Thomas suggests, it does depend on whether you expect to be binding to a single term from the terminology e.g. DNACPR decision in http://clinicalmodels.org.uk/ckm/#showArchetype_1051.32.185 in which case Dmitry's advice is correct and the Archetype Editor allows you to add bindings

Re: Binding to multiple terminologies / code systems

It should also be noted that normally constraints on which terminologies can be used in a particular implementation is done in a template. This can be done on the existing DV_TEXT definition or on a DV_CODED_TEXT constraint. This can be expressed in the template designer, again not the best UI