Hi Diego,
We?re intending to use the IHTSDO syntax (or the idea) for semantic annotation of computational physiology models - using other domain specific languages like CellML<http://www.cellml.org/>, FieldML<http://physiomeproject.org/software/fieldml/about>, SBML etc. There are semantic tools like SemGen<http://sbp.bhi.washington.edu/projects/semgen> or openCOR<http://www.opencor.ws/> which support linking model items to external terminology/ontology similar to Archetypes. The idea is to couple clinical data and related physiological models to create personalised/predictive decision support tools using shared knowledge resources and I think this syntax has a great merit. Cheers, -koray -----Original Message----- From: openEHR-technical [mailto:[email protected]] On Behalf Of Diego Bosc? Sent: Tuesday, 28 April 2015 8:08 p.m. To: For openEHR implementation discussions Cc: openeh technical Subject: Re: SNOMED-CT postcoordination support in ADL 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<mailto: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::80146002Appendectomy424226004Usingdevice86174004Laparosco > pe]> > > > Thanks, > > Luis > > > _______________________________________________ > openEHR-implementers mailing list > openEHR-implementers at lists.openehr.org<mailto:openEHR-implementers at > lists.openehr.org> > http://lists.openehr.org/mailman/listinfo/openehr-implementers_lists.o > penehr.org _______________________________________________ openEHR-technical mailing list openEHR-technical at lists.openehr.org<mailto:openEHR-technical at lists.openehr.org> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20150428/bcf60a22/attachment-0001.html>
