Top 10 Cringe-Worthy Things Wannabe Coders Say

My blog is over six years old!  Seriously, I just checked.  In the last six years as I've put myself out there as the Coder Coach, I've spoken either personally, over the phone, or via email to hundreds - okay, it's really probably dozens - of coders and tried to answer their questions about what it takes to be a coder.  I've been amazed at how those answers have changed since then, from the evolution of technology, which allows most coders to work remotely to finally seeing ICD-10 come to fruition. So I figure it's about time I published my top 10 list: the most cringe-worthy things people say when they tell me they want to be a coder.

Don't get me wrong.  My intent is not to put anyone off, but over the last six years, this coding thing has really caught on and I wouldn't want to steer anyone into a career that isn't right for them.  So take a moment to read through the list and decide if you're guilty of any of these. Since David Letterman's Late Show is no longer a thing, consider this my replacement Top Ten List.

And before you get upset, please read the sign: I'm not arguing, I'm just explaining why I'm right.  In other words, I'm being a coder (occupational hazard).

Number 10:Which type of coder pays the most?

Answer:  A really good one.  Focus your efforts on landing a job and then mastering it.  If you choose your work setting solely for making money, you may find yourself miserable and (maybe) sort of well off.  If you choose to follow your passion, the possibilities - and pay check - are pretty much endless.  Employers are willing to pay good money for really good coders who don't complain about how much they hate their jobs.  I don't actually do any hiring, but if I did, I would hire the hungry novice coder with a good attitude and a willingness to learn over the experienced grouchy coder who seems to hate her job.

Number 9: Should I be a hospital or physician coder?

Have you ever seen the movie City Slickers?  The answer is in that movie when Jack Palance says the meaning to life is "one thing."  Billy Crystal asks him, with great interest, what that one thing is.  The answer: that's what you've gotta figure out.  You and only you can decide which setting is right for you and there is no right or wrong answer.  I love getting an inpatient hospital chart and trying to figure out the latest surgical procedures and how to code them.  I would rather poke my eyes out with a dull pencil than assign an E/M level to a physician's chart.  I know other coders who love E/M coding.  It's like being a cat person or a dog person.  You will probably find that you like one more than the other and there is no wrong answer (unless you are not a cat person, and then we can't be friends anymore).

Number 8: No one will hire me with the coding credential I have; they all want something else

This is probably going to sting a bit, so brace yourself.  Why did you pay to get credential without first looking at local job postings and doing some research?  If you are reading this before going to school or getting certified, then do your homework before you pay any money to any educational institution.  All kinds of people will tell you anything to get your money.  Only local employers will be honest about what credentials they want.

Number 7: Where can I get free continuing education credits?

Free CEUs are out there, you just have to look for them.  Most AAPC local chapters offer free monthly educational sessions.  There are opportunities to summarize articles and get credit.  Coding Clinic offers a quarterly webinar that is free.  Other organizations offer free CEU credits.  Do an internet search and you may be surprised what you will find.  Did you do something, like attend grand rounds at a hospital, that you thought was very educational but you don't have a certificate?  Contact the certifying body and see if they will grant you CEUs for it.

Number 6: I can't afford to join AHIMA or AAPC

This one might sting too.  Find a way to make it happen.  As far as I'm concerned, when I hear this, it tells me you don't want it bad enough.  Granted, I started very young and was still living at home when I first joined AHIMA, but make no mistake, I worked hard to get where I am today. Find a way to afford that membership and show people you are serious about a coding career.  And if you have a credential through and let your membership lapse, you likely lose the credential.  You worked hard for that credential - don't let it go.

Number 5: This is my second (or third) career; I can't afford to start at the bottom

This is a great second or third career for people who discover they missed their passion until later in life.  But here's the reality: you still likely have to start at the bottom.  I've seen people find their way into coding by some very unusual means, but the ones who make it are the tenacious ones who won't take no for an answer.  Pretty much no one starts out in their dream coding job.  You will have to pay your dues.  And please don't think that means  I can't appreciate your experience in your previous profession.  There are definitely things you can bring to the table, but remember that in coding, you are a novice.  I'm a great coder, but I'm pretty sure if I decided to change careers tomorrow and become an aerospace engineer, there would be a bit of a learning curve. 

Number 4: Will you mentor me?

It's an innocent question and I'm flattered.  Really.  But I decided a long time ago that I would mentor from afar by penning this blog.  I don't have a consistent schedule to be able to spend a lot of quality one-on-one time mentoring.  But if you email me a specific question, I will do my best to answer it.  My advice is to find someone local to mentor you.  Ask them if they can meet you once a month for lunch and come prepared.  What are the questions you want answers to?  What challenges have they had in their career that they wish someone would have told them when they were getting started?  This is a great entry into your local coding network.

Number 3: I went to school for (fill in the blank) months/years and I'm certified; I'm qualified to be a coder anywhere

No.  You're really not.  I went to school too for two years and let me just tell you that even though I learned some good fundamentals, the real coding world is nothing like I thought it would be.  I learned everything I really needed to know about being a coder on the job, not in school.  I've now been coding for more than 20 years and I hold four different certifications and I have a news flash for you: I am not qualified to code anywhere.  I lack the practical experience of a physician office coder.  I find coding radiation oncology charts waaaaaayyyy outside my comfort zone.  And please don't ask me to fill out an IRF-PAI for inpatient rehabilitation.  In other words, after 20 years, I am not all that and a bag of chips, so please don't insult the world of experienced coders by thinking you have this all figured out.  I learn something new each. and. every. day.  Keep an open mind and be willing to learn - and admit when you're in over your head.  Natural curiosity and a willingness to learn is a good thing.  Acting too big for your britches is not.

Number 2: How can I get experience if no one will hire an inexperienced coder?

I would give anything if people would stop asking me this question.  Because honestly, I don't know the answer.  I don't know what your background is.  I don't know what your aptitude for coding is - and it is a skill that many people don't possess.  I don't know where you've applied or how hard you've tried to sell yourself.  And probably most importantly, I don't have a clue what it's like to try to get a job today because the atmosphere is so different from 20 years ago.  But this is what I do know.  Don't limit yourself to coding jobs.  Find a job - any job - that will require you to have coding knowledge.  When you do an online job search, search on the code sets (ICD-10 or CPT) and not the word coder.  There are so many jobs out there that revolve around coding that aren't traditional coding jobs.  Getting your foot in the door is one step closer to getting that traditional coding job - or something even better than you ever imagined.  And don't forget to network.  If you want to work with coders, surround yourself with coders.  Who you know may be your golden ticket.

And the Number 1 Cringe-Worthy Thing Wannabe Coders Say is: I want to be a coder because I want to work from home

AACK!!!!  Not a good lead in!  And if this is the first statement out of your mouth when you go into an interview, you probably won't get hired because here's a huge industry secret: hiring managers hate hearing that's why you're there.  It's like going on a first date with someone you just met and gushing about how badly you want to get married and have 6 kids. It's just not done.  If this is the real reason you want to be a coder, please re-evaluate.  Coding is a great career if you love it.  If you don't love it, you will be miserable for 8 hours every day.  And if you are miserable at home for 8 hours a day, that can be really depressing.  Also think about the child care aspect.  I often hear people say they want to work from home because they can't afford child care.  Many coding contracts require you to have child care in place.  Coding takes intense concentration and you can't babysit a kid at the same time.  Working from home is a great perk, I will admit, but it is not the reason I have the job I have.  I refer you back to Number 10 above: follow your passion.  If you're lucky, you can make some good money while you do what you love... from home... in your bathrobe.

So Many Books, So Little Time - Part 1

What's Your Idea of a Best Seller?
Every once in a while I page through a magazine taking keen interest in the best seller and "must read" book lists that everyone is talking about.  I usually tear out the pages for books that are interesting so I can download them later.  And then I rarely read them.  Or it takes me literally months to finish a book.  I love to read, but frankly, after a day of reading code books, and spending a lot of time writing, I just don't have the eye or mental energy to crack a book for fun.

My idea of a best seller is a string of code books that I use every day.  Don't worry though, I find other ways to have fun that have nothing to do with coding!

The last time I moved, I had lots of friends helping me lug boxes and it didn't take long for them to zone in on the heaviest ones: they were labeled "code books."  I have code books for various coding systems going back several years and yes, they are heavy.  And it's hard to explain to the layman why I need so many books in such an electronic age.  I've found it can also be challenging to explain the different code sets to novice coders.  But alas, I am going to give it a try in a series of blog posts because you may not be exposed to all coding systems in coding school, but depending on the setting you work in, you may find you have to become familiar with something new.

I Don't Hate Encoders
Let's get one thing out of the way first, though.  I have no issues with computers or encoders.  In fact, I use a computer for almost everything and, like so many people, I am pretty addicted to my iPhone and iPad.  But as a coding trainer, I learned by the book and I teach by the book and will always default to the book when I have a question.  Encoders are only useful when the user understands the logic behind the program and that logic is based on the book.

ICD is from Mars, HCPCS is from Venus
In healthcare, we deal with two major planets of coding systems: the International Classification of Diseases (ICD) and the Health Care Common Procedure Coding System (HCPCS).  And as if that wasn't enough, those coding systems are divided into further classifications with different uses. Coding for a physician practice?  Then you'd better brush up on different parts of the coding spectrum than what you'd see in a hospital. Coding outpatient services for a hospital? Then you need to know something different than what you would need to know if you were coding hospital inpatient services.  Want to know how to code everything?  Then it's time to become familiar with your new best seller list.  This post will start with the basic coding system that everyone uses.

ICD-9-CM Volumes 1 and 2: Everyone Does it 

You probably aren't surprised to hear that the government determines which codes we use in the U.S.  But you may be surprised to hear that the law that defines those coding systems is a little law called HIPAA. Yes, the same law that addresses privacy and security of medical information also tells us which codes we must use to report healthcare services.  This is why some code books boldly state on the cover that they support HIPAA compliance.  In order to make health information portable and comparable,the Healthcare Portability and Accountability Act of 1996 (HIPAA) makes sure we're all speaking a common language, expressed in codes, before we exchange data electronically. The privacy and security provisions are simply byproducts of making sure health care data can be shared electronically. 

Every health care case, regardless of provider and setting, has one code set in common: ICD diagnosis codes. This coding system was developed by who?  That's right - it was developed by WHO: the World Health Organization. Here in the U.S. we currently use an adaptation of WHO's ICD, which is currently the ninth version. We call the U.S. version a clinical modification. And thus, we have ICD-9-CM: the International Classification of Diseases, 9th Revision, Clinical Modification.

ICD-9-CM has three volumes. The first two volumes include the diagnosis codes.  This includes the tabular (Volume 1) and index (Volume 2). I'll address volume 3 in part 2 of this series. Bottom line here: every HIPAA-covered entity, which includes hospitals and physicians (and excludes workers' compensation and car insurers) utilizes ICD-9-CM codes to report diagnoses on a claim.

