I received this from Angela Hunsberger (used to be Culp) today. She has revised her meaningful checklist form and asked if I would post it for her.
Here it is and hope everyone gets good use out of it.
Thanks Ernie.
Had a question...and forgive me if this is addressed elsewhere. I noticed that all the obsterms for the "reviewed" items are different than what are in my forms I created. For example, for "problem list reviewed" I use obsterm "PROBS REVWD" whereas this form uses "PROBLEMS REV". I could easily change this but was wondering if there were particular obsterms used for MU reporting or something like that. Do the particular obsterms used make a difference?
matt
Ha, you had the same issue I did at first. The only one that I can tell that counts for MU is the one for medications. And either obsterm will work and count on the report for meds.
I ended up just changing my obs to reflect the MU checklist.
I've had a version of this form since October. Were there any changes other than, "Contact By"?
T Ehemann
There is also a spot now to check and see if the patient has a pharmacy listed. Other than that, no other changes.
Can someone provide a .ckt file of this? I do not know how to import a .dlg into CPS.
Thank you so much.
mlambert said:
Thanks Ernie.
Had a question...and forgive me if this is addressed elsewhere. I noticed that all the obsterms for the "reviewed" items are different than what are in my forms I created. For example, for "problem list reviewed" I use obsterm "PROBS REVWD" whereas this form uses "PROBLEMS REV". I could easily change this but was wondering if there were particular obsterms used for MU reporting or something like that. Do the particular obsterms used make a difference?
matt
The difference is important and has less to do with MU as EMR functionality.
In order to link the form to the NATIVE functionality for clinical list reviews, use the following obsterms:
Problems: PROBLEMS REV
Medications: MEDS REVIEW
Allergies: ALLERGY REV
Directives: ADV DIR REV
These all accept a value of 'Done' only to function properly.
By using the native functionality, you ensure that your data points communicate with each other, which I presume is the intent.
Thanks! I will check my obsterms and make sure I'm using those.
Matt
I see that this version only checks to see if there is a value in the smoking status obsterm, not to check if the value is one of the ONC-specific terms. Has anyone worked on creating advanced visibility to make sure it only displays 'done' if the smoking status is one of the ONC-specified terms? I've tried, but am having difficulties getting it to work.
Sam said:
I see that this version only checks to see if there is a value in the smoking status obsterm, not to check if the value is one of the ONC-specific terms. Has anyone worked on creating advanced visibility to make sure it only displays 'done' if the smoking status is one of the ONC-specified terms? I've tried, but am having difficulties getting it to work.
Nevermind, I received help from another Chugger. Thanks!
"Missing" field visibility: LASTOBSVALUE("SMOK STATUS")=="" OR (LASTOBSVALUE("SMOK STATUS")<>"current every day smoker" AND LASTOBSVALUE("SMOK STATUS")<>"current some day smoker" AND LASTOBSVALUE("SMOK STATUS")<>"former smoker" AND LASTOBSVALUE("SMOK STATUS")<>"never smoker" AND LASTOBSVALUE("SMOK STATUS")<>"unknown if ever smoked" AND LASTOBSVALUE("SMOK STATUS")<>"smoker – current status unknown") "Done" field visibility: LASTOBSVALUE("SMOK STATUS")=="current every day smoker" OR LASTOBSVALUE("SMOK STATUS")=="current some day smoker" OR LASTOBSVALUE("SMOK STATUS")=="former smoker" OR LASTOBSVALUE("SMOK STATUS")=="never smoker" OR LASTOBSVALUE("SMOK STATUS")=="unknown if ever smoked" OR LASTOBSVALUE("SMOK STATUS")=="smoker - current status unknown"