{"id":7774,"date":"2022-04-29T17:05:02","date_gmt":"2022-04-29T11:35:02","guid":{"rendered":"https:\/\/www.medisysdata.com\/blog\/?p=7774"},"modified":"2022-11-02T14:14:15","modified_gmt":"2022-11-02T08:44:15","slug":"avoiding-common-documentation-pitfalls","status":"publish","type":"post","link":"https:\/\/www.medisysdata.com\/blog\/avoiding-common-documentation-pitfalls\/","title":{"rendered":"Avoiding Common Documentation Pitfalls"},"content":{"rendered":"<p>Its quite common to receive a request for medical records from insurance carrier who is going to conduct an audit on your claims. Sometimes, in such external\/payer audits, practices receive audit results like, medical necessity not supported; records include conflicting data; or notes are cloned. Audit report also says practice owes them huge amount of money due to \u2018overpaid claims\u2019 and they are putting on pre-payment review until things improve. Practices wonder what went wrong? Because their <a href=\"https:\/\/en.wikipedia.org\/wiki\/Electronic_health_record\" target=\"_blank\" rel=\"noopener\">Electronic Health Record<\/a> (EHR) system was excellent, coders are good at using right codes, clinical notes were voluminous, patients also achieved great outcomes. In this article, we discussed about avoiding common documentation pitfalls especially three of them: Cloning Medical Records, Conflicting Information, and Overstuffed Progress Note.<\/p>\n<h2>Cloning Medical Records<\/h2>\n<p>Auditors whether private and public, loves to deny claims based on allegations that the provider simply copied and pasted prior notes. \u2018Copy\/paste\u2019 type operations that occur without needed modifications to content is a process infamously known as \u2018cloning\u2019. And that doesn\u2019t just refer to the entire progress note as a whole; it can refer to pieces of a progress note that are inaccurate. Those pieces could be integral to billing a distinct procedure, or a crucial element associated with an office visit code. If one or more pieces never, or almost never, change from one visit to the next, the auditor doesn\u2019t know if the information simply didn\u2019t change, or may have changed but just wasn\u2019t edited. In most cases, auditors seem to assume the latter.<\/p>\n<h2>Conflicting Information<\/h2>\n<p>The presence of conflicting information is another red flag. If the history indicates the patient has severe dementia, but the review of the systems template indicates \u201cAll systems were reviewed and negative\u201d, well, that could be a problem. One error of this nature can lead to a reviewer to cast aspersions on the integrity of your note. \u201cWhat else could be wrong with this chart?\u201d, thinks the auditors. Truth be told, these are usually just innocuous mistakes that do not represent any intent to commit billing fraud but the auditors don\u2019t see it that way. They don\u2019t know if you forgot to revise that review of systems because you\u2019re up until 11:30 pm signing off on your notes, or if you\u2019re trying to pad the record with billing elements. All they know is there is a conflict or redundancy which could represent something fraudulent.<\/p>\n<h2>Overstuffed Progress Note<\/h2>\n<p>Another pitfall that may come back to haunt you is the overstuffed progress note. This occurs when the sheer quantity of the displayed items seems wildly disproportionate to the nature of the presenting problems. Taken at face value, it would seem that a single, self-limiting medical condition would not normally warrant a complete review of past medical, family, and social history, a full review of systems and comprehensive exam. Although there may be times when circumstances do require a more intensive evaluation than meets the eye, the payers expect this would be the exception, not the norm.<\/p>\n<p>All of this leads to a presumption that the information in your charts is questionable. Once that notion is planted in an auditor\u2019s head, it colors their perspective. If you happen to be a \u2018high volume\u2019 provider with disproportionately more billing of any particular code or modifier, the notion that there must be something disingenuous going on becomes solidified. This thinly veiled ethical challenge can be insulting and infuriating to hard-working providers who would never intentionally submit an unsupported health claim.<\/p>\n<p><strong>Medisys Data Solutions<\/strong> is a leading medical billing company providing complete billing and coding services for various medical billing specialities. To know more about our <a href=\"https:\/\/www.medisysdata.com\/contact-us\" target=\"_blank\" rel=\"noopener\">medical billing and coding services<\/a>, contact us at info@medisysdata.com\/ 302-261-9187<\/p>\n<p>Reference: <a href=\"https:\/\/www.medicaleconomics.com\/view\/coding-audits-101-how-physicians-can-prepare\">Coding audits 101: How physicians can prepare<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Its quite common to receive a request for medical records from insurance carrier who is going to conduct an audit on your claims. Sometimes, in such external\/payer audits, practices receive audit results like, medical necessity not supported; records include conflicting data; or notes are cloned. Audit report also says practice owes them huge amount of [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":7775,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_coblocks_attr":"","_coblocks_dimensions":"","_coblocks_responsive_height":"","_coblocks_accordion_ie_support":"","footnotes":""},"categories":[3],"tags":[241],"class_list":["post-7774","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-medical-billing-services","tag-medicalbilling-medicalcoding-healthcare-physician-patient"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v21.4 (Yoast SEO v27.2) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Avoiding Common Documentation Pitfalls<\/title>\n<meta name=\"description\" content=\"In this article, we discussed avoiding common documentation pitfalls, especially three of them: Cloning Medical Records, Conflicting Information, and Overstuffed Progress Note.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.medisysdata.com\/blog\/avoiding-common-documentation-pitfalls\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Avoiding Common Documentation Pitfalls\" \/>\n<meta property=\"og:description\" content=\"In this article, we discussed avoiding common documentation pitfalls, especially three of them: Cloning Medical Records, Conflicting Information, and Overstuffed Progress Note.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.medisysdata.com\/blog\/avoiding-common-documentation-pitfalls\/\" \/>\n<meta property=\"og:site_name\" content=\"Leading Medical Billing Outsourcing Services Company in the USA\" \/>\n<meta property=\"article:published_time\" content=\"2022-04-29T11:35:02+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-11-02T08:44:15+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.medisysdata.com\/blog\/wp-content\/uploads\/2022\/04\/Blog-Avoiding-Common-Documentation-Pitfalls.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"748\" \/>\n\t<meta property=\"og:image:height\" content=\"288\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"medisys\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"medisys\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"3 minutes\" \/>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Avoiding Common Documentation Pitfalls","description":"In this article, we discussed avoiding common documentation pitfalls, especially three of them: Cloning Medical Records, Conflicting Information, and Overstuffed Progress Note.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.medisysdata.com\/blog\/avoiding-common-documentation-pitfalls\/","og_locale":"en_US","og_type":"article","og_title":"Avoiding Common Documentation Pitfalls","og_description":"In this article, we discussed avoiding common documentation pitfalls, especially three of them: Cloning Medical Records, Conflicting Information, and Overstuffed Progress Note.","og_url":"https:\/\/www.medisysdata.com\/blog\/avoiding-common-documentation-pitfalls\/","og_site_name":"Leading Medical Billing Outsourcing Services Company in the USA","article_published_time":"2022-04-29T11:35:02+00:00","article_modified_time":"2022-11-02T08:44:15+00:00","og_image":[{"width":748,"height":288,"url":"https:\/\/www.medisysdata.com\/blog\/wp-content\/uploads\/2022\/04\/Blog-Avoiding-Common-Documentation-Pitfalls.jpg","type":"image\/jpeg"}],"author":"medisys","twitter_card":"summary_large_image","twitter_misc":{"Written by":"medisys","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.medisysdata.com\/blog\/avoiding-common-documentation-pitfalls\/#article","isPartOf":{"@id":"https:\/\/www.medisysdata.com\/blog\/avoiding-common-documentation-pitfalls\/"},"author":{"name":"medisys","@id":"https:\/\/www.medisysdata.com\/blog\/#\/schema\/person\/9f5cfa90ddf7805d6badbe7f652e4abf"},"headline":"Avoiding Common Documentation Pitfalls","datePublished":"2022-04-29T11:35:02+00:00","dateModified":"2022-11-02T08:44:15+00:00","mainEntityOfPage":{"@id":"https:\/\/www.medisysdata.com\/blog\/avoiding-common-documentation-pitfalls\/"},"wordCount":638,"commentCount":0,"image":{"@id":"https:\/\/www.medisysdata.com\/blog\/avoiding-common-documentation-pitfalls\/#primaryimage"},"thumbnailUrl":"https:\/\/www.medisysdata.com\/blog\/wp-content\/uploads\/2022\/04\/Blog-Avoiding-Common-Documentation-Pitfalls.jpg","keywords":["#medicalbilling #medicalcoding #healthcare #physician #patient"],"articleSection":["Medical Billing Services"],"inLanguage":"en","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.medisysdata.com\/blog\/avoiding-common-documentation-pitfalls\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.medisysdata.com\/blog\/avoiding-common-documentation-pitfalls\/","url":"https:\/\/www.medisysdata.com\/blog\/avoiding-common-documentation-pitfalls\/","name":"Avoiding Common Documentation Pitfalls","isPartOf":{"@id":"https:\/\/www.medisysdata.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.medisysdata.com\/blog\/avoiding-common-documentation-pitfalls\/#primaryimage"},"image":{"@id":"https:\/\/www.medisysdata.com\/blog\/avoiding-common-documentation-pitfalls\/#primaryimage"},"thumbnailUrl":"https:\/\/www.medisysdata.com\/blog\/wp-content\/uploads\/2022\/04\/Blog-Avoiding-Common-Documentation-Pitfalls.jpg","datePublished":"2022-04-29T11:35:02+00:00","dateModified":"2022-11-02T08:44:15+00:00","author":{"@id":"https:\/\/www.medisysdata.com\/blog\/#\/schema\/person\/9f5cfa90ddf7805d6badbe7f652e4abf"},"description":"In this article, we discussed avoiding common documentation pitfalls, especially three of them: Cloning Medical Records, Conflicting Information, and Overstuffed Progress Note.","breadcrumb":{"@id":"https:\/\/www.medisysdata.com\/blog\/avoiding-common-documentation-pitfalls\/#breadcrumb"},"inLanguage":"en","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.medisysdata.com\/blog\/avoiding-common-documentation-pitfalls\/"]}]},{"@type":"ImageObject","inLanguage":"en","@id":"https:\/\/www.medisysdata.com\/blog\/avoiding-common-documentation-pitfalls\/#primaryimage","url":"https:\/\/www.medisysdata.com\/blog\/wp-content\/uploads\/2022\/04\/Blog-Avoiding-Common-Documentation-Pitfalls.jpg","contentUrl":"https:\/\/www.medisysdata.com\/blog\/wp-content\/uploads\/2022\/04\/Blog-Avoiding-Common-Documentation-Pitfalls.jpg","width":748,"height":288,"caption":"Avoiding Common Documentation Pitfalls"},{"@type":"BreadcrumbList","@id":"https:\/\/www.medisysdata.com\/blog\/avoiding-common-documentation-pitfalls\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.medisysdata.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Avoiding Common Documentation Pitfalls"}]},{"@type":"WebSite","@id":"https:\/\/www.medisysdata.com\/blog\/#website","url":"https:\/\/www.medisysdata.com\/blog\/","name":"Leading Medical Billing Outsourcing Services Company in the USA","description":"You Cure We Secure","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.medisysdata.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en"},{"@type":"Person","@id":"https:\/\/www.medisysdata.com\/blog\/#\/schema\/person\/9f5cfa90ddf7805d6badbe7f652e4abf","name":"medisys","image":{"@type":"ImageObject","inLanguage":"en","@id":"https:\/\/secure.gravatar.com\/avatar\/79d7a562f3c08c721df502178306075752b41ea9a19670eb43265d6e0f4a501d?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/79d7a562f3c08c721df502178306075752b41ea9a19670eb43265d6e0f4a501d?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/79d7a562f3c08c721df502178306075752b41ea9a19670eb43265d6e0f4a501d?s=96&d=mm&r=g","caption":"medisys"},"sameAs":["https:\/\/www.medisysdata.com\/blogs"],"url":"https:\/\/www.medisysdata.com\/blog\/author\/admin\/"}]}},"_links":{"self":[{"href":"https:\/\/www.medisysdata.com\/blog\/wp-json\/wp\/v2\/posts\/7774","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.medisysdata.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.medisysdata.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.medisysdata.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.medisysdata.com\/blog\/wp-json\/wp\/v2\/comments?post=7774"}],"version-history":[{"count":3,"href":"https:\/\/www.medisysdata.com\/blog\/wp-json\/wp\/v2\/posts\/7774\/revisions"}],"predecessor-version":[{"id":8703,"href":"https:\/\/www.medisysdata.com\/blog\/wp-json\/wp\/v2\/posts\/7774\/revisions\/8703"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.medisysdata.com\/blog\/wp-json\/wp\/v2\/media\/7775"}],"wp:attachment":[{"href":"https:\/\/www.medisysdata.com\/blog\/wp-json\/wp\/v2\/media?parent=7774"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.medisysdata.com\/blog\/wp-json\/wp\/v2\/categories?post=7774"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.medisysdata.com\/blog\/wp-json\/wp\/v2\/tags?post=7774"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}