Hello Luis, I think having available a terminology service is some kind of a prerequisite (which I don't agree with). I think openEHR should probably assume the IHTSDO postcoordination syntax for these cases. It would be interesting to know if someone has used or is planning to use this syntax for other terminologies.
2015-04-27 13:49 GMT+02:00 Luis Marco <luismarco at gmail.com>: > Hi, > > I am trying to annotate a set of archetypes with SNOMED-CT. I have noticed > that in the archetype editor, when I introduce a postcoordinated > expressions, the editor deletes the bars and creates a continuous > alphanumeric string. Do you know if postcoordinated expressions can be set > in the ontology section of the archetype? What are current approaches to > overcome this? > > A solution could be to insert an id representing the postcoordinated > expression and resolve it in my terminology server. However, this would hide > knowledge to other implementations based on that archetype outside the > domain of my server. > > > > Example: Let?s assume (without caring about the correctness of it) that we > had an archetype for the concept ?Laparoscopic appendectomy? and we annotate > at000 with (80146002|Appendectomy|:424226004|Using > device|=86174004|Laparoscope|). > > The result in the ADL is: ["at0000"] = > <[SNOMED-CT::80146002Appendectomy424226004Usingdevice86174004Laparoscope]> > > > Thanks, > > Luis > > > _______________________________________________ > openEHR-implementers mailing list > openEHR-implementers at lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr-implementers_lists.openehr.org
