value as a C_ORDINAL?

Implementers (archive)
1

Hi everybody,

I'm working with OpenEHR archetypes from this site
"http://www.openehr.org/svn/knowledge/archetypes/dev/html/index_en.html",
and I can't interpret the following section:

ELEMENT[at0.17] occurrences matches {0..1} matches { -- Volume
value matches {
    0|[local::at0.18], -- Not heard
    1|[local::at0.19], -- Variable
    2|[local::at0.20], -- Soft
    3|[local::at0.21], -- Normal
    4|[local::at0.22]; -- Loud
    0 -- assumed value
  }
}

The problem is that an openehr_ELEMENT, has the property "value", and
according to OpenEHR specification, it can only take a value of type
DATA_VALUE, so, I don't understand why at this example this property
take as value a C_ORDINAL.

How should it be?
  Maybe..

  ELEMENT[at0.17] occurrences matches {0..1} matches { -- Volume
value matches {
  DV_ORDINAL matches {
    Property…

Thank you for your help!

2

Hi Cati,

The openEHR Archetype profile
(http://www.openehr.org/releases/1.0.1/architecture/am/openehr_archetype_profile.pdf)
defines this short syntax...see Chapter 5.2.

Cheers
Sebastian

Cati Martínez wrote:

3

Cati,

Have a look at http://www.openehr.org/releases/1.0.1/architecture/am/openehr_archetype_profile.pdf section 5

  • thomas beale

Cati Martínez wrote:

(attachments)

OceanCsmall.png

4

Hi,

Then, if I'd like to express it without any simplification, I could do
it as follows:

ELEMENT[at0.17] occurrences matches {0..1} matches {
value matches {
    DV_ORDINAL matches {
       value matches {0}
       symbol matches {
            DV_CODED_TEXT matches {
                defining_code matches {[local::at0014]} -- no heartbeat
            }
       }
    }
   DV_ORDINAL matches {
     value matches {1}
     symbol matches {
         DV_CODED_TEXT matches {
             defining_code matches {[local::at0015]} -- less than 100 bpm
         }
     }
   }
   .....
   ....
}

After that, I have another question :), the property "value" of
"ELEMENT" according to the OpenEHR is of type DATA_VALUE but with
occurrences {0..1} and here I have more than one occurrence of type
DV_ORDINAL... Should I change the occurrence to {0..*} for my
implementation?

Thank you again.

Cati,

Have a look at http://www.openehr.org/releases/1.0.1/architecture/am/openehr_archetype_profile.pdf section 5

- thomas beale

Cati Martínez wrote:
Hi everybody,

I'm working with OpenEHR archetypes from this site
MailScanner has detected a possible fraud attempt from
"www.openehr.org" claiming to be
"http://www.openehr.org/svn/knowledge/archetypes/dev/html/index_en.html",
and I can't interpret the following section:

ELEMENT[at0.17] occurrences matches {0..1} matches { -- Volume
value matches {
    0|[local::at0.18], -- Not heard
    1|[local::at0.19], -- Variable
    2|[local::at0.20], -- Soft
    3|[local::at0.21], -- Normal
    4|[local::at0.22]; -- Loud
    0 -- assumed value
  }
}

The problem is that an openehr_ELEMENT, has the property "value", and
according to OpenEHR specification, it can only take a value of type
DATA_VALUE, so, I don't understand why at this example this property
take as value a C_ORDINAL.

How should it be?
  Maybe..

  ELEMENT[at0.17] occurrences matches {0..1} matches { -- Volume
value matches {
  DV_ORDINAL matches {
    Property…

Thank you for your help!

5

Cati Martínez wrote:

Hi,

Then, if I'd like to express it without any simplification, I could do
it as follows:

ELEMENT[at0.17] occurrences matches {0..1} matches {
value matches {
    DV_ORDINAL matches {
       value matches {0}
       symbol matches {
            DV_CODED_TEXT matches {
                defining_code matches {[local::at0014]} -- no heartbeat
            }
       }
    }
   DV_ORDINAL matches {
     value matches {1}
     symbol matches {
         DV_CODED_TEXT matches {
             defining_code matches {[local::at0015]} -- less than 100 bpm
         }
     }
   }
   .....
   ....
}

After that, I have another question :), the property "value" of
"ELEMENT" according to the OpenEHR is of type DATA_VALUE but with
occurrences {0..1} and here I have more than one occurrence of type
DV_ORDINAL... Should I change the occurrence to {0..*} for my
implementation?

Thank you again.
  

I don't think so. It means that in an instance of this archetype you
would only document a maximum of one of these DV_Ordinals, either "no
heartbeat" OR "less than 100bpm" - but not both

6

Cati Martínez wrote:

After that, I have another question :), the property "value" of
"ELEMENT" according to the OpenEHR is of type DATA_VALUE but with
occurrences {0..1} and here I have more than one occurrence of type
DV_ORDINAL... Should I change the occurrence to {0..*} for my
implementation?

*you could, but its not a good idea - you will be out of sync with the
rest of the openEHR world, and not interoperable. Instead, you need to
use the higher level structures like ITEM_TREE and ITEM_LIST to give you
multiplicity, as well as addressing - each Element in an ITEM_LIST for
example as a unique [at-code] which enables proper paths to be generated
to it.

let me know if you need more details.

- t