Fix mergedImprovement
GuidesDevelopersChangelog
Every release and every piece of in-flight work for Medical Auto Coding. Filter by status, kind, or tag, then read the full notes below.
Work that is planned, in progress, or merged and waiting for a production deploy. It is not released yet.
Work processed after carries this change.
Work processed after carries this change.
Work processed after carries this change.
Work processed after carries this change.
Work processed after carries this change.
Work processed after carries this change.
Work processed after carries this change.
Work processed after carries this change.
Work processed after carries this change.
Work processed after carries this change.
Work processed after carries this change.
Diagnosis pairs the classification says cannot be coded together are now resolved by the book, and you see a note instead of a question.
An Excludes1 note in the ICD-10-CM Tabular List says that two conditions are not coded together. For example, the note at K83.1 (obstruction of bile duct) excludes "obstruction of bile duct with cholelithiasis (K80.-)". The autocoder now reads these notes for the fiscal year of the date of service. It gives the diagnosis check each conflicting pair, the note, and any combination code that the classification offers. Then it verifies the result on the finished claim. This applies to anesthesia, surgery, E/M and radiology claims.
Each pair ends in one of these outcomes:
Automated claim validation (ClaimCleaner) now runs two times on an anesthesia claim. The second run checks the finished claim, after the diagnosis check and the Excludes1 resolution. So a combination code that the autocoder applies is checked before the claim reaches you. ClaimCleaner questions come from the second run only, so a question never names a diagnosis that has already left the claim. If the first run fails, the claim carries one failure alert, not two.
See the Anesthesia Alert Reference and Diagnosis Coding for the triggers and what to verify.
Some anesthesia claims bill one anesthesia code on two lines on purpose, one line for each provider:
Automated claim validation (ClaimCleaner) can read these two lines as a duplicate. The second validation check on an anesthesia claim now keeps both lines. Every provider line stays billed, and the claim records the removal that the autocoder did not apply. The kept line also receives the diagnosis and modifier corrections that validation made on the other line of the same anesthesia code. The payment modifiers stay as they are, because the two lines differ there on purpose.
For example: an anesthesiologist supervises five concurrent rooms, and a CRNA gives the anesthetic in one of them. The CRNA line with QX stays on the claim beside the anesthesiologist line with AD.
Automated claim validation (ClaimCleaner) checks an anesthesia claim two times. The second check runs on the finished claim, after the claim-wide diagnosis check. The second check now keeps every diagnosis that the diagnosis check decided from the record.
For example: the record documents a left knee replacement, and the diagnosis check keeps Z96.652 (presence of left artificial knee joint). The second check no longer swaps that code for the right side.
Your facility processing rules can create an alert. When a rule creates an alert and does not set an alert type, the autocoder now picks the type from what the rule does to the claim.
A rule that sets its own alert type always keeps it. The autocoder's shipped rules already set their type, so their alerts do not change.
Every finished claim runs through automated claim validation before it reaches you. Validation checks NCCI procedure pairs, add-on code rules, Medicare payment rules, coverage articles, code validity for the date of service, and diagnosis conventions. This release changes what you see from it in two ways.
Validation alerts now name the rule. Before this release, an alert read "Modifier 59 added by ClaimCleaner" and stopped there. You could see the change but not the rule behind it, so confirming the change meant looking the rule up yourself. Each of these alerts now ends with the rule, in the form "Reason: [the rule's own explanation] [the rule id]". Read that sentence first. It names the payment rule or coding convention that produced the change. The alerts themselves are unchanged: same names, same types, same severities.
The alerts that gained the reason are Anesthesia Code Changed, Diagnosis Added, Modifier Added To An Anesthesia Code, Modifier Added To A Surgical Code, Line Left With No Code, and Line Removed By Validation.
Ten new alerts carry the questions validation could not answer. Validation also reports problems it will not correct on its own, because the answer needs the record, not a rule. Until now none of those reports reached a coder. Ten new alerts carry the ones worth your time:
Each alert reads "ClaimCleaner:" then the rule's explanation and its rule id. The type and the severity come from the rule. Every rule in this set classifies as Compliance today. The alert carries the rule's own classification, so a future validation rule could arrive as Financial. One exception: the units alert for a single line over an absolute limit is Compliance, severity 5, set by the autocoder, because validation marks that finding Informational after reducing the units in its own copy of the claim.
What to look out for. Expect a small number of new alerts, not a flood. An alert appears only when five conditions are true.
The rule is on the autocoder's review list. The rule's own classification is not Informational. Validation did not fix the problem itself. The line is still billable on the finished claim. The diagnosis problem that the finding names is still on the finished claim.
For an Excludes1 pair, the alert stays while the diagnosis that carries the Excludes1 note, or another code under the same note, is still billed together with a diagnosis from the note's family. When the autocoder cannot read the note from the finding, it checks the two named diagnoses instead.
The autocoder removes an alert again when it later moves the line out of billing, or when the diagnosis problem that the finding names is no longer on the finished claim. If the claim-wide diagnosis check replaces the diagnosis that carries the note with another code under the same note, or replaces the other diagnosis with another code from the note's family, the alert stays, because the conflict is still on the claim. The alert then also names the pair that the claim bills now. When the diagnosis check leaves two findings on the same pair of billed diagnoses, or two conflicts land on one line, you get one alert that names each pair. Conflicts on different lines raise one alert each. For the other diagnosis findings, and for an Excludes1 finding whose note the autocoder cannot read, a replacement or removal of a named diagnosis removes the alert. A finding about a diagnosis that is missing, for example no diagnosis for the side billed or no diagnosis that a coverage article covers, stays, because the autocoder cannot tell whether a diagnosis added later qualifies.
Start with the rule text in the alert, then check the record for the fact the rule needs: the side of service, the patient demographics, the covered diagnosis, the distinct service, or the units of service.
If a family of these questions does not fit your workflow, your organization can silence it or route it to a different reviewer role. Ask your Hank representative. A silenced alert still appears as an informational note.
See the Anesthesia Alert Reference for the full list, the trigger for each alert, and what to verify.
A routine extreme-age add-on no longer raises an alert. Before this release, every claim that billed 99100 carried a review alert asking a coder to confirm the patient's age. The autocoder had already verified that age against the date of service. That alert is gone, and so is the alert for a 99100 the autocoder withheld. The decision is on the claim instead:
No alert when a payer class bundles the add-ons. Medicare bundles 99100, 99116, 99135, and 99140 into the base anesthesia code, and your configuration can list other payer classes that do the same. Those claims no longer carry an informational alert. The codes move to the bundled procedures, and the reason on each entry names the payer class that bundles it.
One new alert, for demographics that cannot both be right. If the patient's date of birth is later than the date of service, the claim now carries the Date of Birth Is After the Date of Service alert (HARDSTOP, severity 8), and the extreme-age add-on is withheld. Every date-anchored rule reads those two dates, so this is a demographics question, not an add-on question. The alert fires on every specialty.
A new option to review a 99140 that rests on weak evidence. The autocoder trusts a documented emergency and raises no alert for it. Your organization can now ask for a review of the weak cases only. With the Emergency Add-On 99140 Billed On Weak Documentation rule turned on (FINANCIAL, severity 5), a coder is asked when a billed 99140 cites documentation that shows neither a physical status with the E suffix nor a statement that a delay in treatment would significantly increase the threat to life or body part. The rule is off unless you ask for it. A record that reaches you only as handwriting still raises the handwritten emergency-status alert.
The 99116 and 99135 review alert reads more precisely. It now asks you to confirm the record documents deliberate total body hypothermia (99116) or deliberate controlled hypotension (99135) as an anesthetic technique. The cooling and the low blood pressure that come with cardiopulmonary bypass are not the same thing, and they do not support these codes.
Why: a review alert is a question for a human. When the autocoder has no question, it should record what it did and stay quiet. The extreme-age alert asked a coder to re-check arithmetic the autocoder had already verified against the ASA rule, on a large share of anesthesia cases. The payer-class alert reported a decision your own configuration had made.
Physical status modifiers (P1 to P6) now follow your facility setting exactly. If your facility turns physical status modifiers off, no P1 to P6 value reaches a claim line, no matter where it came from. Before this fix, a physical status value that the coding step placed on a code by itself could stay on the claim after the setting said no. When the autocoder removes such a value, it records the removal with the Physical Status Modifier Removed Per Facility Configuration alert (INFORMATIONAL, severity 2). The documented ASA status still shows on the claim when the record has one.
Two new checks protect facilities that do bill physical status. A P1 to P6 value can be on a claim when the record documents no ASA physical status. The Physical Status Modifier Without a Documented ASA Status alert (FINANCIAL, severity 5) then asks a coder to confirm the status. If the setting is off and a value still slips through, the Physical Status Modifier Present Although the Facility Disables Them alert (FINANCIAL, severity 5) reports it.
The extreme-age add-on 99100 is never reported with 00326, 00561, 00834, or 00836. These anesthesia codes already describe a patient younger than 1 year, and CPT does not allow 99100 with them. The autocoder now moves such a 99100 to the bundled procedures, with a reason that names the anesthesia code. No bypass modifier is added.
99100 is re-decided when the demographics arrive late. When the date of birth is missing at coding time and the automatic gap fill recovers it from the record, the autocoder runs the age test again. A patient who qualifies gets 99100 back on the billable lines. A patient the recovered date of birth disproves loses a 99100 that was billing: it moves to the bundled procedures with the reason. The code also stays bundled when the anesthesia code excludes it, when a facility rule withholds it, or when the payer class does not pay it. Before this fix the code stayed off the claim with no trace.
Configuration problems are now visible on the claim. A qualifying circumstance setting that cannot be read as written raises the Qualifying Circumstance Configuration Is Malformed alert (FINANCIAL, severity 5) and names the fault and the posture the autocoder applied. A processing rules setting that cannot be read raises the Processing Rules Could Not Be Read alert (HARDSTOP, severity 9). Every claim now records which facility configuration built it and which qualifying circumstance posture applied to its payer class.
Facility instructions now follow GI and OB cases. An additional coding instruction configured for the anesthesia lane now also applies when the autocoder handles the case as a GI or obstetric case. Before this fix the instruction was dropped on those cases.
What to look out for:
Teams that used the extreme-age alert as a prompt to review patient demographics will not see it any more. If you want a reviewer on every 99100, ask your Hank representative to turn the alert on for the rule that adds the code:
"processingRules": {
"special_circumstances_99100": {
"action": {
"setBillable": true,
"createHRE": true,
"hreTag": "FINANCIAL",
"hreSeverity": 4,
"hreReviewerRole": "CODER",
"hreTemplate": "99100 billed for an extreme-age patient - confirm the date of birth."
}
}
}The same shape works on the 99140 rule. Give every key: the switch turns the alert on, and the other keys set the type, the severity, the suggested reviewer, and the text the reviewer reads.
Two more points. The "enabled" switch on the physical status rule is now ignored; only its value decides. If you set the value to false and also switched the rule off, the modifiers used to appear anyway. They now stop, which lowers the base units billed on P3 and higher. If you switched the rule off but left the value true, nothing changes. And if your reports counted the informational payer-class alert to find bundled add-ons, count the bundled procedures on the claim instead.
The alert "Incomplete operative documentation" (anes_op_notes_incomplete)
now carries the Coder reviewer role. It carried the Reconciler role
before. The alert itself is unchanged: it stays a HARDSTOP at severity 6,
and it fires in the same situations.
Why: the alert asks for a coding decision. The operative notes do not cover all procedures in the record, and the missing procedures were coded from the procedure summary. A coder confirms the codes against the record.
If your workflow sorts alerts by reviewer role, this alert moves from your reconciliation queue to your coder queue.
To keep the old routing, ask your Hank representative to set
"anes_op_notes_incomplete": "RECONCILER" in your facility configuration.
Alert routing is now configurable for every alert, so other alerts can also
move to the queue that fits your team.
A nerve block line, and the ultrasound guidance line that goes with it, carries only the diagnoses documented for the block itself. That is normally the post-procedural pain code. It does not carry the patient's other conditions, because the reason for the block is the reason for the block, not every condition on the chart.
Claim cleaning runs after coding and can add a diagnosis to a line. When it adds one to a block line that the line is not allowed to carry, the autocoder removes it again. That part is not new.
What is new is that you can see it. Before this change the removal happened quietly, and the system also cleared the "added by claim cleaner" note for that code, so nothing on the claim showed that a diagnosis had come and gone. Now the claim carries an informational alert, "Diagnosis Added After Claim Cleaning Was Removed From a Block Line". The alert names the codes it removed, names the diagnoses the line kept, and identifies the line.
Nothing about which diagnoses get removed has changed.
Expect this alert to be rare. Claim cleaning no longer copies the main anesthesia line's diagnoses onto the other lines, so the situation this cleanup was built for does not arise any more. That is exactly why the alert is worth having: if a diagnosis does get added to a block line today, something unusual put it there, and you should look at it rather than have it disappear without a record.
Read the removed codes in the alert. Confirm that none of them is the correct indication for the block. In almost every case the removed code is a condition that belongs on the main anesthesia line instead.
If one of the removed codes IS the correct indication for the block, add it to the block line and tell your coding lead. The same code will be removed again on the next claim of that shape, so it is worth reporting rather than fixing one claim at a time.
The alert follows your existing block-line diagnosis setting. On the shipped default, a block line keeps only the G89 pain-family codes. A facility configured to keep the documented pain-location codes as well will see the alert less often. A facility that has turned the policy off entirely will never see it, because nothing is removed.
Medicare Advantage and managed Medicaid plans follow the Medicare colonoscopy rules. The autocoder used to pick the payer rules from the plan name alone. A plan whose name carries no Medicare or Medicaid marker, for example Humana Gold Plus, Keystone 65, Devoted Health, or AmeriHealth Caritas, could get the commercial rules of the company that administers the plan. The autocoder now also reads the insurance type recorded on the case. These plans get the Medicare or Medicaid row. A recent audit found such plans on about 2 percent of cases.
A surveillance colonoscopy is billed as a screening for every payer except three. Cigna, UHC, and BCBS Nebraska treat surveillance as diagnostic. That list is complete. Every other payer treats a personal history of colon polyps as a high-risk screening. This includes Medicare, Medicaid, VA, and Tricare. In testing, the autocoder could apply a Medicare surveillance exception that does not exist and produce 00811. The same record now produces 00812.
The discontinuous time alert no longer fires on a labor epidural with a cesarean delivery. The autocoder now groups the anesthesia time segments by anesthesia code before it counts them. A labor epidural line and a cesarean delivery line are two services, not a break in one anesthetic. A provider handover also does not count as a break when the two segments touch, for example one segment that ends at 07:00 and the next that starts at 07:01. A true gap inside one anesthesia code still raises the alert.
Staff and surgeon details that your schedulers enter on the OR schedule now survive to the finished claim. This applies to anesthesia cases where the schedule is passed to the autocoder with the case.
Verified schedule identity wins over the notes. The provider name, NPI, role, and title from the schedule are treated as verified. They replace the same details read out of the notes. A provider who appears only on the schedule is added to the claim.
Times from the notes still win. Anesthesia times read from the record continue to decide the billed time. Schedule times fill in only when the record gives none.
Schedule coverage is the last resort for times. When the record has no anesthesia case times and no procedure summary time pair, the billable times can be derived from the schedule staff coverage. The claim then carries the informational alert "Anesthesia Times Derived From OR Schedule", so a reviewer can see where the times came from.
What to look out for: a role or title left blank on the schedule now stays blank on the claim. The autocoder no longer guesses it, because a wrong role changes medical direction and modifier decisions. Incomplete schedule entries therefore show up as blanks. Ask your schedulers to complete the role and title fields on every entry.
This release changes three things on anesthesia claims that include a peripheral nerve block. Our coding experts directed each change. No action is required on your side.
More blocks qualify for ultrasound guidance (76942). The autocoder now adds 76942 to the following block codes when the record documents ultrasound guidance and image storage: 64400, 64405, 64408, 64418, 64420, 64421, 64425, 64430, 64435, 64449, 64450, 64505, 64510, 64517, 64520, 64530, and 64999. New to the list are 64408 (vagus), 64421 (additional intercostal), 64430 (pudendal), 64435 (paracervical), 64505 (sphenopalatine), 64510 (stellate ganglion), 64517 (superior hypogastric), 64520 (lumbar or thoracic paravertebral sympathetic), and 64530 (celiac plexus). Code 64418 (suprascapular) stays on the list: an earlier version of this entry said it was removed, but our experts confirmed on 2026-08-15 that CPT does not bundle imaging into 64418, so 76942 stays billable with it when ultrasound and image storage are documented.
Add-on block lines no longer carry modifier 59 or the X modifiers. When a block is billed as a primary code plus an add-on code (for example, 64461 with 64462), the add-on line is already distinct by definition. The autocoder no longer places 59, XE, XS, XP, or XU on add-on lines. Primary lines are not affected.
The 76942 line now carries the same diagnoses as its nerve block. The ultrasound guidance line used to copy diagnoses from elsewhere on the claim. It now shows the diagnoses on the block line it supports, such as G89.18 (other acute postprocedural pain), and nothing else.
What to look out for: on claims with a suprascapular, pudendal, paracervical, stellate, celiac, hypogastric, or paravertebral sympathetic block, expect a 76942 line when ultrasound and image storage are documented. On claims with add-on block codes, expect the add-on line without 59 or an X modifier.
This release changes what you will see on anesthesia claims in four areas.
TEE codes now come from one family. A transesophageal echo (TEE) claim carries one TEE code from a single code family. Illegal pairs such as 93312 with 93317 no longer occur. Congenital codes (93315-93317) appear only when the record documents evaluation of a congenital anomaly. Monitoring-only TEE produces no separate TEE code, because NCCI bundles it into the anesthesia service.
Nerve block lines keep only their own pain diagnosis. A separately billed
nerve block line now carries the block's own pain code (a G89 code, for
example G89.18) instead of every diagnosis on the encounter. This is the new
default. If your organization prefers the old behavior, or wants the site
pain code included as well, ask your Hank representative about the
nerveBlockLineIcds setting. A block line that ends up with no diagnosis is
held for review, not billed.
What to look out for: block-line diagnoses will look shorter than before. This is correct and intended.
Paravertebral block add-on units are corrected. A multi-level paravertebral block now bills 64461 plus one unit of 64462, not one 64462 per extra level. Medicare denied the extra units in all cases. Continuous catheter blocks bill 64463. The 64484 add-on is unchanged.
Screening colonoscopy claims (combined GI). The PT modifier on combined GI endoscopy code 00813 is now decided by payer at claim build. Medicare recognizes PT on anesthesia code 00811 only, so 00813 goes to Medicare and Medicare Advantage without PT. PT stays on 00813 only for the short list of commercial payers whose policy requires it (BCBS Independence PA and Moda Health), and never when the payer name carries a Medicare or Medicaid marker. Every other payer, and an unknown payer, gets 00813 without PT. An informational note records each keep or strip. PT on any anesthesia code other than 00811, 00812, or 00813 is removed. (Correction 2026-08-15: an earlier version of this entry described the Medicare rule backwards.)
Fewer cases held for missing times. The autocoder now always asks for staff and case times during extraction. Cases that were held with a "no anesthesia times" alert, even though the times were in the record, now code normally.
This release closes 14 findings from a full review of the anesthesia coding stack. Several of them change what your coders will see.
Every OB case is held for review. A claim whose primary anesthesia code is obstetric (01958-01969) now carries the "OB case review" hold. This rule existed in configuration before but never fired because of a defect. If your organization does not want every OB case held, the rule can be turned off or downgraded per facility.
OB add-on codes require their primary. A claim that bills 01968 or 01969 without the 01967 labor analgesia primary is held. An add-on billed alone is a guaranteed payer rejection.
Supervision cases bill both providers. When medical direction drops to supervision (more than 4 concurrent cases), the claim now bills the physician line with modifier AD and the CRNA line with modifier QX. The CRNA line used to disappear, which underbilled the case.
Deliberate hypothermia and controlled hypotension are billed again. Codes 99116 and 99135 were blocked entirely. They now bill when the record documents the technique, and every such line carries a review flag so a coder confirms the documentation and the payer.
Post-op pain epidurals follow the NCCI rule. An epidural placed for post-op pain bills separately (with modifier 59) only when the case was done under general anesthesia. Under spinal or other anesthesia it is bundled, with the NCCI reason recorded on the claim. Placement in the OR no longer causes a silent drop.
Two new safety holds.
TEFRA settings are honored. A TEFRA attestation requirement your organization turned off is now truly excluded from evaluation. Sites with disabled requirements may see fewer "TEFRA requirements unmet" holds.
What to look out for: more held OB claims (by design), two-line supervision billing, occasional 99116/99135 lines with review flags, and the two new hold reasons in your review queues.
Code 29826 can no longer stand alone as the surgical code on a claim. 29826 is arthroscopic subacromial decompression, an add-on code. An add-on code reports work that is done with a base procedure, so it cannot be the only surgical code on a claim. The autocoder now holds a claim whose only surgical code is 29826. Codes 99100 and 99140 were already held this way, and 29826 joins them.
What to look out for: a shoulder arthroscopy case documented only as the decompression will hold until a coder supplies the base procedure. The base procedure is usually stated in the operative report. Find it, add it, and reprocess the case. If the record documents no base procedure, ask the surgeon for the missing detail before you bill the case.
Our coding experts reviewed the autocoder and directed the rules below. No action is required on your side.
Spine anesthesia 00670 follows the overall extent of the operation. The autocoder selects 00670 when the operation uses instrumentation, or covers three or more vertebral bodies, or covers two or more disc levels. The levels do not need to be next to each other.
Abdominal cases route by the operative field. The autocoder selects between upper abdomen 00790 and lower abdomen 00840 from the field the record documents, not from the name of the procedure alone. A colon case routes to 00790 unless the work is only on the sigmoid or the rectum. An exploratory laparotomy (49000) routes to 00790.
Three diagnosis rules changed. A symptom code or a site pain code is dropped when it is part of a documented condition. A personal history code is dropped when the autocoder codes the current condition. A status code never ranks first on the claim.
What to look out for: spine and abdominal code selection will look different on affected cases. Diagnosis lists will be shorter and ordered differently. Both changes follow the expert review.
O80 is coded only when a delivery happened during this stay. O80 reports an encounter for a full term uncomplicated delivery. A labor only case that carried O80 could be billed as a delivery again when the patient came back. The autocoder now requires a documented delivery in this stay. It also requires an outcome of delivery code (Z37) as a secondary diagnosis. It blocks O80 whenever any pregnancy complication is coded.
External cause codes are suppressed on anesthesia claims. Codes from the V, W, X and Y chapters no longer appear on these claims.
A condition documented as a past event is coded as history. A prior heart attack or a prior stroke gets a history code, not a code for a current condition.
An abdominal case documented above the navel routes to 00790. The autocoder selects the upper abdomen code when the record documents an incision or an exploration above the umbilicus. Anesthesia billing follows the operative field, not only the name of the procedure.
What to look out for: a labor only encounter no longer carries a delivery diagnosis. Confirm that the record states the delivery when you expect O80. An abdominal case documented above the navel carries 00790 and the base units of that code.
The anesthesia code is now selected from all of the notes. The autocoder was dropping the procedure summary whenever the pre-anesthesia evaluation was also cited. That happens on nearly every GI case, so the anesthesia code was often selected from the pre-anesthesia plan alone. The plan states what was intended, not what was done.
Anesthesia codes on GI cases can change, and that is the correction. A colonoscopy planned as screening and completed with a polypectomy is the clearest example. The plan supports 00812. The procedure report documents the polypectomy, and 00811 is correct. The autocoder now reads that report.
Code lookups now use the date of service. Code descriptions and code validity resolve from the real date of service, not from the current calendar year. A back dated claim now gets the codes of the correct year.
The notes cited on the final anesthesia code are the notes the autocoder used. The citation was previously taken from the first matching note in the record.
What to look out for: review GI anesthesia codes after this change, because the selected code can differ from what you saw before. Back dated claims should stop showing current year code descriptions.
A code billed as the anesthesia code must belong to the anesthesia code family. The autocoder now checks the anesthesia code against that family. A code outside the family raises a review alert on the claim. A code that is not a real CPT code at all holds the claim.
A code valid only in 2025 could reach a 2026 claim. The check that validates surgical coding was broken, so a retired code could pass onto a claim with a 2026 date of service. That check works again. The autocoder is also told the target code year while it selects codes.
What to look out for: expect alerts that name an anesthesia code which does not belong to the anesthesia code family. Read the record, then select the correct anesthesia code. Review any recent claim that carries a code retired at the end of 2025.
Codes from a handwritten record now carry a real confidence value. Before this change, every code from a handwritten note was stamped with a confidence of 33. The autocoder now scores the handwriting on how legible it is. Clear handwriting scores high. Genuinely illegible handwriting scores low, and the reason appears in the rationale.
Paper charts produce fewer held claims. The low confidence holds on anesthesia codes, surgical codes and diagnosis codes no longer fire when the autocoder reads the handwriting confidently. An illegible record still scores low and still holds.
Code selection changed on records that mix typed and handwritten notes. A legible handwritten code now competes on equal footing when the primary code is selected. A code that scores below 30 drops out of that selection.
What to look out for: expect fewer review queue items on paper charts. If your team used the confidence value of 33 as a marker for "this is a paper chart", that marker no longer exists. Use the handwritten alerts on the claim instead. They state that a handwritten note is the source.