Eleven ICD-10 Codes You Won't Believe & a Solution for the Transition

By Nicole Fletcher,

766Share on Google+014

ICD stands for International Classification of Diseases’, and is a system set up by the World Health Organization (WHO) to track global mortality statistics. While the previous version, ICD-9, had only 13,000 billing codes, there are now 68,000 with the October 1st ICD-10 update. The goal of this evolution is to streamline billing processes, help overall population health, and reduce healthcare costs as a whole.

All providers now need a simple way to convert claims from the ICD-9 format to ICD-10. In most cases, this is not a direct mapping and therefore, tends to be a manual, time-intensive process. If providers don’t make this shift in a timely manner, they may face returned or incomplete claims submissions, which means, you guessed it, they don’t get paid.

In honor of this change, we thought we’d offer some relevant entertainment - along with a coming soon solution - from our back Pokit, to yours.

Without further ado, here are the 11 most insane ICD-10 codes you won’t believe:


1.  W56.22 Struck by orca

In case you’re in the mood for a Free Willy-esque jetty run, keep this gem of a code in mind. If for whatever reason, your orca has poor depth perception, you may not be humming the sweet melody of Michael Jackson for long - but you will have a shiny new W56.22 on your record.


2.  W61.62XD: Struck by duck, subsequent encounter.

Really makes you re-think ‘Don’t Feed The Ducks’ signs right? Who knew it was for our safety and not their waistlines…


3.  Z63.1: Problems in relationship with in-laws.

Finally. Someone gets it. Never knew it could be a code - but for those of us lucky enough to have a better half (that comes with biological entourage), this makes perfect sense.


4.  W220.2XD: Walked into lamppost, subsequent encounter.

“Come at me” - lamppost.

SUBSEQUENT encounter? Might there may be a deeper issue if someone is just running around slamming into lamp posts all day?


5.  Y93.D: V91.07XD: Burn due to water-skis on fire, subsequent encounter​.

Are water skis even flammable? Wouldn’t you just put them in the water if they were indeed on fire? Wouldn’t you also be more likely to be hit by said water ski than burned by it?


6.  W61.1 Contact with macaw

Let it be known that we’re not trying to contact any macaws - via text, email or otherwise. In fact, we go so far as to avoid pigeons whilst walking on the street. That said, it’s unclear as to who is trying to contact any macaws - but we, and the W61.1, would advise against it.


7.  W59.21 Bitten by turtle

Evil demons, to be sure.


8.  W61.32 Pecked by chicken

Ahhh. I get it. They’re conspiring against us!


9.  V80.2 Occupant of animal-drawn vehicle injured in collision with pedestrian or animal

So you’re saying Santa was injured in a collision between his sleigh, reindeer and the easter bunny? Got it.


10.  R46.1: Bizarre personal appearance.

We get it. Marilyn Manson is indeed a strange looking human, but does he really need his own, super subjective ICD code?


11.  W.56.52 Struck by other fish

We’re not entirely sure what the purpose of the word ‘other’ is in this context - but it can’t be good.


Wildly entertaining codes aside, ideally, all payers would have been able to accept ICD-10 codes yesterday. If that’s not the case, a subset of claims in ICD-9 may need to be submitted. For this reason, software vendors should make ICD-9 codes available to providers. According to athenahealth, those vendors should also allow providers to code diagnoses in ICD-10, with vendors converting claims to ICD-9 as needed for payers not yet ICD-10 compliant.

It appears we’re in a bit of a transition time and while we can’t divulge everything at this time, you’re in luck because we do indeed have an automated ICD-9<-->ICD-10 solution coming your way soon. Stay tuned for details in the days to come.

About Nicole Fletcher

A digital marketing, content and brand expert, Nicole Fletcher is responsible for the content & social strategy at PokitDok. From data silo breakdowns to consumer education, she's passionate about making healthcare better, one tweet at a time.

View All Posts
The opinions expressed in this blog are of the authors and not of PokitDok's. The posts on this blog are for information only, and are not intended to substitute for a doctor-patient or other healthcare professional-patient relationship nor do they constitute medical or healthcare advice.

  Tags: Dev, Enterprise, Provider

Be the first to write a comment.

Your feedback