Hi Thomas, do you know if there is a formal way of how RefSets (=the resulting Snomed CT codes etc.) and the RefSet query (=the query on Snomed CT to get to the RefSet) are expressed and shared? Similar to what is described here but based on RefSets: http://www.openehr.org/wiki/display/term/Ocean+Terminology+Query+Language+%28TQL%29
I agree that RefSets are a good way forward, but they need to be available, reusable and sharable, etc. Sebastian Thomas Beale wrote: > * > * I attended the IHTSDO meeting just finished in Copenhagen. Things > look pretty good for where SNOMED CT is going generally - the RF2 > technical infrastructure seems relatively well designed. There is a > lot of activity in content modeling, the IHTSDO workbench and many > other areas relevant to openEHR. Converely, I believe openEHR will be > very important to make SNOMED CT work in many places, since it will be > via archetypes, templates and associated ref sets that information > systems will be able to connect to terminology in a disciplined way. I > believe that ref sets are the future of SNOMED CT (and any terminology > for that matter) in use in real systems. > > I was asked to present a view from openEHR about 'terminology > binding', i.e. connecting terminology and information models. My > presentation is on this page > http://www.openehr.org/wiki/display/term/Terminology+Binding > or see the following direct links: > > * PDF - > > http://www.openehr.org/wiki/download/attachments/5997267/openEHR_term_binding_IHTSDO_april_2010.pdf > * PPTX - > > http://www.openehr.org/wiki/download/attachments/5997267/openEHR_term_binding_IHTSDO_april_2010.pptx > > I hope this is useful. I will continue to document IHTSDO-related > thoughts on the openEHR wiki, and I encourage others to do the same. > > - thomas beale > > ------------------------------------------------------------------------ > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20100506/f89908db/attachment.html>
