Perficient Healtchare Solutions Blog

Subscribe via Email

Subscribe to RSS feed

Archives

Follow Healthcare Technology on Pinterest

Posts Tagged ‘HIPAA 5010’

Business Intelligence from ICD-10: Are we ready?

The Federal Register outlines the following pros from comments received on the adoption of X12 Version 5010 for HIPAA Transactions: 1) reduction in analysis time and minimization of companion guides; 2) improved efficiency through improved eligibility responses and better search options, reducing phone calls to providers and health plans; 3) improved electronic posting, automation of data entry of reimbursement information; 4) reduction in appeals and cost of sending and processing paper remittance advices; 5) improved clinical data and reporting of diagnosis and procedure codes with the implementation of ICD-10-CM and ICD-10-PCS; and 6) better understanding of clinical data and better monitoring of mortality rates, treatments, lengths of stay, and clinical reasons for seeking health care.[1]

Since the release of these statements in 2009, health plans across the nation have made, or have almost made the transition from 4010 to 5010 and are preparing to meet the ICD-10 mandate date of October, 2013. The industry seems to be pretty excited about all the new information that these changes are going to generate. However, are we appropriately prepared to generate, store, and analyze this information for improvements in our nation’s healthcare system?

It seems there is already a ton of information ready to be generated at our hospitals and health plans, but the appropriate tools are not in place to properly generate and present this information for influential decision making. If we are unable to fully understand the information being processed in our healthcare system today, it may be more difficult than we realize to understand new information and identify how the new mandates have helped us better understand healthcare spending and usage.

For example, health plans process authorizations and claims everyday but do they know what percentage of authorizations turn into paid claims? Or denied claims? Today, there are health plans that are unable to distinguish between approval or denial of an authorization or claim and of individual diagnosis and procedure codes included in it. More specifically, when a Medical Director is requested to review a claim or an authorization, he or she can approve some procedure codes and deny others. So if two codes are approved and two codes are denied, the reporting system will display that only one decision was made because only one form or review was completed. However, that is not the case. The Medical Director actually made four individual decisions. This hides the actual information from leadership, like which codes are being repeatedly approved or denied and why?

With the new ICD-10 codes that are much more specific than the existing ICD-9 codes, being able to better understand clinical data will require the implementation of adequate clinical reporting systems as well. Understanding why authorizations for certain codes were requested and then approved or denied may be more difficult than anticipated. The desire and hope to generate the necessary information does not mean that we are actually ready to generate it. The healthcare industry must invest in robust business intelligence tools to generate actual business intelligence that goes beyond basic metrics. Otherwise, we may be setting ourselves to fall into the same trap we are in today: too much data and not enough information.


[1] Health Insurance Reform: Modifications to the Health Insurance Portability and Accountability Act (HIPAA) Electronic Transaction Standards. Department of Health and Human Services. Federal Register, Vol. 74, No. 11, Friday, January 16, 2009, Rules and Regulations.

AHIP Conference 2012: Day 1 Update

As referenced in the introduction to “America’s Health Insurance Plans (AHIP) Conference,” the decisions that will shape our nation’s health care are near. The Supreme Court Decision. The Presidential election. Implementation decisions within health plans that are shaping the delivery of care.

The intent of the June 20-22 conference in Salt Lake City is to address these factors head on. Many of our nations Health Plans intend to learn firsthand how these decisions will affect their organization’s efforts both immediate and long term.

Close to 200 vendors have either sponsored the conference as content providers or made their Leadership Team available to conference participants.  It is clear that Health Plans have access to an outstanding forum to access a variety of perspectives for navigating their agenda for change.

One theme that has already percolated to the surface of general discussion is the need for industry-wide collaboration.  There may have been good effort already allocated to SOA, 5010, ICD-10, ACOs and general Exchange strategy, but the time has come to transition from plan to action.

AHIP Day 1 included a review of Exchanges as one of the most pressing health care reform implementation issues for health plans, states and national policy makers. AHIP has dedicated a good portion of the agenda to review the policy and operational issues over the past year through examining the critical issues for health plans with a focus on the practical challenges.  Time well spent.

“The Tipping Point” – What one CNO shared with me at HIMSS

Looking back at the last two days of meetings, panels, vendor meetings and sharing I met up with a very close colleague of mine who is one of the brightest CNO’s I have ever met.  Mary Jo and I decided to grab a bite to eat and digest what we saw and learned these past two days at HIMSS.