ICD-9-CM codes have 3-5 digits with a decimal point after the first three digits. All codes are numeric except for V codes, which start with a V and then have two numeric digits and may have up to two more digits after the decimal point; and E codes, which start with an E and have three numeric digits and may have an additional digit after a decimal point. E and V codes are actually "supplementary" codes that are not included in the main part of the ICD-9-CM volumes 1 and 2 code set.

Here are some examples of ICD-9-CM codes:

• 486, Pneumonia, organism unspecified
• 401.9, Essential hypertension, unspecified
• 250.00, Diabetes mellitus without mention of complication, Type II or unspecified type, not stated as uncontrolled

Examples of supplementary codes:

• V08, Asymptomatic HIV infection status
• V27.0, Outcome of delivery, single liveborn
• V76.51, Screening for malignant neoplasm of colon
• E961, Assault by corrosive or caustic substance, except poisoning
• E885.3, Fall from skis

Regardless of who you plan to code for, you will be using ICD-9-CM diagnosis codes for billing.  As such, this is likely the first coding system you learn.  

Frozen

You may notice in my picture that my most recent ICD-9-CM code book is from 2012.  That's because that was the last year that we had updates to the coding system.  ICD-9-CM is under a permanent code freeze as we optimistically await ICD-10 implementation.  Don't worry, I will address ICD-10 in future posts.  For now, you are safe using an ICD-9-CM code book from 2012 or newer, but I wouldn't waste money on a new book if (heaven forbid), ICD-10-CM is not implemented this year.  ICD-9-CM remains forever frozen and is no longer being maintained.  If you want to bone up on ICD-9-CM coding guidelines, they are printed in the front of your code book.  Or you can do what I do and download the PDF document so you can easily search the document for something specific.  Here is a link to the last version of the ICD-9-CM Official Guidelines for Coding and Reporting.  

Next up: ICD-9-CM Volume 3...

Evolution of the Coder Coach

I recently looked over my past blog postings to see what material I haven't covered. Well, there's a lot. And I realize my last few posts have been very heavy on ICD-10 - mainly because that's what I'm working on most of the time. It got me thinking, though - have I strayed from the initial intent of this blog? Who is my audience - current coders or future coders?

