Removal of Retained Hardware Icd 10 Code

February 2019

Coding Corner: Successful Coding of Device Failure
By Amalorpamary Sebastian
For The Tape
Vol. 31 No. 2 P. 26

Recently, word of a legal example in which the attorney cited the apply of the code for "device failure" to support suing the device manufacturer fabricated its mode through the wellness care arena. In Office 803 of the Code of Federal Regulations (revised April ane, 2018), failure of a device is divers as failure to come across its performance specifications or otherwise perform as intended. Operation specifications include all claims made in the labeling for the device. The intended performance of a device refers to the intended use for which the device is labeled or marketed.

When a medical device agin event occurs, coders must carefully consider whether to code it as device failure or complication due to a postoperative condition, which raises the question: Should a complication post-obit a device implant be attributed to the device?

Adverse events are untoward medical occurrences, unintended disease or injury, or untoward clinical signs (including aberrant laboratory findings), whether or not related to the medical device. Agin effect reporting subsequently medical device implantation is essential to empathise the safe and functioning of a device. Device-related adverse events are directly attributable to the device itself.

Procedure-Related Adverse Events
Events that occur from the process, irrespective of the device, are known every bit procedure-related agin events. Examples include postoperative myocardial infarction following a peripheral vascular procedure and deep venous thrombosis following aneurysm repair.

Complications from anesthesia or other procedures incidental to the main procedure nether study are classified as procedure related even if they occur before the bodily implantation of the device.

When a medical device adverse event occurs, the doctor must document the result and the state of affairs must be coded—as whatever complication code should exist—to properly document intendance.

Coding for Complications
Complication coding is a hot topic among coding, clinical, and compliance professionals. It's considered to be ane of the more than challenging aspects of coding. Physicians are hesitant to document postoperative complications because they negatively affect their quality scores on sites that publicly report hospital and dr. quality scores, such as Healthgrades.

For a condition to exist considered a complexity, the following must be true:

• It must be more an expected outcome or occurrence and show bear witness that the provider evaluated, monitored, and treated the condition.

• There must be a documented cause-and-effect relationship between the care given and the complication.

• The physician must document that the condition is a complication.

ICD-10-CM has made information technology easier to code complications by incorporating intraoperative and postprocedural complications into the split torso arrangement chapters.

Choosing Right ICD-x Diagnosis Codes
Complications of care can exist found in each chapter every bit well every bit in T-serial dependent on the following:

• site of surgery;

• organ/organ system affected past the complication;

• blazon of surgery, for example, articulation replacement, pare grafting, and bypass; and

• type of complication, for example, mechanical (eg, breakage, displacement, protrusion, breakup, leakage, obstruction), infection, embolism/thrombosis, pain, fibrosis, and hemorrhage.

Assigning the Correct 7th Character
According to an AHA Coding Clinic for ICD-ten-CM/PCS, Commencement Quarter ICD-10 2015 commodity, applying the seventh character for injury, poisoning, and sure other consequences of external causes, active treatment refers to treatment for the status described by the code, even though it may be related to an earlier precipitating problem.

For instance, code T84.50XA, Infection and inflammatory reaction due to unspecified internal joint prosthesis, initial run into, is used when agile treatment is provided for the infection, fifty-fifty though the condition relates to the prosthetic device, implant, or graft that was placed at a previous encounter.

7th character "A," initial run into, is used while the patient is receiving active handling for the condition. Examples of active treatment are surgical treatment, emergency department encounter, and evaluation and continuing treatment by the same or a dissimilar md.

Seventh character "D," subsequent encounter, is used for encounters after the patient has received agile treatment of the condition and is receiving routine care for the condition during the healing or recovery stage. Examples of subsequent care are removal of external or internal fixation device, medication adjustment, other aftercare, and follow-upwards visits post-obit treatment of the condition.

7th character "S," sequela, is for used for complications or conditions that ascend as a straight result of a condition. The specific type of sequela (eg, scar) is sequenced first, followed by the injury lawmaking.

External Cause Codes
If it is determined that there has been a device failure, the appropriate complication-of-care code related to the specific device/complication is coded. In addition, a related external cause code from lawmaking range Y70–Y82, Medical devices associated with agin incidents in diagnostic and therapeutic employ, is separately reported if the nature of the external cause is not already captured in the complication-of-care lawmaking itself.

ICD-10-CM Official Guidelines for Coding and Reporting, Department I.C.xx, states: "An external cause code may exist used with any code in the range of A00.0–T88.nine, Z00–Z99, classification that represents a health condition due to an external cause. Assign the external cause code, with the appropriate 7th graphic symbol (initial run across, subsequent encounter, or sequela) for each encounter for which the injury or condition is being treated."

About categories in chapter 20 have a seventh character requirement for each applicative code. Most categories in this affiliate have three seventh character values: A, initial encounter; D, subsequent encounter; and S, sequela. While the patient may exist seen by a new or dissimilar provider over the course of treatment for an injury or condition, assignment of the seventh character for external cause should friction match the seventh grapheme of the code assigned for the associated injury or status for the encounter.