Mary Jo had a ton of stuff to get off her chest, so I ordered a bottle of German Riesling wine (our favorite) and asked her, “So what is on your mind?” Mary Jo took a look at me and said, “Are you sure you want me to share? I’ve got a lot on my mind and after these last two days I am now truly concerned about what we do when we both get back to work…”  I poured the wine and got comfortable – and boy was she right, she had a lot on her mind.  She started with:

“As we approach revolutionary changes for healthcare policy in the U.S., the industry itself is undergoing complex and confusing changes, many of which involve information systems. The use of IT in medicine has grown in the same way it is growing within the larger cultural landscape: technology is everywhere and though we are not sure what tools may come next, we do know that it is a mainstay. My problem, Steve, is that my nurses and doctors are not prepared to navigate all this change AND take care of their patients!

Information systems in health care practices have not just penetrated the exotic sciences of biotechnology and nanotechnology. The use of database management systems, network-based infrastructures and the significant growth of web-based systems- all paired with recent government legislation- is part of an industry-wide boom that will forever change the landscape of health care practices and administration. We are headed for the Perfect Storm.” Read the rest of this post »

Were you ready for HIPAA 5010?

Hopefully everyone answered ‘yes’ and you had a smooth transition.  In this blog we will discuss some of the items we need to keep in mind when either transitioning or implementing EDI.

Whether you are getting ready to transition to a new standard or initiating EDI for the first time, remember the most important thing is to KNOW YOUR DATA NEEDS!

Knowing what data you expect to send and receive is one of the most important items you can establish.

First, review the standard for the transaction set(s) you want to use (some of the transaction sets used for healthcare are 835, 834 837, 270/271, etc).  Whether this is for Healthcare, Automotive, or any other standard, this is very important.  This will give you an idea of what data is available and what you can plan to accommodate.  Remember, just because it is in the standard does not mean you need that piece of data.

Once you have reviewed the standards, you need to get everyone involved: business users, a data mapper, a database administrator, trading partners and anyone else who might have a vested interest.  It might surprise you as to what data they will actually need and utilize.  Whether the data is used in the data warehouse or for reports it is important to identify your business needs.  Also, try to plan for future business requirements.  Just because you don’t use that piece of data right now doesn’t mean you might not need it as standards evolve.  You can start with a “wish list” and pare it down from there.  Keep in mind that just because you want to receive a particular piece of data, your translation software may not currently be set up to capture, your trading partner may not be able to accommodate, or your clearinghouse may not have that set up in their maps.  We all would like to have everything, but it is not always practical.

If you are converting to a new standard this is the chance to change things.  Just because it has always been done that way is no reason to continue – that may not be the best practice.  This gives you a chance to make things better and perhaps correct things that were not working right before.  If you are initiating a new transaction set, this is the perfect opportunity to grab the data you need and get everything set up right the first time.  This is where it is important to get the users involved.  As the person doing the research you may not think a piece of data is important, but to them it may be very necessary.

When you have identified all your data needs you are ready to move on to the next step – mapping the fields in the standards to your database.  We will talk about that in our next blog.

Have you initiated EDI? What data issues did you face? How did you overcome them?

The Healthcare Domain Model: Where to start?

Let’s say you are tasked with modernizing an age old payer system with no documentation and it is business critical, with hundreds and thousands of lines of code: where would you start? Evaluation of technology stack, infrastructure, assessing the skill sets available, cost, etc. are all part of standard operating procedure, but we’ll save that for another day. The challenge is to rewrite an existing business critical healthcare application, or service-level agreement, with all the foundation necessary to make it a highly scalable system built on concepts of BPM, BRMS and SOA. One approach would be to start with the data model and then build the application model around it. Though this approach is typical, this would lead in to the classical impedance mismatch problem, compromising the domain integrity in very early stages of development. It would be almost impossible to back track from this though you are only halfway in to the development.

Starting with your domain model simplifies the approach for building a state of art system with a solid framework. For example, in a payer benefit system you would:

  1. Define your business entities like benefits, copay, coinsurance etc.
  2. Determine if there are similarities abstract the concepts in to more generic structures. Service would be generic structure representing ER and office visit
  3. Add attributes to the entities
  4. Define relationships between entities

