{"id":2377,"date":"2017-04-12T14:14:49","date_gmt":"2017-04-12T21:14:49","guid":{"rendered":"https:\/\/www.microsoft.com\/industry\/blog\/uncategorized\/compliance-confusion\/"},"modified":"2023-05-31T16:39:36","modified_gmt":"2023-05-31T23:39:36","slug":"compliance-confusion","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/healthcare\/2017\/04\/12\/compliance-confusion\/","title":{"rendered":"Compliance confusion"},"content":{"rendered":"

Most of us are naturally hesitant about changes to routine. This is especially true in the healthcare industry. When minor deviations in routine have the potential to cause errors that are life-threatening or costly, it\u2019s understandable that many in the healthcare industry are hesitant to take steps forward.<\/p>\n

But change comes nonetheless. Around the globe, government regulators have been making moves to increase the accuracy and precision of medical documentation. One example is the evolution of medical coding standards. The ICD-10, the tenth revision of the WHO\u2019s standard classification of diseases, provides the healthcare industry with a universal method of classifying and coding diseases and symptoms. And in the US, the ICD-10-CM, implemented in 2015 further refined coding standards. While these standards enable healthcare providers to document their patients\u2019 care with more precision than ever before, they also introduce a new layer of complexity and cause confusion among providers.<\/p>\n

This was the point made by Healthcare Dive in their February article, Healthcare reform can create confusion over compliance for providers<\/a>. The author points out that the transition to ICD-10 has made it all too easy for providers to commit unintentional errors when submitting claims while making compliance a bigger struggle. According to the article, \u201cGray areas most frequently occur when highly technical billing requirements are attached to national coverage determinations. In many instances, providers have little in the way of guidance from federal regulators.\u201d<\/p>\n

The burden of fraud, waste, and abuse<\/h2>\n

When providers unintentionally submit improper claims, this adds to the problem of fraud, waste, and abuse (FWA). Each year, $455 billion in worldwide healthcare spending is lost to FWA<\/a> \u2013 that\u2019s over 6% of every dollar spent on healthcare. The World Health Organization lists FWA among the leading causes of inefficiency<\/a> in worldwide health.<\/p>\n

There is no doubt that ill intent is behind some of these improper claims. Physicians that intentionally over report the cost of their services in order to boost their profits and patients who shop around for unnecessary prescriptions, for example, illegally siphon healthcare funds away from their intended purposes. But even providers with the best of intentions can accidentally contribute to FWA. And because a physician\u2019s main priority is usually to treat patients and not necessarily to comply with health plan requirements, payer regulations, or federal standards, auditors should expect a margin of error when dealing with claims.<\/p>\n

With this knowledge, what can health plans do to accommodate the increased amount of claim errors connected to new coding standards and regulatory norms? Rapid recognition and response is key to auditing success. The longer it takes a health plan to recognize an improper claim, the lower the probability that they will be able to recover the lost funds. Furthermore, the slow process of auditing months-old claims adds to already costly administrative efforts. So when it comes to facing FWA, preparedness is everything. Health plans need to arm themselves with the tools to successfully identify and correct improper claims. Overworked auditors simply cannot manually comb through every claim in order to identify and follow up on each claim on their own. And outdated, on-premises software solutions have limited capacity for both volume and analytical power.<\/p>\n

Finding the rights tools for the job<\/h2>\n

To ensure that auditors can detect and correct improper claims quickly and accurately, health plans need CGI ProperPay, built on Microsoft Cloud Technology and using the Cortana Intelligence Suite. This advanced analytics solution enables health plans to detect improper payment scenarios and review high-priority cases. Through machine learning, CGI ProperPay learns and applies patterns and trends in order to accurately identify improper claims and reduce false positives.<\/p>\n

CGI ProperPay has a robust history of fighting healthcare FWA. Since 1990, health plans of all sizes have used the solution to identify and recover over $2.5 billion dollars. Now available on AppSource, the solution has been rebuilt entirely on the Microsoft Cloud to deliver vast improvements in speed, efficiency, and power that further cement CGI ProperPay as a world leader in preventing improper payments.<\/p>\n

There is no perfect fix for fraud, waste, and abuse in healthcare. In reality, even the new standards and regulations that are designed to fight FWA can create their own problems. But health plans can take control of the situation by ensuring that they have the best possible tools for claims screening. If you\u2019re curious to find out what CGI ProperPay can do for your organization, learn more and see a demo of the solution on Microsoft AppSource<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

When minor deviations in routine have the potential to cause errors, it\u2019s understandable that many in the healthcare industry are hesitant to take steps forward.<\/p>\n","protected":false},"author":576,"featured_media":10292,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"ep_exclude_from_search":false,"_classifai_error":"","footnotes":""},"categories":[1507],"post_tag":[],"content-type":[1483],"coauthors":[2577],"class_list":["post-2377","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-healthcare","content-type-thought-leadership"],"yoast_head":"\nCompliance confusion - Microsoft Industry Blogs<\/title>\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.microsoft.com\/en-us\/industry\/blog\/healthcare\/2017\/04\/12\/compliance-confusion\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Compliance confusion - Microsoft Industry Blogs\" \/>\n<meta property=\"og:description\" content=\"When minor deviations in routine have the potential to cause errors, it\u2019s understandable that many in the healthcare industry are hesitant to take steps forward.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/healthcare\/2017\/04\/12\/compliance-confusion\/\" \/>\n<meta property=\"og:site_name\" content=\"Microsoft Industry Blogs\" \/>\n<meta property=\"article:published_time\" content=\"2017-04-12T21:14:49+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-05-31T23:39:36+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/wp-content\/uploads\/2017\/04\/cgi_blog3_feat2.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"960\" \/>\n\t<meta property=\"og:image:height\" content=\"300\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Jenn Roth\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Jenn Roth\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"3 min read\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/healthcare\/2017\/04\/12\/compliance-confusion\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/healthcare\/2017\/04\/12\/compliance-confusion\/\"},\"author\":[{\"@id\":\"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/author\/jenn-roth\/\",\"@type\":\"Person\",\"@name\":\"Jenn Roth\"}],\"headline\":\"Compliance confusion\",\"datePublished\":\"2017-04-12T21:14:49+00:00\",\"dateModified\":\"2023-05-31T23:39:36+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/healthcare\/2017\/04\/12\/compliance-confusion\/\"},\"wordCount\":747,\"publisher\":{\"@id\":\"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/#organization\"},\"image\":{\"@id\":\"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/healthcare\/2017\/04\/12\/compliance-confusion\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/wp-content\/uploads\/2017\/04\/cgi_blog3_feat2.jpg\",\"articleSection\":[\"Healthcare\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/healthcare\/2017\/04\/12\/compliance-confusion\/\",\"url\":\"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/healthcare\/2017\/04\/12\/compliance-confusion\/\",\"name\":\"Compliance confusion - Microsoft Industry Blogs\",\"isPartOf\":{\"@id\":\"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/healthcare\/2017\/04\/12\/compliance-confusion\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/healthcare\/2017\/04\/12\/compliance-confusion\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/wp-content\/uploads\/2017\/04\/cgi_blog3_feat2.jpg\",\"datePublished\":\"2017-04-12T21:14:49+00:00\",\"dateModified\":\"2023-05-31T23:39:36+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/healthcare\/2017\/04\/12\/compliance-confusion\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/healthcare\/2017\/04\/12\/compliance-confusion\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/healthcare\/2017\/04\/12\/compliance-confusion\/#primaryimage\",\"url\":\"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/wp-content\/uploads\/2017\/04\/cgi_blog3_feat2.jpg\",\"contentUrl\":\"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/wp-content\/uploads\/2017\/04\/cgi_blog3_feat2.jpg\",\"width\":960,\"height\":300},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/healthcare\/2017\/04\/12\/compliance-confusion\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Compliance confusion\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/#website\",\"url\":\"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/\",\"name\":\"Microsoft Industry Blogs\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/#organization\",\"name\":\"Microsoft Industry Blogs\",\"url\":\"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/wp-content\/uploads\/2019\/08\/Microsoft-Logo.png\",\"contentUrl\":\"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/wp-content\/uploads\/2019\/08\/Microsoft-Logo.png\",\"width\":259,\"height\":194,\"caption\":\"Microsoft Industry Blogs\"},\"image\":{\"@id\":\"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Compliance confusion - Microsoft Industry Blogs","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.microsoft.com\/en-us\/industry\/blog\/healthcare\/2017\/04\/12\/compliance-confusion\/","og_locale":"en_US","og_type":"article","og_title":"Compliance confusion - Microsoft Industry Blogs","og_description":"When minor deviations in routine have the potential to cause errors, it\u2019s understandable that many in the healthcare industry are hesitant to take steps forward.","og_url":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/healthcare\/2017\/04\/12\/compliance-confusion\/","og_site_name":"Microsoft Industry Blogs","article_published_time":"2017-04-12T21:14:49+00:00","article_modified_time":"2023-05-31T23:39:36+00:00","og_image":[{"width":960,"height":300,"url":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/wp-content\/uploads\/2017\/04\/cgi_blog3_feat2.jpg","type":"image\/jpeg"}],"author":"Jenn Roth","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Jenn Roth","Est. reading time":"3 min read"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/healthcare\/2017\/04\/12\/compliance-confusion\/#article","isPartOf":{"@id":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/healthcare\/2017\/04\/12\/compliance-confusion\/"},"author":[{"@id":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/author\/jenn-roth\/","@type":"Person","@name":"Jenn Roth"}],"headline":"Compliance confusion","datePublished":"2017-04-12T21:14:49+00:00","dateModified":"2023-05-31T23:39:36+00:00","mainEntityOfPage":{"@id":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/healthcare\/2017\/04\/12\/compliance-confusion\/"},"wordCount":747,"publisher":{"@id":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/#organization"},"image":{"@id":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/healthcare\/2017\/04\/12\/compliance-confusion\/#primaryimage"},"thumbnailUrl":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/wp-content\/uploads\/2017\/04\/cgi_blog3_feat2.jpg","articleSection":["Healthcare"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/healthcare\/2017\/04\/12\/compliance-confusion\/","url":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/healthcare\/2017\/04\/12\/compliance-confusion\/","name":"Compliance confusion - Microsoft Industry Blogs","isPartOf":{"@id":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/healthcare\/2017\/04\/12\/compliance-confusion\/#primaryimage"},"image":{"@id":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/healthcare\/2017\/04\/12\/compliance-confusion\/#primaryimage"},"thumbnailUrl":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/wp-content\/uploads\/2017\/04\/cgi_blog3_feat2.jpg","datePublished":"2017-04-12T21:14:49+00:00","dateModified":"2023-05-31T23:39:36+00:00","breadcrumb":{"@id":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/healthcare\/2017\/04\/12\/compliance-confusion\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.microsoft.com\/en-us\/industry\/blog\/healthcare\/2017\/04\/12\/compliance-confusion\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/healthcare\/2017\/04\/12\/compliance-confusion\/#primaryimage","url":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/wp-content\/uploads\/2017\/04\/cgi_blog3_feat2.jpg","contentUrl":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/wp-content\/uploads\/2017\/04\/cgi_blog3_feat2.jpg","width":960,"height":300},{"@type":"BreadcrumbList","@id":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/healthcare\/2017\/04\/12\/compliance-confusion\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/"},{"@type":"ListItem","position":2,"name":"Compliance confusion"}]},{"@type":"WebSite","@id":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/#website","url":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/","name":"Microsoft Industry Blogs","description":"","publisher":{"@id":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/#organization","name":"Microsoft Industry Blogs","url":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/wp-content\/uploads\/2019\/08\/Microsoft-Logo.png","contentUrl":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/wp-content\/uploads\/2019\/08\/Microsoft-Logo.png","width":259,"height":194,"caption":"Microsoft Industry Blogs"},"image":{"@id":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/#\/schema\/logo\/image\/"}}]}},"distributor_meta":false,"distributor_terms":false,"distributor_media":false,"distributor_original_site_name":"Microsoft Industry Blogs","distributor_original_site_url":"https:\/\/www.microsoft.com\/en-us\/industry\/blog","push-errors":false,"_links":{"self":[{"href":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/wp-json\/wp\/v2\/posts\/2377"}],"collection":[{"href":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/wp-json\/wp\/v2\/users\/576"}],"replies":[{"embeddable":true,"href":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/wp-json\/wp\/v2\/comments?post=2377"}],"version-history":[{"count":0,"href":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/wp-json\/wp\/v2\/posts\/2377\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/wp-json\/wp\/v2\/media\/10292"}],"wp:attachment":[{"href":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/wp-json\/wp\/v2\/media?parent=2377"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/wp-json\/wp\/v2\/categories?post=2377"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/wp-json\/wp\/v2\/post_tag?post=2377"},{"taxonomy":"content-type","embeddable":true,"href":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/wp-json\/wp\/v2\/content-type?post=2377"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.microsoft.com\/en-us\/industry\/blog\/wp-json\/wp\/v2\/coauthors?post=2377"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}