[amanda.r.salazar_650]

(Wow I am appalled at no responses). I came across this forum because I *also* am looking for solution while (currently) experiencing PS360 downtime. Right now I call and I type/copy/paste reports directly on the electronic records software. There is a slow connectivity issue that crashed my PS360 requiring server reboot. I have noticed that letting PS rest for an hour gets be back in for 30-45 min then crashes. IT not sure why the data is piling up. An outside source thinks that it could be a faulty switch. Ideas? Thank you

[amanda.r.salazar_650]

(Wow I am appalled at no responses). I came across this forum because I *also* am looking for solution while (currently) experiencing PS360 downtime. Right now I call and I type/copy/paste reports directly on the electronic records software. There is a slow connectivity issue that crashed my PS360 requiring server reboot. I have noticed that letting PS rest for an hour gets be back in for 30-45 min then crashes. IT not sure why the data is piling up. An outside source thinks that it could be a faulty switch. Ideas? Thank you

[amanda.r.salazar_650]

(Wow I am appalled at no responses). I came across this forum because I *also* am looking for solution while (currently) experiencing PS360 downtime. Right now I call and I type/copy/paste reports directly on the electronic records software. Obviously I cant do that forever and things are piling up quickly, it is a funnel solution.There is apparently a slow connectivity issue that crashes my PS360 requiring server reboot. I have noticed that letting PS rest for an hour gets be back in for 30-45 min then crashes. IT not sure why the data is piling up. An outside source thinks that it could be a faulty switch. Ideas? Thank you

[madeleine_jye_81]

Put wet read / preliminary interpretation into either your PACS or EMR until the system comes back online. PS360 should not be going down with that much consistency if properly setup.

[glizzamora_849]

Just ran into this myself a little bit ago. It wasn’t Powerscribe that had the issue but all the interfaces with it went down.  Basically the rads were dead in the water except for calling stat reports to the provider.  I’d like to see if any other places have a contingency plan for issues like this too. 

[iva.marce.07]

We use our PS360 test system for extended downtimes. We change connections in our interface so production HL7 messages are routed to the test server we change the output on PS360 test to point to our normal inbound PS connection. The switching over process takes about 10 minutes or so. 
We ensure the radiologist’s autotext are loaded into test. 

At the client workstation, you can add the test server to the production application and I also have a desktop shortcut that can be used to launch into test. 
The only issue that we can’t cover with this is a network outage to our data center. 
And, once the system is back up, we use our interface to replay the reports back into production PS. 
It’s not ideal for an outage during the highest production hours, but it gets the job done .

[anetteheese_704]

We have a bidirectional results interface with Epic. For scheduled/planned outages we use our PS360 test server.  Radiologist has their voice profile and templates in test, they open up a temporary order, manually bring in the auto-text, dictate the report, then copy/paste the entire report directly into Epic and sign in Epic.
For unplanned downtimes our test server won’t scale, so radiologists can type and use basic smart text to type a very brief report in Epic and sign as prelim.  When PS360 comes back up they clean up the prelims and sign off.
 

[edsonandrade]

Most orgs just copy/paste onto images for referring MDs to see. Some switch to an alternate system to generate reports (like worklist embedded VR) but the cleanup for that is a nightmare. 
 
Extended downtimes are well handled by using test platform, but again cleanup can be laborious. 
 
HL7 downtimes are a whole different problem to solve for. Many facilities we work with have techs hand-enter downtime orders into a simple order entry platform (several worklist solutions have this). Again… cleanup is no fun. 

[iva.marce.07]

You make a good point about other causes of downtimes. Something that PS30 is missing is the ability to dictate locally in the event of a disconnect from the data center. I’ve heard that PS One may have that ability, but it’s way too expensive to move to.