Skip to main content
Written for the surgeon dictating the note, not for the coder decoding it afterward.
General surgery runs on the gallbladder. It is the case most residents scrub first, the one that fills the elective block, and the one that turns up at two in the morning through the emergency department. In most general surgery practices, cholecystectomy is the single highest volume operation performed all year, which makes it the single largest source of coding activity as well.
Here is the frustrating part. The operation is standardized, the anatomy is familiar, and the outcomes are good, yet the coding behind it is anything but tidy. The K80 family alone holds dozens of codes, and the difference between two of them can come down to one word in your dictation. A surgeon who says gallstones and stops has just handed the coder a guess. A surgeon who says calculous cholecystitis, acute on chronic, no obstruction has given them a finished answer.
This guide walks through the diagnosis codes you generate, the procedure codes that follow, and the specific phrases in an operative note that decide which ones get used. It is written to be read once and then kept nearby.
Why Gallbladder Coding Is Harder Than the Operation
The reason cholecystectomy coding is disproportionately detailed is that ICD-10 does not treat gallstone disease as one condition. It treats it as a grid built from four independent questions, and every combination of answers has its own code.
Table 1: The Four Questions Behind Every Gallstone Code
| Question | Possible Answers | Where the Answer Should Appear |
| Where are the stones? | Gallbladder, bile duct, both, or none | Preoperative diagnosis and operative findings |
| Is there inflammation? | None, acute, chronic, acute on chronic, cholangitis | Findings and pathology report |
| Is there obstruction? | Present or absent | Stated explicitly in the note |
| Are there severity findings? | Gangrene, perforation, empyema, hydrops | Operative description of the specimen |
Four questions, each with several answers, produces a large matrix. That is why the K80 category runs so long, and why a vague dictation forces the coder to the least specific option available. The good news is that answering all four takes one sentence, and you already know all four answers before you leave the room.
It also helps to know that this part of the code set is not frozen. ICD-10-CM is revised every October, and the gallbladder codes have been revised within recent memory, including the addition of dedicated codes for gangrene and perforation that did not previously exist. Anything you learned about gallbladder coding early in training may have quietly changed since, which is why the surgeons who stay current on this tend to review the category once a year rather than assuming it looks the way it did during residency.
The K80 Family: Stones, Location, and Obstruction
K80 is cholelithiasis, and it is organized first by where the stone sits, then by what inflammation accompanies it, then by whether obstruction is present. Learn the top level and the rest follows.
Table 2: K80 Subcategories at a Glance
| Subcategory | Describes | Typical Clinical Picture |
| K80.0- | Gallbladder stones with acute cholecystitis | The emergency department admission |
| K80.1- | Gallbladder stones with other cholecystitis, including chronic and acute on chronic | The elective case with a long symptom history |
| K80.2- | Gallbladder stones without cholecystitis | Biliary colic with a quiet gallbladder wall |
| K80.3- | Bile duct stones with cholangitis | Fever, jaundice, and ductal dilation |
| K80.4- | Bile duct stones with cholecystitis | Inflamed gallbladder plus a ductal stone |
| K80.5- | Bile duct stones without cholangitis or cholecystitis | Incidental duct stone found on imaging |
| K80.6- | Stones in both gallbladder and bile duct with cholecystitis | The full package, common in delayed presentations |
| K80.7- | Stones in both locations without cholecystitis | Radiologic finding without an inflammatory response |
| K80.8- | Other cholelithiasis | Presentations that do not fit the categories above |
Biliary colic is worth a separate note because it is the phrase surgeons use most and the one the code set does not recognize. There is no code titled biliary colic. When a patient has intermittent postprandial pain with documented stones and a normal gallbladder wall, the record lands at K80.20. The word colic describes the symptom pattern beautifully and codes to nothing on its own, so pair it with the finding rather than letting it stand alone as the diagnosis.
The Obstruction Character
Almost every K80 code ends with a character that answers one question: obstruction, yes or no. This is the detail surgeons omit most often, and it is the one with the clearest consequence, since it changes the code every single time.
Obstruction here means the stone is blocking flow, not simply that a stone exists. A stone impacted in the neck of the gallbladder producing a distended, tense organ is obstruction. A floating stone in a decompressed gallbladder is not. You already make this distinction while operating. The task is only to say it out loud.
Table 3: How One Word Moves the Code
| What the Note Says | Resulting Code | Difference |
| Gallstones with acute cholecystitis, no obstruction | K80.00 | Baseline acute presentation |
| Gallstones with acute cholecystitis, stone impacted in the neck | K80.01 | Obstruction adds severity |
| Gallstones with chronic cholecystitis, no obstruction | K80.10 | Elective picture |
| Gallstones with acute and chronic cholecystitis, no obstruction | K80.12 | Captures the acute flare on chronic disease |
| Gallstones only, no inflammation, no obstruction | K80.20 | Lowest severity in the family |
| Gallstones, no inflammation, cystic duct obstructed | K80.21 | Obstruction without inflammation |
Acute, Chronic, or Both: Getting the Inflammation Right
The second axis is the inflammatory state, and ICD-10 recognizes that acute and chronic disease often coexist. It gives that combination its own code rather than making you pick one.
This matters more than it may appear. Most elective gallbladders have chronic changes. Many emergency gallbladders have chronic changes underneath the acute inflammation. When the note says only acute, the chronic component is lost, and the code understates what was actually removed.
Table 4: Cholecystitis Without Stones
| Code | Description | When It Applies |
| K81.0 | Acute cholecystitis | Acalculous acute disease, often in the ill inpatient |
| K81.1 | Chronic cholecystitis | Chronic wall changes with no stones identified |
| K81.2 | Acute cholecystitis with chronic cholecystitis | Acute flare on a chronically diseased wall, no stones |
| K81.9 | Cholecystitis, unspecified | Only when the record truly gives no direction |
Severity grading language helps here as well. Many surgeons already think in terms of the Tokyo grading system when deciding on timing and approach for acute cholecystitis, and the same vocabulary strengthens the record. A note describing organ dysfunction, marked local inflammation, or a duration of symptoms beyond seventy two hours gives both the coder and any later reviewer a sense of where the case sat on the spectrum. It costs one clause and explains a great deal about why the operation went the way it did.
Let the Pathology Report Finish the Story
The specimen usually settles the acute versus chronic question better than the operative impression does. If your note says acute cholecystitis and pathology returns chronic cholecystitis with acute exacerbation, the record supports the combined code. Practices that route the pathology result back to the coder before the claim goes out capture that specificity routinely. Practices that code at discharge and never look again lose it every time.
When There Are No Stones
A meaningful share of cholecystectomies are performed on gallbladders that never contained a stone, and this is where coding drifts toward vague defaults fastest. Biliary dyskinesia is the usual example. The patient has classic symptoms, the ultrasound is clean, the ejection fraction is low, and the gallbladder comes out.
Table 5: Stone Free Gallbladder Conditions
| Code | Condition | Documentation That Supports It |
| K82.0 | Obstruction of gallbladder | Cystic duct obstruction without a stone identified |
| K82.1 | Hydrops of gallbladder | Distended, mucus filled organ described in findings |
| K82.2 | Perforation of gallbladder | Free perforation not attributed to cholecystitis |
| K82.3 | Fistula of gallbladder | Cholecystenteric or cholecystoduodenal tract described |
| K82.4 | Cholesterolosis of gallbladder | Pathology describing the strawberry gallbladder |
| K82.8 | Other specified diseases of gallbladder | Biliary dyskinesia with the ejection fraction recorded |
| K82.9 | Disease of gallbladder, unspecified | Should be rare in a surgical record |
Polyps sit in the same neighborhood and follow a similar rule. When a polyp is the reason for the operation, the size measured on imaging belongs in the indication, since size is what separates a surveillance recommendation from an operative one in every published pathway. An incidental polyp found on the specimen after an operation done for stones is a different matter entirely and does not retroactively become the indication.
For dyskinesia specifically, write the diagnosis by name and include the measured ejection fraction from the HIDA study in the preoperative diagnosis. That single number is what separates a supported indication from an operation a payer reads as elective without cause. Prior authorization reviewers look for it directly, and its absence is one of the more common reasons a gallbladder case gets held up before it ever reaches the schedule.
Severity Findings That Change the Picture
Two codes exist specifically for the findings that make a routine case difficult, and they capture severity that no other code in the chapter conveys. If you have ever finished a hard gallbladder and felt the coding did not reflect it, this is usually why.
Table 6: Severity Codes Worth Knowing
| Code | Finding | Phrase to Use in the Note |
| K82.A1 | Gangrene of gallbladder in cholecystitis | Gangrenous cholecystitis with necrotic wall segments |
| K82.A2 | Perforation of gallbladder in cholecystitis | Perforated gallbladder with bile spillage into the field |
These are reported in addition to the underlying cholecystitis code, not instead of it. A gangrenous, stone filled, obstructed gallbladder generates a K80 code and a K82.A1 code together, and the pair describes the case far better than either does alone.
Empyema deserves a mention alongside them. Pus under pressure inside the gallbladder is a different operation from thickened bile, and the note should say pus rather than describing the contents as murky or thick. Coders cannot infer empyema from an adjective.
Mirizzi syndrome deserves a place in this section too. A stone impacted in the cystic duct compressing the common hepatic duct produces obstruction, changes the operative plan, and often drives a subtotal approach. Name the syndrome in the findings and state the obstruction separately. Coders working from a note that describes only dense inflammation near the porta have no way to reach the right code, and the case ends up looking like a routine cholecystitis that happened to take three hours.
Say What You Saw, Not What You Felt
Surgeons describe hard cases in narrative terms that carry no coding value. Hostile, densely adherent, and difficult dissection tell a reader the case was demanding but map to nothing. Necrotic, gangrenous, perforated, purulent, and empyema all map to something. Both kinds of language can live in the same note. Just make sure the second kind is present.
Common Duct Disease and Cholangitis
Once stones move into the duct, the coding shifts and so does the procedure side. The K80.3, K80.4, and K80.5 subcategories all describe ductal stones, separated by what accompanies them.
Table 7: Ductal Disease Coding Paths
| Clinical Situation | Code Family | Documentation Requirement |
| Duct stone with acute cholangitis | K80.3- | Cholangitis named, obstruction status stated |
| Duct stone with cholecystitis | K80.4- | Both conditions named, acute or chronic specified |
| Duct stone alone | K80.5- | Stone location confirmed on imaging or cholangiogram |
| Stones in gallbladder and duct with cholecystitis | K80.6- | Both sites documented in the same note |
| Stones in both sites without cholecystitis | K80.7- | Imaging findings carried into the assessment |
| Cholangitis without stones | K83.0 | Cause identified where possible |
| Duct obstruction without stones | K83.1 | Stricture or extrinsic cause described |
Coordination with endoscopy adds another layer. When a duct stone is cleared by ERCP before or after the operation, that procedure is reported by whoever performed it, on their own claim, and your operative claim covers the surgical work alone. The two encounters should tell a consistent story about what was found and when. Records where the surgeon documents a clear duct while the endoscopist documents stone extraction on the same admission raise questions that are easier to prevent than to answer later.
The intraoperative cholangiogram plays a role here beyond its clinical one. A normal cholangiogram documents the absence of duct stones and supports coding the gallbladder disease alone. An abnormal one establishes the ductal component in the record on the day of surgery rather than retroactively. Either way, the interpretation belongs in the operative note in words, not left as an image in the imaging system.
Gallstone Pancreatitis and Related Conditions
Biliary pancreatitis brings a second chapter into the record and changes the sequencing on an inpatient admission. It has its own codes under acute pancreatitis, subdivided by whether necrosis and infection are present.
Table 8: Conditions That Travel With Gallbladder Disease
| Condition | Code Family | Effect on the Record |
| Biliary acute pancreatitis | K85.1- | Often the principal diagnosis on admission, with severity detail required |
| Obstructive jaundice | K83.1 with the stone code | Supports urgency and ductal intervention |
| Gallbladder polyps | K82.8 | Size should be documented as the operative indication |
| Gallbladder malignancy | C23 | Requires pathology, changes staging and follow-up pathways |
| Porcelain gallbladder | K82.8 | Calcified wall described in imaging and findings |
| Postcholecystectomy syndrome | K91.5 | Applies to later encounters, not the operative one |
Same admission cholecystectomy after gallstone pancreatitis is now expected practice in most settings, and the record should show why the timing went the way it did. If the operation was delayed beyond the admission for a documented reason, write the reason down. Payers and quality programs both look at the interval between the pancreatitis diagnosis and the operation, and an unexplained gap reads as a lapse even when the clinical decision was entirely sound.
An incidental gallbladder cancer found on final pathology deserves its own workflow. The operative claim was correctly coded from what was known that day, and the malignancy is added when the report returns. Both entries are accurate for their moment, and the sequence should be visible in the chart so that later reviewers understand why the codes changed.
Procedure Codes on the Professional Side
The diagnosis tells the payer why. The procedure code tells them what you did, and the choices are narrower but easy to get wrong when additional work is performed.
Table 9: Cholecystectomy Procedure Codes
| Code | Procedure | Selection Point |
| 47562 | Laparoscopic cholecystectomy | The default when no cholangiogram is performed |
| 47563 | Laparoscopic cholecystectomy with cholangiography | Requires interpretation documented in the note |
| 47564 | Laparoscopic cholecystectomy with common duct exploration | Exploration must be described, not just contemplated |
| 47600 | Open cholecystectomy | Used for planned open cases and conversions |
| 47605 | Open cholecystectomy with cholangiography | Same documentation rule as the laparoscopic version |
| 47610 | Cholecystectomy with common duct exploration | Open ductal work |
| 47612 | With choledochoenterostomy | Drainage procedure performed at the same session |
| 47620 | With transduodenal sphincterotomy or sphincteroplasty | Includes cholangiography when performed |
| 47480 | Cholecystotomy with removal of calculus | Gallbladder opened, organ left in place |
| 47490 | Percutaneous cholecystostomy | Tube placement, frequently a bridge in the unwell patient |
Work that feels substantial in the room is not always separately reportable, and knowing which is which prevents both underbilling and overbilling. Lysis of adhesions encountered while reaching the gallbladder is generally part of the operation rather than a separate service, though extensive adhesiolysis can support additional consideration when the time and findings are documented. Drain placement at the operative site is included. A liver biopsy taken for an unrelated finding is genuinely separate and should be described as its own step with its own indication.
The Cholangiogram Rule
Performing a cholangiogram is not the same as billing for one. To support 47563 or 47605, the note has to record that images were obtained and what they showed. A single line does it:
cholangiogram performed showing normal ductal anatomy with free flow into the duodenum and no filling defects. Without an interpretation, the shot exists but the code does not.
The Facility Side and ICD-10-PCS
Surgeons rarely touch procedure coding for the inpatient facility claim, but the note you write drives it entirely, and one distinction is worth understanding because it hinges on a word you control.
In ICD-10-PCS, removing the entire gallbladder is a resection. Removing part of it is an excision. Subtotal cholecystectomy, fenestrating or reconstituting, is excision rather than resection, and the two build different codes with different downstream effects.
Table 10: Procedure Codes on the Facility Claim
| Code | Meaning | Triggering Phrase in the Note |
| 0FT44ZZ | Resection of gallbladder, laparoscopic | Gallbladder removed in its entirety |
| 0FT40ZZ | Resection of gallbladder, open | Open removal of the whole organ |
| 0FB44ZZ | Excision of gallbladder, laparoscopic | Subtotal or partial cholecystectomy |
| 0FB40ZZ | Excision of gallbladder, open | Partial removal through an open approach |
| 0FC94ZZ | Extirpation of matter from common bile duct, laparoscopic | Ductal stone removed laparoscopically |
| 0FC90ZZ | Extirpation of matter from common bile duct, open | Ductal stone removed through an open exploration |
Approach is handled differently on this side of the record than you might expect. A laparoscopic case that finishes open is built as an open procedure in its entirety, because the code reflects how the operation was completed rather than how it started. There is no partial credit for the laparoscopic portion in the procedure code itself, which is precisely why the conversion status code discussed in the next section matters so much for telling the full story.
If you leave a cuff of gallbladder behind because the triangle was unsafe, say so plainly. Subtotal cholecystectomy performed with the posterior wall left in situ is a defensible operative decision
and a specific code. Describing the same case as cholecystectomy completed produces a resection code that does not match what was done, and that mismatch surfaces at the worst possible time if the patient later returns with a retained remnant.
Conversion From Laparoscopic to Open
Conversion is a normal surgical decision and a routine coding scenario, but it is handled counterintuitively, and the mistakes tend to run in the same direction.
When a case starts laparoscopically and finishes open, only the open procedure is reported. The laparoscopic portion is not billed alongside it and is not reported as a discontinued procedure. The work is not lost, though, because ICD-10-CM has a status code specifically for the conversion, and it belongs on the claim.
Table 11: Handling a Converted Case
| Element | Correct Handling | Frequent Error |
| Procedure code | Report the open code only | Reporting both approaches on one claim |
| Conversion status | Add Z53.31 for a laparoscopic procedure converted to open | Omitting it, leaving the conversion invisible |
| Reason for conversion | State it in the note | Recording the fact without the cause |
| Additional work | Consider modifier 22 when clearly documented | Appending it with no supporting narrative |
| Discontinued procedure modifiers | Not applicable to a completed conversion | Using them because part of the plan changed |
Conversion also carries weight well beyond the claim. Surgical registries and internal quality dashboards track conversion rates by surgeon, and the reason recorded is what separates a conversion driven by unclear anatomy, which reflects sound judgment, from one that reads as unexplained. Writing converted to open due to inability to identify the structures within the triangle of Calot despite adequate dissection protects both the patient record and your own numbers. Converted to open, with nothing following it, does neither.
Making Modifier 22 Actually Work
Requests for additional payment on unusually difficult cases succeed when the note quantifies the difficulty rather than asserting it. Compare the operative time to your usual, describe the specific finding that caused it, and name the extra work performed. Dense fibrotic adhesions from prior surgery required ninety minutes of adhesiolysis before the porta could be exposed, extending total operative time to two hundred minutes against a typical seventy, is a statement a reviewer can act on. Extremely difficult case is not.
What the Operative Note Has to Contain
Everything discussed so far comes down to a handful of sentences in one document. This table is the short version, and it is worth taping inside a cabinet door in the dictation room.
Table 12: Operative Note Elements That Drive Coding
| Element | What to State | Code It Determines |
| Stone location | Gallbladder, duct, both, or none | Which K80 subcategory applies |
| Inflammation | Acute, chronic, or acute on chronic | The fourth and fifth characters |
| Obstruction | Present or absent, in plain words | The final character on nearly every K80 code |
| Severity findings | Gangrene, perforation, empyema, hydrops | K82.A1, K82.A2, and related codes |
| Approach | Laparoscopic, open, or converted | 47562 versus 47600, plus Z53.31 |
| Extent of removal | Total or subtotal | Resection versus excision on the facility claim |
| Cholangiogram | Performed, with findings interpreted | 47563 or 47605 |
| Duct exploration | Performed, with method and result | 47564 or 47610 |
| Additional procedures | Adhesiolysis, drain placement, liver biopsy | Separate codes or modifier support |
Templates are useful right up to the point where they start filling in findings you did not observe. A default line stating no gangrene or perforation identified, left unedited on a case where both were present, is worse than no template at all, because it actively contradicts the rest of the note. Build templates that prompt rather than pre-answer, leaving the findings section blank so it has to be spoken aloud on every case.
Nine items. Most of them fit in the findings paragraph you already dictate. The surgeons who never hear from the coding department are not writing longer notes than everyone else. They are writing notes that answer these nine points before anyone has to ask.
Sequencing and Severity on the Inpatient Admission
For admitted patients, the diagnosis codes do more than justify the operation. They determine which payment group the stay falls into, and the gallbladder groups split along lines that follow your documentation exactly.
Table 13: What Separates the Cholecystectomy Payment Groups
| Splitting Factor | Determined By | Documentation That Settles It |
| Approach | Laparoscopic versus open | Approach stated, conversion noted |
| Common duct exploration | Performed or not | Exploration described in the note |
| Presence of major complications | Secondary diagnoses on the claim | Conditions treated during the stay documented individually |
| Presence of lesser complications | Secondary diagnoses on the claim | Same, at a lower severity tier |
Patient status is its own question and it is decided before the coding begins. A straightforward laparoscopic cholecystectomy with a same day discharge is an outpatient case even when it happens inside a hospital, and the expected length of stay is what drives that determination rather than the operating room location. When a patient is genuinely expected to need care spanning two midnights, the record should say why in the admission note. Status disputes are among the most expensive arguments a hospital has, and they turn on documentation written in the first hour.
Two habits raise the accuracy of that grouping without any change to how you operate. Document every condition you actively manage during the admission rather than only the surgical one, since diabetes, kidney injury, and malnutrition all affect the picture when they are treated. And answer present on admission questions carefully, because a condition that arrived with the patient is recorded very differently from one that developed afterward, and that distinction follows your name through quality reporting long after the claim has settled.
The Global Period and Everything After
Cholecystectomy carries a ninety day global period, which means most of what happens after the operation is already paid for. Knowing which encounters fall outside that window keeps legitimate work from being written off.
Table 14: Postoperative Encounters and Their Handling
| Encounter | Handling | Notes |
| Routine wound check and follow-up | Included in the global package | No separate charge, still document fully |
| Return to the operating room for a complication | Modifier 78 | Unplanned return during the global period |
| Planned staged procedure | Modifier 58 | Anticipated at the time of the first operation |
| Unrelated procedure in the same window | Modifier 79 | Different problem entirely |
| Visit for an unrelated condition | Modifier 24 on the visit | Diagnosis must clearly differ |
| Decision for surgery at a consult | Modifier 57 | Applies to major procedures |
| Persistent symptoms after recovery | K91.5 where documented | Applies once the global window has closed |
Assistants are worth a brief mention since gallbladder cases frequently involve one. A physician assistant surgeon is reported with the appropriate assistant modifier, a non-physician assistant carries its own designation, and true co-surgeons sharing the work are reported differently again. Each requires the operative note to name the assistant and describe their role in a sentence.
Payers reject assistant claims on routine cases more often than not, so the note has to explain what the second pair of hands actually did.
Bile leaks and retained stones both fall under the return to theatre rules rather than being folded into the original service. Document them as complications with their own diagnosis, describe the intervention, and let the modifier do its work. Absorbing that work silently helps nobody, least of all the next surgeon reviewing the chart.
Denials, Delays, and the Gaps Behind Them
Gallbladder claims are high volume, which means payers automate their review of them. The denials that result are repetitive, which is good news, because repetitive problems have repeatable fixes.
Table 15: Common Problems and Their Root Cause
| Problem | Usual Root Cause | Prevention |
| Unspecified diagnosis rejected | Note said gallstones with no further detail | Answer the four questions in one sentence |
| Authorization refused for dyskinesia | Ejection fraction never documented | Record the HIDA number in the indication |
| Cholangiography denied | No interpretation in the note | Add one line describing the findings |
| Duct exploration denied | Exploration mentioned but not described | State the method, findings, and result |
| Modifier 22 refused | Difficulty asserted rather than quantified | Give times, findings, and extra work performed |
| Severity not reflected in payment | Gangrene or perforation described loosely | Use the clinical terms that map to codes |
| Conversion questioned | Z53.31 omitted from the claim | Add the status code and the reason |
| Medical necessity challenged on an elective case | Symptom history thin in the office note | Document duration, failed management, and effect on function |
When a gallbladder claim does need appealing, the operative note is almost always the whole
argument. Send it in full with the pathology report and the office notes that established the indication, and point directly to the sentences that answer the payer’s stated reason. Appeals that summarize the case in a cover letter without attaching the underlying record tend to fail, not because the case was weak, but because the reviewer was never given the document that settles it.
Notice how many of these begin in the office rather than the operating room. The strongest indication for an elective cholecystectomy is built across two or three clinic notes describing symptoms, imaging, and what was tried before surgery was offered. When that history is thin, the operative note is left defending the case alone, and it was never designed to do that job.
A Dictation Routine That Takes Twenty Seconds
None of this requires a longer note. It requires a fixed order of statements that you say the same way every time until it becomes automatic, the way a timeout becomes automatic.
The Sequence
Name the stones and their location, or state clearly that none were present.
Name the inflammation as acute, chronic, or acute on chronic.
State obstruction as present or absent, using that word.
Describe severity findings in clinical terms, not impressions.
State the approach, and if converted, say why.
State whether the gallbladder came out whole or in part.
Record any cholangiogram along with what it showed.
Describe any duct work by method and result.
List anything else performed, including adhesiolysis and drains.
Building this into the record system is a one time task worth an afternoon. A dictation macro that prints the nine prompts as blank fields, or a smart phrase that expands into the skeleton above, moves the whole department at once rather than one surgeon at a time. Departments that have done this describe the same outcome: query volume on gallbladder cases drops sharply within a quarter, and it stays down without anyone monitoring it.
What It Sounds Like in Practice
Findings: multiple calculi within a distended gallbladder with a stone impacted at the neck producing obstruction, acute on chronic cholecystitis with patchy wall necrosis consistent with early gangrenous change, no perforation. Procedure completed laparoscopically with total removal of the gallbladder. Cholangiogram obtained showing normal ductal anatomy with free flow into the duodenum and no filling defects.
That is three sentences. It answers every question in this guide, generates a specific K80 code with the obstruction character, adds the gangrene code, supports the laparoscopic procedure code with cholangiography, and confirms total rather than subtotal removal. No coder will call you about that case.
Table 16: Who Handles What After You Close
| Stage | Owner | Timing | Check Before Moving On |
| Operative note dictated | Surgeon | Same day | All nine elements addressed |
| Pathology reviewed against the note | Coder | On receipt of the report | Inflammation detail reconciled |
| Diagnosis and procedure coded | Coder | Within one business day | Obstruction character supported |
| Query if anything is unclear | Coding staff | Same week | Neutral wording, one question |
| Claim submitted | Billing | Within 48 hours | Conversion and severity codes present |
| Denial reviewed | AR staff | Within 7 days | Root cause logged by category |
Gallbladder surgery is where most general surgeons do their highest volume work, and volume magnifies everything. A phrase you leave out once costs nothing. The same phrase left out four hundred times a year reshapes how your case mix looks to every payer and quality program that examines it, and it does so without ever telling you.
The remedy is not more paperwork. It is the same three sentences, dictated in the same order, on every case. Say where the stones were, what the inflammation was doing, whether anything was obstructed, what the gallbladder looked like, how you got it out, and whether all of it came with you. Everything else in this guide follows from that.
Get the coding right the first time. Explore our revenue cycle management services to see how we help general surgery practices reduce denials and shorten the days-in-A/R on high-volume procedures like cholecystectomy. Or talk to our medical billing team about auditing your current gallbladder claims for the documentation gaps this guide covers.
