200 likes | 343 Views
Bringing Electronic Document Delivery to Small Hospital Libraries. doc MD:. Eric H. Schnell (schnell.9@osu.edu) Associate Professor Prior Health Sciences Library The Ohio State University.
E N D
Bringing Electronic Document Delivery to Small Hospital Libraries docMD: Eric H. Schnell (schnell.9@osu.edu) Associate Professor Prior Health Sciences Library The Ohio State University docMD is funded through support by the National Network of Libraries of Medicine, Greater Midwest Region.
docMDGoal “ To establish an electronic document delivery service for hospital libraries that are unable to support such a service themselves due to limited human, financial, or technical resources “
docMD Objectives Establish a mediated direct-to-customer document delivery service for hospital libraries Identify the costs involved in providing such a service Develop a model for use by other resource libraries in other regions of the country
What is IDD? Internet Document Delivery Library to library (Odyssey / Ariel) Library to library to customer (patron delivery) Lending library to requesting customer (future)
Why IDD /docMD? Reduces telecom costs (Landes ’97) Reduces turnaround time 13.76 days (Budd ‘86) reduced to 2.52 days (Sellen ‘99) Reduces supply costs (Weible ’02)
Barriers to IDD Implementation Firewalls (McKnight 2001) communication ports network authority Workflow / staffing (Jackson 1993) Access to technical staff Fiscal resources
How docMD Jumps these Barriers Firewalls a common communication port is used (80) Workflow / staffing ILL processing remains the same Less physical processing of documents Access to technical staff Technical staff at mediation center Little site support needed Fiscal resources NLM / GMR supported
Traditional ILL/IDD Customer Processing Model Customer IDD Local Library OCLC / DOCLINE Lending “A” Lending “B” Scans/Sends though IDD Scans/Sends though IDD Web Server
Email Alert Customer Email with docID# Local Library OCLC /DOCLINE Lending “A” Lending “B” Scans/Sends though IDD Scans/Sends though IDD docMD Web Server docMD Delivery Model
docMD Statistics (as of Aug 5, ‘05) 406 registered customers 3111 documents processed <1% required reposting <1% alternative distribution <1% posting failures ~15% have gone unviewed >40% sent to the librarian
docMD Statistics Average document processing time: 1 minute Average number of documents requiring follow up: 1 per week Percentage of documents arriving upside down: 20% -> 1% Number of customers contacting docMD central regarding difficulty in downloading a document: 1
Turnaround Time Pre – docMD: 6.53 days (max 19 days) Post – docMD: 3.11 days (max 9)
Feedback “Our docs are always so delighted when personalized mail arrives for them.” one has a “raft of administrators tooling past his office wanting to know how his articles were retrieved electronically. They believe that he magically pulled them up all by himself. “ “another test subject… has been running around Nursing telling people…”
Issues: Geography: Project leaders / librarian face-to-face contact difficult Geography II: Difficult if not impossible to organize group training Geography III: Email helps. Phone is more effective but more time consuming
Issues: How docMD is implemented at a site is dependent on the hospital librarian Level of participation is dependent on the marketing performed by the hospital librarians Too much hand-holding or separation anxiety?
Issues: Funding Pay-to-Play (1) Each hospital pays a fee based on scale determined by the number of documents they normally process through DOCLINE in relation to other participants in a tiered fee schedule. Pay-to-Play (2) Each hospital pays a per-document fee based on the actual number of documents they process using docMD and is billed on a quarterly or annual or per-document basis. Subsidized (1) Each NNLM region establishes funding opportunities for resource libraries to support a docMD service for their resource area. Resource libraries apply for the available awards. Subsidized (2) Each NNLM region provides a funded mandate to each resource library to establish a docMD service in their area. Benevolent Any library can provide the service but supports it using their individual operating funds and can pursue reimbursement from the participants.
Issues: Standards GEDI: Generic Electronic Document Interchange Established in early 1990s Ariel 1.x - 3.4 Odyssey Open Standard Ariel 4.x ???? proprietary
Issues: Standards Lack of IDD standards will result in the project ending in December 2004 Lack of IDD standards will prevent a wide scale implementation of the concept
Thanks! E-mail: schnell.9@osu.edu Project: docmd.med.ohio-state.edu