> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> > <html> > <head> > <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> > </head> > <body bgcolor="#ffffff" text="#000000"> > Hi Bert<br> > <br> > The CODE_PHRASE is the space for keeping the link from the > DV_CODED_TEXT (or any other coded information) and the terminology from > which it has arisen. The text of the DV_CODED_TEXT (inherited from > DV_TEXT) is where you display what the terminology provides as text in > that language for that code. These <i>have</i> to be in tune.<br> > <br> > If the user edits the textural display then the CODE_PHRASE can only be > a TERM_MAPPING, as the code_string is no longer defining of the text.<br> > <br> > Ocean's terminology server (which provides access to LOINC and SNOMED > with ICD_10 on the way) has a well developed service interface. Hugh > Grady will provide documentation for this as it works with the Template > Designer - it is based on CTS but has a different approach to meet the > needs of archetypes. There is a CTS (Common Terminology Service) > specification from HL7 - which is moving to version 2. Russel Hamm is > the guru.<br> > <br> > I hope this helps, Sam<br>
Thanks, Sam, it sure gives some places to look at. The only remaining problem will be that I will write a terminology-service on my own, because I need it, and good or bad, but probably not in sync with further developments on OpenEhr-specs. But that is where we have versions for, isn't it? ;-) I didn't know about CTS, I will look at the HL7-site to find more information regards Bert Verhees _______________________________________________ openEHR-technical mailing list openEHR-technical at openehr.org http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
