ELECTRONIC WORKFLOW    SSP Technology Blitz      Philadelphia, PA     November 18, 2004
About the American College of Physicians§ The nation’s largest medical specialty  society§ 116,000 physician members  spec...
ACP’s premier publications§ Annals of Internal Medicine: An original  research journal; published twice monthly§ ACP Journ...
Other publications produced by ACP§ About a dozen downloadable PDA products§ About a dozen new book titles per year§ Web s...
Five years ago: a very traditional environment § Autonomous content factories or “silos” § Inherently incompatible technol...
Pursuit of a new strategy: content ubiquity§ Readily accessible to authorized ACP staff and  ultimately, under access cont...
Content Development/Deployment                      Conceptual DesignContent Creation                                     ...
Today: a new, integrated environment§ A common infrastructure§ Shared templates, programs, and  editorial tools§ Collabora...
Our guiding principles§ Never sacrifice quality to achieve higher  productivity§ Never sacrifice productivity to achieve  ...
What is “electronic” workflow?§   Paperless editorial production§   Computer-assisted editing§   Computer-transformed rend...
Paperless editorial production§   Author-submitted manuscript§   Copyedited manuscript§   Unpaginated galleys§   Page proo...
Computer-assisted editing§   Editorial macros§   “Cleanup” routines§   “Edit-checker” routines§   Scripted global search-a...
Computer-transformed renderings§   Word-to-XML§   XML-to-Xyvision XML§   XML-to-Quark§   XML-to-HTML§   XML-to-PDF§   XML-...
DMS-driven processesRoutine DMS tasks previously performedby hand are now automated, such as:§   Automated import and expo...
DMS-executed tasksNon-DMS-related editorial tasks previouslyperformed by human editors are nowexecuted in an entirely unas...
The workflow is less rigid but more complex§    The flexibility needed to respond to new     opportunities drives the opti...
It may appear “busier,” but it’s not chaotic                BEFORE                                                  AFTER ...
Lessons learned (so far)1.   Implementing XML backwards up the workflow,     step by step, not all at once, causes the lea...
Lessons learned (so far)4.   Developing, testing, and implementing a live but     lower risk “pilot” project first ease th...
Lessons learned (so far)7.   Developing applications programming capabilities     within your staff results in flexibility...
Upcoming SlideShare
Loading in...5
×

76 linda drumheller

89

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

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

No notes for slide

