Which code in code_string symbol for DV_ORDINAL?

2011-03-16 Thread Moretti Leonardo 
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
valueElement name/value
/name
value xsi:type=DV_ORDINAL
value5/value
symbol
valueDescription 5/value
defining_code
terminology_id
valuelocal/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 at 
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

Which code in code_string symbol for DV_ORDINAL?

2011-03-16 Thread Thomas Beale 

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
 valueElement name/value
 /name
 value xsi:type=DV_ORDINAL
 value5/value
 symbol
 valueDescription 5/value
 defining_code
 terminology_id
 valuelocal/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 at
 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

future ADL-versions

2011-03-16 Thread Thomas Beale 

Hi Bert,

I hope to get back on the spec in the next couple of weeks. With respect 
to your specific question below, can you be a bit more precise? There 
are ways to express this kind of thing, but we need to be clear on 
distinguishing references to:

* elements in the same archetype - as in a rule like:
  o /path/to/systolic/pressure/value 
/path/to/diastolic/pressure/value
* elements in data elsewhere in the same EHR like:
  o $date_of_birth:ISO8601_DATE ::= query(ehr, date_of_birth)
  o this is still being finalised, so don't depend on it;
however it is the left hand side that matters, i.e.
$date_of_birth
* environmental values, like
  o $current_date
  o $current_time

Some of this is still being finalised, but the general syntax will look 
like Xpath and the object model will be what you would expect from that.

- thomas

On 10/03/2011 15:48, Bert Verhees wrote:
 Hi,

 I am sorry, but I am to busy to read all the discussions on future
 ADL-versions.
 So, now I have a small question, which possible is already explained,

 Is it possible to write conditional constraints in future ADL?

 The question is about implementing care-protocol into an archetype.

 For example, if blood-pressure is  200, force to use another entry, for
 example also look at heartbeat

 Is there any idea when this new specifications will be in final version?

 Thanks
 Bert




 ___
 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/20110316/11d179c4/attachment.html