There are requirements for some data to be reported to federal and international organisations. For instance, these codes are also used on death certificates I think, so they can track whether a lot of people are dieing of flu (primary cause) after contact with duck (qualifier) and there is a bird flu outbreak.
There are many coding systems - semi-standard extensions of ICD used to identify very specific types of cancer or the ontology based SNOMED which is rarely used as intended but none the less is becoming the standard.
These codes are used for billing in the US to some extent but also for lots of other things, they are just a standardized set of codes that hospital IT systems use to talk about what is wrong with patients so they can somewhat interoperate - and they are forced to use them by government because the vendors prefer walled gardens over interoperability.
I’ve lost count of all these times a freshly onboarded dev, replacing the old one, decided the système was needlessly complex, nothing made sense, and it’d be easier to just rebuild everything from the ground up.
Only to end up with a similarly complicated nonsense, because the complexity actually was in the domain, and he knew nothing of it.
This is the root of the problem. These codes should not be used for billing. That should be much more coarse. They bill you for visiting the GP. They bill you for a surgery. Adding the codes to the records is fine and good, but really should just be an internal detail that isn't that relevant to the patient.
Rabies, which is not just animals but also predators (snakes) that eat animals with rabies. There is even a disease called "seal finger" that is linked to seal bites. And bats, all sorts of nasty stuff can come from bats.
Unfortunately, some doctors are willing to take advantage of this.
Everyone is actually collaborating against you which is why in the US we only provide free health care for a small fraction of the populace but still manage to pay for THOSE folks as much as some other developed nations pay to cover their entire population.
You could say this 30 years ago, but it's not really the case today. The majority of physicians are now salaried, not independent. And even for many of the ones in independent private practice, the amount they make is not necessarily tied anymore to the services they provide, due to the rise of capitation and other forms of bundled service agreements.
Nowadays, it's actually statistically more likely that you receive care from a doctor who has an explicit incentive to undertreat, because they receive a fixed amount of money per patient per year, and the costs of treatment come out of pocket directly with no additional reimbursement.
(I only happen to know this because they complain nearly incessantly about the wRVU system! I make no claim to be an expert on the topic.)
[0] https://www.physiciansthrive.com/physician-compensation/wrvu...
That is FFS (fee-for-service) billing. And indeed that does not use the diagnosis code, except for reporting purposes and documentation that the treatments were appropriate/necessary.
The diagnosis code would be used if billing in a DRG (diagnostic-related groups) model, which is an overall fee for overall treatment related to the condition -- exam, stitches, etc.
It's extraordinarily difficult to capture this information after the encounter... the patient is gone, the provider is working from notes/memory, and now it's this additional specific burden. How are you supposed to run an epidemiological study on the prevalence of duck bites if everyone involved has vanished into the ether? If you're going to capture it, it has to be rolled into the diagnosis codes and captured during the encounter. Also, you really want to capture the contemporaneous narrative including any misdiagnoses/etc - the CDC wants to know how much that is happening too!
really those low-level codes are kinda just there, they're not really used in practice, and most billing systems would care about the higher levels of the hierarchy anyway. The part insurance cares about is "cleaning and stitches after small wild animal bite", not the levels of the coding scheme that indicate that it's a duck bite.
(but you can see how it is potentially useful to shake some of these details out - is it a large animal, or a small one? a pet or a wild animal? a wild bear bite and a pet duck bite are two very different scenarios for the provider+insurer!)
It's also really more about things like "gunshot wound from stranger" vs "gunshot wound from partner" vs "gunshot wound from LEO" where there is obvious value in capturing what is going on. Jokes aside, nobody is super concerned about duck bites, it's just a funny example of how detailed the coding system can be (not must be... at least yet).
The real travesty is the idea that the same action using the same materials in the same facility can be billed 2 different ways based on two different ICD codes, not that ICD codes include the diagnosis data. It shouldn't matter if it's a duck or a cat, it's a superficial clean-and-bandage, that's what procedure coding (CPT) is supposed to capture. If there's major variations in how you perform a procedure based on how the patient presents, such that cost is substantially impacted... that is a deficiency in CPT and needs to be fixed independently, not forcing everyone to track CPT+ICD for eternity.
~~CPT itself incorporates a huge amount of nuance and sub-coding for this exact reason.~~ Simple example but we'd spit out CPT codes like "MRI with contrast-enhancer" vs "without", "MRI 3-tesla" vs "1.5T" vs "Open", "CT 64-slice" vs "40-slice", etc. If you're not capturing some aspect of the procedure you need to take it up with the CPT people, not make it everyone else's problem.
edit: superfun memory this just triggered, in fact this imprecision in CPT coding actually does lead to different things having the same CPT code and operators have to select from a picker of these possibilities that are specific to their organization's coding/billing systems. Forgot about that, awesome!
Medical data systems are the absolute worst