Thomas,

All the information in both the EHRsystem and the prescription on  
paper or electronicly is the same archetype/template.
Only the intention is different.
In the former it is about documentation.
The latter is the prescription order that was documented.

Can we agree that documentation is within the scope of OpenEHR (and  
EN136060) and that the electronic prescription as an order is not?
And that the electronic prescription as an order is THE scope of  
HL7v2 and HL7v3 messages.

In my view this subtle distinction in scope indicates where OpenEHR/ 
CEN and HL7 are active and where they meet and are able to co-operate.

When we agree about the scopes. I suggest that we revisit the present  
scope statements of OpenEHR and EN13606 and make things more explicit.

Gerard


--  <private> --
Gerard Freriks, arts
Huigsloterdijk 378
2158 LR Buitenkaag
The Netherlands

T: +31 252 544896
M: +31 654 792800


On 17-sep-2005, at 1:19, Thomas Beale wrote:

>
>
>> Thomas,
>>
>> When we agree that the scope of OpenEHR is to document the  
>> professional opinions and the facts on which these are based then:
>>
>>
>>> An instance of an Instruction documents roughly what might be in  
>>> a prescription
>>>
>>
>>
>> But it is semantically  NEVER the same.  It is the documentation  
>> of the process that lead to a prescription. It is NOT a prescription.
>>
>
> clearly not. A prescription is a piece of paper in my hand from  
> your doctor's rooms, containing an order for a medication from a  
> pharmacy, and instructions to me (to be typed or printed at the  
> pharmacy). But, if you wanted to generate such a physical (or  
> electronic) document from an openEHR Instruction, all the  
> information would be there (the only exception would be if you  
> wanted to indicate a particular pharmacy to go to).
>
> - thomas

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.openehr.org/mailman/private/openehr-clinical_lists.openehr.org/attachments/20050917/81693c08/attachment.html>

Reply via email to