Periprosthetic fracture coding requires careful attention to fracture type, anatomical location, laterality, encounter character, and the presence or absence of a prosthesis complication. For orthopedic practices, hospitals, and medical billing teams, incorrect code selection or sequencing can lead to claim rejections, reimbursement delays, compliance concerns, and additional administrative work.
The ICD-10-CM category M97 identifies fractures around internal prosthetic joints. However, M97 coding does not replace the code that identifies the specific type and cause of the fracture. Understanding how these codes work together is essential for accurate orthopedic medical coding and appropriate claim submission.
This guide explains periprosthetic fracture ICD-10-CM coding, sequencing requirements, common documentation issues, practical coding examples, and ways to strengthen orthopedic billing accuracy. Practices experiencing recurring coding errors or orthopedic claim denials can also use these principles to identify when a professional coding review or medical billing audit may be beneficial.
What Is a Periprosthetic Fracture?
A periprosthetic fracture is a fracture occurring around an existing internal prosthetic joint, such as a hip, knee, shoulder, or ankle replacement. The fracture may result from trauma, an underlying pathological condition, or another documented cause.
The distinction between a fracture around an implant and a fracture involving the implant itself is important because these situations can require different ICD-10-CM codes.
For example, a patient may sustain a femoral fracture after falling despite having a structurally intact hip replacement. This is different from a case in which the prosthetic joint itself breaks or another documented mechanical complication affects the implant.
Accurate classification requires a review of the clinical record, imaging findings, provider documentation, and applicable coding instructions.
Why Accurate Periprosthetic Fracture Coding Matters
Incorrect coding can affect more than the diagnosis field on a claim. It may create problems with medical necessity review, payer edits, claim adjudication, and subsequent audits.
Common risk areas include:
Reporting an M97 code without identifying the documented fracture type and cause when required.
Selecting the wrong anatomical site or laterality.
Using an encounter character that does not match the stage of treatment.
Confusing a fracture around a prosthetic joint with a fracture of the prosthesis itself.
Missing relevant documentation about osteoporosis, trauma, or a mechanical implant complication.
Failing to follow applicable sequencing instructions.
Practices that repeatedly encounter these issues may benefit from a structured coding quality review. The Medicator’s medical billing audit services can help identify coding and billing workflow issues that warrant further review.
ICD-10-CM Periprosthetic Fracture Codes: Understanding Category M97
Category M97 is used for periprosthetic fractures around internal prosthetic joints. The appropriate code depends on the joint involved and the documented anatomical details.
Common M97 code families include:
| ICD-10-CM category | Description |
|---|---|
| M97.0 | Periprosthetic fracture around an internal prosthetic hip joint |
| M97.1 | Periprosthetic fracture around an internal prosthetic knee joint |
| M97.2 | Periprosthetic fracture around an internal prosthetic ankle joint |
| M97.3 | Periprosthetic fracture around an internal prosthetic shoulder joint |
| M97.4 | Periprosthetic fracture around an internal prosthetic elbow joint |
| M97.8 | Periprosthetic fracture around another internal prosthetic joint |
| M97.9 | Periprosthetic fracture around an unspecified internal prosthetic joint |
The more specific code identifies the applicable joint and, where supported, laterality. The complete billable code must also satisfy the applicable character requirements.
These categories are a starting point, not a substitute for reviewing the current ICD-10-CM Tabular List and Index. Verify the complete code, inclusion and exclusion notes, and applicable annual code-set requirements before submitting a claim.
For reference, consult the AAPC ICD-10-CM M97 coding reference.
How to Identify the Correct M97 Code
A reliable coding workflow should establish the following details before the claim is finalized:
Joint involved: Identify whether the fracture is around a hip, knee, shoulder, ankle, elbow, or another prosthetic joint.
Laterality: Confirm the right or left side when documented.
Fracture type and cause: Determine whether the fracture is traumatic, pathological, or otherwise classified based on the clinical record.
Encounter phase: Select the appropriate seventh character based on the treatment phase.
Associated complications: Determine whether the record documents a separate complication involving the prosthesis itself.
When documentation is incomplete or contradictory, the coding team should follow applicable clarification and query procedures rather than assume missing clinical details.
ICD-10-CM Seventh Characters for Periprosthetic Fractures
M97 codes require the applicable seventh character. The character must reflect the encounter’s treatment phase rather than simply the number of times the patient has visited the provider.
A: Initial encounter. Generally used while the patient is receiving active treatment for the condition.
D: Subsequent encounter. Generally used during routine care in the healing or recovery phase.
S: Sequela. Used for a residual condition resulting from the earlier fracture after the acute phase has ended.
The appropriate seventh character must be assigned according to the applicable code-set instructions and documented treatment circumstances.
Coding teams should not automatically assign A to every first visit with a new provider or D to every follow-up appointment. The nature of the treatment is the key consideration.
Periprosthetic Fracture Coding and Sequencing Rules
Correct sequencing depends on the type and cause of the fracture, applicable tabular instructions, and the clinical circumstances.
Rule 1: Code the Specific Type and Cause of Fracture First When Required
The M97 category includes a “code first” instruction for the specific type and cause of the fracture, when known, such as a traumatic or pathological fracture.
Consequently, coding commonly involves two codes:
A code identifying the specific traumatic or pathological fracture.
The appropriate M97 code identifying its relationship to the internal prosthetic joint.
For a traumatic fracture, the appropriate code may come from the relevant injury category. For a pathological fracture, a code from the applicable pathological fracture category may be appropriate.
The exact code selection depends on the documented fracture, anatomical site, encounter phase, and current coding requirements. Do not select a generic fracture code when the documentation supports greater specificity.
Rule 2: Do Not Confuse a Periprosthetic Fracture With a Prosthesis Complication
A fracture around a prosthetic joint does not, by itself, establish that the prosthesis has failed.
Category M97 identifies the periprosthetic fracture. By contrast, the T84 category includes complications of internal orthopedic prosthetic devices, implants, and grafts.
For example, the code family T84.01- addresses breakage of an internal joint prosthesis. Other T84 codes may apply to documented mechanical or other prosthesis complications.
The coding team should distinguish between:
A fracture around an intact prosthetic joint.
A fracture or breakage of the prosthesis itself.
A fracture associated with a separately documented mechanical complication.
A fracture occurring during or following an orthopedic procedure, for which other specific coding provisions may apply.
Use the code family that reflects the documented condition and follow all relevant inclusion, exclusion, and sequencing instructions.
Rule 3: Review Traumatic Fracture Coding Requirements
When a periprosthetic fracture results from a fall or another traumatic event, the applicable traumatic fracture code may be required in addition to the M97 code.
Do not automatically exclude codes from the S00-T88 range simply because the fracture is periprosthetic. The underlying fracture type and cause must be established first, and the appropriate injury code should be selected according to the documentation and current coding guidance.
Where the fracture is pathological, select the appropriate code for the documented pathological fracture instead.
Rule 4: Evaluate External Cause Coding
When the record documents an external event, such as a fall from stairs, an external cause code may be appropriate when required or supported by the applicable reporting rules and payer requirements.
External cause codes provide information about the circumstances of an injury. Their reporting requirements can vary by setting and jurisdiction, so the coding team should confirm whether they are applicable to the claim.
Rule 5: Confirm Documentation and Medical Necessity Support
The medical record should support the reported fracture type, location, laterality, treatment phase, and any associated prosthesis complication.
Depending on the clinical situation, relevant documentation may include:
Emergency department or admission records.
Orthopedic consultation notes.
Imaging reports.
Operative reports.
Documentation of active treatment or routine healing.
Provider statements concerning the fracture’s cause.
Records supporting any separately reported prosthesis complication.
When a diagnosis or its underlying cause cannot be established from the record, follow the organization’s coding query policy and applicable official guidance.
Real-World Periprosthetic Fracture Coding Examples
The following examples illustrate the coding logic. They are educational examples, not a substitute for reviewing the full clinical record and current code-set instructions.
Example 1: Traumatic Periprosthetic Knee Fracture
Clinical scenario: A patient falls down several steps and sustains a fracture of the lower end of the left femur around a total knee replacement. The provider documents that the prosthesis itself remains intact.
Coding approach:
Select the appropriate traumatic fracture code based on the documented fracture location, specificity, displacement, open or closed status, and encounter phase.
Assign the appropriate M97 code for the periprosthetic fracture around the internal prosthetic left knee joint.
Consider an applicable external cause code when supported and required.
The traumatic fracture code is sequenced before the M97 code when the applicable coding instructions require it.
An unspecified femoral fracture code should not be used automatically if the documentation supports a more specific diagnosis.
Example 2: Pathological Periprosthetic Shoulder Fracture
Clinical scenario: A patient with a previous left shoulder replacement develops a humeral fracture associated with documented osteoporosis. The prosthesis itself is not fractured.
Coding approach:
Select the appropriate pathological fracture code according to the documented site, cause, and encounter phase.
Assign the appropriate M97 code for the periprosthetic fracture around the internal prosthetic left shoulder joint.
Report the underlying osteoporosis diagnosis when supported and required by applicable coding instructions.
The pathological fracture code is sequenced before the M97 code when the applicable instructions require this order.
Example 3: Fracture of the Prosthetic Joint Itself
Clinical scenario: A patient presents with documented breakage of an internal joint prosthesis.
Coding approach:
Review the provider’s diagnosis and supporting documentation.
Evaluate the applicable T84 code family for a prosthetic joint breakage or other documented complication.
Follow the relevant sequencing, encounter-character, and additional-code requirements.
This situation differs from a fracture occurring around an intact prosthetic joint. The M97 category should not be used as a substitute for the code describing a fracture of the prosthesis itself.
Common Periprosthetic Fracture Coding Errors That Can Affect Reimbursement
Orthopedic coding errors can delay payment, increase rework, and make it more difficult to track claim performance. The most useful way to address these issues is to identify their underlying causes rather than repeatedly correcting individual claims.
Common errors include:
Incorrect fracture sequencing: Reporting the M97 code before the underlying fracture code when the applicable instructions require the reverse.
Incorrect laterality: Selecting the wrong side or using an unspecified code despite adequate documentation.
Wrong encounter character: Failing to distinguish active treatment from routine healing or sequela care.
Incorrect complication classification: Confusing a fracture around a prosthesis with breakage or another complication of the device.
Insufficient documentation: Reporting a level of specificity that the clinical record does not support.
Incomplete claim review: Missing relevant diagnosis codes or applicable coding instructions before submission.
For a broader review of orthopedic coding risks, read our guide to common ICD-10 coding errors in orthopedic billing.
Practices can also explore why orthopedic claims get denied and how to prevent them to understand how coding, documentation, and claim-submission issues affect reimbursement.
How Professional Medical Coding Services Can Help Orthopedic Practices
When coding errors recur across claims, a practice may need more than an isolated correction. A structured review can help determine whether the problem originates in documentation, code selection, sequencing, staff training, claim edits, or communication between clinical and billing teams.
Professional medical coding services may support orthopedic practices through:
ICD-10-CM coding review: Checking diagnosis selection, specificity, laterality, and applicable sequencing instructions.
Documentation review: Identifying missing or conflicting information that requires clarification.
Pre-submission claim review: Evaluating coding and claim details before submission.
Coding audits: Reviewing selected claims to identify recurring errors and opportunities for process improvement.
Denial analysis: Categorizing coding-related denials and identifying corrective actions.
Ongoing quality monitoring: Tracking error patterns and helping establish consistent coding workflows.
The Medicator’s provides medical billing and coding services and supports orthopedic billing workflows involving coding review, claims management, and reimbursement follow-up.
If your practice is experiencing recurring diagnosis-code errors, unexplained denials, or increasing administrative rework, a coding and billing review may help identify where additional controls are needed.
When Should a Practice Consider an Orthopedic Coding Audit?
An audit can be useful when a practice needs to understand whether individual errors indicate a broader workflow problem.
Consider reviewing your coding process when:
Similar ICD-10-CM errors appear repeatedly.
Claims are denied because of diagnosis selection or coding inconsistencies.
Staff members disagree about fracture sequencing requirements.
Documentation frequently lacks sufficient specificity.
Corrected claims and appeals consume increasing administrative time.
The practice is preparing for an internal compliance review or a change in billing operations.
A coding audit should be designed around the practice’s actual risks, specialties, claim volume, and applicable requirements. The objective is to identify supported findings and practical corrective actions, not to assume that every denied claim is a coding error.
Explore The Medicator’s medical billing audit services for support reviewing coding and billing workflows.
Improving Orthopedic Claim Performance Beyond Coding
Correct coding is an important part of reimbursement, but it is only one stage of the revenue cycle. A correctly coded claim can still encounter problems involving eligibility, authorization, claim edits, payer processing, or follow-up.
Orthopedic practices should evaluate the full claim workflow, including:
Reviewing patient eligibility and coverage requirements.
Confirming that documentation supports the services reported.
Checking claims for coding and submission errors.
Monitoring rejected and denied claims.
Investigating underpayments and unresolved payer responses.
Following up on outstanding accounts receivable.
Reviewing performance reports to identify recurring problems.
The Medicator’s orthopedic billing services provide an example of specialty-focused support for orthopedic coding, claim management, and reimbursement workflows. Practices looking for broader support can also review our revenue cycle management services.
The right approach depends on whether a practice needs a targeted coding review, help resolving a backlog, or ongoing billing and revenue cycle support.
Frequently Asked Questions About Periprosthetic Fracture Coding
What ICD-10-CM code is used for a periprosthetic fracture?
Category M97 identifies periprosthetic fractures around internal prosthetic joints. The complete code depends on the joint involved and the documented anatomical details. The appropriate code for the underlying traumatic or pathological fracture may also be required.
Does M97 replace the underlying fracture code?
No. Category M97 includes a code-first instruction for the specific type and cause of fracture, when known. The applicable traumatic or pathological fracture code is generally reported first, followed by the appropriate M97 code when required.
Is a periprosthetic fracture always a prosthesis complication?
No. A fracture around a prosthetic joint does not automatically mean the prosthesis itself has failed. A fracture involving breakage of the prosthetic joint or another documented device complication must be evaluated under the applicable complication coding rules.
Which seventh character is used for M97 codes?
The applicable seventh character generally identifies initial encounter during active treatment, subsequent encounter during routine healing or recovery, or sequela. The character must reflect the documented treatment phase and the current code-set instructions.
Can incorrect periprosthetic fracture coding lead to claim denials?
Yes. Incorrect code selection, sequencing, laterality, encounter characters, or insufficient documentation can contribute to claim denials, rejections, and payment delays. Other payer or claim-processing issues may also affect reimbursement.
When should an orthopedic practice outsource medical coding?
Outsourcing may be worth evaluating when a practice has recurring coding errors, limited internal coding capacity, growing claim volume, persistent denials, or a need for additional coding quality controls. The decision should account for service scope, specialty expertise, reporting, cost, and operational needs.
Can a medical billing audit identify orthopedic coding problems?
A well-designed audit can review selected claims, documentation, code assignments, and billing processes to identify potential errors and recurring patterns. Findings should be validated against the medical record and applicable coding requirements before corrective action is taken.
Strengthen Your Orthopedic Coding and Billing Workflow
Periprosthetic fracture coding requires a clear understanding of fracture etiology, M97 code selection, sequencing instructions, and the distinction between a fracture around a prosthesis and a complication involving the prosthesis itself.
For orthopedic practices, reliable coding processes can also support more consistent claim submission, fewer avoidable corrections, and better visibility into reimbursement problems.
If your team needs help identifying coding issues, reviewing claims, or improving billing operations, The Medicator’s can help you evaluate your options.
Request a practice revenue analysis to discuss your coding and billing workflow, identify areas that may need attention, and determine whether specialized orthopedic billing or medical coding support fits your practice.
Visit The Medicator’s to learn more about our medical billing, coding, audit, and revenue cycle management services.
