{"id":20612,"date":"2023-08-02T12:00:29","date_gmt":"2023-08-02T12:00:29","guid":{"rendered":"https:\/\/www.varshabi.com\/HCIM2\/?p=20612"},"modified":"2023-08-02T19:51:55","modified_gmt":"2023-08-02T19:51:55","slug":"data-integrity-are-you-putting-your-organization-at-risk","status":"publish","type":"post","link":"https:\/\/www.varshabi.com\/HCIM2\/data-integrity-are-you-putting-your-organization-at-risk\/","title":{"rendered":"Data Integrity: Are you putting your organization at risk?"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

For many payers, mundane tasks such as claim adjustments, recoupments, and retroactive changes are relegated to SQL scripts for the perceived benefit of freeing up more time in their examiner\u2019s day.<\/p>

While this seems like an efficient practice that allows staff to focus their attention on more complex tasks, many organizations are unaware that while SQL scripts may seem like an easy fix, this practice could be putting their organization at risk.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

What is a SQL script?<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

SQL (Structured Query Language) is a domain-specific language used in programming and designed for managing data held in a relational database management system (RDBMS<\/a>) or for stream processing in a relational data stream management system (RDSMS).<\/p>

A SQL script is a series of commands or a sequence of instructions that can be written and saved as a stored procedure, allowing the designated user to run the script to complete the defined task.<\/p>

SQL Scripts include the following commands:<\/strong><\/span><\/p>

UPDATE \u2013 editing records in a database to modify certain fields in specified table(s)<\/strong><\/span><\/p>

INSERT INTO \u2013 add specified records in a table<\/strong><\/span><\/p>

DELETE \u2013 delete selected records from a table<\/strong><\/span><\/p>

There are also commands for creating a table, modifying a table structure, creating a database, modifying a database, and removing a table from a database.<\/p>

Running scripts has become a common solution many small to midsize payer organizations lean on to automate their manual processes and save time and resources.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

What are the drawbacks to running SQL scripts?<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

While this may seem like a convenient solution, SQL scripts can have significant drawbacks. The scripts are generally created by someone in the organization\u2019s IT team who is relying on specifications from the operations team. Writing SQL scripts requires a high level of expertise; qualified individuals generally have at least 5\u20137 years of experience. Because of the expertise required, even a small gap in communication between the teams can result in unintentional errors that could very easily compromise or corrupt claims data.<\/p>

The core issue with SQL scripts is they make data changes to the back end of the claims system and, in most cases, do not track the changes that have been made to the data. This means that anytime a SQL script is run, it can potentially corrupt the data in the system. Errors from something as simple as running the wrong script, deleting the wrong data, updating data fields (i.e., \u201cfind and replace\u201d), or unintentionally applying changes to claim lines that weren\u2019t intended to be altered, could all have a significant impact on operations.<\/p>

While it is possible to write a script that includes logging actions taken, many do not take that extra step. Without this important tracking, there is no audit trail, making it nearly impossible to track what the values were in claim lines before the changes were made by the script. This not only creates a compliance risk but would be problematic if the action needed to be undone due to a programming error.<\/p>

Even if a user can immediately catch a mistake, they likely will have no way of knowing which lines were accidentally compromised unless they are logging which records are changed. Most organizations rely on database backups as their fallback solution when something goes wrong, but this option also has its flaws. Restoring a previous version means starting from scratch, and undoing all changes that were made. In a worst-case scenario, if the change is made during production hours, all the work of the claim examiners would also be undone in an attempt to undo the change. Database comparison is a lengthy and complicated process, so manually identifying inconsistencies requires substantial resources.<\/p>

Another issue with scripts is it is impossible to identify the end user that applied the changes to the data, and because SQL scripts bypass all built-in application security, they do not account for whether that user had the skill or authority to make those changes in the first place.<\/p>

What all this uncertainty means is that, at any given time, a company\u2019s data can be compromised by its use of SQL scripts. This could jeopardize the organization and result in a failed audit.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

Are SQL scripts really a compliance issue?<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Healthcare Data Governance (DG) is vital to an organization\u2019s success and a key component of any audit. Ensuring data quality is a fundamental responsibility of all operations professionals, not just those who manage compliance. AHIMA defines Data Quality and Integrity<\/a> as \u201cthe extent to which healthcare data are complete, accurate, consistent and timely throughout its lifecycle including collection, application (including aggregation), warehousing, and analysis.\u201d<\/p>

From an audit perspective, it is crucial to have an accurate and complete audit trail of any data changes or updates. The log should provide all key information, with sequential user and system activities including a timestamp when changes to system records occur. When running a SQL script, the log of actions taken may be incomplete or skipped altogether. From claims data to eligibility to authorizations, there are a myriad of requirements and policies passed down from government agencies. When violated, they could result in lawsuits or penalties that will severely impact the organization.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

How can I automate processes while still preserving data integrity?<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Fortunately, this does not mean claims processing needs to be a painful, manual process simply to protect your data. There is a way to have all the time-saving benefits of SQL scripts without the associated risks.<\/p>

SymKey, HCIM\u2019s tried-and-true solution, can automate manual processes without compromising data integrity. SymKey software leverages IntelliRPA\u00ae<\/sup> robotic process automation to process claims more efficiently and securely than SQL scripts.<\/p>

SymKey can process claims up to 8x faster than a claims examiner and with 100% accuracy, eliminating the chance of human error and freeing up your staff for more complex tasks.<\/p>

Since it runs entirely through the front-end of your claims system, just like a claims examiner would, your operations and IT departments can rest easy knowing all processes are secure and there is no direct writing to the database tables.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

SQL Script<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

SymKey<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Protects data integrity by making changes from the user interface, not on the back end<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t

\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t
\n\t\t\t<\/i>\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t
\n\t\t\t<\/i>\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Logs every action<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t

\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Sometimes\/Rarely<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t

\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t
\n\t\t\t<\/i>\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Bypasses system edits and messages that potentially would automatically pend a claim<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t

\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t
\n\t\t\t<\/i>\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Never<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Requires high level of experience<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t

\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t
\n\t\t\t<\/i>\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t
\n\t\t\t<\/i>\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Bypasses all built in application security and security assigned to user profiles<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t

\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t
\n\t\t\t<\/i>\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t
\n\t\t\t<\/i>\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Automatic tracking to easily identify claims that were updated<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t

\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t
\n\t\t\t<\/i>\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t
\n\t\t\t<\/i>\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Compliant and audit friendly<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t

\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t
\n\t\t\t<\/i>\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t
\n\t\t\t<\/i>\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

The benefits of SymKey.<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Aside from security and data integrity, SymKey has many other benefits to help optimize your company\u2019s operations.<\/p>

SymKey delivers:<\/h3>

Greater Efficiency <\/strong><\/span>\u2014 Our robots can complete months\u2019 worth of work in a fraction of the time, letting you focus on the complex tasks that help your business grow.<\/p>

Increased Accuracy<\/strong><\/span> \u2014 SymKey consistently applies business rules and ensures complete and thorough documentation on each and every claim, ensuring accuracy and compliance.<\/p>

Cost Savings<\/strong> <\/span>\u2014 SymKey is an affordable solution that delivers an immediate return on investment by increasing productivity and reducing manual processes.<\/p>

SymKey can touch and edit virtually any claim header or detail line field in your claims system. With this powerful tool, users can automate an unending list of manual workflows with claims, provider, and authorizations modules.\u00a0 Some examples include reprocessing paid claims, retroactively adjusting or denying claims, duplicating claim logic, matching authorizations, providers data updates, and so much more. SymKey robots provide unique flexibility and control using customized scenarios based on your business rules.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

How can my company optimize operations with SymKey?<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

HCIM has been helping streamline payer operations for over 23 years. We are dedicated to partnering with our clients to deliver automation solutions that meet the demands of the ever-evolving market.<\/p>

Whether you\u2019re looking to improve your data management processes, enhance the accuracy of your claims processing, or streamline your workflows, HCIM\u2019s SymKey solution can help you achieve your goals and deliver value.<\/p>

Reach out today<\/a> to speak to one of our health plan operations experts and learn more about how we can help you turn your complexity into simplicity and drive better results for your organization.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t
<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t
<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t
<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"

For many payers, mundane tasks such as claim adjustments, recoupments, and retroactive changes are relegated to SQL scripts for the perceived benefit of freeing up more time in their examiner\u2019s day. While this seems like an efficient practice that allows staff to focus their attention on more complex tasks, many organizations are unaware that while […]<\/p>\n","protected":false},"author":1,"featured_media":20614,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[38,79,86,57,85,30],"class_list":["post-20612","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-healthcare-information-management","tag-blog","tag-cms","tag-data-integrity","tag-hcim","tag-healthcare-spending","tag-symkey"],"_links":{"self":[{"href":"https:\/\/www.varshabi.com\/HCIM2\/wp-json\/wp\/v2\/posts\/20612","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.varshabi.com\/HCIM2\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.varshabi.com\/HCIM2\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.varshabi.com\/HCIM2\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.varshabi.com\/HCIM2\/wp-json\/wp\/v2\/comments?post=20612"}],"version-history":[{"count":10,"href":"https:\/\/www.varshabi.com\/HCIM2\/wp-json\/wp\/v2\/posts\/20612\/revisions"}],"predecessor-version":[{"id":20688,"href":"https:\/\/www.varshabi.com\/HCIM2\/wp-json\/wp\/v2\/posts\/20612\/revisions\/20688"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.varshabi.com\/HCIM2\/wp-json\/wp\/v2\/media\/20614"}],"wp:attachment":[{"href":"https:\/\/www.varshabi.com\/HCIM2\/wp-json\/wp\/v2\/media?parent=20612"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.varshabi.com\/HCIM2\/wp-json\/wp\/v2\/categories?post=20612"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.varshabi.com\/HCIM2\/wp-json\/wp\/v2\/tags?post=20612"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}