Koray Atalag wrote: > Hi there, > > I had a similar issue lately and just came up with an idea for > local/custom terminology bindings - i.e. linking at codes to external > terminologies not formally defined in UMLS or elsewhere. > > My problem was to bind terms to latest version of SNOMED through which > I access from UMLS. In the Ocean Archetype Editor when you want to add > a new terminology, a list is presented (possibly taken from UMLS > knowledge sources) which contains only SNOMED CT 2002 version. So I > added SNOMED_CT manually via text editor: > > ontology > terminologies_available = <"MST2", "UMLS", "SNOMED_CT"> > > NOTE: editor does not like spaces in term name!
Hi Koray, that's because it is illegal in the openEHR specification - TERMINOLOGY_ID type in the Identification packge in the Support IM. Also note that the only names that can be used are (crrently) the UMLS names - see the spec. Also the version/revision should be indicated in () after, e.g. SNOMED_CT(2008v2)::123456 or however they are identifying it. We need to determine how UMLS is naming all of these variants / releases. > > So custom/local terminologies can be handled this way and the > implementation will be left to developers....BUT this may result in > different implementations which may render interoperability in the > long run.... > > So I suggest a sub-section within ontology section where used > terminologies are declared explicitly; i.e. "umls": 2008AA version of > NLM UMLS knowledge sources. Perhaps an URI and other details can be > specified (i.e. WSDL). I think it is easier for the community to agree > on such a naming convention. you can already do this - umls(2008AA)::123456 etc - thomas beale
