1. NIC Meeting 10-7-14 By: Cecilia Molina-Clark
P2DA and SLXN
NIC Meeting
By: Cecilia Molina-Clark

2. MEDICAL DEVICES

3. INTERFACING DEVICES
Interfacing devices in Cerner allows results to be pulled directly into the patient’s chart
Example:
Admit patient to SL monitor
Associate device to patient in Cerner
Pull in results from the monitor into i-View

4. CURRENT PROCESS: BMDI

6. NEW PROCESS: P2DA and SLXN

7. WHAT IS P2DA? P2DA = Patient to Device Association
Mechanism to associate devices (monitors, infusion pumps, cardiac output monitors, etc)
Can associate more than one device to a patient
Can be used for retroactive associations
Will alert when the same device is associated to more than one patient

8. WHAT’S NEW? IT’S EASIER!! New Icon
P2DA window to associate the devices
Scanning the device’s barcode
Can manually associate a device – when the scanner is not working or one is not available
IT’S EASIER!!

9. P2DA Icon

10. P2DA Window

11. DEMO -

12. EDUCATION MATERIALS
Karen Broz

13. ROLLOUT – Process to Convert
Start Time - ~ 10:00 AM
Nurse:
Charts vitals up to conversion time
Disassociate/Discharge all patients from Cerner and Spacelabs
Disassociate other devices
Unit will be down for ~ 30 min – for conversion
Nurse manually enters the downtime vital signs during conversion
Team configures new system
Nurse
Re-associates all devices with the new system using P2DA
Resets alarm limits on the monitor

14. Lessons Learned
Susan Heimsoth

15. PROPOSED ROLLOUT SCHEDULE
Taking into consideration:
Units must be moved to the new P2DA/SLXN system before rolling out
One day between rollouts for better support
Rollouts done on Tuesdays and Thursday
: Upgrade of PROD Citrix servers
11-2 week: Cerner Health Conference
: Blood Transfusion go-live
Thanksgiving and Christmas

16. DATE
ACTION/UNIT
Oct 13 wk
Upgrade of PROD servers from W2003 to W2008 R2
Oct 23
Go no-go decision to rollout to other units
Oct 28
DIALYSIS
Oct 30
CICU
Nov 18
SICU
Nov 20
NSICU
Nov 25
PACU and HOLDING
Dec 2
PROGRESSIVE CARE
Dec 9
FAIRVIEW CLINIC – GI
Dec 9 ??
MICU3 (after move)
Dec 11
GI ENDOSCOPY
Dec 16
MOI
??? ED

17. TWO SYSTEMS IN USE! Some units on P2DA Some units on BMDI ISSUE:
Not disassociating or discharging patients creates issues
In P2DA – the disassociated monitor displays as dithered
Never allow a patient to be on more than one Spacelabs monitor!!!
Results get garbled; if a another patient is attached – these patients results will be sent

18. QUESTIONS?

20. Steps to Admit a Patient to SL Monitor
Click on MONITOR SETUP

21. Click on ADMIT/ DISCHARGE

22. The Patient Demographic screen will open, click ADMIT

23. A window will open with the question Purge existing data on this bed
A window will open with the question Purge existing data on this bed? Click YES

24. The Monitor Setup screen will open and the ID1 field will be clear
If an ID is not entered within 30 seconds, a default identification number appears (number begins with UV)

25. If the default number appears in the ID1 field, highlight the default number and click the Del button

26. Type the FIN# number in the ID1 field and click Enter
Note: Only type in the FIN#, the other information will come through from IDX.

27. Once Enter has been clicked the SAVE button will activate
Once Enter has been clicked the SAVE button will activate. Click SAVE (SAVE will dither)

28. What is SLXN? SLXN = Spacelabs ExpressNet
Is a feature that allows a patient to be admitted to a Spacelabs’ monitor directly from P2DA
No need to enter the Visit# on the SL monitor to pull in the patient name
The patient name will display on the monitor in the lower left corner of the screen
The linking/unlinking of a patient to a networked Spacelabs monitor is now done within Cerner!
SLXN does not apply to portable or telemetry monitors

29. Why can’t we have it NOW?

30. SLXN Technical Considerations
Must move over 500 monitors to the new SLXN architecture
Requires careful coordination among the server team, networking, and clinical engineering
Each monitor must be configured to work with SLXN

31. Migration Plan June 30-July 25th July 29th wk – Aug 5th - Aug 8-22nd –
Migrate UH and MOI monitors to the new network
July 29th wk –
Start first with MICU and test workflows
Aug 5th
Go-no-go decision meeting
Aug 8-22nd –
Complete migration of WCH monitors to new VLAN
Aug-Sept
Rollout to other units, unit by unit

32. Education Plan and Materials (Karen Broz)
Classroom training not necessary
Will provide handouts and cards for staff
On-line training module will be available