Hi,

I started wondering about different representations of ISM_TRANSITIONs of
the ism_transition attribute in the ACTION archetypes. I found that the
below example:

            ISM_TRANSITION matches {
                current_state matches {
                    CODED_TEXT matches {
                        code matches {[openehr::524]}
                    }
                }
                careflow_step matches {
                    CODED_TEXT matches {
                        code matches {[local::at0001]}        -- Planned
                    }
                }
            }
            ISM_TRANSITION matches {
                current_state matches {
                    CODED_TEXT matches {
                        code matches {[openehr::524]}
                    }
                }
                careflow_step matches {
                    CODED_TEXT matches {
                        code matches {[local::at0004]}        -- Requested
                    }
                }
            }

could be compressed into this:

            ISM_TRANSITION matches {
                current_state matches {
                    CODED_TEXT matches {
                        code matches {[openehr::524]}
                    }
                }
                careflow_step matches {
                    CODED_TEXT matches {
                        code matches {[local::at0001, -- Planned
                                               at0004]}         -- Requested
                    }
                }
            }

The examples have the same semantic meaning. However, at data entry the
second example would mean that a choice must be made concerning the
careflow_step, i.e. either at0001 or at0004. Should the archetype editors
support both examples? The first example is the only one I've seen in
archetypes...

Regards,

Mattias
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20061031/157cba55/attachment.html>
-------------- next part --------------
_______________________________________________
openEHR-technical mailing list
openEHR-technical at openehr.org
http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical

Reply via email to