Remember, you are only conceptualizing based on business entities and not letting the relational or object framework dictate your business model. Now you can build your object or data model based on conceptual model. Though this seems very straight forward and SOP it is not. One would need a strong domain SME who could articulate the domain as well as perform domain analysis of the business rules that have been built over decades. If you have a strong domain model to start with, technology or the architecture approach will not make you to go back to the drawing board. The concept of a copay will remain copay forever, irrespective of SOA or *OA, 5010, ICD-10 or HL7. Let’s get the basics right and be nimble …start with the domain!

What processes have you found to be successful? How have you improved your healthcare domain model? 

New White Paper! The HIT Trifecta: Meaningful Use, ICD-10 and HIPAA 5010

Inefficiencies are cited for contributing heavily to the spiraling costs associated with healthcare. Amazingly, much of the healthcare industry operates with ill-equipped, outdated technology systems which hamper efficiency and effectiveness. To remedy this problem, the government is incentivizing healthcare organizations to make substantial business changes that rely on sizable investments in Healthcare Information Technology (HIT).

Meaningful Use, ICD-10 and the HIPAA 5010 transition are important HIT initiatives tied directly to healthcare revenue streams. However, the benefits of investing in this HIT trifecta reach beyond reimbursement dollars. Meeting compliance deadlines will help organizations avoid unnecessary headaches, empower decision makers and positively impact the bottom line.

Download our new white paper, The HIT Trifecta: Meaningful Use, ICD-10 and HIPAA 5010 to learn more about this topic.  You can also visit our Regulatory Compliance page on the healthcare microsite for more content on this topic.

Also, you can watch a recast of last weeks webinar Opportunities Abound: How to Leverage Increased Data Granularity in the ICD-10 Code Set”.  The replay and slides are now available on the Regulatory Compliance page of our website.

How the Healthcare CIO Saves Lives: #1 Ensures Care is Given at the Correct Time

When we think of a Health IT project like Health Information Exchange, many focus on the technology-oriented aspects of designing, selecting, implementing, and managing a technology project. However, Health IT should ultimately be driven by the clinical goal of ensuring that the appropriate level of care is provided to patients in a timely manner.  By connecting all of the disparate parts of a healthcare system, the Healthcare CIO is instrumental in ensuring the timeliness of  this care.

The true clinical goals include:

Enable clinicians in their care processes: By providing clinicians with longitudinal patient healthcare data, physicians will be able to see all healthcare-related services that have been provided, even if that physician was not the individual that delivered that care. In addition, physicians can review healthcare results including laboratory results and prescribed medications.  Physicians can also collaborate on the same patient data to improve outcomes. 

Improving the quality of care for patients across a given condition: This would include quality outcomes around selected disease states as well as specific geographic, ethnic, and gender factors to better target and deliver specific healthcare education and associated services.

Reduce costs associated with providing quality care: Though one of the most important aspects of Health IT is improved quality of care for patients, controlling and being aware of the cost of the care is just as important. By including costs in the exchange of clinical information both healthcare systems and government agencies can begin to understand the correlation between the quality of care and the costs associated with that care. By understanding what was the cost of care, better clinical guidelines and programs can be established to balance cost with better clinical outcomes.

Ensure that personal information remains protected: As more and more clinical information is put into an electronic format, many citizens and patients worry about how this information is protected from unauthorized access. Even with the HIPAA security rules and regulations, healthcare systems, and state government agencies must ensure that as EHR and HIE go live, these solutions provides the necessary protection and access controls to build trust and confidence in those that patients that participate.

A successful Health IT project must be secure, accurate, dependable, appropriate, and responsive to the needs of the users of clinical information to ensure that the appropriate care is delivered. The technology selected should be supportive of these crucial clinical goals rather than become the overriding focus of IT implementation.  When this is achieved, then Health IT can also achieve the ultimate goal of delivering important care at the appropriate time can become a reality.

Don’t Drop the ICD-10 Ball in the Regulatory Deadline Juggle

We are at the AHIP Conference this week, which is one of our favorite events of the year.  It is good fun to meet with the many tech-savvy professionals that make up the health insurance industry.  This year we meet as many regulatory pressures and deadlines are closing in, which is certain to ignite some excellent conversations and knowledge sharing.

Leaders in the healthcare industry are juggling a series of regulatory deadlines and are struggling to keep up.  With 5010, ICD-10, ACO, HIPAA privacy updates, and Meaningful Use, many feel that there are just too many IT projects to keep straight.  With regard to ICD-10, and the prerequisite 5010 transaction set, survey after survey has shown that the healthcare industry is procrastinating.  This is not a surprise.  Fair or not, the healthcare industry has a reputation for procrastination.  One main reason for this procrastination is the hope that the government will blink and push back deadlines.  This game of chicken could prove very costly.

