Starting with claims for services on January 1, 2023, the 2 E/M visit families titled “Domiciliary, Rest Home (e.g., Boarding Home), or Custodial Care Services” and “Home Services” are now 1 E/M code family. The new family is titled “Home or Residence Services.” Use the codes in this family to report E/M services you provide to a patient in:
Artificial Intelligence (AI) solutions have been hyped up in everything from customer service to disease diagnosis – and the healthcare revenue cycle hasn’t been exempt.
You’ve likely heard about how AI is a great fit for the healthcare revenue cycle – revenue cycle is a treasure trove of data and workflows that require manual input. Many healthcare leaders have looked specifically to medical coding solutions, asking whether AI could be beneficial there.
While AI is a tempting solution, anyone considering applying AI to their medical coding services should take a step back and consider the idea that while AI might show amazing promise, it might be a bit too early to consider for the healthcare revenue cycle. This means that making a decision too soon might be difficult to reverse.
Data Quality Is a Challenge
An ancient truth of data applies even more to AI – “garbage in, garbage out”. This lesson has emerged clearly in clinical analytics, where organizations have learned that their results depend on clinicians feeding clean and comprehensive data into their EHRs. They’ve learned that if information was entered incorrectly, it flows to other people using the data, comprising data quality and record integrity .
This means that the same issues with inaccuracies that you might have had in the past will persist even under an AI solution. This includes inaccurate information, but also gaps in coding data you might not yet have resolved.
No matter how good your AI models are, you won’t get the results that you’re looking for if your data quality isn’t where it needs to be – no matter what quantity of data you feed into it. Any organization evaluating AI will need to answer some tough questions about their data governance policies and strategies before even considering investing in an AI solution. Skip this step at your own risk.
Trust Should Be a Priority
AI has a particular problem with trust and it’s especially acute in healthcare. Consider some recent commentary on “the black box problem” in AI and machine learning.
“There is much confusion about the black box problem of AI. Many AI algorithms are not explainable, even by the programmers who created them, as the code evolves over several virtual generations and ends up as a complex code whose working is opaque to us humans. We are unable to see the ‘rough work,’ only the final answer. Thus, especially in the critical field of healthcare, there is a big doubt whether we can trust AI.” 
It’s worth asking if you can find a solution you trust enough to implement in your revenue cycle.
Security Is an Issue
Healthcare as an industry has led the pack in identity theft for years now, and while many organizations have made significant progress in their cybersecurity efforts, hackers and cyber criminals still find healthcare extremely appealing. For any organization that is still struggling with security risks or that has just found their footing, AI solutions for medical coding could derail present or future progress.
AI runs on your data networks, which means it’s inherently vulnerable to security risks. Consider its differences from traditional software. Vulnerabilities in traditional software generally flow back to issues with design and source code. In AI, this extends to images, text, audio files, and whatever data that was used to train and run models. Your security team will need to be aware of an entirely new level of threat to keep your data safe from malactors .
You’ll Still Need People
The way some people discuss AI in the revenue cycle, you’d think it was as simple as flipping a switch and enjoying the benefits of increased efficiency and reduced long-term costs. The truth about any AI solution, though, is that while they’ve come a long way, AI still needs some level of human surveillance. While AI can reduce your need for certain positions, it will also launch you into a new phase of hiring and recruitment.
You will need an AI team to manage your projects. This team will require a range of skills and backgrounds and need to operate at high levels of collaboration for you to get the results you’re looking for. Gartner has estimated that half of IT leaders will struggle with any AI project they have beyond the conceptual level – partly because the data scientists they have are doing too much . This is largely because of a talent shortage in other roles. Consider that AI itself is dealing with a labor, skills, expertise, and knowledge shortage – an issue that stands out as the number one barrier to adoption for many organizations.
Ethical Issues Still Exist
Ethics are paramount at all levels in healthcare, revenue cycle included. Unfortunately, incorporating ethics and morality into AI is still a struggle. This is especially true as the importance of social determinants of health (SDoH) continues to grow for healthcare decision makers. AI still might not be able to make considerations that are specific to certain situations.
Risk of Failure
Perhaps the greatest risk of jumping too early into AI for a medical coding solution is what happens if the solution doesn’t work out.
As things stand now, if your AI solution fails, you’re left with little recourse, either experiencing a severe interruption in your revenue cycle while you rebuild or having to quickly hire and train new human staff or possibly even scrambling to sort through medical coding companies and medical coding solutions to help you get moving again.
While we believe in the potential for AI in medical coding services, we also believe that now might be too early for most organizations to take a step. To learn what medical coding services could be a smarter choice for you as AI finds its footing, start here.
 J. Bresnick, “What are the barriers to clinical analytics, big data success?,” Health IT Analytics, 30 July 2014. Available: https://healthitanalytics.com/news/what-are-the-barriers-to-clinical-analytics-big-data-success.
 J. D. Akkara and A. Kuriakose, “Commentary: Is human supervision needed for artificial intelligence?,” Indian J Ophthalmol, vol. 70, no. 4, p. 1138–1139, 2022.
 B. Dickson, “Machine learning security vulnerabilities are a growing threat to the web, report highlights,” PortSwigger Ltd., 30 June 2021. Available: https://portswigger.net/daily-swig/machine-learning-security-vulnerabilities-are-a-growing-threat-to-the-web-report-highlights.
 L. Goasduff, “How to Staff Your AI Team,” Gartner, 15 December 2020. Available: https://www.gartner.com/smarterwithgartner/how-to-staff-your-ai-team.
Clinical Laboratory Improvement Amendments (CLIA) regulations require a facility to be appropriately certified for each test they do. CMS edits laboratory claims at the CLIA certificate level to make sure that Medicare and Medicaid only pay for laboratory tests in a facility with a valid, current CLIA certificate.
Data on telecommunications technology use during a 30-day period of care at the patient level isn’t currently collected on the Home Health (HH) claim. While the provision of services provided via a telecommunications system must be in the patient’s plan of care, the Centers for Medicare & Medicaid Services (CMS) doesn’t routinely review plans of care to determine the extent these services are actually provided.
Effective, January 3, 2023, CMS will add the following codes to the home health consolidated billing non-routine supply code list: