Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the redux-framework domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/linkenwd/wws.wonderws.com/wp-includes/functions.php on line 6131

Deprecated: Optional parameter $attach_id declared before required parameter $height is implicitly treated as a required parameter in /home/linkenwd/wws.wonderws.com/wp-content/plugins/case-theme-core/inc/helpers/resize-image.php on line 23

Deprecated: Optional parameter $img_url declared before required parameter $height is implicitly treated as a required parameter in /home/linkenwd/wws.wonderws.com/wp-content/plugins/case-theme-core/inc/helpers/resize-image.php on line 23

Deprecated: Return type of YITH_WCWL_Wishlist::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/linkenwd/wws.wonderws.com/wp-content/plugins/yith-woocommerce-wishlist/includes/class-yith-wcwl-wishlist.php on line 865

Deprecated: Return type of YITH_WCWL_Wishlist::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/linkenwd/wws.wonderws.com/wp-content/plugins/yith-woocommerce-wishlist/includes/class-yith-wcwl-wishlist.php on line 882

Deprecated: Return type of YITH_WCWL_Wishlist::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/linkenwd/wws.wonderws.com/wp-content/plugins/yith-woocommerce-wishlist/includes/class-yith-wcwl-wishlist.php on line 831

Deprecated: Return type of YITH_WCWL_Wishlist::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/linkenwd/wws.wonderws.com/wp-content/plugins/yith-woocommerce-wishlist/includes/class-yith-wcwl-wishlist.php on line 847

Deprecated: Return type of YITH_WCWL_Wishlist_Item::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/linkenwd/wws.wonderws.com/wp-content/plugins/yith-woocommerce-wishlist/includes/class-yith-wcwl-wishlist-item.php on line 651

Deprecated: Return type of YITH_WCWL_Wishlist_Item::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/linkenwd/wws.wonderws.com/wp-content/plugins/yith-woocommerce-wishlist/includes/class-yith-wcwl-wishlist-item.php on line 668

Deprecated: Return type of YITH_WCWL_Wishlist_Item::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/linkenwd/wws.wonderws.com/wp-content/plugins/yith-woocommerce-wishlist/includes/class-yith-wcwl-wishlist-item.php on line 617

Deprecated: Return type of YITH_WCWL_Wishlist_Item::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/linkenwd/wws.wonderws.com/wp-content/plugins/yith-woocommerce-wishlist/includes/class-yith-wcwl-wishlist-item.php on line 633

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ninja-forms domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/linkenwd/wws.wonderws.com/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the mailchimp-for-wp domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/linkenwd/wws.wonderws.com/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the redux-framework domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/linkenwd/wws.wonderws.com/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the consultio domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/linkenwd/wws.wonderws.com/wp-includes/functions.php on line 6131

Deprecated: Function Redux::getOption is deprecated since version Redux 4.3! Use Redux::get_option( $opt_name, $key, $default ) instead. in /home/linkenwd/wws.wonderws.com/wp-includes/functions.php on line 6131

Warning: Cannot modify header information - headers already sent by (output started at /home/linkenwd/wws.wonderws.com/wp-includes/functions.php:6131) in /home/linkenwd/wws.wonderws.com/wp-includes/feed-rss2.php on line 8
Medical Coding and Documentation – WWS https://wws.wonderws.com Empowering HME Providers Nationwide Mon, 15 Jun 2015 13:15:07 +0000 en-US hourly 1 https://wordpress.org/?v=6.9.4 ICD – 10 CM Medical Coding and Documentation for Myocardial Infractions https://wws.wonderws.com/2015/06/15/icd-10-cm-medical-coding-documentation-myocardial-infractions/ https://wws.wonderws.com/2015/06/15/icd-10-cm-medical-coding-documentation-myocardial-infractions/#respond Mon, 15 Jun 2015 13:15:07 +0000 http://www.wonderws.com/?p=5828 A myocardial infarction (MI) or acute myocardial infarction (AMI), commonly referred to as a heart attack, occurs when one or more coronary arteries that carry blood to the heart are blocked. Symptoms include chest pain, pressure, or tightness, which may move into the jaw, neck, throat, or arm(s). Patients also may experience shortness of breath, excessive sweating, and/or indigestion or burning in the throat and/or chest. MI is a medical emergency. Left untreated, it can cause permanent harm to the heart muscle, brain damage, and death within a short time.

MI

MI is part of the leading cause of death in the United States: Approximately 450,000 people die from coronary disease per year, according to the America Heart Association.

The upcoming ICD-10 implementation will bring significant changes in medical coding for myocardial infarctions. The implementation will have an impact on how medical billing and Coding companies as well as Cardiology Coding in Medical offices approach their coding. The changing definition of “initial” and “subsequent” as well as “duration” is crucial among them. Let’s take a detailed look into ICD-10 coding and documentation for MI.

To code an MI in ICD-10, you will need to know:

  • The location of the infarct (anterior, inferior, or other);
  • Initial or subsequent episode; and,
  • STEMI or NSTEMI.

Codes for the STEMI are also based on the coronary artery involved:

  • Anterior MI (I21.0 ST elevation (STEMI) myocardial infarction of anterior wall) is either left main, left anterior descending, or other coronary artery.
  • Inferior MI (I21.1 ST elevation (STEMI) myocardial infarction of inferior wall) breaks down to right coronary or other coronary artery.
  • STEMI of other sites involve infarct of the left circumflex artery or other sites.

ICD-10 Codes:

Apart from the initial and subsequent episode and MI type, you should also consider the location of the infarct (anterior, inferior or other) while choosing the relevant ICD-10-CM codes. The ICD-10-CM codes for MI are as follows:

I21.01     ST elevation (STEMI) myocardial infarction involving the left main coronary artery

I21.02     ST elevation (STEMI) myocardial infarction involving the left anterior descending coronary artery

I21.09     ST elevation (STEMI) myocardial infarction involving other coronary artery of anterior wall

I21.11     ST elevation (STEMI) myocardial infarction involving right coronary artery

I21.19     ST elevation (STEMI) myocardial infarction involving other coronary artery of inferior wall

I21.21     ST elevation (STEMI) myocardial infarction involving left circumflex coronary artery

I21.29     ST elevation (STEMI) myocardial infarction involving other sites

I21.3      ST elevation (STEMI) myocardial infarction of unspecified site

I21.4      Non-ST elevation (NSTEMI) myocardial infarction

I22.0      Subsequent ST elevation (STEMI) myocardial infarction of anterior wall

I22.1      Subsequent ST elevation (STEMI) myocardial infarction of inferior wall

I22.2      Subsequent non-ST elevation (NSTEMI) myocardial infarction

I22.8      Subsequent ST elevation (STEMI) myocardial infarction of other sites

I22.9      Subsequent ST elevation (STEMI) myocardial infarction of unspecified site

I25.2      Old myocardial infarction

Documentation for MI:

As you know, ICD-10-CM will increase the level of detail required for MI. Here are the details to be included in your documentation.

  • Identify and document the number of weeks since the AMI
  • Indicate subsequent MI appropriately
  • Document when a NSTEMI evolves into a STEMI and when a STEMI converts into a NSTEMI as a result of thrombolytic therapy
  • If the patient is still receiving care for the MI, then you should use the term ‘aftercare’ and if the patient no longer receives care for the MI, use the term ‘old’ or ‘healed’ MI
  • Document the exact site (for example, left main coronary)

 

]]> https://wws.wonderws.com/2015/06/15/icd-10-cm-medical-coding-documentation-myocardial-infractions/feed/ 0