Diego, that's what the code_string attribute is for - it carries a single concept code or a post-coordinated code-string, or 'code phrase', generated by the terminology service. It is not the job of an openEHR system to 'understand' these strings, just to store them faithfully. Currently (AFAIK) only SNOMED has a properly defined syntax for post-coordinations, but the code_string could carry any string expression expressing a post-coordination from any terminology.
- thomas On 21/03/2011 10:42, Diego Bosc? wrote: > Hello, > > So I was looking to the Text package in the data_types specification > and I was wondering how is supposed a DV_CODED_TEXT to handle a > post-coordinated term (from for example SNOMED). If I understand > correctly is something that relies in a supposed terminology service? > isn't doing that making the system dependent of a technology or how a > system understands some terminology queries? Can someone provide a XML > snippet for the example ?foot has-laterality left?? > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > * * -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20110321/90ba3bd7/attachment.html>
