Hi Ian I like the idea of a web service - this fits very nicely with the idea of a service oriented architecture where you can pick and choose what services that you want to use. A smart service like this would cache on the local machine or server so that only updates/or new interactions would pause the system (although with enough grunt at the other end you might not notice the pause - done a google search lately!?).
Broadband internet is going to become a necessity and not a luxury at some stage and failover support for these kind of services will also become a necessity. Regards Hugh Dr Hugh Leslie Ocean Informatics Pty Ltd M: 0404 033 767 E: [EMAIL PROTECTED] > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Ian Haywood > Sent: Monday, 19 June 2006 6:48 PM > To: General Practice Computing Group Talk > Subject: Re: [GPCG_TALK] NPS drug interaction project > > > > James Reeve wrote: > > NPS is convening an expert panel to review existing drug > interaction > > decision support in prescribing and dispensing software in > Australia. > > If shortcomings are identified, the panel will review a range of > > reference sources to identify the most appropriate one for > use in the > > Australian setting. NPS is not developing drug interaction > information > > knowledge bases - there are a number of quality information > resources > > already available in Australia and overseas. > thanks for that clarification. > > > NPS is also investigating the feasibility of offering drug > interaction > > decision support via a Web service, using the drug interaction > > reference > This presents the same usability problem: double entry of > drugs, which will slow your uptake severely, people will > always use the interaction data built into the EHR where they > have already entered drugs. > > > source identified by the expert panel. The Web service would be > > maintained by NPS, while the drug interaction information would > > continue to be maintained by the developers of the information. By > > offering drug interaction information as a Web service, NPS > hopes to > > create an opportunity for interested vendors to link prescribing or > > dispensing software directly to a single source of quality drug > > interaction information. Users can then choose whether they use > > existing drug interaction decision support, or use the > content delivered by NPS (or both). > Ok, I see what you are getting at. However I fear few GPs > would have internet access fast and reliable enough for this > to be popular. > They would find their computer pauses for every script as it > checks with the NPS server, you'll find most people won't accept this. > And they especially won't accept not being able to prescribe > when their connection goes down, so they'll turn it off the > first time that happens, and probably won't turn it on again. > > FWIW I would suggest blessing a datasource, [a very useful > excerise in and of itself] and then negotiating a nationwide > licence for it, for vendors to incorporate the data into > their programs. > > Ian > _______________________________________________ > Gpcg_talk mailing list > [email protected] > http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk _______________________________________________ Gpcg_talk mailing list [email protected] http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
