On Sat, 5 Jul 2003, Tim Cook wrote: ... > > For the purpose of illustrating the embedding of terminology within an > > EMR (which was my purpose in mentioning this fragment of TORCH exported > > record), I thought it sufficient to show just a small example. > > You were incorrect as there was no example of any standard terminology > embedding at all.
Tim, Yes, I know that TORCH does not support SNOMED CT at this time. However, TORCH does come with a terminology, which perhaps is a mixture of ICD and TORCH-specific "terms". > There "may" have been an example of of the use of a coding system (ICD) > elsewhere in the export. ok. > > --> In this example, "social history" is one of the "terminology" used by > > TORCH. Will TORCH reconcile this "social history" term with similar > > terms (if any) in SNOMED CT ? > > Hmmmmmmm....that's top secret stuff. <vbg> Keep it top secret if you prefer. ... > ...and your point is? My point is that this is a common challenged faced by multiple projects. Keep your thoughts top-secret if you like. Sorry that I even asked. > > Just so that you won't mistakenly conclude that I am singling out TORCH, > > GnuMed, OSCAR, TkFP, and other EMR's will also have to address the same > > challenge. > > I see that the OIO project is missing from this list, do you (or > whomever is writing the OIO code) not intend to, "...address the same > challenge."? I said in a prior message that OIO is not an EMR and does not include a medical terminology. see: http://www.mail-archive.com/[EMAIL PROTECTED]/msg08710.html Thus, the OIO project will continue to address a different challenge. Nandalal Gunaratne raised this issue back in May 2003 and I posted my response on the Open-Outcomes list. Here is the transcript of our discussion, fully in the open for public review and comment: http://sourceforge.net/mailarchive/message.php?msg_id=4945053 http://sourceforge.net/mailarchive/message.php?msg_id=4947844 http://sourceforge.net/mailarchive/message.php?msg_id=4954516 > > Your willingness to share your thoughts on this can help many > > of us plan a better strategy. > > Really? How so? If your proposed approach has any clear flaws, then describing it at this point can make its flaws visible and save you and others (with same or similar ideas) some time and grief. On the other hand, if your approach seems reasonable and workable, then other groups can copy your approach and save themselves much grief and wasted time. Either way, making your plans clear to others makes it more likely that individuals and groups can become interested in working with / working on TORCH. Keeping secrects will not lead to a sustainable software project, in my humble opinion. You have already decided to provide source code through GPL and free download. Why keep your design and ideas secret? :-) Best regards, Andrew --- Andrew P. Ho, M.D. OIO: Open Infrastructure for Outcomes www.TxOutcome.Org
