But then if we want to communicate this coded string outside from our openEHR system would be impossible to know 100% what it is. I don't get the point of having 'mappings' (which could also be done by a terminology service) and not having a 'qualifiers' or whatever.
Doesn't Loinc also allow post-coordination? 2011/3/21 Thomas Beale <thomas.beale at oceaninformatics.com>: > > 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 > > > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > >
