Archive for November, 2019

In The Know: Introduction to the IOCE V20.3

Posted by Samantha Serfass on November 19, 2019 in Blog, News

All institutional outpatient claims, regardless of facility type, process through the Integrated Outpatient Code Editor (IOCE). The IOCE is a program utilized by Medicare Administrative Contractors (MAC) for outpatient hospitals both subject to and not subject to the Outpatient Prospective Payment System (OPPS).

The IOCE performs two major functions:

  1. Edit the claims data to identify errors and return a series of edit flags.
  2. Assign an Ambulatory Payment Classification (APC) number for each service covered under OPPS to be used as input to an OPPS PRICER program. For Non-OPPS claims, a series of Non-OPPS applicable edits are returned.

All applicable services should be submitted as a single claim record to the IOCE. The IOCE only functions on a single claim and does not have any cross-claim capabilities. The IOCE accepts up to 450-line items per claim. The IOCE software is responsible for ordering line items by date of service. The span of time that a claim represents is controlled by the From and Through dates identified on the claim. If the claim spans more than one calendar day, the IOCE subdivides the claim into separate days for the purpose of determining discounting and multiple visits on the same calendar day.

The IOCE identifies individual errors. Each edit is unique, as it directly links the reason the edit is returned, any related information at the line or claim level, and the action required indicated by the edit disposition. The IOCE performs all functions referencing HCPCS codes, modifiers and ICD-10-CM diagnosis codes. Since these coding systems are complex, the centralization of the direct reference to these codes and modifiers in a single program reduces effort and reduces the chance of inconsistent processing of claims.

The current version includes 111 edits. We highlighted 27 edits below of specific interest to outpatient coders.

Edit Edit Description Reason for Edit Generation Disposition
1 Invalid diagnosis code The principal diagnosis field is blank, there are no diagnoses entered on the claim, or the entered diagnosis code is not valid. RTP
2 Diagnosis and age conflict The diagnosis code includes an age range, and the age reported is outside that range. RTP
3 Diagnosis and sex conflict The diagnosis code includes sex designation, and the sex does not match. This edit is bypassed if condition code 45 is present on the claim. RTP
5 External cause of morbidity code cannot be used as principal diagnosis The diagnoses reported is considered a morbidity code and cannot be used as the principal diagnoses RTP
6 Invalid procedure code The entered HCPCS code is not valid for the selected version of the program. RTP
8 Procedure and sex conflict The sex of the patient does not match the sex designated for the procedure code reported. This edit is bypassed if condition code 45 is present on the claim. RTP
12 Questionable covered service The procedure reported is flagged as a Questionable covered service. Suspend
17 Inappropriate specification of bilateral procedure The same inherent bilateral procedure code occurs two or more times on the same service date. This edit is applied to all relevant bilateral procedure lines, except when modifier 76 or 77 is submitted on the second or subsequent line or units of an inherently bilateral code. Note: For codes with an SI of V that are also on the Inherent Bilateral list, condition code G0 will take precedence over the bilateral edit; these claims will not receive edit 17. This edit is also bypassed if the bill type is 85x. RTP
20 Code2 of a code pair that is not allowed by NCCI even if appropriate modifier is present The second procedure reported is part of an NCCI pair, which will cause the generation of edit 20 to LIR even in the presence of a modifier. LIR
21 Medical visit on the same day as a type T or S procedure without modifier 25 One or more type T or S procedures occur on the same day as a line item containing an E&M code, without modifier 25. RTP
22 Invalid modifier The modifier is not in the list of valid modifier entries and the revenue code is not 540. RTP
23 Invalid data The service date and/or the from and through dates are invalid. Or the Service date falls outside the range of the From and Through dates. This edit terminates processing for the claim. RTP
27 Only incidental services reported All line items are incidental (status indicator N). If edit 27 is present no other edits are performed. Claim Rejection
37 Terminated bilateral procedure or terminated procedure with units greater than one A modifier 52 or 73 is present, as well as: an independent or conditional bilateral procedure with modifier 50 or a procedure with units greater than 1. RTP
40 Code2 of a code pair that would be allowed by NCCI if appropriate modifier were present The procedure is identified as part of another procedure on the claim coded on the same day, where the modifier was either not coded or is not an NCCI modifier. Only the code in column 2 of a code pair is rejected; the column 1 code of the pair is not marked as an edit. LIR
42 Multiple medical visits on same day with same revenue code without condition code G0 Multiple medical visits (based on units and/or lines) are present on the same day with the same revenue code, without condition code G0 to indicate that the visits were distinct and independent of each other. RTP
43 Transfusion or blood product exchange without specification of blood product A blood transfusion or exchange is coded but no blood product is reported. RTP
44 Observation revenue code on line item with non-observation HCPCS code A 762 (observation) revenue code is used with a HCPCS other than observation 99217-99220, 99234-99236, G0378, reported. RTP
48 Revenue center requires HCPCS The bill type is 13x, 74x, 75x, 76x, or 12x/14x without condition code 41, HCPCS is blank, and the revenue center status indicator is not N or F. This edit is bypassed when the revenue code is 100x, 210x, 310x, 099x, 0905-0907, 0500, 0509, 0583, 0660-0663, 0669, 0931, 0932, 0521, 0522, 0524, 0525, 0527, 0528, 0637, or 0948; see also edit 65. RTP
60 Use of modifier CA with more than one procedure not allowed Modifier CA is present on more than one line or Modifier CA is submitted on a line with multiple units. RTP
70 CA modifier requires patient discharge status indicating expired or transferred CA modifier requires patient discharge status indicating expired or transferred. RTP
73 Incorrect billing of blood and blood products Blood product claims lack two identical lines (of HCPCS code, units, and modifier BL), one line with revenue code 38x and the other line with revenue code 39x. RTP
74 Units greater than one for bilateral procedure billed with modifier 50 Any code on the Conditional or Independent bilateral list is submitted with modifier 50 and units of service are greater than one on the same line. RTP
79 Incorrect billing of revenue code with HCPCS code The revenue code is 381 with a HCPCS code other than packed red cells (P9016, P9021, P9022, P9038, P9039, P9040, P9051, P9054, P9057, P9058) or The revenue code is 382 with a HCPCS code other than whole blood P9010, P9051, P9054, and P9056). RTP
84 Claim lacks required primary code Certain claims are returned to the provider if a specified add-on code is submitted without a code for a required primary procedure on the same date of service (edit 84). Add-on codes 33225, 90785, 90833, 90836 or 90838 are submitted without one of the required primary codes on the same day. RTP
86 Manifestation code not allowed as principal diagnosis A diagnosis code considered to be a manifestation code from the Medicare Code Editor (MCE) manifestation diagnosis list is reported as the principal diagnosis code on a hospice bill type claim 81X, 82X. RTP
92 Device-dependent procedure reported without device code A device-dependent procedure is reported without a device code. RTP

