RE: CDI involvement with electronic systemsdevelopment

I agree very much with Robert --
*Talk / plan / note what features (specific, concrete) you want in an ideal EMR. Don't worry if these things are technically difficult, at least get the concepts out there and being considered (how can we do xxx?).
*Advocate to be included.
*Look at your reporting chain and forward your input -- whether CDI is directly involved or represented, it will be to the benefit of the organization.
*Be an early adapter -- discover how the EMR works, what functionality is available, how that can be adapted for better documentation, advocate to be a resource to help providers in creating/designing templates......

The recent article about debridements -- development of a template -- is a great example of how CDI / Coding / HIMS can be involved. That template just screams for inclusion in an EMR and then widely distributed & education to providers.

Politics and power do seem to play a role, and may interfere with the input from a CDI function....but a CDI program that has a strong and collaborative relationship with providers, leadership, etc. will find a way in.

And no, when our EMR was being designed 4+ years ago, CDI was not involved. The process was focused through IS and provider/clinician perspectives. Today, that would be different.

Don


Sign In or Register to comment.