i am just wondering if any other users has similar issues and if a fix is available:
I have found the the CAMOS content does not get posted from time to time even though there is a confirmation number coming back to say the content was submitted. this happens randomly, but seems can be corrected by redo the submission SOMETIMES, or by reloading the patient visit and submitt camos content immediatly–this seems to fix the problem most of the tiem, if not every time.
could that be some settings that disconnect the open window’s info to the patient account data, that can be corrected?
In the CAMOS form, “Submit selected content” requires the content in the “Content” field to be selected manually. Only if it is selected and the button is clicked, the values will be posted otherwise just a confirmation notification “submitted” will be shown but really the values will not get posted. The label of the button just literally conveys the functionality.
The “Submit all content” work as you expect i.e without selecting the “Content” fields values, if you click this button this will get posted.
Hope this helps.
N.B Even you can post the same in bug tracker - When values in the “Content” is not selected and if ‘Submit selected content’ is clicked, instead of giving a irrelevant notification “Submitted” we can notify as “Nothing to submit” or something more relevant.
Thanks for all the info. Yes, i have read through some info about CAMOS system, and currently use firefox, and i always try to remember to highlight the content i wanted to post before clicking on “submit selected content”, or just use the button at bottom of frame to submitt all content.
i have noticed the random failure to post happens in both types of submission (all or selected contents), but seems to happen when the system is left unused for a while (10-20min or longer?), so i am guessing there might be a general timeout setting somewhere.
there could be another patient file open in another tab, i did not know this would affect its behavior? i will pay attention to see if they are related.
Problem solved by keeping only one tab open in the browser, since i keep only one tab open for openemr, this has not happened again, not sure why, but it fixed the issue.