76 linda drumheller

  1. 1. ELECTRONIC WORKFLOW SSP Technology Blitz Philadelphia, PA November 18, 2004
  2. 2. About the American College of Physicians§ The nation’s largest medical specialty society§ 116,000 physician members specializing in internal medicine and its subspecialties§ Staff of 350 located mostly in Philadelphia§ Not-for-profit
  3. 3. ACP’s premier publications§ Annals of Internal Medicine: An original research journal; published twice monthly§ ACP Journal Club: A secondary research journal; 6 issues per year§ Physicians’ Information and Education Resource (PIER): An online clinical guidelines database; continuously published and updated§ Medical Knowledge and Self-Assessment Program (MKSAP): A multipart Continuing Medical Education (CME) product; published every 3 years
  4. 4. Other publications produced by ACP§ About a dozen downloadable PDA products§ About a dozen new book titles per year§ Web support for our Annual Session, the world’s largest internal medicine meeting§ A wide variety of other CME products and ACP member services available in print and online§ Eleven Web sites totaling over 277,000 HTML pages§ Many products also available on CD-ROM and/or through third-party licensing partners such as Ovid
  5. 5. Five years ago: a very traditional environment § Autonomous content factories or “silos” § Inherently incompatible technologies § Product-specific workflows § Uncoordinated content development efforts resulting in overlapping content § Linear workflows to produce multiple deliverables from each product’s content
  6. 6. Pursuit of a new strategy: content ubiquity§ Readily accessible to authorized ACP staff and ultimately, under access control, to authors, peer reviewers, and end users§ Cohesively indexed and searchable in a variety of methods so that interrelated subject matter is easy to find regardless of its originating source§ Deliverable through automated systems that support the ACP’s ability to publish the right information in the right form at the right time to the right audience
  7. 7. Content Development/Deployment Conceptual DesignContent Creation Content Deployment Print Products • Annals of Internal Medicine • MKSAP • ACP Journal Club • PIER • Journal Club Electronic Products • MKSAP • Annals Content Repository • PIER Documentum • acpjc.org • Others… Document Management System • annals.org • MKSAP • PDAs • e-commerce Business Partners • Allscripts • Ovid • NextGen • EBSCO • StatRef • Infotrieve Other Products • Skyscape • Hybrid Web sites • Clinical decision support tools
  8. 8. Today: a new, integrated environment§ A common infrastructure§ Shared templates, programs, and editorial tools§ Collaboration and coordination of content development efforts§ A single workflow to produce multiple deliverables from the same content§ A common way of work for all products
  9. 9. Our guiding principles§ Never sacrifice quality to achieve higher productivity§ Never sacrifice productivity to achieve higher quality§ Attempt to improve BOTH quality and productivity with every change
  10. 10. What is “electronic” workflow?§ Paperless editorial production§ Computer-assisted editing§ Computer-transformed renderings§ DMS-driven process§ DMS-executed tasks DMS = Document Management System
  11. 11. Paperless editorial production§ Author-submitted manuscript§ Copyedited manuscript§ Unpaginated galleys§ Page proofs§ Bluelines
  12. 12. Computer-assisted editing§ Editorial macros§ “Cleanup” routines§ “Edit-checker” routines§ Scripted global search-and-replace§ Online reference checkers§ Metadata insertion programs§ XML transforms for reorganizing content or changing tagging structures
  13. 13. Computer-transformed renderings§ Word-to-XML§ XML-to-Xyvision XML§ XML-to-Quark§ XML-to-HTML§ XML-to-PDF§ XML-to-PDA§ XML-to-partner-specific output§ XML-to-Word (one-way or round-trip)
  14. 14. DMS-driven processesRoutine DMS tasks previously performedby hand are now automated, such as:§ Automated import and export§ Automated check-in, check-out, and parsing§ Automated promotion to next lifecycle stage§ Automated rollup and chunking of XML§ “Task-ready” email alerts to next editor§ Automated status reporting
  15. 15. DMS-executed tasksNon-DMS-related editorial tasks previouslyperformed by human editors are nowexecuted in an entirely unassisted mannerby the DMS:§ Automated “cleanup” routines§ Automated content transformation§ Automated retention policies
  16. 16. The workflow is less rigid but more complex§ The flexibility needed to respond to new opportunities drives the optimization of production for existing products§ Every change has an impact on everything else§ Quality assurance surfaces problems with the data that were never noticed in print§ Workflows are moving targets that are constantly being tested and tweaked§ The number of precomposition steps increases, but many are automated using plug-ins§ Most new steps can be carried out by editorial assistants
  17. 17. It may appear “busier,” but it’s not chaotic BEFORE AFTER End-user Experience Common services Editorial production systems Back-end systems Infrastructure .© 2003 Hewlett-Packard Development Company, L.P Used with permission.
  18. 18. Lessons learned (so far)1. Implementing XML backwards up the workflow, step by step, not all at once, causes the least disruption and the most immediate benefits.2. Justifying each change in terms of clear, specific, and immediate benefits to productivity, quality, and deliverability determines what step is next.3. Completing tiny steps and using the editors for testing and implementation avoids dropping a “black box” like a bomb on the editorial staff and builds editorial competence, trust, and ownership.
  19. 19. Lessons learned (so far)4. Developing, testing, and implementing a live but lower risk “pilot” project first ease the sharing of a new capability with other products because the benefits are already proven and the procedures are already shaken out.5. Separating content from presentation enormously simplifies content development. Use Cascading Style Sheets (CSSs) and XML transformations (XSLTs) to render content for print composition and electronic presentation.6. Planning, organizing, and documenting the new production process are very necessary steps but also very labor-intensive.
  20. 20. Lessons learned (so far)7. Developing applications programming capabilities within your staff results in flexibility and reusability. We rely on the corporate IT function only for hardware, systems software, and network infrastructure. We outsource programming only when absolutely necessary and then transfer the technology to internal staff upon completion.8. Encouraging editors who are inclined by interest and aptitude to consider a programming career path produces very informed technical skills.9. Using project leaders with real-life “been to the mountain” experience provides champions and cheerleaders who can give encouragement, direction, and reassurance to the staff.
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×