Monday, November 25, 2013

Keeping Your Healthcare Plan: Complications and Updates

The Obama Administration repeatedly stated “If you like your healthcare plan, you can keep it,” once the Affordable Care Act is enacted. However, millions of people received cancellation notices from their insurance companies because their policies did not meet the minimum requirements of basic coverage mandated by the Affordable Care Act.

The minimum requirements include coverage for preexisting conditions, hospitalization, prescription drugs, emergency services, maternity and newborn care, mental health and substance abuse services, laboratory services, rehabilitative  services and devices, pediatric services including oral and vision, ambulatory patient services and preventative and wellness services and chronic disease management. The plans that were canceled do not offer coverage for one or many of these conditions. All of the plans on the healthcare exchanges will cover these basic conditions.

On November 14th President Obama held a news conference announcing the decision to allow insurance companies to keep individuals on health insurance plans that do not meet the law’s requirements for an additional year.  The directive does not require insurance companies to allow customers that were already notified of cancellations to come back. It does give insurance companies the discretion to take back customers to offer the non-compliant insurance plans for one more year.

The ‘fix’ caught state insurance regulators by surprise and was not well-received by representatives of some states.  Many states require insurance commissioners to approve policy changes before the insurers will be allowed to reissue the plans. Regulators in six states will not allow consumers with noncompliant insurance plans to renew their coverage for next year. These regulators based their refusal on concerns about the effects on the state health exchanges, the weak benefits the canceled plans offer, and the increased premiums insurance companies were charging individuals that wanted to keep or reenroll in their canceled plans.  

Like many parts of the Health Care Exchange roll out, this aspect is more complicated than advertised. However, the Obama Administration stated that the individuals that lost their plans had ‘subpar’ health insurance and that their coverage would eventually be upgraded to a health insurance plan that includes many more benefits as required under the Affordable Care Act. 

Protecting Patients' Privacy: Data Security Mishaps

Patient privacy is a top priority for the medical community. Patient data should be virtually secured. It is critical that staff understands what security measures are required and how to implement and utilize those methods. 

Last Tuesday the Redwood Memorial Hospital announced that it lost a thumb drive that may have contained information on more than 1,000 patients. This information contained data that could lead to identifying individual patients. The thumb drive was not encrypted.  The hospital notified patients that are potentially affected and set up a hotline to answer questions related to the situation.

There were multiple factors leading to the security failure in this situation. The first, and most obvious breach is that all patient data should be encrypted. The second mistake leading to the leak is identifiable patient data should not travel offsite unless necessary to transfer information.

There are multiple ways to encrypt patient data. Facilities should have network security measures, two-factor authentications for individual computers, and encrypted portable devices.

Important Tips

Monday, November 11, 2013

Subsidizing Indigent Patients on Exchanges: Fraud and Abuse Concerns



Qualified Health Plans Are Not Considered "Federal Health Care Programs"

Many questions surround the implementation of the Affordable Care Act and how it interacts with existing laws. In an effort to gain clarity, Rep. Jim McDermott wrote to the Department of Health and Human Services to inquire about the status of qualified health plans sold on the healthcare.gov exchanges under Section 112B of the Social Security Act. Specifically the inquiry was whether the qualified health plans fell under the definition for "federal health care programs." 

The guidance was requested  to determine how the interaction of qualified health plans and other benefits known as beneficiary inducements offered with other federal programs. Rep. McDermott's concern centered around individuals receiving duplicative benefits, and the solvency of the federally-funded programs if individuals were allowed to receive benefits from multiple government healthcare programs. Rep. McDermott argued that receiving all of these benefits would generally be forbidden by the Anti-Kickback Statute or the Civil Monetary Penalty Statute. 

The Department of Health and Human Services (HHS) stated qualified health programs are not considered federal health care programs and the Anti-Kickback Statute is not applicable. HHS addressed Rep. McDermott's concerns regarding the solvency of of the federally-funded program by outlining regulation and provisions that establish oversight procedures and authority of the federal exchange marketplace for health insurance. These procedures, the Affordable Care Act, and the False Claim Act allow HHS and the Office of Inspector General to investigate and issue appropriate civil or criminal penalties to those wishing to cheat the federally-funded program. 

In practice this means that healthcare providers that assist indigent patients by subsidizing their premiums on health exchanges may be able to do so without concern about being prosecuted under the Anti-Kickback Statute. The HHS letter suggests that this extends even if the parties receive a tax subsidy. 


A link to Rep. McDermott's letter to HHS can be found here: 
http://mcdermott.house.gov/images/Letter%20August%206%202013.pdf

A link to the response letter from HHS can be found here:
http://mcdermott.house.gov/images/The%20Honorable%20Jim%20McDermott.pdf

Friday, November 1, 2013

Changes to Medical Billing and Coding Requirements

Big changes are coming to the world of medical billing and coding. The introduction of Electronic Medical Record and the 10th edition of the International Classification of Diseases, Clinical Modification and Procedure Coding System (ICD-10) are creating a flurry of activity to ensure a smooth transition. These new developments will affect all medical practitioners’ medical billing and coding and submission of claims. The developers of ICD-10 claim that the new code sets will provide more accuracy in medical coding, which will result in quicker reimbursements and fewer denials.  This will result in better patient care all around.

By October 2014 all ICD-9 code sets used to report medical diagnoses and inpatient procedures must be replaced with ICD-10 code sets. This means that all electronic transactions must use Version 5010 standards to accommodate the ICD-10 codes. Previous versions, Version 4010 and Version 4010 A standards will not accommodate the ICD-10 codes. This should not be a problem for the majority of medical billers because Version 5010 has been required since January 1, 2012.

It is important to note that any claim with ICD-9 codes for services provided on or after the compliance deadline cannot be paid.


The Basics of Preparation

It is important to take several steps before the deadline to make sure the medical billing and coding for each practitioner is up to date. All practitioners that are covered by the Health Insurance Portability Accountability Act are required to transition to ICD-10 code sets.

The software used for EMR and medical billing should be upgraded to a version that incorporates ICD-10. In some cases, hardware upgrades will be necessary. Reaching out to software vendors is an important part of the implementation plan. Ideally the software will be updated and installed with enough time to test it before the compliance deadline.

This is the first in a series of blogs explaining the ICD-10 requirements and ways to have a seamless implementation.