That&#x27;s exactly how the codes are designed. Categories, sub-categories, etc to describe what caused it, what damage it did, and how many times it did it. For example, let&#x27;s take an example of an &quot;Angel of Death&quot; situation, where a nurse has been repeatedly overdosing a patient with morphine in order to try to kill them. You&#x27;re going to want to discuss all of the details of what went on, so you choose T41.1X3S [1], which is Poisoning, or other effects from anesthetics. First you look up where poisoning is, T41. Then you look up the code for anesthetics, which is 1X. It&#x27;s intentional, so that&#x27;s class 3. From there, you can describe each incident, A for the first, D for the second, and S for any incidents after that. If you look at other areas, like an insect bite, you&#x27;d do similar, and some up with S80.262A [2].<p>Standardizing the format for the codes is really useful, because it can give precise instructions as to what happened. But, you can quickly figure out what happened byt the first code, with the code after the decimal point giving the exact details, if needed. Yes, it allows for ridiculous combinations, but any decently designed charting system has similar. Medicare, for example, has beneficiary codes extending to Second disabled surviving divorced husband [3].<p>[1] <a href="http:&#x2F;&#x2F;www.icd10data.com&#x2F;ICD10CM&#x2F;Codes&#x2F;S00-T88&#x2F;T36-T50&#x2F;T41-&#x2F;T41.1X3S" rel="nofollow">http:&#x2F;&#x2F;www.icd10data.com&#x2F;ICD10CM&#x2F;Codes&#x2F;S00-T88&#x2F;T36-T50&#x2F;T41-&#x2F;...</a>
[2] <a href="http:&#x2F;&#x2F;www.icd10data.com&#x2F;ICD10CM&#x2F;Codes&#x2F;S00-T88&#x2F;S80-S89&#x2F;S80-&#x2F;S80.262A" rel="nofollow">http:&#x2F;&#x2F;www.icd10data.com&#x2F;ICD10CM&#x2F;Codes&#x2F;S00-T88&#x2F;S80-S89&#x2F;S80-&#x2F;...</a>
[3] <a href="http:&#x2F;&#x2F;www.ncdoi.com&#x2F;_Publications&#x2F;Beneficiary%20Identification%20Codes_SNE1.pdf" rel="nofollow">http:&#x2F;&#x2F;www.ncdoi.com&#x2F;_Publications&#x2F;Beneficiary%20Identificat...</a>