PubDrug.org Brief History

995
-1

Published on

An abbreviated history on the PubDrug project, by Stewart Brower, January 26, 2007

Published in: Health & Medicine, Technology
1 Comment
0 Likes
Statistics
Notes
  • After you got all the information on Fioricet, another point on your agenda should be the price for it. http://www.fioricetsupply.com resolves this problem. Now you can make the decision to buy.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

No Downloads
Views
Total Views
995
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
1
Likes
0
Embeds 0
No embeds

No notes for slide

PubDrug.org Brief History

  1. 1. PubDrug: A brief history Stewart Brower, MLIS, AHIP Associate Librarian University at Buffalo
  2. 2. Introductions <ul><li>Linda M Catanzaro </li></ul><ul><li>William J Loeffler </li></ul><ul><li>Amyjo Michnik </li></ul>
  3. 3. Short Timeline <ul><li>Early Fall 2006, SOPPS reports having trouble accessing drug information online </li></ul><ul><li>November 2006, PubDrug.org was launched </li></ul><ul><li>December 2006, Discussions with PIC committee about PubDrug </li></ul><ul><li>January 2007, two P4s on pharmacoinformatics rotations assigned to develop PubDrug monographs, carefully document their work </li></ul><ul><li>February 2007 – forward… </li></ul>
  4. 4. Pharmacoinformatics training <ul><li>HSL partners with SOPPS on Pharmacotherapy Information Center (PIC) </li></ul><ul><li>Pharmacoinformatics clerkship designed to demonstrate significant understanding of drug information and resources </li></ul><ul><li>HSL liaison to SOPPS </li></ul>
  5. 5. Basic project parameters <ul><li>Copyright/royalty-free information </li></ul><ul><li>Full drug monographs with detailed information, fully referenced </li></ul><ul><li>Open access/downloadable </li></ul><ul><li>Searchable, user-friendly </li></ul><ul><li>Simple interface for developers and users </li></ul><ul><li>“Just the right amount” of editorial control </li></ul><ul><li>Regularly updated </li></ul>
  6. 6. Why Wiki? <ul><li>Allows unlimited numbers of interested parties to collaborate and easily add/update drug monographs: </li></ul><ul><ul><li>Pharmacy faculty and students </li></ul></ul><ul><ul><li>Professional pharmacists </li></ul></ul><ul><ul><li>Medical librarians </li></ul></ul><ul><ul><li>Everyone else… </li></ul></ul><ul><li>Allows significant editorial controls without inhibiting “viral” expansion of content </li></ul>
  7. 7. Intended outcomes <ul><li>A copyright-free, royalty-free knowledge base of drug information </li></ul><ul><li>Freely accessible and filled with valuable, accurate information – A true alternative to vendor-based drug resources </li></ul><ul><li>Reasonable degree of editorial control (quality control, fact-checking, plagiarism-checking, vandalism prevention) </li></ul>
  8. 8. Ancillary outcomes <ul><li>Benefits for information literacy/information fluency instruction: </li></ul><ul><ul><li>Pharmacy & other health sciences students improve understanding of drug information sources, PubMed searching, journal articles, proper use of references and citation styles, copyright, EndNote, information technologies, database design… yadda yadda… </li></ul></ul><ul><ul><li>Students help to create content, for acknowledgement or course credit (or both) </li></ul></ul>
  9. 9. One other outcome <ul><li>Optimally, the knowledge base should be capable of being extracted easily and can be re-integrated into any number of various informatics initiatives: EMRs, pharmacy inventories and formularies, clinical-decision systems, patient education systems, etc. </li></ul>
  10. 10. That’s all! <ul><li>Now let’s hear what Amy and Bill have to say… </li></ul><ul><li>Stewart Brower, MLIS, AHIP </li></ul><ul><ul><li>[email_address] </li></ul></ul><ul><ul><li>AIM: StewartMBrower </li></ul></ul><ul><ul><li>716-829-3900 x111 </li></ul></ul><ul><ul><li>http://notes.smbrower.com (my blog) </li></ul></ul><ul><ul><li>http://www.pubdrug.org (project site) </li></ul></ul>

×