Notifications
Clear all
Topic starter
We have a patient who has a very large chart because he is seen often. The chart takes forever to load and crashes frequently during chart updates. I created an SR two months ago, but GE Service will not respond to the ticket. I would like to archive data or create a "volume 2" for this patient. Does anyone know how to do this? We are on CPS12.
Posted : July 7, 2015 10:19 am
There is no way to archive patient data as we were able to do in the paper charts world. The only Archive function that exists the "Archive OBS Tool". Basically, it is a SQL script or Stored Procedure that you run against your database to limit the number of OBS terms that are pulled per patient record. Read the fine print, there is no undo for this. I have ran this in my test environment and I did not notice any improvement at all.
A few CHUGS ago, I asked the Engineering team to have this feature added for several reasons, but one main is for Legal reasons. We should be able to archive patient data based on the State regulations. Of course, I have not heard anything on this since then.
Posted : July 7, 2015 4:05 pm
This may or may not help, but in case you aren't aware, you can define a document age the system will go back when displaying a chart. In Administration > System > User and Resource Management > Users > Preferences > User Preferences, you can set the preferred age to display based on user, user group, or globally.
You might also consider starting a new chart for the patient with the first update a note that the patient has a chart volume 1.
As an additional FYI, we have a test chart with 3340 updates/documents in the chart. We display the last 1 year of updates. It took about 15 seconds to load and brought up 240 updates. I use the chart all the time for testing and can't say that I recall a crash waiting for it to load. In our environment we have about 100 active users at any time sharing 4 terminal servers.
Posted : July 8, 2015 4:16 am
The ArchiveObs store procedure will put 'A' in the ARCHIVE column of each observation term that meets the criteria for the archive and 'L' for the last instance of that observation term to archive. You can easily undo this by setting everything in the ARCHIVE column back to NULL for that patient.
UPDATE OBS SET ARCHIVE = NULL WHERE PID = 16_DIGIT_PATIENT_ID_HERE
This improves performance for the flowsheet and forms. Depending on the extent your forms access observations, it may improve improve performance by quite a bit. Overall, this is just a band-aid because the document encounters have very flawed programming when it comes to observations and watcher functions. We've started to use smaller, compact forms based on the type of encounter to help with speed within the forms.
There is also a setting in user preferences under Patient Charts>Documents that lets you limit how far back the chart will load documents for a patient. This can improve chart load speed for patients that have really old charts. Unlike archive obs, the hidden documents can be loaded at any time by the user by clicking on the red section that hides them within the Documents section of the chart.
Posted : July 8, 2015 4:33 am
Both archiveobs and setting the age to display documents will help quite a bit. I'm curious about the crashing though. How many documents does this pt have? I'm also going to send you an email.
Posted : July 8, 2015 6:05 am