On the provider side, if organizations do not meet the October 1, 2013 deadline, then they will not be able to bill health plans for services.  These deadlines can represent a tremendous cost burden as a result.  If things continue at this rate, then health plans may start receiving claims in both ICD-9 and ICD-10.  Imagine the administrative burden of running two operating systems at the same time.  If they choose not to take on the burden of a dual system, these health plans will need to decide if a claim transmitted with the old ICD-9 code set will be rejected.  Doing work and not getting paid for it is the ultimate cost of procrastination.  Even a 1% decrease in revenues could prove disastrous.

Reward for the Pain of 5010 and ICD-10

Many feel that there are just too many IT projects on the table at once.  However, the transition to ICD-10, and the 5010 precursor, are not just IT projects.  These changes denote a transformation in the way of doing business in healthcare.  This is particularly true for health insurance plans.  This is because data integration is key to completing these conversions.  There are numerous siloed data systems across a healthcare organization in terms of clinical systems, claims, A/R, etc. which become integrated as a result of remediation.  This data integration in and of itself creates a bevy of “next generation” operational benefits, such as those experienced by BCBS of Massachusetts.  As highlighted in an earlier post, there is a reward for the pain of 5010 and ICD-10.  These rewards include:

  • A new level of transactional analysis by virtue of the expansion of the sheer number of new codes from ICD-9
  • The ability to generate more specific clinical data for quality metrics and tracking of resource use, which could save money
  • Improving the quality of operations and the level of understanding in a complex healthcare business, which can save time, money and maximize return in the long run for the U.S. healthcare delivery system
  • The ability to re-structure how a healthcare organization views its service lines for operations and profitability
  • Analysis, database remediation, database migration and testing brings a new detailed capability to examine the profitability and costs by procedure, the costs of specific diagnoses, and potential operational savings from best practice
  • Using re-worked analytic reports built around ICD-9 codes to examine the bigger picture of how business intelligence, decision support and analytics should perform
  • New opportunities for building more comprehensive data marts and stronger operational reporting including digital operations dashboards
  • For the more progressive IT teams, ICD-10 remediation could be an opportunity to move to a self-service model for reporting that capitalizes on a new generation of business intelligence tools

The best advice to healthcare organizations watching the ICD-10 time clock: Don’t treat ICD-10 as just another compliance issue.  Instead, use this as an opportunity to transform into a world-class healthcare organization.

2011 AHIP Conference Trend Watch

The 2011 AHIP national conference  is almost here.  Our team will be out in San Francisco for the June 15-17 event.  With all of the changes we are witnessing in the health insurance industry, this year’s conference promises to address the many needs of conference attendees.  Whether it is meeting regulatory compliance issues or preparing for health insurance exchanges,  the AHIP conference will be the place to be this week.

Participants should leverage the AHIP conference to attend many of their peer organization presentations to learn from personal experience.  We look forward to visiting the exhibit floor to listen and observe what is being highlighted by the vendors as well as what our peers are saying and asking.  Health insurance companies can use this information to formulate how to address important issues.

Most importantly, enjoy the educational and collaborative nature of this event and network with your colleagues and solution providers so you can see the potential that can be achieved.  Take advantage of intelligence and expertise that will be found in San Francisco this week that will enable your health insurance system to be among the world-class organizations.

We would love to meet with you at the conference.  Leave a comment, catch up with us in person, visit our AHIP page, or contact us on Twitter (@Perficient_HC) to discuss what you think the hot topics for health insurance are this year.  Here is what we think:

UTILIZATION MANAGEMENT

Utilization Management (UM) is a process for assessing the delivery of healthcare services to determine if patient care is medically necessary, appropriate, efficient and meets quality standards.

  • Healthcare and BPMS Services: Streamline Payor’s UM processes for higher productivity, and faster turnaround
  • Rules Engines: Create and maintain flexible business processes to meet changing marketing and regulatory needs
  • SMART SOA: Can streamline the IT architecture and speed implementation of automated business processes
  • ECM Practice: Incorporate document management into your UM process to speed review
  • Healthcare Payor Knowledge: Bring value to the design of your UM solution

 ICD-10 IMPLEMENTATION

