I'm hoping to have a form automatically load the default text that it loads only with the push of a button (trying to save that click!) I believe the form is the 'CCCQE-User-Edit-PE-SS-Adult-TFE' form. Under each of the headings (General, Head, Eyes, Ears, Nose, Mouth), there are buttons that say 'NORMAL'. Pushing that button enters text such as (for 'General' - well developed, well nourished, in no acute distress.)
The line in the file shows this:
ccc_Adult_PE_exec()fn ccc_Adult_GEN_PE() {"General^Gen appear^cachexia,mild respiratory distress,moderate respiratory distress,obese^mild pain/distress,moderate pain/distress,poor hygiene,unkept^well developed, well nourished, in no acute distress. ^yes"}
Obviously, I see the text that gets entered with the press of the button after the second-to-last carat (^) bolded above, but is there a way to trigger that text to show when the form is loaded?
This is next level click elimination 😉
We don't use CCC content, but I would think you could initialize the variables or obsterms to the defaults in the MEL space. I f you did so you would want to create a way to easily clear too.
The athenahealth ccc content is a bit tricky to revise as you are describing but it can be done if you edit the raw kit files (efm/xlw). For each edit, you must log and verify before updating to a new version, otherwise the changes may be lost. Changes can include loss/addition of functionality and added/removed/altered variable names. The latter is what you will be most concerned with.
That said, you might be able to create a small form or text component to add to the udpate. That form/component would hold the code to evaluate for existing data in the desired variable field. If empty, add the text, if not, do nothing. Be certain to test the code well, to include placing on hold and reopening as well as signing the update (both actions cause a full execution of MEL in the update).
Of course, you will want to verify with your billing manager to ensure that you are not going to send your providers wading into gray areas for medicare/insurance 'carbon copy' violations as well as probable liabilities for improper/erroneous documentation elevating potential for patient harm and fraud accusations.
There is a lot to consider and an elevation of risk with increasing automated documentation. 'First do no harm' extends to medical IT too. I do not think that current technology is up to the task of recognizing or preventing the type of errors that would be introduced by this style of workflow.
For what it is worth, I've traveled this path. Providers quickly became frustrated with the amount of editing required that they either stopped using it or their corrections to the default text became increasingly 'sloppy' (usually due to the belief that they would remember to fix it later but often did not). Your mileage may vary, or not.
The allure of 'one click charting' is tempting and the ultimate dream...until it becomes a nightmare.
I forgot to click the check-mark to be notified of answers, so I apologize for my tardy response here. Thank you both, especially your very thoughtful response Lee. As I said, I knew it was a long shot and in considering what you point out, I don't think it's worth it and I will make the case to the Provider. Thanks again.