In addition, ICD-10-CM provides iii sets of external cause codes to indicate medical or surgical care as the crusade of a complication, i of which is specifically related to devices: Y70–Y82, Medical devices associated with adverse incidents in diagnostic and therapeutic use.

Categories Y70–Y82 are used to written report breakup or malfunction of medical devices during use, after implantation, or with ongoing use. This code range covers agin incidents in a multifariousness of devices including types used in anesthesiology, cardiology, obstetrics, and plastic surgery procedures. It is the coder's responsibility to thoroughly review the ICD-10-CM alphabetize to ensure the correct code is reported.

Documentation of Complications of Care
How can documentation in these cases be more clear? The answer is to query. The importance of clear, curtailed physician documentation in these cases cannot be overstated. ICD-10-CM Official Guidelines for Coding and Reporting take specific documentation requirements that coders must adhere to for accurate code assignment and to remain in compliance with these published guidelines.

Cause-Effect Relationship Established by Provider
Code consignment is based on the provider's documentation of the human relationship betwixt the condition and the care or procedure, unless otherwise instructed by the classification. The guideline extends to whatever complications of intendance, regardless of the affiliate the code is located. It is important to note that not all weather condition that occur during or following medical care or surgery are classified as complications.

Expected Upshot Cannot Be Coded as Complication
Not all conditions that occur during or following surgery are classified as complications. First, in that location must be more than than a routinely expected condition or occurrence. The coder cannot make the determination whether something that occurred during surgery is a complication or an expected outcome. If it is not clearly documented, the coder should query the physician for clarification (ICD-9-CM Coding Clinic , First Quarter 2011).

Insignificant Incidental Findings
During a procedure, small injuries/tears may occur incidentally, which almost resolve during the intra/postoperative course without any intervention. The surgeon should exist queried as to whether the small tear was an incidental occurrence inherent in the surgical procedure or whether the tear should be considered by the medico to be a complication of the procedure. If the provider documents that a tear/injury is a complication of the surgery, the coder must assign the appropriate chapter-specific code or T88.8 series lawmaking.

Iatrogenic Weather
Coders should seek clarification before assigning iatrogenic—which means "relating to affliction caused by medical examination or treatment"—codes.

When to Query
Queries should be generated in cases with incomplete, contradictory, or vague documentation. Primal elements to include in queries are clinical indicators, positive findings, the physical exam, treatment provided, and an assessment regarding the documentation and whether data is missing or unclear.

For case, a query could be generated related to device failure in the case of periprosthetic fractures. There has been a lot of confusion about coding periprosthetic fractures. While ICD-9-CM Coding Clinic , 4th Quarter 2005, considers periprosthetic fractures to be complications of prosthesis and coded to 996.43, a alter took event in 2016. Yet, that change has since been revised by the American Academy of Orthopedic Surgeons, which antiseptic that periprosthetic fractures are not complications of the prosthesis (the prosthesis itself is not fractured, the expanse effectually the prosthesis is fractured). Equally a issue, they are now captured with lawmaking series M97.

Periprosthetic fractures occur as a effect of trauma or pathological atmospheric condition. A code for any underlying condition as well as a code for the specific type of fracture (traumatic or pathological) should also be assigned. If the reason for admission/encounter is the fracture, the specific type of fracture (traumatic or pathological) should be sequenced first with the periprosthetic fracture lawmaking sequenced as a secondary diagnosis.

The "fracture" of the articulation prosthesis can be coded every bit a complexity when the articulation prosthesis is cleaved nether the post-obit conditions:

• Information technology must be clinically evaluated, diagnostically tested, and therapeutically treated.

• According to a contempo HCPro newsletter, the complication must as well effect in an extended length of stay in the hospital necessitating increased resource related to intendance.

• The status should not be part of routine care or the routine outcome of an expected procedure.

To help identify potential postoperative complications, including device failure, keep in heed the following:

• Not all conditions that occur in the postoperative phase are complications; look for a crusade-and-outcome relationship and clinical testify of a complication.

• There is no time limit for the evolution of a complication of care. Information technology can occur during the infirmary stay, shortly after discharge, or in some cases, years afterward, which is often seen with implants such as orthopedic devices, mesh implants, and joint replacements.

• Postoperative complications or complications of care are defined as unexpected or unusual outcomes that occur following the care provided.

• Await for documentation such equally "due to," "resulted from," and "the event of" to identify a complication of intendance.

• If there is a causal human relationship that is documented and implicit of the condition, it is non necessary for the medico to provide further documentation for the link—for example, surgical wound infection or wound dehiscence.

• A preexisting status that was present prior to the transplant can be coded as a complexity if it impacts the function of the transplanted organ.

When coding complications from medical devices occur, extra caution is to be used in society to accurately correspond the cause of the problem. Coding as medical device failure must be confirmed accurate; it can impact outcomes such every bit lawsuits against the manufacturer.

Certainly, coding affects value-based functioning and quality metrics. Md documentation must be accurate, and coders must follow the guidelines, query if the documentation is not articulate, and ensure that codes are validated before submitting for claims.

— Amalorpamary Sebastian is senior managing director of operations at nThrive.

Share this post