I have a friend and avid blogger (who's blog I am sorely behind in reading!) whom I consulted before I started the Coder Coach blog and I asked her, "What do I blog about?" She said, "Whatever you want!" Perfect! Because if I can't write about something I truly want to write about, what's the point of having a blog?! And today it really hit home - my audience has expanded.

I started the Coder Coach group and blog about 2 years ago because I identified an alarming trend. Schools are turning out coding professionals by the dozens and many of them are becoming certified. They spend a lot of time, money, and effort to get the training they will need to land them in a lucrative career only to have the doors of employers slammed in their faces because they lack experience. I've talked to my peers and we're all under regulatory pressures that make it difficult for us to train new employees. But can we ever really expect to hire someone who can truly hit the ground running without any training?

The Coder Coach isn't just this blog, it's also a Facebook group (where I post links to this blog and others) and it's a group of curious individuals in the Denver area who get together every couple of months to learn something about coding from a pro (not always me!) that goes above and beyond classroom learning. In my mind, the Coder Coach is helping to fill that big gap between school and experience.

But as I mentioned, my audience is growing. The unknown isn't just limited to coding students and new grads right now. The coding field is about to undergo a monster transition and at the same time, health information management (HIM) professionals are struggling with implementation of electronic health records (EHRs), health information exchanges (HIEs), and meaningful use standards. As an HIM professional and coder, I see and talk to many people who are paving the way for the future of these professions. My mother is a retired RHIT who was before her time - she retired about 10 years ago and before her retirement was really excited about the future of EHRs. When I tell her about what's going on in the field right now, she is in awe - we are just starting to realize what she had a vision for 15 years ago.

And as I've toured the state of Colorado, conducting outreach through our ICD-10 Task Force, I've had many HIM practitioners asking me questions that coding students ask me. Should they consider a change from the operational side of HIM to coding and what's the best way to do it? So I will try to give a good balance in my blog postings of basic things I think anyone interested in a coding career should know now along with what everyone seems to need - a little insight into what it will be like as an ICD-10 coder.

Happy evolving to all of us!

Evolution of the Coder

When I started the HIM program at the local community college in... ahem, a few years ago (sly smile), I split my time working as a file clerk in a doctor's office and a catch-all clerk in a physician's billing office. The doctor's office was a family practice managed by the owner of the billing office, which was located just next door. I remember my coworkers asking me why I was going to school to learn about medical records because I was already a file clerk. I also remember hearing one of the billers grumble about an insurance company denying claims for a male patient with pelvic pain and "can't men have pelvic pain?!"

Well, it didn't take me long to realize that the HIM field was more than filing - especially these days as hospitals and physicians move to electronic health records. And it didn't take me long to learn that, at least in the eyes of ICD-9-CM, men can't have pelvic pain - at least not the kind classified to code 625.9, Unspecified symptom associated with female genital organs (as evidenced by the word "female" in the code description and the little female symbol next to the code).

That was a long time ago and a lot has changed in the coding (and HIM) field since then. As a consultant, I work with hospitals to identify areas for coding education and then develop a curriculum and deliver training. It used to be as simple as telling my client to have all their coders at the training at a specific time and date. But not anymore. You see, the coders in a hospital aren't just sitting in the coding unit (physical or virtual) anymore. There could be coders all across a hospital. There could be people coding who don't even know they're coding. There could be nurses working with doctors to improve their documentation to ensure proper code-based reimbursement. There could be clinic coders coding the professional side for physicians working in hospital-based clinics. Finding coders in a facility is a challenge!

In short, coding has evolved.

And this is a great thing - this means that if you have the skill to be a coder - and it is a skill - there are many directions your career path can take you. So what's your passion? Do you relate to transactional work? Are you production oriented? Do you like the clinical puzzle involved in coding and secretly harbor fantasies of being Dr. Gregory House and solving the diagnostic dilemma in front of you? Do you like finance? Are you a data hound? Do you love to do research? If you answered yes to any of the above, there's a niche for you in coding.

The Transactional/Production Coder
I'll be honest. As a coder, my production, in general, stinks. At least it did the last time I did it. Some days I could concentrate very well and knock out a bunch of records. Some days it was like ADD kicked in and I just couldn't concentrate on the documentation in front of me. But there is a group of very special people who are production-based and enjoy transactional work. These are the people who are a coding manager's dream. They come to work, know how many accounts they need to code for the day, and they get it done. I have a lot of respect for those people. I wish that was me!

The Dr. House Coder
I use the TV show, House, a lot in my training sessions and blogs. I watch it and see if I can diagnose the patient before Dr. House. Usually not. But it's fun to try! Physicians and nurses alike are often surprised when they talk to coders to learn how much coders know about clinical practice and disease process. If you read enough medical records in your lifetime and see the treatment plans, it starts to rub off! If you love the clinical stuff like me, there's a lot of opportunity. Clinical documentation improvement (CDI) programs are popping up all over hospitals. The point: get the physician to document as specific as possible to ensure proper reimbursement for the hospital. Clinical documentation specialist (CDSs) are on the floor, looking at charts while the patient is in-house and talking directly with physicians. This is a job that can be done by a nurse or a coder who has been given proper clinical training. Some hospitals employ both coders and nurses as CDSs for a collaborative effort. I don't really have a desire to go back to working for a hospital, but if I did, I think I would like to be a CDS.

The Code-Based Reimbursement Coder
More and more I see coders being placed in the billing departments of hospitals. Or certified coders being given the role of charge description master (CDM) analyst. As Medicare and other code-based payers get really sticky with their billing requirements, it gets more difficult to get a clean claim out the door. Coders working on the revenue side are typically ensuring hospital systems that incorporate the use of codes are updated and interfacing/functioning properly.

A CDM analyst maintains the hospitals list of charges. If you're looking for a picture of what a CDM looks like, it's a massive spreadsheet for each department in the hospital with a line item for everything they could possibly charge for along with prices for those services and supplies. And some of those line items are attached to codes. CDM analysts work with clinical department heads to make sure charges are set up for all their services and supplies. They also make sure CPT and HCPCS codes in the CDM are updated according to regulatory standards. They might be called into a clinical department to assist in training personnel who are responsible for charging.

For lack of a better title, the code-based reimbursement analyst (an aptly named title I borrowed from a former employer where I was responsible for training code-based reimbursement analysts), is a catch-all before a claim goes out the door. Or someone who audits claims and makes corrections. This person may be responsible for working NCCI edits to get claims through the hospital scrubber and may also work closely with the coders, educating them on the latest Medicare reimbursement changes.

Code-based reimbursement analysts may also be placed in departments prone to frequent coding and charging errors, like interventional radiology, wound care, or injections and infusions. These specialty coders often work not only with documentation, but also with nurses entering charges and physicians regarding their documentation. They may also have a link to billing so they can see how their coding is translating to claim denials and errors.

If you like the revenue and compliance side of coding, there are lots of opportunities for you. Students and recent grads interested in this area often ask me where they can get training or certification for this type of job. Well, there really isn't a specific type of training for it. The best thing you can do is try to get your foot in the door and learn on the job. The coding piece of this is probably the hardest - the rest you learn from your employer. Revenue cycle is part of what I do as a consultant and I like it. I particularly like trying to figure out the complex changes Medicare has put into effect and walking that tightrope between ensuring the provider is getting paid as much as possible while maintaining revenue compliance. Let's just call this code-based coder the "Goldilocks" coder - don't code too much, don't code too little, code just right!

The Data Coder
Maybe you like analyzing data. I for one, find it dull after about 15 minutes. But I've had the joy of working with people who love doing that so we can leverage our skills for the greater good. There are many opportunities for the data-oriented coder. Of course, we should all be concerned about data integrity and coding what was done. But there are positions for people who want to slice and dice and interpret coded data. Registry programs (e.g., cancer, trauma, cardiac) often incorporate the use of codes and then some. The plus to being a registrar is that you usually become an expert in one particular area. For example, I know a cancer registrar who has been to enough tumor board meetings where cancer cases are discussed among physicians, she can effectively diagnose skin cancers most of the time (of course, the real diagnosis comes from a physician!).

Coded data is used by many - health departments, clearinghouses, universities, state hospital associations - and the list goes on. As the government becomes more concerned about outcomes of care and pay-for-performance in hospitals, there is a heavier reliance on accurate coded data. Independent companies like HealthGrades rely on coded data to compare the quality of healthcare among providers and report it to consumers. Someone is behind that data ensuring it's accuracy and interpreting it's impact and meaning. That could be you!

The "Why" Coder
I saved the best for last - well, in my opinion anyway. The "why" coder is the one who loves research and wants to know why. Why will Medicare not pay for a biopsy and an excision of a lesion done at the same time? Why does Medicare pay less for certain patients who have been discharged to a nursing home rather than home? What's the difference between two codes that at first glance appear to have identical code descriptions? Why can't men have pelvic pain?! And this is why I have trouble being a production coder. It's hard to produce when you keep asking why. Luckily, I am able to put my investigative skills to work and do research to build training materials for other coders - like production coders - so they can do their jobs efficiently. The best thing about the "why" coder is that it's free. You can learn just about anything you ever wanted to know about Medicare and their why's and not pay a cent. Of course, the price for accessing public domain information is the sheer amount of information you need to paw through to answer a single question - it can be several hundred pages.

So what's your passion? What kind of coder will you be? The opportunities are endless and we need all kinds!

Opportunity Happens: ICD-10 is Mine

To quote my recent Facebook posting, "Ever notice that amazing opportunities are followed by boatloads of work?" That's my excuse for where I've been: opportunities and their resulting heavy workload. For me, opportunity is cleverly disguised as ICD-10. What is your opportunity?

Just to catch you up, I recently accepted a senior consulting position with a new consulting firm. Haugen Consulting Group is based locally in Denver and while I will be pretty much doing what I've been doing - coding consulting and education - I will also be working with a team of amazing consultants as we lead our clients through the ICD-10 implementation.

I am also chairing the Colorado Health Information Management Association's ICD-10 Task Force, which is gaining momentum each month. For the last month I've visited two of Colorado's three regional HIM associations and also had the opportunity to speak on ICD-10 and HIPAA 5010 implementation last month in Montana and do an audio conference on the new leg revascularization CPT codes for HCPro. Later this month I will present at CHIMA's spring meeting on the importance of mentoring our future workforce (I'm going to bat for all of you!) and will also moderate an ICD-10 panel. These speaking engagements lead to more speaking engagements, which is what I love to do. And sometimes the speaking engagements lead to contracts, writing opportunities, and other networking opportunities.

While I've been working on some exciting prospects of my own, some of the people I've been mentoring have also received some opportunities. I recently got a call from a recruiter asking about one such candidate and another recent grad got a part-time position in an HIM department based on her work there as a volunteer. And my advice to them now that they have their feet in the door is to work hard to keep those opportunities coming.

So if you've completed a coding or HIM program and are having trouble finding work, here's a reminder of some of the things I recommend for getting your start:

• Network! I've received jobs from 4 people I knew or worked with in the past. And I've hired people I've worked with in volunteer organizations. Who you know matters!
• View everything as a learning experience. Work is work, no matter how much you enjoy what you do. There are days when you won't like the tasks that have been assigned, but there may come a day when you need to tap into that experience.
• Find a workplace mentor. Once you get your foot in the door, find someone you can go to with questions. This doesn't have to be a manager - it can be a lead, a person who has worked there "forever" or even a team of people.
  
• Keep a positive attitude. No one wants to work with someone who is negative and miserable. A positive attitude goes a long way in any industry.
• Don't give up - because opportunity happens!
  

Two Track Mind: ICD-10 and Vascular CPT Coding

Do I seem like a stranger? Because I feel like a stranger. These days I have two things on my mind: ICD-10 and the CPT coding changes for vascular procedures. And pretty much anything outside of these two topics isn't getting much of my attention lately - including blogging. So in an effort to provide you with a recent blog post - and to keep my attention focused on the tasks at hand - I figured I would blog about what I've been up to recently. This will give some insight into the challenges that existing coding professionals are facing today.

Before I let you in on what's been on my plate, I should mention that there is no crossover between these two topics. They are two very different aspects of coding that use two entirely different parts of the human brain. Or at least, they use two very different parts of my brain! When asked why I am so deeply involved in two areas that are so vastly different, all I can say is, I love a challenge. And challenged I've been!

CPT Code Changes

I know what you're thinking. "It's March, Kristi, the CPT code changes were effective January 1 so that's old news." Well, the reality is, it takes some time to get used to new codes. Since I spend a significant amount of time as a subject matter expert (SME) for my clients in the realm of cardiac catheterization and peripheral vascular interventional radiology coding and charging, I can tell you that 2011 has presented my clients with some significant challenges. First of all - the deletion and nearly complete overhaul of the cardiac catheterization section of CPT. If you have a chance to look at a 2011 CPT codebook (I recommend the Professional Edition since it shows all code changes in color-coded fashion), and compare it to a 2010 book, you'll see what I mean.

My biggest challenge? They changed the code descriptions and code numbers, but in many cases used the same digits - just in a different order. A dyslexic's nightmare and yes, yours truly is dyslexic. There are a couple of perks now - we no longer have to worry about coding left ventriculography separately, it's bundled into the left heart catheterization code, and for the most part, supervision and interpretation (S&I) codes are a thing of the past.

The peripheral vascular coding is getting really interesting. This year the American Medical Association (AMA) decided that leg revascularization procedures could be more effectively reported using bundled codes. This new Wal-Mart approach to coding is becoming more commonplace in interventional radiology (IR) coding. What do I mean about Wal-Mart codes? Well, vascular IR coding has historically involved the separate reporting of all procedure codes, including the catheterization or approach, which is typically a no-no in coding. The end result is often a list of 4 or 5 codes to describe one procedure. Wal-Mart coding is "one stop shopping" where everything is included in a single code. Maybe I should call them Ragu codes for those who remember the old Ragu pasta sauce commercials. You know - "It's in there!" This Wal-Mart or Ragu concept of coding means unlearning many complex IR coding guidelines that have been ingrained in our brains over the past few years.

The new leg revascularization codes are set up based on a heirarchy - angioplasty followed by atherectomy followed by stenting - with newly established vascular territories. The iliac territory consists of three vessels. The femoral-popliteal territory is treated as a single vessel. And the tibioperoneal territory as three vessels. To make things more confusing, the AMA deleted all of the atherectomy codes from Category I in CPT and moved them to Category III.

And because IR is arguably the most difficult area of CPT coding (as an IR SME I may be biased), someone has to research all this and educate coders on the changes. Thus, I find myself updating training materials with these changes and presenting the changes. If the areas of cardiac catheterization and IR interest you, I suggest you acquire a solid foundation on basic medical coding first. These 2 areas are difficult for even the most seasoned coders.

ICD-10-CM and ICD-10-PCS

Well if you're a coder, a coding student, or have done any research at all about the coding field, you know we're in for a huge change with the implementation of ICD-10-CM and ICD-10-PCS in 2013. I would like to say that all organizations are in full swing and getting ready for the transition. What I'm hearing as I talk with organizations, though, is that they are just getting started - a full 1-2 years behind the recommended schedule.

In recent weeks I've taken my ICD-10-CM/PCS trainer recertification through AHIMA and kicked off a Task Force through the Colorado Health Information Management Association (CHIMA). As chairperson of the ICD-10 Task Force here in Colorado, I've had the chance to meet with providers and organizations who will be impacted by the ICD-10 code sets. And I am also embarking on a project through AHIMA to get ensure that Colorado Medicaid is ready for the transition.

In addition to that, I'm preparing presentations for the spring conference season and developing ICD-10 tools and training programs for my company. Here's a shameless plug for The Wilshire Group - just in case you're looking for some additional ICD-10 references! My favorite part is the ICD-10 countdown. I've set this as one of my home pages so I can feel the urgency every time I open my browser!

Prepare for Your Challenge

If you really have a passion for coding, then this commentary got you really excited to learn more. I wish I could properly convey how much more difficult coding is than simply looking up a code in a book. And I wish you could get an accurate depiction of what your daily work will look like as a coder. But the truth is, you don't really "get it" until you get into it and although I know so many are frustrated because they can't get the required experience to get hired, I've said it time and again - keep trying to find an angle to get the experience you need to get your foot in the door. And once you're in, I hope you're ready for the challenge because it's a constant learning experience.

What the Heck is a DRG? And Why Should I Care About Case Mix?

So you want to be a coder. And not just that, you want to be a hospital coder because, on average, they make more money than physician coders. And you don't just want to be a hospital coder, you want to be an inpatient hospital coder because then you get to look at the whole chart and piece together the patient's clinical picture. If this is your goal, then everything you need to know you will not learn in school. And that's mainly because there is so much to learn and practical experience is key.

Most of all, if you want to be an inpatient coder, you need to know diagnosis-related groups (DRGs) because in hospitals, it's all about DRGs and case mix - and compliance. If you have no idea what I'm talking about, fear not - here's a primer on DRGs! I wish I could say I cover it all here, but this is just a beginning!

What is a DRG?
The ICD-9-CM coding system contains about 16,000 diagnosis codes and ICD-10-CM contains over 68,000 codes. Imagine trying to determine a payment amount for each individual condition. And that doesn't include accounting for procedures. The most logical solution is to create a system that allows for broader classification of conditions and services for easier comparison and assignment into payment categories. DRGs were created for this purpose. I look at DRGs as a way to "organize the junk drawer" where patients are grouped into different categories based on similar conditions and cost to treat the patient.

History
DRGs were first developed at Yale University in 1975 for the purpose of grouping together patients with similar treatments and conditions for comparative studies. On October 1, 1983, DRGs were adopted by Medicare as a basis of payment for inpatient hospital services in order to attempt to control hospital costs. Since then, the original DRG system has been changed and advanced by various companies and agencies and represents a rather generic term. These days, we have various DRG systems in use - some proprietary and some a matter of public record - all of which group patients in different ways. Two of the main DRG systems currently in use are the Medicare Severity DRG (MS-DRGs) and 3M's All Patient Refined DRGs (APR-DRGs). Different DRG systems are used by different payers.

How to Get a DRG
All DRG systems are a little different, but the basic premise is the same. DRGs are based on codes. In effect, DRGs are codes made up of codes. The following elements are taken into consideration when grouping a DRG:

• ICD-9-CM diagnosis codes
• ICD-9-CM procedure codes
• Discharge disposition
• Patient gender
• Patient age
• Coding definitions as defined by the Uniform Hospital Discharge Data Set (UHDDS) - in other words, the sequence of codes on the claim

Back in the 80s, DRGs were grouped manually using decision trees. These days, DRGs are grouped with the touch of a button and DRG groupers are a big part of encoding software. But I would be doing you a disservice if I didn't at least give you an idea of the grouper logic. As I mentioned, there are different DRG systems and probably the most popular is the MS-DRG system, so I will explain how MS-DRG grouper logic works.

MS-DRG Grouper Logic
The first step in assigning an MS-DRG is to classify the case into one of the 25 major diagnostic categories (MDC). These MDCs are based on the principal (first) diagnosis and, with a few exceptions, are based on body systems, such as the female reproductive system. Five MDCs are not based on body systems (injuries, poison and toxic effect of drugs; burns; factors influencing health status (V codes); multiple significant trauma; and human immunodeficiency virus infection). Organ transplant cases are not assigned to MDCs, but are immediately classified based on procedure, rather than diagnosis. These are called pre-MDC DRGs.

Once a case has been assigned into an MDC (with the exception of the transplant pre-MDCs), it is determined to be either medical or surgical. Surgical cases require more resource consumption (that's industry speak for "costs more!"), so they must be separated from the medical cases. If there are no procedure codes on the case (e.g., a patient with pneumonia may have no procedure codes), then it's simple - it's a medical case. But if the patient had a procedure, that procedure may or may not be considered surgical. For example, an appendectomy is quite clearly a surgical procedure. But something like suturing a laceration is not. It's all based on resource consumption - the cost of performing the procedure. In general, anything requiring an operating room is surgical.

Quick sidebar here - this is why skin debridement is such a hot topic in the world of coding compliance. Nonexcisional debridement (code 86.28) groups as a medical case. However, excisional debridement (code 86.22) groups as a surgical case and the change in reimbursement is rather drastic.

Okay, so now that we have our MDC and a designation as medical or surgical, we need to look at the other diagnoses on the claim. Right now, Medicare is able to process the first 9 diagnoses on the claim (even though 18 are reportable). These other diagnoses, depending on their severity, may be designated as complications and comorbidities (CCs) or major complications and comorbidities (MCCs). Medicare maintains lists of CCs and MCCs and updates them annually. CCs and MCCs are conditions that have been identified as significantly impacting hospital costs for treating patient with those conditions. For example, it's been determined that congestive heart failure without further specification does not significantly impact costs and it is not a CC/MCC. However, patients with chronic systolic or diastolic heart failure do have slightly higher costs, so those conditions are CCs. More so, patients with acute systolic or diastolic heart failure have even higher costs, so they are designated as MCCs. Are you beginning to see how slight changes in a physician's diagnostic statement impact coding and thus payment?

DRG Weights
Okay, so we know the MDC, whether the case is medical or surgical, and whether or not there are any CCs or MCCs. How does that translate into reimbursement? Well, if you're using an encoder (and if you code for a hospital, you will), you hit a button and presto! You have a DRG with a relative weight. Now if only you knew what that relative weight meant. The DRG relative weight is the average amount of resources it takes to treat a patient in that DRG. Huh?

Let me demonstrate. The baseline relative weight is 1 and represents average resource consumption for all patients. Anything less than 1 uses less than average resources. Anything above 1 uses more than average resources. So let's compare some respiratory MS-DRGs:

• MS-DRG for lung transplant has a relative weight of 9.3350
• MS-DRG for simple pneumonia (no CC/MCC) has a relative weight of 0.7096
• MS-DRG for chronic obstructive pulmonary disease with an MCC has a weight of 1.1924

You can see how different combinations of codes lead to different MS-DRGs with different relative weights. In order to convert that into monetary terms, we multiply the relative weight by the hospital base rate. Now I'm sure you want to know how to get that hospital base rate. Me too. Well, up to a point. The base rate is exclusive to each hospital and takes a lot of historical, facility-specific data into account, like what they've been paid in the past, whether or not they are an urban or rural hospital, and how much the hospital pays out in wages. That's just more math than my poor little head can comprehend! So for the purposes of this exercise, let's pretend like this hospital - we'll call it Happyville Hospital - has a base rate of $5000. So if we multiply the relative weights above by $5000, our reimbursement for those cases, respectively, is $46,675, $3,548, and $5,962.

Case Mix
You just might be asked in an interview if you understand case mix. It's a good indication of whether or not someone really understands DRGs. And I have to admit, in my sometimes sadistic manner, I like seeing that look of glazed-over confusion on someone's face when I bring up case mix. But case mix is simple. It's the average relative weight for a hospital. So get out a big piece of paper for your hospital and start writing down the relative weights for every single case and then divide to get your average. Okay, so it's computerized now. But that's all case mix is - an average.

In the industry, we officially refer to case mix as the type of patients a hospital treats. Let's say at Happyville, we have a high volume of transplant cases plus a trauma center and a well-renowned cardiac program. These are all highly weighted types of cases and our overall case mix will be higher than say, Anytown Hospital down the street that has no trauma center, no transplant program, and basic cardiac services (they transfer all their serious cardiac cases to Happyville!). Happyville's case mix will be higher than Anytown's.

As a coder, you don't need to know what your specific hospital's case mix is at any given time. But knowing what impacts case mix is an indication that you know your stuff. First and foremost, case mix fluctuates. Most hospitals monitor case mix on a monthly basis because changes in case mix are a precursor to changes in reimbursement. Of course your CFO wants case mix to continue to rise, but that could be a red flag. And he certainly doesn't want case mix to fall. If case mix begins to decrease, the first place hospital administration usually looks is coding - after all, case mix is based on DRGs, which are based on codes. But there are lots of things that can impact case mix and many of them have nothing to do with coding, such as:

• The addition or removal of a heavy admitting physician - especially specialty surgeons
• Opening or closing a specialty unit
• Changes in a facility's trauma level designation
• Movement of cases from the inpatient setting to outpatient, and
• Anything else that impacts the type of services the hospital provides

Your Life as an Inpatient Coder
As an inpatient coder your job is to make sure you get all the codes on the claim in the correct order so that the accurate DRG is assigned and the hospital gets paid appropriately. When I put it that way, it sounds so easy! The reality is, with more and more patients being treated as outpatients, those who are admitted as inpatients are sicker than they've ever been. And sicker means harder to code. For instance, the patient comes in with shortness of breath and the final diagnosis is acute exacerbation of COPD, stapholococcal pneumonia, and respiratory failure. How you code and sequence the case will determine the appropriate DRG and reimbursement. The good news is, you'll have an encoder to help you model the DRGs and see what pays what. The bad news is, you have to paw through the medical record to determine the true underlying cause of that shortness of breath.

So are you ready for the challenge? Are you ready to apply DRGs?

There's No Future in Coding... or is There?

When I graduated from college 15 years ago, there was a big local trend in my area to train RHITs to become utilization review (UR) case managers. In case you haven't heard of UR, they are typically nurses who review medical record documentation against criteria from insurance companies to help the doctors know when it would be best to discharge patients and they help arrange post-hospitalization care if needed. There was a local company created by an RHIT who received her first post-grad job from none other than my mom (also an RHIT) and she promised me an interview when I graduated. See? Networking is important!

Once I graduated, I called in the favor and met with her HR recruiter. The only problem was, I had just finished doing a lot of coding at an internship and I had fallen in love with it. Believe it or not, at that time there were no open coding positions. I used to joke that the only way I would get hired as a coder is if someone moved out of state or retired! So I took the interview at the UR company and it sounded okay. It sounded like something I could do and they were willing to train. They were even willing to give me raise once I passed my RHIT exam.

And then I got the call from my internship supervisor. She was excited to tell me that they had just run the numbers and decided they needed another outpatient coder. She really wanted to hire me as an inpatient coder, but this is what she could offer me to get my foot in the door. It was more money than the starting position at the UR company, but less than I would make at the UR company once I passed my RHIT. But I didn't care about the money, I wanted to code. So I took the coding job and graciously declined the UR position. And I was told by the HR recruiter at the UR company that there was no future in coding - the future was UR.

I'm sure there are still some RHITs out there doing UR, but within a few years of beginning my coding career, the coding industry exploded. We had OIG investigations and new code-based payment systems and a seemingly endless list of things to keep the job new and fresh. Now I look back on that time 15 years ago when I wondered if I was making a mistake because I followed my gut rather than looking at trends. And then I look forward at the challenges we're facing in the future of coding and can say with a resounding "hooray!" - I think I made the right decision!

Is the Future EHRs?
These days I'm starting to hear it again - "Go into electronic health records (EHRs), there's no future in coding." What?! That's absurd! I'm not here to tell you there is no future in EHRs, but don't let anyone tell you there's no future in coding either. The health information management (HIM) field has historically been divided into operations, i.e., managing patient health information, and coding.

These days the most innovative thing to hit operations is the EHR. More hospitals are moving toward EHRs that will allow for better accessibility to patient health information for continuity of care. There are programs popping up everywhere to close the education gap between HIM and information systems and the term "health informatics" is the new buzz term for the early part of the 21st century.

I have a lot of colleagues who are are firmly embedded in EHR implementations. As a matter of fact, my company is an EHR implementation company. But most of us currently working in the field know that while there is an absolute future in EHRs for any HIM professional, coding is not and never will be a dead-end career. And if you can understand how coding relates to EHRs and vice versa, you can be very marketable.

RHIT vs. RHIA
When I received my RHIT, I assumed I would go into management like my mom. She was an RHIT who had been everything from a coder in her early career to director of HIM and quality for a small psych hospital. RHITs are not typically managers, though, they are usually more ingrained in technical work. The associates program for HIM that precedes the RHIT certification exam is loaded with classes on the technical aspects of managing patient information - including coding - with a few management classes thrown in. The bachelors program that prepares one to sit for the RHIA exam is less technical and more management.

What we tell folks is, if they want to manage an HIM program, become an RHIA. If you want to be a technical worker, like a coder or cancer registrar, become an RHIT. But this isn't a hard and fast rule. I recently talked to an RHIA student who really thinks she wants to be a coder, but her fellow students are telling her there is no future in coding, the future is in managing EHR implementations. She really wants to pursue coding, though.

Follow Your Bliss
I'm not really one for corny sayings like "follow your bliss" but this is your career we're talking about. No matter what your educational background - RHIT or RHIA - if you're trying to decide between coding and EHRs, don't let anyone else influence your decision. Even if you're an RHIA who wants to be a coder or an RHIT who aspires to manage some day (it can and has been done!), go after what you want.

And don't let anyone tell you there is no future in coding or EHRs. All I see for the future of HIM is opportunity in every direction I look.

It's Coding Season!

I'm sometimes asked if there's a busy time of year for coders or if it's pretty much status quo. As a matter of fact, there is a busy time of year for coders and this is it!

Every year, we gear up for all the upcoming year's coding changes. That means letting coders know which codes have been deleted, expanded, and added and letting coders, physicians, administrators, and revenue cycle personnel know how code-based reimbursement will be affected in the coming year. This may seem rather straightforward, but since we work with more than one code set with different implementation dates, fourth quarter of each year can be pretty crazy!

ICD-9-CM Codes
The ICD-9-CM diagnosis and procedure codes are updated annually with the Center for Medicare and Medicaid Services' (CMS) fiscal year (FY), which begins October 1. These codes are used to report diagnoses for all health care settings and procedures for hospital inpatients. Right now, you will find coders acquiring their FY 2011 ICD-9-CM code books and attending seminars on the code updates. Some of this year's highlights include:

Diagnosis Codes:

• A new code for obesity hypoventilation syndrome
• Expansion of fluid overload code to differentiate between transfusion-associated fluid overload and other causes
  
• Expansion of the avian flu codes to include manifestations of the disease
• Expansion of the blood transfusion incompatibility codes to differentiate between ABO and Rh incompatibility
• Additional personal history codes
• Expansion of the body mass index (BMI) codes up to allow for classification of BMI in varying increments up to 70 and over
• A new section of V codes to report retained foreign body fragments
• A new section of V codes to report the number of placentae associated with multiple fetal gestations

ICD-9-CM diagnosis codes are within the public domain and the 2011 revisions can be found on the National Center for Health Statistics' (NCHS) website.

Procedure Codes:

• New code for placement of a central venous catheter under imaging guidance
• New codes for carotid sinus stimulation components and devices

Changes to the ICD-9-CM procedure codes are within the public domain and are available on CMS' website.

IPPS and MS-DRGs
The inpatient prospective payment system (IPPS), the system used for Medicare payments for inpatient hospitalizations, is also updated each year on October 1. This includes recalibration of the relative weights for the classification system used under IPPS - the Medicare severity diagnosis related groups (MS-DRGs). This year, the major changes to the MS-DRGs include:

• A documentation and coding adjustment of -2.9%, wherein CMS will discount payments in FY 2011 to hospitals by 2.9% in order to remain budget neutral. The attempt to remain budget neutral is to counteract the financial impact of implementing a severity-based DRG system 3 years ago.
• The addition of 12 new quality measures to be reported by hospitals under the Reporting Hospital Quality Data for Annual Payment Update (RHQDAPU) program.
• A revamping of Medicare's 3-day rule, which bundles payment for outpatient services provided within 3 days of inpatient admission into the inpatient payment.

Changes to the IPPS and MS-DRGs are available in the public domain through CMS' website as well as the Federal Register.

CPT Codes
Changes to CPT codes become effective with each calendar year on January 1. These codes are used to report procedures and services for physicians and hospital outpatients. Because CPT codes are owned and maintained by the American Medical Association (AMA), they are not available in the public domain. As such, finding a list of upcoming CPT code changes is often a closely guarded secret until the CPT book is published, generally around November or December each year.

The best way to get updates on upcoming CPT codes is to attend either the AHIMA's Annual Clinical Coding Meeting (September 25 and 26, 2010 in Orlando) for the national code update or the AMA's CPT and RBRVS Symposium (November 10-12, 2010 in Chicago). After the AMA's Symposium, it's common to see articles appearing in coding journals and publications discussing the upcoming coding changes.

HCPCS Codes
HCPCS codes are developed and maintained by CMS to report services, supplies, and procedures that are not found in CPT. They are utilized by physicians and hospital outpatient reporting. HCPCS codes are potentially updated quarterly, although an update isn't always required that frequently. HCPCS codebooks may be purchased on an annual basis with the calendar year and quarterly updates are found on CMS' website. HCPCS codes are in the public domain and general information about their use can also be found on CMS' website.

OPPS and APCs
The outpatient prospective payment system (OPPS) is the payment system utilized by Medicare to pay for hospital outpatient claims. This is updated on January 1 each year, along with the CPT and HCPCS codes. The proposed rule was published in the Federal Register on August 3 and CMS accepted public comment on that proposed rule through August 31. CMS will review the comments, make final determinations, and finalize the rule by November 1.

OPPS changes include recalibration of the relative weights for ambulatory payment classifications (APCs), the categories used to group similar procedures for payment.

Some highlights of the proposed rule include:

• Two areas that have undergone frequent changes or requested changes will remain static for 2011: drug and substance administration and hospital outpatient evaluation and management visit guidelines
• Establishment of a list of services that must be performed under physician supervision
• Removal of three orthopedic codes from the inpatient-only list, making them reimbursable as outpatients under Medicare
• A new method of paying for separately payable drugs
  

Information about OPPS and APCs can be found on CMS' website.

Physician Fee Schedule and RVUs
Physician payment, as outlined in the physician fee schedule, is updated annually on January 1 by Medicare. The proposed rule was published in the Federal Register on July 13 and the comment period ended on August 24. The physician fee schedule outlines the relative value units (RVUs) for each CPT code based on the amount of work the physician performs. Information on the Medicare physician fee schedule and RVUs is within the public domain and can be found on Medicare's website.

Too Much Information?
It sounds like an awful lot of information, but remember this - not every coding professional needs to learn the ins and outs of every coding and payment system. Because I work with hospital clients, I will be focusing on everything but the physician fee schedule. And those who work in physician offices will focus on ICD-9-CM diagnosis code changes, CPT/HCPCS code changes, and the physician fee schedule only. Even so, it's enough of an impact to call fourth quarter "coding season!"

Why Wait?

Are you currently a coding student? Are you nearing graduation? Are you waiting until you graduate to look for a job? If you answered yes to any of the above, I ask you, why wait? Start applying for coding jobs now.

We all know it can be hard to get that first coding job or even to land in an entry-level position. So if you can make it work, I recommend applying for any job now that will boost your chances of moving into a coding position. That might mean working as a file clerk or scanner (someone who scans in medical record documentation into the hospital's imaging system). Anything that will get you closer than you are today to being a coder.

If you start now you will also find that you won't be competing with your fellow graduates for the same jobs come graduation day. And for all you kinesthetic (learn-by-doing) learners out there, you may find it will help you piece together the puzzle we call health care revenue. In other words, you'll get experience!

So take this time to get a leg up on your coding career and get started! Good luck!

Top Ten Reasons to be a Coding Professional

I would love to take credit for making up this list of reasons to be a coder, but I can't. It's a list that came out about 15 years ago and I believe it was published in The Journal of AHIMA. This list was popular when I first started coding in the mid-90s. I have yet to see an electronic copy of it, but found a photocopied list in a scrapbook (er, chart) my coworkers gave me when I left my first coding job. This list graced my bulletin board for a long time!

Some of these are a bit dated, but most still ring pretty true and I updated Ms. Scichilone's credentials as she is still a well-respected practicing HIM professional. I hope you enjoy this little bit of levity!

Top Ten Reasons to be a Coding Professional
by Rita Scichilone, MHSA, RHIA, CCS, CCS-P, CHC

10. You love to read really small print.

9. Carrying around code books is better weight training than those cute little dumbbells you buy at the fitness store.

8. Classification systems and nomenclatures make great party conversation. "I'll bet you don't know what SNODO* is!"

7. If a patient can do it, get it, or hurt it, you can code it.

6. You love explaining what you do each day - "Oh, I typically transform sixty-five or so pages of complicated clinical information written in a foreign language (medical terminology) into numeric codes that will fit on a one-page form."

5. When you get carpal tunnel syndrome from turning those pages and burning up a computer keyboard, you'll know how to code it for your insurance company.

4. You can impress your friends by saying you'll meet them after work for some 94.38 at your favorite hangout."**

3. You are passionate about acronyms (DRG, APG, HCPCS, HCFA, HEDIS, CPT, UHDDS, ICD-9-CM, CHMIS, WEDI, UB-92)***

2. When you hear "The AR days dropped again today," you get goosebumps.

1. The eternal mysteries of ICD-9-CM and HCPCS CPT-4 are transformed at your touch into essential mastery of critical clinical data indexing that can change the health of America!


*Standard Nomenclature of Disease and Operations (SNODO) was a coding system that predated ICD-9-CM

**94.38, Supportive verbal psychotherapy

*** Ambulatory patient groups (APGs) were proposed prior to the use of ambulatory payment classifications (APCs); the Health Care Financing Administration (HCFA) was renamed the Centers for Medicare and Medicaid Services (CMS) in 2000, the uniform bill 1992 has been updated and replaced with the uniform bill 2004 (UB-04)

What Are You Going to do About It?

I will be the first one to admit when I’m bad at something (like math), but as far as joke-telling goes, I think I’m actually quite good. It’s the remembering part that’s tricky. But I do have a few favorite jokes in my arsenal – a blonde joke or two (it’s okay, I’m blonde!), a couple of jokes that are only truly appreciated by kids under the age of 8, and one joke that teaches a lesson. I am going to share the latter with you now.

A damn broke uphill from a town and the entire town had to be evacuated before the eventual flooding and devastation that was going to occur. One man began to pray and asked that God protect him from the flood. The police came to his door and told him to evacuate and he said, “No thank you. I believe and have faith that the Lord will provide.” The police left. Soon the flood waters were starting to make their way into the town and the man was forced to move to the second story of his home. He prayed again and asked God to protect him. A motor boat with rescuers came by offering to take the man to safety but again he said, “No thank you. I believe and have faith that the Lord will provide.” The rescuers sighed and shook their heads and moved on. Soon after that, the flood waters were so high the man had to take refuge on his roof. He maintained his prayer for safety. In one final attempt to clear the town, rescuers came by in a helicopter but the man refused to get on board. He said, “No thank you. I believe and have faith that the Lord will provide.” Soon there was no place left to climb and the unfortunate man drowned. When he got to heaven and spoke to God he said, “Lord, I believed in you and had faith that you would save me. Why did you let me drown?” And God said to him, “I provided you with the police, a motor boat, and a helicopter. What else was I supposed to do?!”

I’ve heard the joke many times – sometimes as part of a sermon, sometimes as an anecdote to get people to realize they have more control over their lives than they think. I receive many phone calls and emails from students and novice coders who are frustrated with the hiring process. And since I’ve committed to mentoring, I try to find time to respond to each of those emails. I am always happy to give a little pep talk or give a little advice that may guide them in the right direction. But occasionally, I get an email that is a series of complaints and blame games and all I can think is: what are you going to do about it?

Don’t get me wrong. No one loves a good venting session more than me. I even have friends that I can email and rant to and they won’t take it personally. I can type a 2 page email and usually get the response, “Feel better now?” and usually I do. I am all for venting frustration. But at some point, you have to make a decision to do something about the problem or change course. Otherwise you’ll go crazy. Think of Einstein’s famous quote about the definition of insanity: “doing the same thing over and over again and expecting different results.” So if you’re stuck in venting mode or you haven’t tried a different attempt at getting what you want, it’s time to break the monotony and move on.

I recently started reading The Last Lecture by Randy Pausch with Jeffrey Zaslow. I don’t get a lot of time to read and I am by no means a speed reader, so it will probably take me at least a week to get through this “quick read.” The story, if you are unfamiliar, chronicles the last lecture given by Randy Pausch, a professor at Carnegie Mellon University before he succumbed to pancreatic cancer. He was 47-years-old and left a wife and three young children behind. His lecture entitled “Really Achieving Your Childhood Dreams” was really directed at his children (the lecture was recorded) and is so inspiring, it yielded a spotlight on a national TV news program, the book, and countless videos on YouTube.

In the book, Pausch dedicates an entire chapter to his parents and their parenting skills. One of the things his parents did for him was to encourage him to find answers to the unknown. This is something I felt I had in common with him – my parents were always telling me to “look it up” if I didn’t know an answer. In fact, my mother always told me, “Knowledge isn’t what you know; it’s whether or not you know where to find the answer.” And as much as I hated the look-it-up-response (I actually thought they were lazy), I appreciate it now because now I don’t rely on someone else to figure everything out for me.

I am at a point in my life where I am probably the happiest I’ve ever been. And I’ve noticed that as a happy person, the last people I want to be around are unhappy people. Unfortunately, I have a few in my life – friends, acquaintances – who every time I talk to them dump every last problem on me and then wait for me to speak. Sometimes I mess up and give them advice. What I’ve found to be more effective is to ask them what they plan to do about it. If all they want to do is complain about their situation and aren’t willing to do anything about it, there’s really not much else I can do other than listen and wait it out until they’re done. But every once in awhile, I see something flicker in their eyes and I can tell they haven’t really thought what they would do about it. And I sometimes suspect they’re waiting for someone to tell them what to do. My hope is that my question is a virtual slap-in-the-face to get them past the complaining stage and onto the fixing stage.

Are you one of these people? Are you waiting for the magic opportunity that will get you into the coding profession? Have you really tried everything to get into the industry? I defer again to Randy Pausch, who created a list of childhood dreams. On that list was “being in zero gravity.” His students won a contest that enabled them to experience NASA’s plane “The Weightless Wonder,” which helps astronauts get used to a zero gravity environment. Unfortunately for Pausch, no faculty was allowed. So he found a loophole and withdrew his application as faculty and resubmitted it as press (for which he had to do some additional work to get the story into the media). It worked and Pausch was able to cross one thing off his childhood to do list. So I ask you again, if you’ve tried to get a job and have failed, what are you going to do about it?