Sam wrote: >In developing an ontology for health record recordings - an archetype >ontology - I have come to the idea that there is a great deal of utility in >the idea of an 'action specification'. This is the part of an instruction >that says what to do - not when (or under what conditions) to do it. > >Let me give you an example: > > A medication order is an instruction: > > medication=Amoxycillin: dose=250mg: route=IV: >frequency=three times daily > > The action specification is: > > medication=Amoxycillin: dose=250mg: route=IV > > The when part is: > > frequency=three times daily
Indeed. A very valuable specification. Might I add that one of the strategic aims of a system is to reduce medical error risks. In the example above, one could imagine practical applications towards that goal by emphasising the specific action (for example, route=IV: route=not intra thecal), or some suitable alert. Better at the information model level than the application. Ahmad Risk - If you have any questions about using this list, please send a message to d.lloyd at openehr.org
