ANSI 5010 and ICD-10-CM
ANSI 5010 and ICD-10-CM
ANSI 5010 and Medisoft 17
HIPAA 2.0 requires ANSI 5010 formatting for all electronic claims submission.
Question: ANSI 5010 will not be required until January 2012. So why worry about it now?
Answer: There are quite a few new fields required for ANSI 5010. Do you really want to just start using them and have to catch up on all your patients next January? It's best to go ahead and get Medisoft 17 and start getting up to speed with what you'll need to do to insure a seemless transition to the new year!
Medisoft ANSI Crosswalk
Medisoft 5010 compliant Practice Information
Fields added:
- Practice Email
- Phone Extension (not an ANSI 5010 requirement, but just added in Medisoft)
Medisoft ANSI 5010 compliant Patient / Guarantor
Fields added:
- Race - Based on the US Census Guidelines
- American Indian or Alaskan Native (I)
- Asian (A)
- Black (B)
- Caucasian (C)
- Other (E)
- Pacific Islander (P)
- Ethnicity - Based on the US Census Guidelines
- Hispanic (H)
- Non-Hispanic (N)
- Language
- Death Date
Medisoft ANSI 5010 compliant Case Policy 1 tab
Fields added:
Group Name
Medisoft ANSI 5010 compliant Case Policy 2 tab
Fields added:
- Medicare Secondary Reason (only if Insurance 2 is Medicare)
- Black Lung (41)
- Disabled Beneficiary Under Age 65 with LGHP (43)
- End-Stage Renal Disease (13)
- No-fault Insurance including Auto is Primary (14)
- Other Liability Insurance is Primary (47)
- Public Health Service (PHS) or Other Federal Agency (16)
- Vetern's Administration (42)
- Worker's Compensation (15)
- Working Aged (12)
Medisoft ANSI 5010 compliant Case Condition tab
Fields added:
- Nature of Accident
- Injured at home
- Injured at School
- Injured during Recreation
- Work Injury/Self Employed
- Work Injury/Non-collision
- Work Injury/Collision
- Motorcycle Injury
What is ANSI 5010?
ANSI 5010 is the new version of HIPAA transaction standards that regulates the electronic transmission of healthcare transactions. The 5010 standards will replace the existing 4010/4010A1 version of HIPAA transactions and address many of the shortcomings in the current version, including the fact that 4010 does not support forthcoming ICD-10 coding. The Centers for Medicare and Medicaid Services (CMS) requires that all entities covered under HIPAA conform to the new 5010 standards by January 1, 2012. Similar to the National Provider Identifier (NPI) transition, practices will need to upgrade their practice management solution in order to be compliant with ANSI 5010.
Who does the ANSI 5010 change affect?
The ANSI 5010 change affects physicians, payors, software vendors and clearinghouses/ third-party billers.
When must the transition to ANSI 5010 be completed?
By January 1, 2012, practices will need to complete electronic transactions in an ANSI 5010-compliant format. These electronic transactions include claims, eligibility inquiries and remittance advices. Failure to comply may result in denied claims, slower payments and increased customer service issues.
What is the urgency to upgrade my practice management system?
Significant changes have been made to McKesson’s Medisoft practice management systems to comply with the new ANSI 5010 standards. These changes affect the amount of data and the way data is stored in the systems as well as your practice workflow. If you are on an older version of the software, the implementation of the compliant versions will be more complex and time-consuming than previous upgrades. In addition, testing of the new ANSI 5010 standards has already begun. By upgrading now, you can take advantage of the testing period and ensure that your claims are compliant in advance of the deadline.
How can Dibb Solutions help?
We are here to help your practice transition to ANSI 5010. Medisoft v17 is our ANSI 5010 compliant releases. Medisoft v17 is currently available! Don’t wait to start preparing. Call us today at 910-424-0227.
The HIPAA/EDI provision was scheduled to take effect from October 16, 2003 with a one-year extension for certain "small plans". However, due to widespread confusion and difficulty in implementing the rule, CMS granted a one-year extension to all parties. On January 1, 2012 the newest version 5010 becomes effective, replacing the version 4010. This allows for the larger field size of ICD-10-CM as well as other improvements.
After July 1, 2005 most medical providers that file electronically did have to file their electronic claims using the HIPAA standards in order to be paid.
Key EDI(X12) transactions used for HIPAA compliance are:
EDI Health Care Claim Transaction set (837) is used to submit health care claim billing information, encounter information, or both, except for retail pharmacy claims (see EDI Retail Pharmacy Claim Transaction). It can be sent from providers of health care services to payers, either directly or via intermediary billers and claims clearinghouses. It can also be used to transmit health care claims and billing payment information between payers with different payment responsibilities where coordination of benefits is required or between payers and regulatory agencies to monitor the rendering, billing, and/or payment of health care services within a specific health care/insurance industry segment.
For example, a state mental health agency may mandate all healthcare claims, Providers and health plans who trade professional (medical) health care claims electronically must use the 837 Health Care Claim: Professional standard to send in claims. As there are many different business applications for the Health Care claim, there can be slight derivations to cover off claims involving unique claims such as for Institutions, Professionals, Chiropractors, and Dentists etc.
EDI Retail Pharmacy Claim Transaction (NCPDP Telecommunications Standard version 5.1) is used to submit retail pharmacy claims to payers by health care professionals who dispense medications, either directly or via intermediary billers and claims clearinghouses. It can also be used to transmit claims for retail pharmacy services and billing payment information between payers with different payment responsibilities where coordination of benefits is required or between payers and regulatory agencies to monitor the rendering, billing, and/or payment of retail pharmacy services within the pharmacy health care/insurance industry segment.
EDI Health Care Claim Payment/Advice Transaction Set (835) can be used to make a payment, send an Explanation of Benefits (EOB), send an Explanation of Payments (EOP) remittance advice, or make a payment and send an EOP remittance advice only from a health insurer to a health care provider either directly or via a financial institution.
EDI Benefit Enrollment and Maintenance Set (834) can be used by employers, unions, government agencies, associations or insurance agencies to enroll members to a payer. The payer is a healthcare organization that pays claims, administers insurance or benefit or product. Examples of payers include an insurance company, health care professional (HMO), preferred provider organization (PPO), government agency (Medicaid, Medicare etc.) or any organization that may be contracted by one of these former groups.
EDI Payroll Deducted and other group Premium Payment for Insurance Products (820) is a transaction set which can be used to make a premium payment for insurance products. It can be used to order a financial institution to make a payment to a payee.
EDI Health Care Eligibility/Benefit Inquiry (270) is used to inquire about the health care benefits and eligibility associated with a subscriber or dependent.
EDI Health Care Eligibility/Benefit Response (271) is used to respond to a request inquire about the health care benefits and eligibility associated with a subscriber or dependent.
EDI Health Care Claim Status Request (276) This transaction set can be used by a provider, recipient of health care products or services or their authorized agent to request the status of a health care claim.
EDI Health Care Claim Status Notification (277) This transaction set can be used by a health care payer or authorized agent to notify a provider, recipient or authorized agent regarding the status of a health care claim or encounter, or to request additional information from the provider regarding a health care claim or encounter. This transaction set is not intended to replace the Health Care Claim Payment/Advice Transaction Set (835) and therefore, is not used for account payment posting. The notification is at a summary or service line detail level. The notification may be solicited or unsolicited.
EDI Health Care Service Review Information (278) This transaction set can be used to transmit health care service information, such as subscriber, patient, demographic, diagnosis or treatment data for the purpose of request for review, certification, notification or reporting the outcome of a health care services review.
EDI Functional Acknowledgement Transaction Set (997) this transaction set can be used to define the control structures for a set of acknowledgments to indicate the results of the syntactical analysis of the electronically encoded documents. Although it is not specifically named in the HIPAA Legislation or Final Rule, it is necessary for X12 transaction set processing . The encoded documents are the transaction sets, which are grouped in functional groups, used in defining transactions for business data interchange. This standard does not cover the semantic meaning of the information encoded in the transaction sets.
Can your practice afford to lose $5,000? How about $25,000?
That’s the risk you run if you are not able to submit your claims in the upcoming ANSI 5010 electronic standard.
If you aren’t using the ANSI 5010-compliant Medisoft® v17 software, you may see an increase in claim rejections: Say you submit $500,000 in claims each year. A 1% increase in claim rejections can mean $5,000 in lost revenue to your practice. A 5% increase in rejections is $25,000 in lost revenue!
The MSRP on a new Medisoft Advanced license is $1,299. MSRP on a new Medisoft Network Professional is $3,599. Upgrades from one or two version old are much less. Is it worth the risk?
Consider just a few of the new data fields required by ANSI 5010 that aren’t possible with older versions of Medisoft:
Special federal programs now require additional information that states that a patient is part of the program in order to get funding.
ANSI 5010 requires more information to be submitted for claims, which increases the need to submit additional documentation.
Condition codes, which are specific to a patient, are now required on professional claims.
Without Medisoft v17, how will you get this information to your clearinghouse? How will you be sure that your claims are correct?
ANSI 5010 testing began January 1, 2011. Get started now by upgrading to Medisoft v17 and get peace of mind that your claims will be paid.
In addition to ANSI 5010 compliance, Medisoft v17 features an array of enhanced capabilities:
BillFlash integration – enables submission of patient statements electronically to BillFlash directly from Statement Management; BillFlash replaces costly and time-consuming manual patient statement processing with a low-cost electronic statement processing service
Office Hours Professional now included – enhances scheduling workflow
Revenue Management now included at no additional charge – enables pre-claim editing, eligibility verification and intuitive remittance posting
Revenue Management “click reduction” enhancements make the feature easier to use and improve office workflow
Configuration enhancements – simplify ERA processing
The Health Insurance Portability and Accountability Act (HIPAA) of 1996 (P.L.104-191) [HIPAA] was enacted by the U.S. Congress in 1996. It was originally sponsored by Sen. Edward Kennedy (D-Mass.) and Sen. Nancy Kassebaum (R-Kan.). According to the Centers for Medicare and Medicaid Services (CMS) website, Title I of HIPAA protects health insurance coverage for workers and their families when they change or lose their jobs. Title II of HIPAA, known as the Administrative Simplification (AS) provisions, requires the establishment of national standards for electronic health care transactions and national identifiers for providers, health insurance plans, and employers.
The Administration Simplification provisions also address the security and privacy of health data. The standards are meant to improve the efficiency and effectiveness of the nation's health care system by encouraging the widespread use of electronic data interchange in the U.S. health care system.
Docs face problems as they fall behind on HIPAA 5010
By bmonegain
Created 06/16/2011
ENGLEWOOD, CO – A majority of medical groups have not completed critical software upgrades for transition to HIPAA Version 5010 electronics standard, nor have they scheduled testing with health plans, according to follow-up research by the Medical Group Management Association (MGMA).
Medical practices face disruptions in claims processing and other essential administrative transactions if they don't successfully implement Version 5010 by the Jan. 1, 2012, compliance date. To assist physician practices with the transition, MGMA is calling on practice management system software vendors to intensify their rollout of compliant products, and on health plans to schedule testing. MGMA has also called on the government to develop contingency plans should the industry not be ready to meet the compliance date.
Most groups rely on their practice management system software to conduct the HIPAA electronic transactions. Only 29 percent of respondents believed their current practice management system software would permit them to use Version 5010, and 50.3 percent of respondents said their software would require an update. Also, 4.5 percent of respondents indicated their software would need to be replaced. More than 30 percent of respondents indicated they had not received any communication from their practice management software vendors regarding the change to Version 5010.
"We are growing increasingly concerned regarding the ability of medical group practices to meet the Jan. 1 deadline," said William F. Jessee, MD, MGMA president and CEO. "Our research indicates a significant number of practices have been forced to wait for their practice management system software vendors to make the required modifications before they can begin to test with clearinghouses and health plans.
"Respondents who have already upgraded or replaced their software have incurred more than $16,000 per physician in expenses, which includes the cost of software, hardware and staff training,” Jessee said. “This is a significant expense for a medical practice in this challenging economy. It is critical that vendors communicate their readiness status and the expected transition costs to groups quickly to permit practices to appropriately budget and plan."
MGMA's research also found:
- Implementation – Many respondents (45.2 percent) stated they have not started their implementation of Version 5010; 45.9 percent have partially completed implementation, and only 2 percent reported they had completed implementation.
- Testing – Nearly 40 percent of respondents (38.2) indicated internal testing had not yet been scheduled; 40.8 percent said they planned to start testing between March 2011 and December 2011. Another 2 percent did not plan to start internal testing until after January 2012 (the deadline for compliance with the new standard), while 9.2 percent of respondents had started to test.
A large number of respondents (49.7 percent) reported that external testing had yet to be scheduled with major health plans; only 2.7 percent reported that this external testing had already been initiated with all of their major health plans.
"As only six months remain before the compliance date, the Centers for Medicare & Medicaid Services must aggressively augment its outreach to both physician practices and practice management system vendors," Jessee said. "MGMA urges the government to institute an appropriate contingency plan to avoid widespread cash flow disruption in the industry, should dramatic improvements in the implementation status of providers not be observed in the next few months."
MGMA and the American Medical Association have jointly developed several tools to help practices meet the new requirements, such as the Selecting a Practice Management system Toolkit and the Practice Management System Software Directory.
Source URL: http://www.healthcareitnews.com/news/docs-face-problems-they-fall-behind-hipaa-5010
Some physician practices may be too slow out of the gate when it comes to meeting the deadline for conversion to Health Information Portability and Accountability Act (HIPAA) version 5010.
Just 29% of respondents to an American College of Physicians (ACP) survey say they have taken action to prepare for conversion to HIPAA version 5010. More than half of the respondents (52%), however, expected their practices to be compliant by the January 1, 2012, deadline.
That expectation may be overly optimistic. Not only do physicians need to upgrade their practice management systems or ensure that their billing service has made the necessary updates, they will need to collect and report additional information for claims to be processed, and change established billing practices.
Respondents who had not started to make the transition cited lack of staff and time, budget constraints, and competing transitions as the primary barriers to undertaking the conversion process.
Practices worried about the cost of converting to 5010 need to make room in their budgets or risk seeing their revenue diminished beginning in 2012. “If you are not ready, your claims will not be paid,” according to the Centers for Medicare and Medicaid Services (CMS) Web site. And it isn’t just Medicare or Medicaid payments that will be affected. The new standards regulate and standardize the electronic transmission of specific healthcare transactions such as eligibility, claims, referrals, and remittances for all health plans, clearinghouses and billing services, and providers.
Some of the new requirements will alter practices’ standard billing procedures. For instance, all practices must provide their street addresses and nine-digit zip codes rather than a post office box, and the “billing provider” can no longer be a billing service or clearinghouse. The new system also expands the number of diagnosis codes that can be reported from eight to 12.
According to the CMS Small Providers Compliance Timeline, practices should now be finalizing testing of their systems with health plans and CMS, making any necessary changes in office procedures, and completing final deployment of new systems. For the 71% of practices that have yet to start the transition, the Medical Group Management Association and the American Medical Association recently developed an online practice management system software directory that identifies vendors who are already 5010 compliant. Medisoft V17 is ANSI 5010 compliant.
The ACP survey was one of five concurrent surveys conducted to assess industry readiness for 5010 and ICD-10 conversions in which 396 individuals participated, mostly coders who work in physician practices. The ACP had 31 physician respondents.
If you are not on version 17 of Medisoft, your software is not 5010 ready. Time is literally running out, give me a call at 910-424-0227 for a free quote.