A Process for Replacing CPT Codes

January 27, 2011
Dr. Michael Koriwchak
2 Min Read

Those of you who have been kind enough to read my blog know I criticize CPT coding on a regular basis.  Finally after my last tirade, a comment from John finally said what I have been dreading to hear:  “I’d love to hear more about what you think a good replacement to the current CPT system would look like.”

That is the question, isn’t it?   I’ve been criticizing long enough.  Time to put up or shut up.  A brief Internet search does not reveal any significant activity regarding a replacement for CPT except for vague “pay for performance” concepts that would pay for results rather than the care itself.  I must confess that despite thinking about CPT replacement for the past few months I don’t have any bright ideas either.

But since I raised the question in the first place I’m willing to take a shot at it.  Ignorance has never stopped me before…

I would like to begin a 4 step brainstorming process with you:

  1. Outline the shortcomings of CPT coding
  2. Translate those shortcomings into desired characteristics for a replacement system
  3. Explore applicable technologies that allow us to leverage the use of EMR to create an IT-based payment system with the desired characteristics
  4. Formulate proposals to replace CPT

I’m going to resist the urge to write my usual 1000 word post and stop here.  Please share your thoughts regarding the wisdom of this project and whether or not these 4 steps are the best way to approach the question of a replacement for CPT.

Tags

About the author

View All Posts

Dr. Michael Koriwchak

Dr. Michael J. Koriwchak received his medical degree from Duke University School of Medicine in 1988. He completed both his Internship in General Surgery and Residency in Otolaryngology-Head and Neck Surgery at Vanderbilt University Medical Center. Dr. Koriwchak continued at Vanderbilt for a fellowship in Laryngology and Care of the Professional Voice. He is board certified by the American Board of Otolaryngology-Head and Neck Surgery.
After training Dr. Koriwchak moved to Atlanta in 1995 to become one of the original physicians in Ear, Nose and Throat of Georgia. He has built a thriving practice in Laryngology, Care of the Professional Voice, Thyroid/Parathyroid Surgery, Endoscopic Sinus Surgery and General Otolaryngology. A singer himself, many of his patients are people who depend on their voice for their careers, including some well-known entertainers. Dr. Koriwchak has also performed thousands of thyroid, parathyroid and head and neck cancer operations.
Dr. Koriwchak has been working with information technology since 1977. While an undergraduate at Bucknell University he taught a computer-programming course. In medical school he wrote his own software for his laboratory research. In the 1990’s he adapted generic forms software to create one the first electronic prescription applications. Soon afterward he wrote his own chart note templates using visual BASIC script. In 2003 he became the physician champion for ENT of Georgia’s EMR implementation project. This included not only design and implementation strategy but also writing code. In 2008 the EMR implementation earned the e-Technology award from the Medical Association of Georgia.
With 7 years EMR experience, 18 years in private medical practice and over 35 years of IT experience, Dr. Koriwchak seeks opportunities to merge the information technology and medical communities, bringing information technology to health care.

1 Comment

  • Dr. I have enjoyed your viewpoints and I have learned a lot from your blogging and thank you, however, in back in your blog about EMR and CPT codes was the first time, I thought, “man, he would have to get the insurance industry to buy into that before anything would happen on that front.” I seriously think the easier way to go would be to approach it from a software application view. In this day and age, there is usually “an app for that.” And if there is not, someone can create it. What would it need to be to ease the CPT Code pain? A workflow change of some sort?

Click here to post a comment
   

Categories