i2iTracks and ICD-10

i2i Systems has worked diligently to make the transition from ICD-9 to ICD-10 as easy as possible. Since i2i data is

based on the interface from the EHR, we have modified many of our interfaces to include the new ICD-10 data as it

becomes available in the EHR. These interfaces include those to NextGen and GE Centricity for example.*

Our ICD library stores both ICD-9 AND ICD-10 codes, where you can view number of occurrences, number of

patients, and drill down to the patient level to see what patients were assigned a specified code. ICD-9 and ICD-10

codes can also be viewed for an individual patient when looking at their visit history.

When it comes to analytics, reports, and dashboards, we have a built-in crosswalk that can be utilized to select

corresponding ICD-9/ICD-10 codes.

Below is an example of the Diagnosis Code Selection, showing the equivalent ICD-9 code for a selected ICD-10

code:

The following i2iTracks features allow you to select ICD-9 and/or ICD-10 codes:

• Patient Search

• Linked Visit Types

• Report Mappings

• iPHA Reports

• iPHA Dashboards

• PopIQ Connector

• Patient Referrals

• Patient Problems

The following i2iTracks features allow you to view ICD-9 and/or ICD-10 codes:

• External Data Diagnostics Tool

• Patient Visit Summaries

• External Problem List

• Patient Information

• Patient Visit History

Built-in crosswalk between

ICD-9 and ICD-10 codes

Since many of the i2iTracks functionality requires mapping to ICD codes, this mapping will need to be updated to

reflect both code sets – ICD-9 AND ICD-10. i2i Systems is currently working on an automated way to complete the

mapping based on the crosswalk, so that the equivalent codes do not have to be entered manually. This

automation tool will be available at the end September, 2015. Watch for more information coming soon.

If you desire to complete this task manually, use this checklist as your guide to find the screens in i2iTracks to

update your existing mappings.

To see what ICD-9 codes have been mapped to Linked Visit Types, Problems and Reports, you can use the External

Data Diagnostics Tool and review the associated mappings for the commonly used ICD-9 codes. To access: Go to

File > Tools > External Data Diagnostics, and click the ICDs tab.

In the above example, you can see that ICD-9 code 402.00 was mapped to iPHA elements, Linked Visit Type of Dx

HTN Visit, PopIQ and UDS reports. Note: This mapping column does not include Patient Searches.

You can follow the checklist below to review i2iTracks functions that may include ICD-9 mappings, and update

according to the instructions.

i2iTracks function Description of task to be completed Completed

date

Linked Visit Types

(Setup > Linked Visit

Types)

Review your library of Linked Visit Types. For each

Linked Visit Type that is mapped to ICD-9 codes you will

need to map to equivalent ICD-10 codes.

Problems (Setup

> Patient Profile Items

> Problems)

Do you update the i2iTracks Problem list based on ICD

codes? If so, review your Problems library. For each

problem that is mapped to ICD-9 codes you will need to

map to equivalent ICD-10 codes. Note: It is a good

practice to also review your External Problems tab to

assure correct and up-to-date mapping of your EHR

problems. Some sites only map to the EHR problems

and do not assign problems based on ICD codes.

Patient Search

(Patients > Search for

Patients)

Any Patient Search that uses an ICD-9 code as a visit

history filter will need to be reviewed so that it included

both ICD-9 and ICD-10 codes. Start by reviewing Patient

Searches that you know are being used on a regular

basis and update the ICD codes. For remaining Patient

Searches, a good practice would be to review the

desired Patient Search prior to running the search and

do the updates as needed. (Remember, the automation

tool will identify all Patient Searches mapped to ICD-9

codes and update with the ICD-10s based on the

crosswalk)

Population Analytics

Data Elements

(Setup > Printing &

Reporting > Population

Analytics > Reports >

Custom Data Elements)

All Custom Data Elements used in iPHA reports and

dashboards that are mapped to ICD-9 codes will need to

be mapped to equivalent ICD-10 codes. Start by

reviewing the categories that you defined. Review your

categories where you store problems or

visits/encounters. Review the mappings and update as

needed. (Remember, the automation tool will identify all

Custom Data Elements mapped to ICD-9 codes and

update with the ICD-10s based on the crosswalk)

Population Analytics

Report Mappings

(Setup > Printing &

Reporting > Population

Analytics > Reports)

Review your iPHA reports that have been imported.

Highlight the imported report and click Map Report.

Review the mappings to look for items mapped to ICD-9

codes. Add mappings for the equivalent ICD-10 codes.

Population Analytics

Dashboard Mappings

(Setup > Printing &

Reporting > Population

Analytics >

Dashboards)

Review your iPHA dashbaords that have been imported.

Highlight the imported dashboard and click Map

Dashboard. Review the mappings to look for items

mapped to ICD-9 codes. Add mappings for the

equivalent ICD-10 codes.

Standard Reports

(Setup > Printing &

Reporting > )

All standard reports that are currently mapped to ICD-9

codes will need to be re-mapped to include mappings

for the equivalent ICD-10 codes. This included UDS,

Meaningful Use, IHS reports, etc.) It is not necessary to

re-map those reports that you do not use in i2iTracks.

*Some interfaces were created to build the Diagnosis library as codes are assigned to visits. In that instance, you

will not start seeing the ICD-10 codes until they are being assigned to patient charges.