Personal History Of H Pylori Icd 10

Using Z86.14 for H. Pylori: What Actually Happens When You Code It

Personal History Of H Pylori Icd 10 maps to code Z86.14. That is straightforward enough. The harder part is knowing when to use it and when you should not, because the people reading your charts do not always agree with each other about what "personal history" means in a given encounter. Z86.14 is for patients who were treated for H. pylori in the past and have since cleared the infection. The key word is cleared. If a patient still has an active infection, you are using A00.5, not Z86.14. Mixing those two up is one of the most common errors I see in audit reports, and it usually happens when a clinician documents "history of H. pylori" while the chart shows an active positive test or ongoing treatment. The code sits in the chapter on factors influencing health status and contact with health services. It is not a diagnosis in the traditional sense. It is a status code. Status codes are perfectly billable when they are the reason for the encounter or when they influence the care being provided. That last part matters more than most coders realize.

How I Handle This in Practice

When I review a chart for Z86.14, I check three things before I approve the code. First, is there documented evidence the patient was previously infected. Second, is there documentation the infection has resolved or been eradicated. Third, is the code supporting a current service or interaction. Here is a scenario that tripped me up recently and probably will trip you up too. A gastroenterologist ordered a follow-up test for a patient with Z86.14 on file. The test was a urea breath test to confirm the patient remained H. pylori-negative after a prior treatment course. The ordering physician wrote "rule out recurrence" in the notes. The initial thought is to code Z86.14. But the second thought should be to ask whether the encounter is really about the history or about ruling out an active problem. In that case, the more accurate code may be R10.1 or Z03.89 depending on the clinical documentation, and Z86.14 becomes secondary at best. I learned to stop assuming Z86.14 is the primary code just because it appeared in the problem list. I now pull the actual reason for the visit from the clinical note. If the reason is surveillance after successful treatment, Z86.14 works as a secondary code alongside whatever surveillance code or evaluation code is appropriate. If the reason is a new GI symptom, Z86.14 may not be relevant at all unless the provider explicitly ties the history to the current decision-making.

Common Pitfalls That Waste Time

The biggest waste comes from ambiguous documentation. A physician writes "H. pylori history" and leaves it at that. You do not know if the patient is currently infected, was never treated, or was successfully eradicated. In those cases, the right move is to query the provider. Do not guess. A query takes fifteen minutes and saves you from a claim denial that takes three weeks to reverse. Another trap is using Z86.14 when the patient has a peptic ulcer that resulted from the prior H. pylori infection. If the ulcer is a sequela, K27.- is more specific. Z86.14 alone does not capture the ulcer. Coding both may be appropriate if the ulcer is healing and the H. pylori is a separate historical factor, but you need to verify the encounter supports both. Many payers will deny the K27 code if the documentation suggests the ulcer is fully resolved and only the bacterial history remains. There is also a timing issue with follow-up visits. Some clinics automatically carry Z86.14 forward on every subsequent visit for patients who had H. pylori eradicated years ago. That is not wrong, but it is also not useful unless the history is affecting current management. Putting it on every encounter clutters the record and can confuse automated coding tools that prioritize primary codes.

When Z86.14 Is the Right Call

The cleanest use case is a routine follow-up visit after confirmed eradication where no active symptoms are present. The patient is being monitored to ensure the infection stays cleared. The provider is checking adherence, reviewing lab results, and discussing prevention. Z86.14 accurately describes why the patient is being seen in that context. Pair it with a Z-code for aftercare or follow-up if your payer prefers that structure. I also see Z86.14 used appropriately when a patient with a history of H. pylori is being evaluated for unrelated conditions that carry higher risk due to that history. A patient with a prior H. pylori infection and a family history of gastric cancer might have Z86.14 listed alongside the cancer screening codes. The history justifies the vigilance even though the current encounter is about screening, not about the bacteria itself.

Bottom Line

Z86.14 is useful but easily misapplied. The code requires clear documentation that the infection is in the past and resolved. It is not a substitute for an active diagnosis. It is not a catch-all for any GI-related encounter. Before you assign it, confirm the clinical story matches the code. When in doubt, ask the provider to clarify. That single question will save more time than any shortcut through ambiguous documentation.