Dirk
The idea of an order entry is that it is an instruction. The class
INSTRUCTION is described in the openEHR reference model
RM.Composition.Content.Entry package. Tom and I have spent a day last week
reviewing this as we have been under some pressure to do so. The instruction
has a number of features - state (as an internal state machine) and an
action specification as a STRUCTURE. It is this class that would be used to
specify exactly what is ordered, the state would describe whether it has
been acted on and completed.
It would be good to involve you in this detailed debate if you are
interested. I have been working with the Pathologists on this area for some
time and it would be useful to see what others need from this. Remember, if
the order is to go beyond the local machine as part of an EHR, it has to be
part of a composition in an extract. Alternatively, and more commonly at
present, the order may go as a message or a paper order.
we do not, at present, have the capability of archetyping instructions but
this is why we are reviewing this area of work. Also, South Australia
University have been working on the state machine required to manage
instructions in the EHR for some time - and we are moving in that
direction - allowing an external workflow engine to utilise the EHR if
required.
Finally, we have a set of codes for laboratory tests in Australia that
Michael Legg can help you with if that is useful.
I look forward to hearing from you.
Yours sincerely, Sam Heard