Notifications
Clear all
Topic starter
Does anyone notice a problem with the OBSANY or LASTOBSVALUE data symbols or is there something that I am doing incorrectly?
Currently, if the doctor puts in a work note in their clinical list update, we have a button that saves the work note form to an obsterm. We then have a work note letter that has LASTOBSVALUE("obsterm") to pull in that work note. While this works fine when the note is signed, there are times when the doctor may put the clinical list update on hold and they just sign the clinical list changes.
This has worked for us before where it will still pull the most recent information into the letter. Every so often, it won't work and we get the previous value for that obsterm from an old clinical list update. We haven't made any changes to the form to have caused this to suddenly not work and in the definition of the data symbols it states that lastobsvalue and obsany should include the current clinical list changes.
Sometimes we switch from LASTOBSVALUE to OBSANY and it works again and other times it doesn't work. I'm not sure if this is a CPS issue or a programming issue. We are currently on CPS 12.0.7. Any ideas would help!
Thanks in advance!
Bree
Posted : February 3, 2015 8:16 am
Bree,
From my experience, the OBSANY function has been less reliable than the LASTOBSVALUE, where it loads information later in the process after the first cycle that processes watcher statements. Similarly OBSPREV is less reliable than the LAST_SIGNED_OBS_VALUE function. Depending on what you are trying to achieve, you can sometimes get away with using either one, but sometimes using the OBSANY and OBSPREV functions will have a negative impact on your coding.
If you have providers signing clinical list changes, but not signing the documents, you will see issues with observation functions. New documents / updates can only pull values from documents that were signed before the new document was created. Signing the clinical list changes will commit orders, allergies, problems, medications, etc but not observations. I have not found a solution beyond having the staff fully sign the document.
Please let me know if you need any clarification about my above statements.
Thanks,
Mike Baeske
Posted : February 3, 2015 7:04 pm
Topic starter
Mike, thank you for your explanation. I think the misunderstanding was that obsterms would be saved with signing clinical list changes. The only way I've found being able to use the current obsterms outside of the update was by having the update in progress and then printing a letter that uses lastobsvalue. In the end, we'll have to make sure our documents are just signed first. Thanks for the tips on LASTOBSVALUE and LAST_SIGNED_OBS_VALUE versus OBSANY and OBSPREV as well!
Thanks!
Bree
Posted : February 4, 2015 2:57 am