Perficient’s ICD-10 solution begins with a phased roadmap of coordinated projects beginning with a careful analysis of your healthcare IT applications and ending with the cultural transition of using the expanded code set.

  • Impact Analytics: Automates the identification and visualization of relationships between ICD-9 in historical claims data and corresponding ICD-10 code matches with eight separate levels of complexity and risk.
  • ICD-10 Code Management: A medical ontology based code management system that allows modeling and mapping of ICD-9 codes into ICD-10 equivalents, and vice versa.
  • ICD-10 Test Management Automates the creation of large volumes of ICD-10 test data and shows the differences between results processed in ICD-9 and in ICD-10.
  • ICD-10 Code Translation A scalable, high-performance translation engine that enables ICD code translation (forward/backward)
  • ICD-10 Consulting Services: Provides expert support for the software toolset and services.

HIPAA 4010 TO 5010 CONVERSION

Perficient’s HIPAA 4010 to 5010 solutions are a full scope effort within your organization including:

  • Assessment: Identify the tools and technologies that best fit your environment. Clarify the benefits and opportunities you can expect. Define the people and process changes that will facilitate a 5010 upgrade program
  • Solution Roadmap: Define an actionable roadmap that clearly articulates the steps required for a successful upgrade. Align to business goals while mitigating risks.
  • Implementation: Execute this roadmap with a flexible project approach. We work in concert with your team to deliver results at lower costs than our competitors.
  • Business Process Improvement: Improve business processes for electronic data transactions (824 – application reporting, 820 – premium payments); transaction reprocessing and transaction management; new stricter enforcement of the HIPAA legislation; new regulations convert business associates as covered entities under HIPAA.

BCBS Massachusetts HIPAA 5010 and Next Generation Capabilities

In this video Joel Thimsen of Perficient and Larry Rosen of BCBS of Massachusetts discuss the architecture of the next generation EDI and SOA solution in support of HIPAA 5010 and modernization of Blue Cross middleware infrastructure in support of scaling to next generation capabilities.

3 Reasons for using a Managed Private Cloud for Interoperability

Cloud computing is a popular topic in IT circles today, and with this year’s Interoperability Showcase at HIMSS, the cloud’s impact on Interoperability will be an interesting topic of discussion.  In healthcare circles, cloud computing conjures up fears for protecting private healthcare information and security concerns.  There is a business case for a special type of cloud computing for healthcare called a Managed Private Cloud.  A Managed Private Cloud could address the security concerns and deliver:

  1. cost reduction
  2. the  ability to scale, and
  3. better utilization of IT resources.

Cost reduction in healthcare organizations is clearly at the top of the list. The cost reductions derived from cloud computing aren’t new technologies, but a combination of existing technologies.  Virtualization drives higher utilization of resources and thus lowers capital expenses. Standardization also lowers capital and labor costs, and automation reduces the management costs. In addition, automation automates many of the manual tasks, especially related to system integration and interoperability and their associated costs.  The other key aspect of cloud computing is availability and stability both of which improve the end-user satisfaction and reduce lost productivity.

The concept of a Managed Private Cloud is different from the public cloud that many people understand from Amazon and Google.  A Managed Private Cloud would have the advantages of cloud computing but be owned by the enterprise (your healthcare organization), be capable of mission-critical applications, handle packaged applications and have high security compliance because it is controlled by your owners – your organization.  But there is one big difference – a Managed Private Cloud is typically third-party operated and removes the challenge of managing the virtual infrastructure from your organization.  This concept is a very different way of receiving and using compute application resources.  It is especially important when there are needs to scale up and down depending on compute needs.

Let’s examine a key application for the use of a Managed Private Cloud – system integration and interoperability.  Most healthcare organizations tackle this challenge by provisioning their own hardware, wrestling with operating systems, loading software and meeting the infrastructure management challenges on a day to day basis.  By contrast, a Managed Private Cloud maintains the hardware infrastructure, the operating systems, the storage management and infrastructure support activities.  This utility allows the customer to focus on the real task at hand – creating the connections between disparate systems and external partners. 

Scale-ability is an important feature of the Managed Private Cloud.  The Managed Private Cloud can scale up a development, testing or next version production environment as needed or on-demand.  More importantly, it can scale down as well.  As integrated EMR applications take over the silo’ed software systems that are currently integrated, then the managed infrastructure can be reduced along with their associated costs.   Time savings are significant from the Managed Private Cloud due to better utilization of resources to avoid waiting on the acquisition of new hardware or loading of operating systems (provisioning) just to get a project started.  This environment is ideal for organizations that prefer to prototype new applications then scale them up to production.

