Hello,
I'm trying to add support for ITEM_TABLE in the Java Archetype Editor and I
have looked at the only archetype I've found that contains a data structure
like this. It is openEHR-EHR-OBSERVATION.tendon_babinski_reflexes.v1.adl and
it can be found here http://oceaninformatics.biz/archetypes/. When I
compared the attributes for the ITEM_TABLE in the data structures
specifications (found here
http://svn.openehr.org/specification/TRUNK/publishing/architecture/rm/data_structures_im.pdf)
with the ones that existed in the archetype I saw that the attributes had
nothing in common. Maybe someone can explain to me how the ITEM_TABLE look
like once and for all :-)
The archetype looks like this:
ITEM_TABLE[at0003] matches { -- structure
//// COMMENT: The attributes below adhere to the ITEM_TABLE that you get
when you create a table structure in the Ocean Archetype Editor, but I
haven't seen any of these three attributes specified anywhere. I would be
glad if anyone could point them out to me.
rotated matches {True}
number_key_columns matches {|1|}
rows cardinality matches {0..1; unordered} matches {
CLUSTER[at0050] occurrences matches {0..2} matches { -- row
items cardinality matches {7; ordered} matches {
//// COMMENT: This first element has a CODED_TEXT which contains coded terms
that are represented as columns in the Ocean Archetype Editor.
ELEMENT[at0012] occurrences matches {0..1} matches { --
row_head
value matches {
CODED_TEXT matches {
code matches {
[local::
at0011, -- Left
at0013] -- Right
}
}
}
}
//// COMMENT: This element and all succeding elements are represented as rows
in the Ocean Archetype Editor.
ELEMENT[at0004] occurrences matches {0..1} matches { --
Biceps
value matches {
ORDINAL matches {
value matches {
...
}
}
}
}
-------------------------
But in the specification the ITEM_TABLE it looks like this:
CLASS ITEM_TABLE
Purpose
Logical table data structure, in which columns are named and ordered. Some
columns
may be designated 'key' columns, containing key data for each row, in the
manner of relational tables. This allows row-naming, where each row
represents
a body site, a blood antigen etc. All values in a column have the same data
type.
Use Used to represent any data which is logically a table of values, such as
blood
pressure, most protocols, many blood tests etc.
MisUse Not used for time-based data, which should be represented with the
temporal
class HISTORY. The table may be empty.
Entry type.
Inherit ITEM_STRUCTURE
Attributes
0..1 columns: List<CLUSTER>
Physical representation of the table
as a list of CLUSTERs, each containing
the data of one column of the
table.
Hope someone can help me.
Regards,
Mattias Forss
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20060511/d69c8b7c/attachment.html>
