Unexpected logging out and losing information - time consuming RIS Upgrade scheduled for September 2016. It is anticipated that the upgrade will address this. Booking now roughly 8mins to complete in Carestream compared to roughly 1-2mins previously in Kestal This will be monitored closely. PACS shows 1 region when using multi-region in Carestream – having to delete exam and re-add individually for Radiographers to complete exam - time consuming Change approved by SAMI, RFC currently being processed. ESMI system is a complex system which has many functions but they don’t flow. You need to go in and out to achieve simple tasks. To investigate this, SAMI Support would need more detail from the specific users/users making this statement. This appears to be a generalised statement. We would need to perform a workflow analysis to understand the meaning of this statement and what exactly does not flow. Could this be an education/training issue? The menu and pathway options are so awkward they required 15 steps before anything happens. PSA to provide documentation regarding the ‘awkward’ pathway, and the 15 steps identified. This appears to be a generalised comment, and some baseline documentation to describe the problem, be a very useful tool in troubleshooting/addressing the issue. Everything we do takes longer and the system pauses for every single click and sometimes the wait symbol can appear for a minute or so. Initially this was reported and addressed by the vendor as a known issue and a small ‘patch’ was applied to the Carestream RIS software to alleviate LDAP association issues.
RIS Upgrade scheduled for September 2016 may assist. There are points in entering information on ESMI that it simply won’t let you and you need to close and reopen continually. PSA to provide documentation that describes these points in detail in order for SAMI to respond. This appears to be a generalised comment, and some baseline documentation to describe the problem, would be a very useful tool in troubleshooting/addressing the issue. Most of the historical services that were “migrated” to ESMI from Kestral came across as completely wrong study, eg arms showed as legs and heads showed as arms and a lot came up as simply “DM RAH Historic Study” As part of the configuration discovery, sites original codes were mapped to the enterprise codes and documented. All sites were asked to approve and sign off on these mappings. These studies before November 2015 do not always open from ESMI (lucky some days to have any open) More information required from the PSA in order to understand the issue and respond. The PACS server that used to contain all historic services seems to no longer run (it's either dead, unreliable or no longer attached to the program) More information required from the PSA in order to understand the issue and respond. ESMI loses it's connection regularly throughout the day. RIS Upgrade scheduled for September 2016. It is anticipated that the upgrade will address this. To simply look up anything can require opening many parts of the same order and sometimes back out repeatedly to open it up a More information required from the PSA that describes this issue in detail. Any further explanation or understanding of the
browser and they right click to choose labels If you want to up an order, the browser defaults to LMH order but it won’t let you use it, you have to go to the trouble of clicking RAH before you can print it Only one SAMI order from QEH EPAS go live, fixed. If you close a room eg service from 1 to 2pm then try and book a patient at 2pm it won’t let you unless you make the booking at 2.01 or change the closed room time to 1.59 This is correct and expected functionality. The user specifies the exception by date and time. If the room is closed 2pm, then it makes sense that nothing is booked til after 2pm. As the exception does not take into account seconds then 2:01 pm is logical. When you have a patient scheduled then change it back to ordered as is a problem with the first date, but you will definitely be able to book it soon, the initial scheduled shows as “cancelled” but it doesn’t hint it's on the ordered browser or allow you to write in a “reason” More information required from the PSA that describes this issue in detail. I went to schedule a patient and the patient was not free to come down so I went to cancel the booking I was making, and it me whether I wanted to save my changes so I said yes as I had already chosen cancel and because I assume “no” would bounce you back into the booking again… it went ahead and scheduled the procedure without my being aware. More information required from the PSA that describes this issue in detail for further investigation. Potentially sounds like a workflow/education issue which should be further investigated. “new visit” being a long way from the top and staff having to scroll Related to Issue 23 - please see response to 23