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
DME Protocols – WWS https://wws.wonderws.com Empowering HME Providers Nationwide Wed, 16 May 2018 16:20:24 +0000 en-US hourly 1 https://wordpress.org/?v=6.9.4 Incorporating DME Into Treatment Protocols: Can This Transform Your Practice? https://wws.wonderws.com/2018/05/16/incorporating-dme-treatment-protocols/ https://wws.wonderws.com/2018/05/16/incorporating-dme-treatment-protocols/#respond Wed, 16 May 2018 16:20:24 +0000 http://www.wonderws.com/?p=7198
How to incorporate durable medical equipment (DME) into the equation?

While streamlining care is designed to improve patient outcomes and reduce overall health care costs, there is also an opportunity to increase practice revenue. Incorporating durable medical equipment (DME) into our treatment protocols for conditions of biomechanical etiology requiring stabilization may be beneficial in several respects.

Durable medical equipment provides readily available modalities when the patient presents. Utilizing DME enables you to get immediate patient feedback on the comfort and benefits of the given modality. Additionally, the availability and demonstration of DME products in the office can help facilitate both patient adherence and patient satisfaction.

These are the conditions that offer the greatest benefit of integrating a streamlined approach to care. If you recommend a prefabricated ankle-foot orthotic (AFO) as a part of the treatment protocol, there should be a direct correlation between the incidence of the condition and the number of DME items dispensed.

After identifying the most common diagnoses you see, determine the DME items to use with each. Create treatment protocols for each visit and vary these by severity. Create protocols for follow-up visits depending on how well the condition is improving.

The DME recommendations should be based on the concept of providing items that are therapeutically appropriate and the least expensive. Recognize that some conditions are best treated by an orthotics who has more experience in the range of customized orthoses and related products.

There are a number of factors to consider when selecting DME products. For ease of ordering, seek out products from a few distributors as possible in order to obtain the best pricing and streamline ordering and bill paying. Look for distributors to match manufacturer direct pricing.

Favor products from companies that support podiatry through the American Podiatric Medical Association (APMA), American Academy of Podiatric Practice Management (AAPPM), American Academy of Podiatric Sports Medicine (AAPSM) and young practitioners associations. Work with distributors that offer ready technical assistance.

Maximizing Efficiency With DME Protocols

For every patient, the front office should determine, in advance of the doctor seeing the patient, if the insurance plan covers DME and whether the podiatrist is allowed to provide the specific DME product. If the plan includes coverage and the podiatrist can dispense it, determine whether the plan has an annual deductible or lifetime coverage amount. If the patient has coverage and the podiatrist is not allowing to dispense the product, the patient needs a referral.

The medical assistant can do the initial intake. Based on an understanding of treatment protocols, the assistant can then make the DME products readily available for the physician to recommend. The physician should review the initial intake and perform an evaluation. The physician describes the plan of treatment and therapeutic objectives of DME. The medical assistant reviews the application of DME with the patient.

When a patient’s therapeutic needs are beyond the ability of the provider make a referral for consultation or further treatment.

Schedule a free demo http://localhost/main-site-update/live-demo/ for more information.
]]>
https://wws.wonderws.com/2018/05/16/incorporating-dme-treatment-protocols/feed/ 0