RE: cdi_talk digest: February 22, 2011
Melissa,
I am very happy to see this question posted on the CDI's role in the implementation of the EHR.I have been vocal in my organization asking that I be involved in CPOE, and especially when we start on the development of physician documentation and surgery templates. I feel that people do not understand our value in this very important process and will develop these tools that will not be in the best interest for the organization relative to clinician documentation and coding.We need to be proactive instead of backtracking and get all the appropriate people around the table.Unfortunately,people do not always know someones value especially in large organizations.
Lois
________________________________________
From: CDI Talk digest [cdi_talk@hcprotalk.com]
Sent: Wednesday, February 23, 2011 12:00 AM
To: cdi_talk digest recipients
Subject: cdi_talk digest: February 22, 2011
CDI_TALK Digest for Tuesday, February 22, 2011.
1. Re: CHF question
2. Travel CDS
3. Re: Travel CDS
4. ESRD vs CKD5
5. Re: ESRD vs CKD5
6. RE: ESRD vs CKD5
7. Re: ESRD vs CKD5
8. RE: ESRD vs CKD5
9. CDI involvement with electronic systems development
----------------------------------------------------------------------
Subject: Re: CHF question
From: dallendeb@comcast.net
Date: Tue, 22 Feb 2011 00:00:00 -0500
X-Message-Number: 1
I tell my orientees on their first day - "Coding doesn't always make sense - it does not always appear logical - it is what it is. As long as everyone follows the rules, we are okay."
----- Original Message -----
From: CDI Talk
To: dallendeb@comcast.net
Sent: Mon, 21 Feb 2011 20:06:58 -0000 (UTC)
Subject: [cdi_talk] CHF question
I was just reviewing a coding summary. Pt came in w/DOE, weight gain. I was expecting to see the final code 293 CHF without CC/MCC. The coder used 404.91 as the PDx,
I am very happy to see this question posted on the CDI's role in the implementation of the EHR.I have been vocal in my organization asking that I be involved in CPOE, and especially when we start on the development of physician documentation and surgery templates. I feel that people do not understand our value in this very important process and will develop these tools that will not be in the best interest for the organization relative to clinician documentation and coding.We need to be proactive instead of backtracking and get all the appropriate people around the table.Unfortunately,people do not always know someones value especially in large organizations.
Lois
________________________________________
From: CDI Talk digest [cdi_talk@hcprotalk.com]
Sent: Wednesday, February 23, 2011 12:00 AM
To: cdi_talk digest recipients
Subject: cdi_talk digest: February 22, 2011
CDI_TALK Digest for Tuesday, February 22, 2011.
1. Re: CHF question
2. Travel CDS
3. Re: Travel CDS
4. ESRD vs CKD5
5. Re: ESRD vs CKD5
6. RE: ESRD vs CKD5
7. Re: ESRD vs CKD5
8. RE: ESRD vs CKD5
9. CDI involvement with electronic systems development
----------------------------------------------------------------------
Subject: Re: CHF question
From: dallendeb@comcast.net
Date: Tue, 22 Feb 2011 00:00:00 -0500
X-Message-Number: 1
I tell my orientees on their first day - "Coding doesn't always make sense - it does not always appear logical - it is what it is. As long as everyone follows the rules, we are okay."
----- Original Message -----
From: CDI Talk
To: dallendeb@comcast.net
Sent: Mon, 21 Feb 2011 20:06:58 -0000 (UTC)
Subject: [cdi_talk] CHF question
I was just reviewing a coding summary. Pt came in w/DOE, weight gain. I was expecting to see the final code 293 CHF without CC/MCC. The coder used 404.91 as the PDx,
Comments
From there will come electronic physician documentation. Getting the right people around the table is crucial as we develop tools and make potential changes in processes.
Thanks,
Colleen Stukenberg