Notifications
Clear all
Topic starter
Has anyone notice improvement in performace, and stablity with SP2?
Thanks
Posted : July 17, 2012 6:39 am
Have the same question, we are very cautious when doing these SP updates, since no prior ones have helped.
Posted : July 19, 2012 12:50 am
Topic starter
I talked to consultanting group. They have installed SP2 for 2 of thier clients. They had no issues thus far. Users have reported a performance increase in parts of the chart.
My account manager also informed me there will be a Diagnostic Patch released at the end of this month. 🙂
Posted : July 19, 2012 10:00 am
The problem with me is that our office has Cysolution plugins and each time we have to apply these patches, we have to schedule a re-install of they plugins... headache...
Posted : July 19, 2012 2:43 pm
acantu said:
The problem with me is that our office has Cysolution plugins and each time we have to apply these patches, we have to schedule a re-install of they plugins... headache...
Welcome to the club acantu. The largest part of our upgrade schedule is the Cysolutions plugin. While the GE scripts can run in approximately 2 hours, the Cysolutions scripts can take up to 12 hours to run.
Posted : July 20, 2012 1:05 am
We installed this patch approximately 2 weeks ago. There is Definitely some small improvement in chart opening.
overall no other stability issues that were not previously noted
unfortunately on the schedule this update started causing duplicate tickets when using the status of check out. This is a known issue with GE and will be addressed in the future patch–the work around his to create another check out Status
Overall no real urgency to install. Looking forward to future patches and service PACKs that we'll address the problem with Dragon 11 and overall speed.
The script took about 4 hrs on a 68GB Database. Do Not interrupt the script while upgrading.
Good fortune,
JJC
Posted : July 22, 2012 2:33 am
JJC, we just upgraded from 10.0.2 to 10.1.2 and are having the same problem where duplicate tickets are created.
You mentioned it's due to using a status of "check out". We don't actually have a status of check out. We use the default status that Centricity comes with called "Completed"
When we post a co-pay, the visit automatically changes to a status of "Completed". But then a duplicate ticket is automatically being created.
Does it have to do with either the HL7 mapping OR Category for any of the appointment statuses?
-mjj
Posted : July 24, 2012 12:50 am
We are scheduled to perform this upgrade this coming weekend, so I would appreciate a more detailed explanation of exactly what is causing this problem and the work around that has been mentioned. In particular, does this work-around with a new appointment status result in anything that would normally be automated having to be done manually?
Posted : July 25, 2012 2:13 am
sstouffs, we received the following email from GE support:
"I think this is a defect which was introduced
in 10.1.2.210. I have seen this happen primarily when the patient’s
appointment is set to “complete” or “checked out” before the visit is touched
to change the visit from new to in progress. If this is the workflow for
this client then the easiest workaround is this. What creates the
duplicate is when a visit is modified from New to In Progress, CPS is trying
change the appointment status to a status assigned to the CATEGORY of Checked
Out in the Administration->Appointment Status dialog. If it is already
in this category, it creates a duplicate visit. What I have been doing is
finding out what status the front office us using to check a patient, and
setting the category for that status to NONE. Then you have to create
another appointment status that they will not be selecting and set its category
to Checked Out. That way they can keep the same workflow, and the
appointment will be able to flip to that category when the visit is updated and
a duplicate will not be created. So for example, if the front office is
changing the appointment status to “checked out” and it is in a category of
Checked Out, then I would change that status’s category to None, and then
create a new status called “completed” and assign it to the category of Checked
Out. That way the front office doesn’t have to change their workflow and
the duplicates will stop. If that doesn’t make sense let me know."
So here is what we did:
- Created an Appt Status of "Checked Out" with a Category of "none"
- Left Appt Status of "Completed" with a Category of "Checked Out"
- Re-organized the list of Appt Statuses.
- moved "Checked Out" near the top (for staff to use)
- moved "Completed" to the bottom (not for staff use)
- Educated Staff to change Appointment status at check out to "Checked Out" rather than "Completed"
In addition, we also found that the system would automatically update the Appointment
status to "Completed" if a co-pay was posted. In theory, it's not a problem as long as
the check out staff changes the Appt Status to "Checked Out", however, this also causes
a problem for the clinical staff looking at the schedule to see if the appt is
"Arrived (Checked-in)". So the staff posting the co-pay must go back to the appt and
change the status from "Completed" to "Arrived (Checked-in)"
We also tried not having ANY appt statuses set with a Category of "Checked Out". But that
resulted in duplicate tickets as well.
Let me know if you have any questions. -mjj
Posted : July 25, 2012 7:18 am
