The Ocean Terminology server takes care of archetype bindings to SNOMED terminology. There is no free version of OTS however.
Regards, O. Pishev, Ocean Informatics ----- Original Message ----- From: "Ruth Kidd" <[email protected]> To: "For openEHR technical discussions" <openehr-technical at openehr.org>; <ian at mcmi.co.uk> Sent: Saturday, December 16, 2006 12:39 AM Subject: Re: Suggestions re Term binding in Archetype Editor >>> This would be much easier within the editor if the Term bindings screen >>> displayed the node name as well as the Node ID, as it is easy to forget >>> which local term you are trying to bind by the time you have rummaged >>> around >>> in Snomed for a bit!! > > I would definitely second this! > > -- > Regards > > Ruth Kidd > > HL7 Messaging Practitioner > Communications and Messaging > NHS Connecting for Health > > Tel: +44 (0)113 280 6599 > Mob: +44 (0)7798 781427 > > Ruth.Kidd at nhs.net > http://www.connectingforhealth.nhs.uk > > NHS Connecting for Health supports the NHS in providing better, safer > care by delivering computer systems and services which improve the way > patient information is stored and accessed. > > > Ian McNicoll wrote: >> >> >> Hi, >> >> I am currently working my way slowly through the Scottish Cardiac >> dataset, >> converting it to archetypes as proof-of-concept, using the OE editor. >> >> Term binding (to SNOMED) will be a crucial aspect from our perspective, >> especially binding local (interface) terms to SNOMED concepts. >> >> This would be much easier within the editor if the Term bindings screen >> displayed the node name as well as the Node ID, as it is easy to forget >> which local term you are trying to bind by the time you have rummaged >> around >> in Snomed for a bit!!. The "Choose Nodes" dialog might also be a little >> easier if the Node parent name and Node name were included. When only the >> node name is visible this can cause confusion if similar local terms are >> used for different nodes e.g. "Not known". >> >> Finally in the ADL, I think it would be very helpful to be able to >> include >> the text of the Bound term text as well as its code. This would allow >> much >> easier checking for errors and documenting >> >> I have done this by enclosing the bound term text in [] for now. >> >> e.g. >> term_binding = < >> ["SNOMED-CT"] = < >> items = < >> ["at0000"] = <[SNOMED-CT::229819007 [Tobacco >> use and Exposure]]> >> ["at0006"] = <[SNOMED-CT::?Non Tobacco >> user]> >> ["at0009"] = <[SNOMED-CT::]> >> ["at0011"] = <[SNOMED-CT::[Ex-smoker] >> 8517006]> >> ["at0012"] = <[SNOMED-CT::[Current >> non-smoker] 160618006]> >> >> Regards, >> >> Ian >> >> _______________________________________________ >> openEHR-technical mailing list >> openEHR-technical at openehr.org >> http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > > > ********************************************************************** > Information in this message may contain confidential and privileged > information. If you are not the intended recipient please accept our > apologies; please do not disclose, copy or distribute information in > this e-mail or take any action in reliance on its contents: to do so > is strictly prohibited and may be unlawful. Please inform us that this > message has gone astray before deleting it. Thank you for your > co-operation. > > NHSmail is used daily by over 100,000 staff in the NHS. Over a million > messages are sent every day by the system. To find out why more and > more NHS personnel are switching to this NHS Connecting for Health > system please visit www.connectingforhealth.nhs.uk/nhsmail > ********************************************************************** > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical _______________________________________________ openEHR-technical mailing list openEHR-technical at openehr.org http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
