Welcome to the NEW CHUG— your ultimate destination for cutting-edge insights and discussions at the intersection of healthcare and technology.

Our platform is dedicated to exploring the dynamic landscape of healthcare technology, empowering professionals, enthusiasts, and innovators alike with the knowledge and resources to navigate the rapidly evolving field.

From telemedicine revolutionizing patient care to the transformative potential of artificial intelligence in diagnostics, we delve into a myriad of topics shaping the future of healthcare delivery. Whether you’re a seasoned healthcare IT professional, an aspiring entrepreneur in the digital health space, or simply curious about the latest innovations, our curated content, expert interviews, and thought-provoking articles provide a comprehensive exploration of healthcare technology’s most pressing issues.

Join us as we navigate the forefront of innovation, driving forward the transformation of healthcare for a healthier, more connected world.

Have questions or suggestions? Please use the contact button below.

Notifications

Clear all

Meaningful Use Checklist - Newest version

Trading Post

Last Post by Sam 12 years ago

13 Posts

7 Users

0 Reactions

91 Views

RSS

ErnieT

(@erniet)

Posts: 479

Honorable Member

Topic starter

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.

Meaningful Use Checklist

Posted : May 14, 2012 12:25 am

Anonymous

(@Anonymous)

Posts: 0

New Member Guest

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

Posted : May 15, 2012 12:06 pm

ErnieT

(@erniet)

Posts: 479

Honorable Member

Topic starter

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.

Posted : May 15, 2012 1:20 pm

Teresa

(@teresa)

Posts: 27

Eminent Member

I've had a version of this form since October. Were there any changes other than, "Contact By"?

T Ehemann

Posted : May 29, 2012 11:24 pm

ErnieT

(@erniet)

Posts: 479

Honorable Member

Topic starter

There is also a spot now to check and see if the patient has a pharmacy listed. Other than that, no other changes.

Posted : May 29, 2012 11:29 pm

abulsara

(@abulsara)

Posts: 150

Estimable Member

Can someone provide a .ckt file of this? I do not know how to import a .dlg into CPS.

Posted : June 6, 2012 8:16 am

aballard

(@aballard)

Posts: 43

Trusted Member

Here ya go: Clinical Kit

Posted : June 7, 2012 6:08 am

abulsara

(@abulsara)

Posts: 150

Estimable Member

Thank you so much.

Posted : June 7, 2012 10:08 am

Lee

(@lee-cooper)

Posts: 348

Reputable Member

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. Wink

Posted : June 8, 2012 4:40 am

Anonymous

(@Anonymous)

Posts: 0

New Member Guest

Thanks! I will check my obsterms and make sure I'm using those.
Matt

Posted : June 12, 2012 1:08 pm

Sam

(@sam)

Posts: 371

Honorable Member

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.

Posted : October 7, 2012 11:17 pm

Sam

(@sam)

Posts: 371

Honorable Member

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!

Posted : October 9, 2012 3:52 am

Sam

(@sam)

Posts: 371

Honorable Member

"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"

Posted : October 9, 2012 3:53 am

24 Forums
9,942 Topics
39.9 K Posts
1 Online
6,470 Members

Forum Icons: Forum contains no unread posts Forum contains unread posts

Topic Icons: Not Replied Replied Active Hot Sticky Unapproved Solved Private Closed