Moving away from the traditional approach of pulling hardware resources together and deploying them in support of a business function workload, essentially one project at a time actually contributes to the silos that make interoperability costly for many healthcare organizations.  More importantly, the Managed Private Cloud is designed for the 24x7x365 nature of healthcare, especially with a high degree of system integration.  This is a task that is very challenging for an internal IT team, especially in geographic areas where IT infrastructure skills are scarce or costly due to competition for talent.

A Managed Private Cloud is a better use of IT resources when a healthcare organization is considering a healthcare information exchange (HIE), particularly if the HIE involves multiple hospitals, private practices and laboratories.  Cloud technology has unique advantages to support this need: economies of scale, better resource utilization and the security of a private organizational ownership.  The connections to the various units of the organization from the Managed Private Cloud would be secure, private and, yet, always available.  The burden of the infrastructure provisioning and day-to-day management of the environments wouldn’t fall on the largest hospital or organizational unit.

In summary, the Managed Private Cloud is a prime time idea for healthcare and due to its design can address the security, compliance and other cloud concerns while delivering cost reductions, the ability to scale, and better utilization of IT resources.  Interoperability projects, especially HIEs, have a great affinity for the cloud computing model both technically and from a risk/reward perspective.  Just like good interoperability is about adopting standards, standardizing the provisioning for IT projects will lead to better economics.

If you would like to discuss this idea or other healthcare-related topics, please stop by Perficient’s booth (#3681) at HIMSS on Monday, February 21, 2011 from 1:30 p.m. to 3:00 p.m. or Tuesday, February 22, 2011 from  2:00 – 5:00 p.m.  See you there!

Don’t Get Lost with HIPAA 5010 – Try Translation!

If you have ever struggled just to get out of town to start a long trip, then you can relate to the challenges facing healthcare payers and providers in implementing HIPAA 5010 and meeting the rapidly approaching deadlines.  Citing difficulties with competing healthcare IT projects, HIMSS noted in August that its most recent ICD-10/HIPAA 5010 Provider Readiness Survey showed that most healthcare providers will not be ready to start HIPAA 5010 testing by the recommended date of January 1, 2011. The HIMSS study found that only 38 percent of providers reported having an ongoing HIPAA 5010 initiative, while 35 percent indicated they have no timeline plans for implementing such a project.

While many providers claim to have a roadmap on how to implement HIPAA in another study, the majority of them believe that an upgrade by their software vendor will solve the problem.  Such transitions, for both 5010 and ICD-10, will be difficult and complex for the software vendors. Payers, for instance, have hundreds of vendors, many of whom have something to do with HIPAA 5010 or ICD-10 codes, and they have to manage all of them, individually. That same goes for providers.  Here is the kicker – whether vendors deliver the updates on time or not, the ultimate responsibility resides with providers and payers.  The healthcare providers are at the mercy of the vendors for timing, and the software vendors are not small companies.  The payers and providers are ultimately the ones who get the penalty for a non-compliant claim.

Providers or payers facing a software vendor who is not going to make the deadline can take the dramatic approach of switching to another vendor who will meet the deadline or adopting a short term “fix” to inbound and outbound HIPAA 5010 transactions.  The solution is to stay compliant through translation of the 4010 to 5010 transactions in both directions. By adopting this approach, the payer or provider can isolate that software application until it meets 5010 or ICD-10 compliance and they can continue operating.

Translation is the approach that would take an inbound HIPAA 5010 transaction, validate it, translate it to a 4010 transaction and send it to the existing software applications for consumption.  Conversely, when the existing software applications produced a 4010 transaction, it would be translated to HIPAA 5010, validated and then sent to the trading partner.  This step-up, step-down translation approach can help payers or providers that don’t have time for lengthy remediation or competing IT projects – like an EMR implementation meet the deadlines for testing without the big “rip and replace” or anxiety of running multiple large parallel projects.

Another advantage of translation is that as existing software applications become HIPAA 5010 compliant, then simply stop translating – validate, then send or receive.  This systematic implementation of HIPAA 5010 allows incremental cut-over of the many software packages in the typical healthcare IT environment and that reduces the time pressure on the journey to ICD-10.  Most trips are less stressful, when you can take a leisurely approach and, when in a foreign land, have a translator handy.

To read more about the time-saving translation approach: http://www.edifecs.com/downloads/Edifecs5010-StepUp-StepDown.pdf