For more information on the index, check out CMS.

Lisa Marks, VP of HIM Services


Posted by Samantha Serfass on November 12, 2019 in Blog, News


Wearable technology is making big impacts in the Telehealth field.  Wearable technology collects patient data outside of the hospital and clinic walls and report back to care providers information based on measure data, instead of human memory & recall.  

Departments throughout hospital systems see advantages to wearable technology, specifically chronic disease and geriatric health management. Heart attack and heart failure patients are also a targeted demographic for wearable technology.

With the adoption of Current Procedural Terminology, CPT, codes for Remote Patient Monitoring (RPM) and Chronic Care Management (CCM) by CMS, healthcare providers are more able to be reimbursed by Medicare for implementing patient wearables. The reimburse model can not only pay for a wearable, but it can also show an ROI addressing high risk and costly patients within the healthcare system.

Engaged patients are healthier patients and they reduce the cost needed to support a population within an ACO. By combining wearable technology and patient engagement, health systems are able to reduce the risk in a risk adjustment payment model all while collecting important clinical data.

Collecting a patients clinical data outside hospital walls can help increase patient engagement through text messages and secure messaging alerting the patient to their specific health information.  Patient engagement strategies can incorporate displaying personalized care plans on smart phones, remind patient to take medications, perform prescribed activities, measure vitals, etc. The wearable solution should be integrated with the healthcare organizations patient engagement solution.

It’s important to collect the data over a period of time to ensure patients are staying on track with their care plan. The type, time and frequency of messaging with a patient can be automated and crafted for the specific wearable and targeted outcome – allowing patients to receive critical information in real time.

There are many types of wearables on the market, what type and how the wearable is worn can dramatically impact the quality of the data collected by the wearable. Below is an example of the different types of wearables, their functionality and where they are worn. 

Source: Piwek L, Ellis DA, Andrews S, Joinson A. The rise of consumer health wearables: promises and barriers. PLoS Med. 2016;13(2):e1001953.

There are several factors to consider when looking at a wearable solution; quality, usability, comfort, durability and arguably most important – accuracy. Not all wearables require FDA approval, some devices can even report measurements with a significant deviation from the true reading so it’s important to research the options extensively.

There are many things to consider when entering into a patient care model that extends into the patients home. The patient experience can be greatly improved via nursing and informatics’. Nursing can make sure upon discharge that the patient knows how important the data is, how to wear the devices, and who to call with questions, this should be considered the basics. 

Home Health services can provide follow up support ensuring the patient knows how to use the devices and is collecting accurate data, this can be a key part to reducing readmission rates.

At Excite Health Partners we can help you identify areas of opportunity to utilize wearable solutions.  We start with a phased approach to ease your health system into properly using wearable technology and collecting the data.

 We help identify solutions specific to each facility needs. Below is a common phased approach we use:  

  1. Using existing hardware (such as iPhones) and automated reminders  
  2. Addition of one wearable device and integration into one EHR
  3. Secure messaging to improve patient engagement
  4. Adding additional EHR integration and additional Wearables

Through the phased approach, organizations are able to ease into wearable technology and its benefits and a low cost with immediate results. We have the experience and expertise to identify the best fit solution for your organization while increasing patient engagement, quality outcomes, and reducing costs with a healthier patient population.

Todd Klein, CIO VP of EHR Services & Digital Solutions