1.ICD-10 codes have a different structure
and composition (syntax) than ICD-9 codes.

2.The overlap between ICD-9 and ICD-10
codes that make it impossible to distinguish a specific code set (ICD-9 or
ICD-10) on inspection.

3.Determining the type of code set depends
on the data of service (professional claims) or discharge date (institutional
claims)

4.The
ability to access transaction history as ICD-10 codes become mixed with ICD-9
codes must be accommodated for the immediate period before and after the
implementation date; and also to support mandated audit periods of up to 10
years.

5.Most organizations have a number of systems
to remediate and some databases will require remediation in advance of the
compliance deadline.

What should your Database
Remediation Strategy include?

1.A
means to use data type and/or code attributes to facilitate logic for searching
and matching single codes and ranges of codes.

2.Use
of a code indicator or prefix to discretely distinguish between I- 9 and I-10
codes.

3. Include
attributes to facilitate accurate identification of professional vs. institutional
processing logic and to provide the fidelity necessary for analytic reporting.

5. A
means to track remediation strategy used across multiple systems and scenarios with
all applications using the same code set to ensure enterprise-wide consistency,
compatibility and auditability. In addition, consider an approach for building
a brand new data structure containing ICD Code attributes vs. extending
existing structures.

Hopefully
the above post provides some ideas for developing a database remediation
strategy.Stay tuned for a future post
on topics related to ICD-10 logic remediation strategies.

You would design the "specifications" for the database, including the data to be included, the kinds of information the system should produce, and the activities you want to accomplish, such as mailing lists and monthly reports. An outside contractor can then take your requirements and develop a database.create dashboard for oracle