Leonardo,

In this case, since terminology_id = 'local', code_string will be some 
string like 'at0.13' (based on your extract below). If the 
terminology_id had been SNOMEDCT_2009_01_01 then code_string has to be a 
SNOMED CT code... and so on.

- thomas

On 16/03/2011 17:40, Moretti Leonardo wrote:
> I'm wondering how to set code_string value for a DV_ORDINAL.
>
> Having a DV_ORDINAL a structure like this:
> <items archetype_node_id="at0004.1" xsi:type="ELEMENT">
> <name>
> <value>Element name</value>
> </name>
> <value xsi:type="DV_ORDINAL">
> <value>5</value>
> <symbol>
> <value>Description 5</value>
> <defining_code>
> <terminology_id>
> <value>local</value>
> </terminology_id>
> <code_string>???</code_string>
> </defining_code>
> </symbol>
> </value>
> </items>
>
> which information should I use in code_string of DV_ORDINAL element? The 
> integer value or the atxxxx
> code?
>
> For example, if I defined an ordinal element as
> ELEMENT[at0004.1] occurrences matches {0..1} matches {    -- Igiene Personale
>       value matches {
>           5|[local::at0.15],     -- Description 5
>           4|[local::at0.14],     -- Description 4
>           3|[local::at0.13],     -- Description 3
>           2|[local::at0.12],     -- Description 2
>           1|[local::at0.11]     -- Description 1
>       }
> }
>
> has code_string to be set with at0.1x codes or with integer  values (1, 2, 3, 
> 4, 5)?
>
> Thanks for your help!
> Regards
>
> leo
>
>
> _______________________________________________
> openEHR-technical mailing list
> openEHR-technical at openehr.org
> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
>


-- 
Ocean Informatics       *Thomas Beale
Chief Technology Officer, Ocean Informatics 
<http://www.oceaninformatics.com/>*

Chair Architectural Review Board, /open/EHR Foundation 
<http://www.openehr.org/>
Honorary Research Fellow, University College London 
<http://www.chime.ucl.ac.uk/>
Chartered IT Professional Fellow, BCS, British Computer Society 
<http://www.bcs.org.uk/>
Health IT blog <http://www.wolandscat.net/>


*
*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20110316/a29fdfe9/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ocean_full_small.jpg
Type: image/jpeg
Size: 5828 bytes
Desc: not available
URL: 
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20110316/a29fdfe9/attachment.jpg>

Reply via email to