The ICD-10 code set has 200,000 codes, almost 10 times the 24,000 codes in the ICD-9 code set. Providers and payers will need to completely redesign their business processes and systems to handle these hundreds of thousands of new codes. Before the transition to ICD-10 can begin, industry must move to the next generation of HIPAA transactions (version 5010) because the current version (4010) will not work with ICD-10. Version 5010 is a major re-write of the HIPAA transaction standards, with more than 850 individual changes.
The Department of Health and Human Services recently proposed rules to implement 5010 by April 2010 and ICD-10 by October 2011. This may appear to be a staggered implementation of these daunting initiatives but in reality, it is not quite that easy. There is no debate as to whether or not 5010 must be implemented prior to conversion to ICD-10 as the expanded diagnosis codes cannot be worked into the standard HIPAA transactions until the appropriate fields have been expanded. The question becomes, is 18 months enough time to have the standard transactions modified, tested, and implemented prior to moving to the enhanced code set? Many think that the timeline is not realistic.
Preparing for 5010 and ICD-10 can hardly be classified under regular system maintenance and operations. Carrying the hefty estimated price tag of $10-20 million, preparing for these changes really falls into to the category of major system modification. As such, many States will be asking for contracted help to perform this work. The feds have hinted that they will pay enhanced (90%) funding for the 5010/ICD-10 work; qualifying for this funding will require an APD and then either a contract modification or an RFP. If a State were to begin today by writing and submitting a planning APD to explain to the feds their approach and plans for 5010/ICD-10 compliance, it would likely be a full year before the final implementation APD and contract mod were approved. If an RFP is involved, add 6-8 months for the award process. On this schedule, work would not even begin until late 2009/early 2010, hardly in time to meet the first deadline of April 2010.
The National Committee for Vital and Health Statistics--an advisory body to HHS—made a recommendation to implement HIPAA 5010 first followed by ICD-10. If the NCVHS process were followed and started now, the soonest ICD-10 could be completed is late 2013, this seems like a more realistic timeframe.
Another consideration is the provider side of the equation. A key lesson learned from HIPAA is that provider education and outreach is critical to ensure providers are aware of the changes that must be made and adequate time is given to make those changes. Providers are looking at a vastly expanded set of options for assigning diagnosis codes. This means that they all must be trained in the awareness and use of the codes and many practice management systems will need to be enhanced, or likely replaced in order to comply with use of the expanded codes. Will this occur on schedule currently presented for payer system compliance? Probably not. The enhancements for 5010 and ICD-10 are not “backward compatible” and so we are looking at the potential for crippling claims backlogs, inaccurate and delayed payments, and an inability to detect fraud and abuse. Is the accelerated timeline worth all of this?
The MITA community needs to give some serious thought into how MITA fits with these two initiatives. How can resources be integrated in such a way that states are moving toward both HIPAA II and MITA compliance in a combined effort? Can MITA business services at level three maturity be built as 5010/ICD-10 compliant? It doesn’t seem practical to keep MITA and HIPAA II as separate activities; there must be a way to kill two birds with one stone here.
Thoughts?
Monday, October 6, 2008
Friday, October 3, 2008
HL7 MITA Project Pics Added
Click on the slide show at the top of the MITA Matters homepage to see a few pictures of the HL7 MITA Project group during a meeting at MMIS 2008 in Nashville. Sent by a friend of the blog, thanks!
Thursday, October 2, 2008
MITA Governance Update
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjFacRmfVVZQu0VvlVWkfY_3BFjS1WiP7HWdRZ_pJIEmSkfiuv4To8xIOpvxdSVdUPlAC94H-N5pn_Jh39c6RNq3WU3Pkt4F6XMNQt2tm20PhpWMOxzgxycs59Chhol3xqaZfCEukEeSlnI/s320/MITA+Governance.jpg)
I have it on good authority that Chairpersons have been selected for both the MITA Technical Architecture Review Boards (TARB) and MITA Information Architecture Review Board (IARB). This is good news because these boards are one the critical path to establishing a fully-fledged MITA repository, populated with approved artifacts from each of the three architectures.
Among the TARB’s initial tasks will be a review of the Technical Function Templates that are being completed by the MITA Technical Architecture Committee (TAC). The IARB first official act is likely to be a review of the HL7 MITA Project’s MITA Development Methodology document. It will be interesting to see where these documents are posted once they are approved. I have not heard anything regarding an update to CMS plans for a new repository site. Currently, approved MITA Business Architecture documents can be found here: http://hl7projects.hl7.nscee.edu/docman/?group_id=40.
Among the TARB’s initial tasks will be a review of the Technical Function Templates that are being completed by the MITA Technical Architecture Committee (TAC). The IARB first official act is likely to be a review of the HL7 MITA Project’s MITA Development Methodology document. It will be interesting to see where these documents are posted once they are approved. I have not heard anything regarding an update to CMS plans for a new repository site. Currently, approved MITA Business Architecture documents can be found here: http://hl7projects.hl7.nscee.edu/docman/?group_id=40.
Wednesday, October 1, 2008
HL7 MITA Project Meeting Announcement
The HL7 MITA Project will be holding a teleconference meeting tomorrow aftern0on from 2:30 pm - 4:00 pm EDT. Anyone with an interest in the MITA Information Architecture is welcome to attend the meeting. This group meets every Thursday afternoon.
Meeting Title: HL7 MITA Project
Date & Time: Weekly, Thursday
11:30 PT, 12:30 Mtn, 1:30 CT, 2:30 ET
Join Link: https://ahcccs.ilinc.com/join/kfrxpt
Dial In Number: 770-657-9270
Participant PIN: 451256
Meeting Agenda:
1. Call to order
2. Establish/determine minute taker
3. Review Agenda
4. Approve call minutes for 09/04/2008
5. Working Group Updates/Changes
Ø Introduce Roger Todd, our MITA Project, Project Manager
Ø Discuss sub-workgroups
6. HL7 V3 Ballot Reconciliation
http://www.hl7.org/v3ballot/html/welcome/environment/index.htm
See screen print following agenda for additional reference
6. Review Deliverables for next call
Internal Updates and Com
Respond to Provider
Circle back, final check on all sub-phases
7. Agenda for next call, October 09, 2008
Meeting Title: HL7 MITA Project
Date & Time: Weekly, Thursday
11:30 PT, 12:30 Mtn, 1:30 CT, 2:30 ET
Join Link: https://ahcccs.ilinc.com/join/kfrxpt
Dial In Number: 770-657-9270
Participant PIN: 451256
Meeting Agenda:
1. Call to order
2. Establish/determine minute taker
3. Review Agenda
4. Approve call minutes for 09/04/2008
5. Working Group Updates/Changes
Ø Introduce Roger Todd, our MITA Project, Project Manager
Ø Discuss sub-workgroups
6. HL7 V3 Ballot Reconciliation
http://www.hl7.org/v3ballot/html/welcome/environment/index.htm
See screen print following agenda for additional reference
6. Review Deliverables for next call
Internal Updates and Com
Respond to Provider
Circle back, final check on all sub-phases
7. Agenda for next call, October 09, 2008
Subscribe to:
Posts (Atom)