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 but you get there... Not sure that archetype constraint bindings help in this step.
Regards Heath On 30 Oct 2015, at 5:37 am, Ian McNicoll <i...@freshehr.com<mailto:i...@freshehr.com>> wrote: 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 to any/all of the terms via the terminology, then term-binding tab. Not the nicest UI but you get there!! If the target needs to be selected from a list of possible options then Thomas's advice is appropriate. One issue is that we do not have good industry standard ways of defining these external refset bindings, though it looks as if FHIR might get some traction. Examples in this archetype http://clinicalmodels.org.uk/ckm/#showArchetype_1051.32.4 Ian Dr Ian McNicoll mobile +44 (0)775 209 7859 office +44 (0)1536 414994 skype: ianmcnicoll email: i...@freshehr.com<mailto:i...@freshehr.com> twitter: @ianmcnicoll [https://docs.google.com/uc?id=0BzLo3mNUvbAjT2R5Sm1DdFZYTU0&export=download] Co-Chair, openEHR Foundation ian.mcnic...@openehr.org<mailto:ian.mcnic...@openehr.org> Director, freshEHR Clinical Informatics Ltd. Director, HANDIHealth CIC Hon. Senior Research Associate, CHIME, UCL On 29 October 2015 at 18:24, Thomas Beale <thomas.be...@openehr.org<mailto:thomas.be...@openehr.org>> wrote: The answer isn't completely simple. Some background here<http://www.openehr.org/releases/AM/latest/docs/ADL2/ADL2.html#_terminology_integration>. 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 constraint is given, the implication is that any code from any terminology with a binding may be used at runtime. Since this is normally on a value-set by value-set basis, each value set (each distinct ac-code) will have a binding entry only in those terminology groups in the binding section that make sense. On 29/10/2015 15:31, Barnet David (HEALTH AND SOCIAL CARE INFORMATION CENTRE) wrote: All I have a modelling issue where I’m trying to bind a single data point or an archetype to a choice of terminology & code systems. The actual use case is that I’m modelling a new-born hips examination, and the result may be given as either a SNOMED CT concept, a Read 2 code or a CTV3 code (for those unfamiliar with Read 2 & CTV3, they are code systems used (mostly) in primary care in the UK). In the actual instance, each code/concept will have a code system identifier to distinguish the actual code system used For example, a result of “no abnormalities and no risk factors” can be represented as either SNOMED CT Read2 CTV3 ID FSN ID Term ID Term 985701000000100 Newborn and Infant Physical Examination Screening Programme, hip examination done, no abnormality and no risk factor 9OqJ1 NIPE hip, no abnor&no rsk fctr XadAN NIPE hip, no abnor&no rsk fctr In the modelling tools I see you can have a choice, but I can’t see how the choice supports multiple terminologies. I see that it does support a choice of a terminology & Free text. Is there a “standard” way of saying a data point may be represented by one of 3 terminologies/codes systems? Or is this something the tooling deliberately stops you doing? Thanks in advance Dave Barnet Interoperability Lead Interoperability Specifications Health & Social Care Information Centre NHS in England _______________________________________________ openEHR-technical mailing list openEHR-technical@lists.openehr.org<mailto:openEHR-technical@lists.openehr.org> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org _______________________________________________ openEHR-technical mailing list openEHR-technical@lists.openehr.org<mailto:openEHR-technical@lists.openehr.org> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
_______________________________________________ openEHR-technical mailing list openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
