Geoff, there are aspects of what you say that I both agree and disagree with. In the case of the users needs, they need to specify them and have them delivered, so I don't have any problem with you saying this type of user needs these analytics and concomitant services. BUT it is not up to me to define what computing services are needed to create what changes that are desirable - that's up to you the practitioners.
With a different hat on (the research into delivering ANY form of EMF) I have to ask different questions and provide a different CLASS of answers. It seems that when I talk with this hat I may not make the distinction that I have shifted hats. Nevertheless in this hat wearing state I don't care about what any particular practitioner/CEO/client wants but rather how do I provide the class of services that suits all their needs. The physician roles that I have defined tell me that the key class of service is analytics and I wish to call it Generalised Data Analytics (GDA). It is a key class because it supercedes "retrieval', that is once you get GDA you have retrieval for free. With this hat I don't care about all the items in your message - but that is not to deny their importance in the ultimate deliverables. I do disagree with your last point > Don't collect data or analysis data unless you are able to implement > change... Without certain types of data telling you something needs fixing you won't know it needs to change. This is why I have framed the maxim stated in my previous email - "the System has to allow the posing of any question that is answerable from the stored data", and that includes all the questions you don't think of asking when you design your system. cheers (from hawaii) jon -- Jon Patrick Chair of Language Technology Australian R&D Centre for Health Informatics School of Information Technologies University of Sydney Quoting Geoff Sayer <[EMAIL PROTECTED]>: > It needs to be more than just graphs to the CEO... the CEO is not > treating > the patients in the ER. The practice manager is not treating the > patients in > the GP consulting room. The epidemiologist is getting caught up in the > numbers and looking to do the monthly report. Wouldn't it be better that > once a threshold of something occurs eg. antibiotic for URTI greater > than > 20% (not the best example) we implement our electronic reminder for > practitioners in the clinical application that URTIs don't need > antibiotics... the value of the information is actually implementing > change. > > Don't collect data or analysis data unless you are able to implement > change... > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > On Behalf Of Jon David Patrick > Sent: Thursday, 5 April 2007 9:30 a.m. > To: General Practice Computing Group Talk > Subject: Re: [GPCG_TALK] Ultimate EMR or EMF - waiting room bar graphs > > This is something that we are working on at SWAHS and it is supposed to > be > part of the "CEO Dashboard". There's no good reason why it can't be > delivered - data quality excepted. > jon > -- > Jon Patrick > Chair of Language Technology > Australian R&D Centre for Health Informatics > School of Information Technologies > University of Sydney > > > Quoting john hilton <[EMAIL PROTECTED]>: > > > On Thursday 05 April 2007 7:01 am, Elizabeth Dodd wrote: > > > On Thursday 05 April 2007 08:58, Tim Churches wrote: > > > > Mind you, I think that *every* health informatics project or > product > > > > and *every* deployment of a clinical information system in a > > hospital or > > > > health system should have a population health and/or clinical > > > > epidemiologist in a key role on the team to make sure that > > opportunities > > > > for useful and valuable secondary, aggregate use of information > are > > not > > > > missed, as they routinely and repeatedly are at present. > > > > > > a common question is "is this going round doc?" and that can't be > > answered > > > except out of my head at present. there is no added input from the > > other 5 > > > docs here on that point > > > obviously if each one of saw one person with a rare condition, we'd > > still > > > think it was rare, but 6 could still make a significant cluster. > > > > > > I'd love to see a constantly updating display in the waiting room, bar > > graphs > > and all, today's diagnoses, or this week's diagnoses. > > jh > > -- > > There's a crowd outside > > That's screaming for your blood > > They want action now > > From a man whose name is mud > > > > Split Enz - > > No Mischief (N Finn) > > _______________________________________________ > > Gpcg_talk mailing list > > [email protected] > > http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk > > > > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > _______________________________________________ > 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 > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. _______________________________________________ Gpcg_talk mailing list [email protected] http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
