1 / 23

Content:

ivria
Download Presentation

Content:

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Installation of a Clinical Universal Workstation Networked Printer: Set up ItemsProblem Solving Flowcharts

  2. Content: • This presentation has been reviewed and approved by the key stakeholders mentioned • This presentation will provide resources to contact for setup and problem solving—on each slide • Steps to successfully set up a networked CUWS printer—slides #3 & 4 • Troubleshooting suggestions—slides # 5-15 • Confirmation of this information from all key stakeholders in the process-prior to publication • Glossary of frequently used terms—slides#16-21 • Footnotes—slides 22 -24

  3. Flowchart: New Printer Set up Steps NEW Printer installation in NEW Nursing Unit? Manager of unit requesting printer set up will complete CSR or contact Helpdesk to initiate a CSR If electricity, network connection or counter construction needed, send request to Plant Ops by Manager of nsg. unit n y Help Desk notifies CUWS team of CSR* CUWS team contacts nsg. Unit manager or SSS dept. for decisions re: printer set up Manager of unit requesting printer will Contact Dept. of Finance for room & bed changes. Provide nursing unit name, bed numbers & phone numbers Network Printer Change Request (NPC) Completed by CUWS team Changes must be Tested before implementation to confirm complete set up in all necessary applications. All action steps taken by all parties contacted by NPC to prepare for requested print capabilities. NPC Auto- generated to all appropriate I.M. depts. *See footnote on pg.22

  4. Testing Printer After Installation • Testing team must be qualified and have access to applications to be tested • Make sure printer has “READY ” display • Check all “printer correction options”* if printer display doesn’t read “READY” before calling helpdesk • *Power on, power line connected to outlet, network cord connected to outlet and NOT pinched in any way, printer on-line (display reading READY), paper supply sufficient and not jammed, toner adequate, printer powered off and back on to reconnect network… • Test demand print • Print internet document-go to internet explorer, then click file, print, ok… • Test all types of print from all applications required to print to installed printer

  5. Troubleshooting:Unsuccessful Daily Order Sheet Print Check all “printer correction options” if display doesn’t read “Ready” * D.O.S. NOT printing in Batch on a given nursing unit. New Nursing Unit? Printer working properly? Contact CUWS team via Help Desk for repairs n n y y Contact Help Desk to verify VS030BC Database (Auto-tech team) report destination has correct printer listed for the nursing unit and ask that print be “rebundled” If failure to print persists: every step for confirmation of action taken indicating that print is still NOT successful Contact Autotech team via Help Desk to add printer to table n Print still NOT successful Escalate to Incident Response Center via Help Desk • * See glossary slide #20 y

  6. Troubleshooting: Unsuccessful EDOCS Print “PD” is an available printer option in dialogue box 1. Caller to Help Desk states unable to print ANY document from all choice within EDOCS Check “file, print” to see dialogue box User contacts CUWS team via Help Desk to have PD printer option added n y 2. Caller to Help Desk states unable to print from EDOCS from one of the possible options,i.e. eyeglasses, single or multiple print mode Technical team from CUWS & EDOCS correct items on their side Check Printer correction options before calling Help Desk * Help Desk contact EDOCS with information If failure to print persists: Revisit every step for confirmation of action Taken indicating that print is still NOT successful Print still NOT Successful Escalate to Incident Response Center via Help Desk * See glossary slide #20

  7. Troubleshooting:Unsuccessful Embosser Print CSR submitted by manager of nsng. unit adding printer: requesting connection to network for printer? Embosser printer not printing* Printer NEW ? Refer to slide #3 for guidance on submitting CSR y n n Contact person from designated application that should print to embosser for verification that the printer is set in application table y If failure to print persists: revisit every step for confirmation of actions taken indicating that print is still NOT successful Application contact sets printer in application for printing n Contact CUWS team to check Jet Direct box & hardware y Escalate to Incident Response Center via Help Desk Print still NOT successful * See glossary slide #20

  8. Troubleshooting:Unsuccessful EPIC Print HD contacts CUWS team to confirm CWS is configured for EPIC print Notify Help Desk** CUWS team corrects terminal setting to allow EPIC print EPIC document not printing from CWS terminal * n Help Desk contacts MID Range team to verify that terminal is listed in database y EPIC has accurate CWS ID & location in required tables If failure to print persists: revisit every step for confirmation of action taken indicating that print is still NOT successful y y * See glossary slide #20 n n Mid Range team adds terminal to database Print still NOT successful EPIC team adds CWS to table Escalate to Incident Response Center via Help Desk **footnotes: slide #23

  9. Troubleshooting:Unsuccessful Label Print New Printer? CSR submitted by manager of unit adding printer: requesting connection of network to label printer? Label printer not printing Refer to slide #3 for guidance on submitting CSR y n N y If failure to print persists: CUWS team will contact vendor and provide a backup printer to floor until repairs completed Contact Help Desk to trouble shoot and then contact person from designated application that should print to label printer to verify that the printer is set in application table Application contact sets printer in application for printing Escalate to Incident Response Center via Help Desk Print still NOT successful Contact CUWS team to check Jet Direct box & hardware

  10. Troubleshooting: Unsuccessful Daily AM Batch Lab Reqs Print Check all “printer correction options” if display doesn’t read “Ready * Daily AM Batch Lab Requisitions NOT printing on nursing unit Printer working Properly? Notify CUWS team to repair New Nursing Unit? n n y y If failure to print persists: Have nursing unit staff review all AM lab orders for each patient and REPRINT each req. needed Contact Help Desk to verify with AUTOTECH team that DB2 Database has correct printer listed for the nursing unit & DB2 is functioning properly DB2 Database Autotech team add printer to table Escalate to Incident Response Center Print still NOT successful *See glossary slide #20

  11. Troubleshooting:Unsuccessful Medipac Print Help Desk to contact CUWS team to verify that machine is configured for MPAC print Medipac document not printing from CWS terminal CUWS team adds workstation to terminal table n Mainframe team verifies accurate location listed in database If failure to print persists: revisit every step for confirmation of actions taken indicating that print is still NOT successful y Contact Help Desk to further trouble shoot and verify with Application support and Tech support Medipac team verifies terminal listed in application correctly y y Print still NOT successful n n Mainframe team adds to print subsystem Escalate to Incident Response Center via Help Desk Medipac team adds terminal to application

  12. Troubleshooting:Unsuccessful WIZ Print of Demand Documents: COS,CMR,etc Check all “printer correction options” if display doesn’t read “Ready” * Designated Demand printer working properly? COS / CMR Not printing from WIZ Contact CUWS team via Help Desk for repair n Is printer in expected location for Demand Print? Other demand documents (I.e. e-mails) print okay? y Next Page CUWS team confirms that the terminals reported are set to print default to designated demand printer. n n Contact Help Desk to troubleshoot and verify with CUWS team, if necessary re: printer assignment to terminal y y If failure to print persists: revisit every step for confirmation of actions taken indicating that print is still NOT successful * See Glossary slide #20 Print still NOT successful Escalate to Incident Response Center via Help Desk

  13. Troubleshooting: Slide #12 ContinuedUnsuccessful WIZ Print of Demand Documents: Unit leadership decides to allow print documents to go to current location? Is printer in expected location for Demand Print ? Prior Page Submit CSR to request that the CUWS team to move printer to expected location or identify another printer as the designated Demand printer y y n n y Educate staff re: location of demand printer

  14. Troubleshooting: Unsuccessful WIZ Print: Orders ONLY WIZ Orders (POS & REQ) documents not printing on NURSING UNIT IE, internet documents print @ designated printer Check all “printer correction options” if display doesn’t read “Ready” * Printer is working? Contact CUWS team for repair n n Nursing unit NEW? Print subsystem shows documents printed? y Contact Mainframe/Technical team via Help Desk to ensure accurate location is listed in database/ print subsystem n y Contact nsg. unit to ensure printer is “ready”, document wasn’t picked up accidentally by someone else. y y Nursing unit approved by Dept of Finance n n CUWS & WIZ team collaborate to ensure both tables have accurate location name ** If failure to print persists: revisit every step for confirmation of action taken indicating that print is still NOT successful Contact Finance Dept. y Notify Wiz & CUWS team to determine if location in their tables are named EXACTLY the same New unit set up in Medipac n Print still NOT successful Escalate to Incident Response Center via Help Desk * See glossary slide #20 **Refer to footnote on slide #23 y

  15. Troubleshooting: Unsuccessful Wiz Print:reprint Requisitions Check all “printer correction options” if display doesn’t read “Ready” * Other demand printer working properly Contact CUWS team via Help Desk for repairs Lab Reprint reqs. not printing n y Is “nearest” printer also Demand Print? If failure to print persists: revisit every step for Confirmation of action taken indicating that print is still NOT successful CUWS team via Help Desk confirmed ID of “Nearest Printer” to which Reprint Req. should print. y n Print still NOT successful Escalate via Help Desk to Incident Response Center Educate staff re: correct destination for Reprint Reqs. * See glossary slide #20

  16. Frequently Used Terms:Glossary • COS—Abbreviation for WIZ document titled Current Order Sheet • CMR--Abbreviation for WIZ document titled Current Meds & Results • Demand print- • Printer chosen by staff on nsg. unit for demand print is set during the build of the terminal as the default printer for all demand document printing • E-drain status- • the Edrained status in VPS can occur anytime the mainframe fails to send active print jobs to the printer. This could be due to out of paper conditions, loss of network connectivity, paper jams, configuration errors, or anything else that causes the printer to become unavailable when the mainframe is trying to route print to the printer.*see footnotes slide #23.

  17. Glossary Continued: • HIP monitor- • The HIP monitor is a utility that resides on the VUMCPORTAL server and monitors all critical printers • If one of these printers encounters a problem, the HIP monitor will display the printer ID in “the printers needing an intervention window” at the top of the HIP monitor screen • The “Monitor” will also receive an audio alert stating "please check your printer monitor“ The Help Desk then notifies appropriate staff. • This audio alert will only be announced once for each occurrence (HIP monitor is planned for replacement by service desk soon) • This “Monitor” resides on & is monitored by the Help Desk. The Help Desk notifies the unit impacted • The HIP Monitor is not integrated with the VPS system on the Mainframe & may not alert the Help Desk to all VPS “e-drain” status errors.

  18. Glossary Continued: • IRC-Incident Response Center- • Escalation process via help desk to which unresolved problems should be routed • Logical printer table- • PRTVLOCT (see WIZ location tables) orders printer location table created by CUWS team to correlate printer ID to print destination table in WIZ • MPAC location table— • Table (YALOC) which contains all approved location codes where patients can be bedded within the inpatient and outpatient procedural areas • Used for patient tracking of admit,discharge, transfer

  19. Glossary:continued • Nearest printer table- • based on the terminal location code table (VTMVTRMT) which drives where WIZ prints reprinted reqs;This table is maintained by CUWS team • Network printer change request (NPC)- • Web based process for LAN Managers or CUWS Specialists to communicate and request printer changes from their responsible areas to the various Informatics Center departments required to enable to device to print the required user application printouts. This web based application can be accessed @ https://trutto.mc.vanderbilt.edu/ncs/

  20. Glossary Continued: • POS—Abbreviation for WIZ document titled Physician Order Sheet • Printer correction options- • Power cord plugged in, power printer off & on to reconnect network to printer, network cord is connected to back of printer and NOT pinched, printer on-line (display reading READY), paper supply sufficient and not jammed, toner adequate… • Print Sub-system- • CICSPAC2-a Mainframe based CICS (customer Information Control System) application developed in-house which identifies each document sent to any networked printer by date, time & content of document

  21. Glossary Continued: • REQ– Abbreviation for WIZ document titled Lab Requisition • WIZ location table— • PRTVLOCT (orders printer location tables): • U$HIPRINT(nursing unit WIZ printers) • U$DPPRINT (departmental WIZ printers, I.E. ECHO lab) • WIZ uses these tables to match orders printing to patient (Medipac) location for accurate print of automatically generated documents to correct pt. care location*Refer to slide #23 for further detail.

  22. * Footnotes: • Slide #2--* the qualifiers for installation of a CUWS printer are: there must be a CUWS workstation involved. • If there is an existing NON- CUWS printer in place, when it becomes a CUWS printer, the CUWS team then is responsible for the maintenance and life-cycling of that printer. • Slide # 7—Help Desk has access to allow the printer to be pinged, restart printer queues, clear printer queues, etc….

  23. * Footnotes:Continued • Slide # 14 & 21—Within Wiz Order, there is a matching table that maps beds to printer names in U$HIPRINT. There's another table that maps units and/or workstations to label printers (via their hostname/IP address). Requisitions to departments (mapping orderable department/sub department to U$DPPRNT printer name) are hard coded. • Slide # 16– See Slide # 17 for description of term E-Drain

More Related