I couldn't agree more.

 From my perspective I would like to advocate that this DCM/archetype  
takes the self-registration of drug use by the patient/ citizen into  
account. I really think that for the coming years self-registration  
will be the fastest route to a drug use registration that provides  
the best possible reflection of the reality. Also if we don't come up  
with a good solution that allows citizen involved, other parties, who  
might have less interest in open standards,  could take over that  
domain.
Since I've been trying to work this out for quite some time now, I  
finally took the time to write down my thoughts on this topic. For  
those of you interested it can be found here:
http://www.vivici.nl/ 
a_three_level_model_for_the_registration_of_drug_use/

Maybe this can be of some help in the discussions coming...

Cheers,

Stef


Op 23-nov-2008, om 20:21 heeft Sam Heard het volgende geschreven:

> Thanks William.
>
>
>
> So lets do a medication archetype that contains all the standard  
> information constructs required to do this, and CCD and CCR. We can  
> include Microsoft if we want as well just to have the world  
> reasonably covered off.
>
>
>
> The point here is there are a plethora of specifications being  
> developed and no one knows quite what they mean or how to use them.  
> Lets do it in openEHR and try to nail it down.
>
>
>
> Cheers, Sam
>
>
>
> From: openehr-clinical-bounces at openehr.org [mailto:openehr-clinical- 
> bounces at openehr.org] On Behalf Of Williamtfgoossen at cs.com
> Sent: Sunday, 23 November 2008 7:15 AM
> To: openehr-clinical at openehr.org
> Subject: Re: Top 10 of Detailed Clinical Models
>
>
>
> Hi Thomas,
>
> The Netherlands is implementing the exchange of medication messages  
> in order to achieve the full list of a patient of current and past  
> medications and prescriptions.
> Current pharmacy and gp systems have a DSS system in place that  
> tackles interactions.
>
> It is probably not perfect, but coming in the direction you suggest.
>
> I agree that this is an interesting topic to tackle further and  
> harmonize.
> A lot is already put into the HL7 CEN ISO CDISC and IHTSDO  
> harmonization work, where pharmacy is now a priority topic.
>
> William
>
> In a message dated 22-11-2008 12:20:57 W. Europe Standard Time,  
> thomas.beale at oceaninformatics.com writes:
>
>
>
> Gerard Freriks wrote:
> >When medication is considered be aware that there is already a huge
> >amount of requirements collection in HL7v2, HL7v3 space and in
> >European standards.
> >I think that with a limited amount of work the Clinical Models can be
> >produced and discussed.
> >In addition we need this all over the world and there is one European
> >project needing it : epSOS.
> >
> *
> I would suggest that the 2 key requirements today are:
> a) being able to merge medication lists for a given patient from
> multiple sources
> b) being able to handle entries in the list that were prescribed (and
> that are recorded in some structured, standard way) and medications  
> that
> the patient says they are on already, including non-prescription and
> herbal etc.
>
> Being able to do this would generate a list that can actually be used
> for decision support (interactions testing) for a new prescription.
>
> I don't think either of these is dealt with directly by any of the
> current standards.
>
> - thomas beale
>
>
>
> Sincerely yours,
>
> dr. William TF Goossen
> director
> Results 4 Care b.v.
> De Stinse 15
> 3823 VM Amersfoort
> the Netherlands
> email: Results4Care at cs.com
> phone + 31654614458
> fax +3133 2570169
> www.results4care.nl
> Dutch Chamber of Commerce number: 32133713
>
> _______________________________________________
> openEHR-clinical mailing list
> openEHR-clinical at openehr.org
> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.openehr.org/mailman/private/openehr-clinical_lists.openehr.org/attachments/20081124/9cb013ed/attachment.html>

Reply via email to