<?xml version="1.0" encoding="utf-8"?>
  <rss version="2.0"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
    xmlns:admin="http://webns.net/mvcb/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:content="http://purl.org/rss/1.0/modules/content/">

    <title>PPS Plus Software News
    </title>
    <link>http://www.ppsplus.com</link>
    <description></description>
    <dc:language>en</dc:language>
    <dc:creator>jacqui@ppsplus.com</dc:creator>
    <dc:rights>Copyright 2010</dc:rights>
    <dc:date>2010-03-10T21:09:17+00:00</dc:date>
    <admin:generatorAgent rdf:resource="http://expressionengine.com/" />

    <channel>
    
      

    <item>
      <title>Coding Tip of the Month &#45; March 2010</title>
      <link>http://ppsplus.com/news/coding-tip-of-the-month-march-2010/</link>
      <guid>/news/coding-tip-of-the-month-march-2010/</guid>
      <description>

        <![CDATA[ 
          <p>Coding Complicated Surgical Wounds</p>
        ]]>

      </description>
      <dc:subject>Coding, Education</dc:subject>
      <dc:date>2010-03-10T21:09:17+00:00</dc:date>
    </item>


    <item>
      <title>Version 6.0.0.25 Release Notes</title>
      <link>http://ppsplus.com/news/version-60025-release-notes/</link>
      <guid>/news/version-60025-release-notes/</guid>
      <description>

        <![CDATA[ 
          <h3>by Brad Huffman<br />Software Development / IT Director</h3>
<p>Since the release of version 6 of PPS Plus - Home Health Edition, the technical team has been hard at work handling installations, support requests and customer suggestions. If you've had an opportunity to speak with one of our technical team members, I hope that the experience more than met your expectations. We strive to provide our customers with the highest level of support to go along with, what we consider to be, the premier tool for clinical data analysis and reporting in the home health industry.</p>
<p>The release of version 6 was a significant milestone, in that it was a return to the drawing board for us. We looked at where the application was and where we wanted it to go. Version 6 is the first step in that direction. Look out for some exciting new features and services from PPS Plus in the future.</p>
<p>With that out of the way, if you're reading this, you're probably wondering what's new in the application. This list isn't all-inclusive, but it does cover the major additions, fixes and improvements to the application since its initial release in December.&nbsp; If you've been waiting on or looking for a specific feature or bit of
functionality that you don't see below, please contact your account
manager or a member of our technical staff (<a target="_blank" href="http://ppsplus.com/about-us/our-team/">find our contact info here</a>). We always welcome your suggestions and critiques.</p>
<p>&nbsp;- Brad</p>
<div style="background-color:#eaf1fa;">
<p><b>User Interface</b><br />&bull;	<i>Added</i>:  Admit Patient screen lets you search existing patients (inactive).<br />&bull;	<i>Added</i>:  Re-Admit/Discharge Patient button to Tasks in the Patients context area.<br />&bull;	<i>Added</i>:  Filtering by name functionality was added to the patient filters area.<br />&bull;	<i>Fixed</i>:   Patient and Assessment grids should refresh appropriately after certain events occur (deleting, importing, modifying data, etc.).</p>
<p><b>Import</b><br />&bull;	<i>Added</i>:    The Update Existing Assessments that existed in previous versions of the program has been added back.<br />&bull;	<i>Updated</i>: Import screen now displays three tabs after an import is finished processing. Only the necessary tabs will be displayed after an import. (Ex. If all records were successfully imported, only the imported tab will be displayed.) </p>
<p style="padding-left: 30px;">o	The Imported tab lists patients/assessments that were successfully imported during the last import operation. <br />o	The Skipped tab contains records that were skipped because they did not match certain criteria or the user did not have the Update Existing Assessments option selected. <br />o	The Errors tab indicates records that were not imported because they contained errors, or an error occurred during the import process.</p>
<p>&bull;	<i>Updated</i>: Several updates and corrections have been made to the import system to reflect changes in the various data sources that the program imports data from.</p>
<p><b>Reports</b><br />&bull;	<i>Updated</i>:  The report header on patient reports (Assessment Detail, OASIS Analysis, etc.) shows case mix and reimbursement information.<br />&bull;	<i>Added</i>:     Report header added to all pages of Assessment Detail report.<br />&bull;	<i>Added</i>:     Items left blank on an assessment should now show up on the Assessment Detail report.<br />&bull;	<i>Added</i>:     Process Measures section was added to the Assessment Detail report.<br />&bull;	<i>Fixed</i>:      Service Dimension now appearing on the Assessment Detail report.<br />&bull;	<i>Fixed</i>:      Manifestation codes being improperly flagged as not having a valid etiology code in the OASIS Analysis report.<br />&bull;	<i>Fixed</i>:      Report header was not displaying anything on second and subsequent pages on OASIS Analysis report.<br />&bull;	<i>Updated</i>:  Various updates and additions to the OASIS Analysis.<br />&bull;	<i>Added</i>:     Additional filters have been added to various reports.</p>
</div>
        ]]>

      </description>
      <dc:subject>Software</dc:subject>
      <dc:date>2010-03-10T19:15:34+00:00</dc:date>
    </item>


    <item>
      <title>M2250d: Depression Interventions on Plan of Care</title>
      <link>http://ppsplus.com/news/m2250d-depression-interventions-on-plan-of-care/</link>
      <guid>/news/m2250d-depression-interventions-on-plan-of-care/</guid>
      <description>

        <![CDATA[ 
          <h3>by Ann Giles, RN, BSN, HCS-D, COS-C</h3>
<p><br />In my last blog post I discussed some strategies for answering M2250 correctly. I feel as if line item d needs special attention, as it is often scored incorrectly. <br /><br />The latest set of Q&amp;A's released on January 20 clarifies that "NA" is only appropriate if the patient has NO diagnosis of depression AND the clinician completed an assessment that indicated that the patient has no symptoms of depression. If the patient DOES have a diagnosis of depression, only responses "no" and "yes" are appropriate. If a depression assessment was NOT completed, only responses "no" and "yes" are appropriate. Is it acceptable to have a diagnosis of depression, not be symptomatic and have interventions on the plan of care related to this? Absolutely! Even if your patient does not have a diagnosis of depression (or if he/she does have the diagnosis and is not symptomatic) you can implement depression interventions for monitoring. Again, I cannot emphasize enough the importance of referring to the OASIS manual and OASIS Q&amp;A's for guidance on these OASIS items.</p>
        ]]>

      </description>
      <dc:subject>Coding, Education</dc:subject>
      <dc:date>2010-03-05T16:01:39+00:00</dc:date>
    </item>


    <item>
      <title>Is Your Agency Going to Receive a Slice of the Pie?</title>
      <link>http://ppsplus.com/news/is-your-agency-going-to-receive-a-slice-of-the-pie/</link>
      <guid>/news/is-your-agency-going-to-receive-a-slice-of-the-pie/</guid>
      <description>

        <![CDATA[ 
          <h3>by Jennifer Warfield, RN, BSN, HCS-D, COS-C<br /><br /></h3>
<p>If you have been around home health at all in the past three to four years, there is no doubt that you have heard about P4P (pay for performance). P4P has been in place in other areas of patient care for a couple of years and now it is homecare's time to be rewarded for providing outstanding care to its patients. What has been proposed is that bonus payments be awarded to HHA's (in their respective states) that ranked among the highest performance level in certain patient outcomes.</p>
<p>The HHP4P demonstration was done from January 2008 through December 2009 in seven states: Illinois, Connecticut, Massachusetts, Georgia, Alabama, Tennessee and California. Agencies choosing to participate in the demonstration did so on a voluntary basis. Incentives were made available based on improvement in patient status and actual monetary savings to Medicare.</p>
<p>The results: All participating agencies received their regular Medicare payments without any reductions. Additionally, incentive payments (a total of $15.4 million), is currently being awarded to HHA's that ranked in their respective state's highest performance level or highest level of improvement in patient outcomes. The $15.4 million was based on actual savings to the Medicare program because of better patient outcomes for 2008 only. Additional money will probably be available for outcomes in 2009 also.</p>
<p>What criteria were used in deciding on disbursements? Outcomes from OBQI data were used to evaluate this data. Since this data is automatically submitted for agencies that already submit OASIS data, there was no additional work required for participating agencies. These seven outcome measures were used in the demonstration:<br /><br />1. Incidence of Acute Care Hospitalization<br />2. Incidence of Any Emergent Care<br />3. Improvement in Bathing<br />4. Improvement in Ambulation/Locomotion<br />5. Improvement in Transferring<br />6. Improvement in Status of Surgical Wounds<br />7. Improvement in Management of Oral Medications<br /><br />The plan to go forward is currently being formulated whereby P4P will be instituted nationwide for all Medicare HHAs. So if you have wondered why CMS "makes such a big deal" about evaluating your agency's outcomes, wonder no more. $15.4 million looks like a big deal to me.<br /><br />For more information on the demonstration, click on <a href="http://www.hhp4p.info">www.hhp4p.info</a>. </p>
        ]]>

      </description>
      <dc:subject>Coding, Education</dc:subject>
      <dc:date>2010-03-01T16:05:05+00:00</dc:date>
    </item>


    <item>
      <title>Confusion with M2250</title>
      <link>http://ppsplus.com/news/confusion-with-m2250/</link>
      <guid>/news/confusion-with-m2250/</guid>
      <description>

        <![CDATA[ 
          <h3>by Ann Giles, RN, BSN, HCS-D, COS-C</h3>
<p><br />One of the new OASIS-C items that is frequently answered incorrectly is M2250. One of the most helpful tips I have heard is to start on the right and work your way to the left when answering each of the line items in this question.  The common mistake is to answer "no" when the appropriate response is "na."  Let's take a couple of line items to use as examples:</p>
<p><br /> <b>Let's first look at line "b."</b>  If you start on the right, you will see the first option is that the "patient is not diabetic or is bilateral amputee."  The next column over is response "yes," indicating that the patient is diabetic and the physician-ordered plan of care does include interventions for diabetic foot care and monitoring for skin lesions.  And the last option would be "no," indicating that the patient is diabetic and the physician ordered plan of care does not include diabetic foot care. The common mistake is to start on the left. Clinicians see response "no" and select it for non-diabetic patients, knowing that the plan of care does not include the above mentioned interventions, when the more appropriate response is "na."  Misunderstanding the responses in the item can affect process measure data.  </p>
<p><br /><b>Let's take a look at line item "f."</b>  A common mistake is to answer "no" for patients that are not at risk for developing pressure ulcers.  If you start on the right, the chances of answering incorrectly are minimized.  You will find that the first response on the left is that the patient is not assessed to be at risk for pressure ulcers. This is a much more appropriate response if a screening was completed and no risk was found. You then move on to "yes" and "no," indicating that the physician-ordered plan of care includes or does not include prevention interventions.</p>
<p>Again, misunderstanding the responses in the item can affect process measure data.  I cannot emphasize enough the importance of referring to the OASIS manual and OASIS Q&amp;A's for guidance on these OASIS items.</p>
        ]]>

      </description>
      <dc:subject>Coding, Education</dc:subject>
      <dc:date>2010-02-19T23:02:46+00:00</dc:date>
    </item>


    <item>
      <title>Best Practices and Service Excellence In Action</title>
      <link>http://ppsplus.com/news/best-practices-and-service-excellence-in-action-1/</link>
      <guid>/news/best-practices-and-service-excellence-in-action-1/</guid>
      <description>

        <![CDATA[ 
          <h3>by Lois Kinsella, RN, BSN, MS, HCS-D<br /></h3>
<p>Through many years of practicing the profession of nursing, I have learned that one of the best ways to teach is through the process of story telling. So here is our story. The saga began in December of 2008. My husband suffers for frequent gout attacks primarily in joint of his left great toe bunion. He decided he had had enough and wanted to get the bunion fixed, so he went to a local podiatrist who determined the circulation to his left foot was not the greatest. There was no palpable pedal pulse. My husband was referred to a vascular surgeon for further evaluation.</p>
<p><br />In early 2009, the vascular examination was done, with ultra sound exams of both legs: the left leg had a blocked popliteal aneurysm and the right leg had an open popliteal aneurysm about 4 cm long.  Since his body created co-lateral circulation on the left, the doctor focused on the right aneurysm for further treatment: a fem-pop (femoral popliteal) bypass was planned for early August. During the pre-operative assessments and evaluations, a stress test was performed. Results showed an ejection fraction (heart function test) of 35% so further tests were ordered. An angiogram done in August 2009 revealed one coronary artery that was 100% blocked and one that was 95% blocked. With no acute cardiac symptoms whatsoever, it was hard to believe that my husband was scheduled for open heart surgery on September 1, 2009 instead of a bunionectomy!</p>
<p><br />My husband has been treated for high blood pressure for several years and has prided himself in the fact that he only had to take two medications a day, both for hypertension. After the surgery and the four day hospital stay, my husband came home on Friday to begin the healing and recovery process with all 21 of his new medications!</p>
<p><br />Having been a home health nurse for several years, I thought I could care for my husband until I ran into the biggest brick wall I had ever faced. He absolutely refused to take his medications. He vehemently said, "I don't need all these pills and I'm not going to take them."  In fact, I found pills in his pants pockets and on the floor. I was very anxious for the home health nurse, Mike, to arrive on Sunday. Maybe he could talk some sense into my husband. </p>
<p><br />At the time, I was the Agency Supervisor for the home health program that was ordered to provide nursing and therapy services. Mike arrived at our house, introduced himself and began creating a miracle. I sat quietly in the room observing, hoping to not intimidate Mike by my presence. Clearly, Mike knew exactly what he was doing and what my husband needed.</p>
<p><br />First, he listened. He listened to the frustration my husband was feeling about his health decline and about the medication extravaganza. Mike did not make any judgment statements, he just listened.</p>
<p><br />Then he began to teach: each medication on the list, what its function was and why it was important for the healing process. He used terms such as "pipes," "garden hose," "engine," "spark plugs," "roto rooter" to name a few. I sat in amazement as I witnessed the transformation in my husband, watching him and listening to him, as he verbalized total understanding of the importance of each medication. Mike taught him using language and terms he could understand. Since that Sunday, my husband has been very diligent about taking each medication that has been ordered. I have celebrated with him each time one of the medications is discontinued and encouraged him if another new medication is ordered.</p>
<p><br />The best practices care plan for oral medication management includes providing a comprehensive medication review at the home health start of care: review the proper administration, side effects, contraindications, food and drug interactions, and adverse reactions; assess the client's ability to self-medicate and compliance with medication use; instruct on correct medication administration including information about the drug, time/frequency, dose, route and what to do if a dose is missed, and storage issues; instruct on signs and symptoms that require immediate attention; instruct on the importance of using one pharmacy and instruct on the importance of taking an updated medication list to each doctor's appointment. Our addition to the best practice care plan for oral medication management:</p>
<p><br />Listen to the concerns and fears of the client/patient and family in regard to their medications. Teach in terms the client/patient and family can understand, don't read from a drug book or expect understanding from pharmacy printed materials, though these can be used to guide your teaching. Teach using real life examples.</p>
<p>As Brian Parsley wrote in the Newswire article last month, "You can make a difference," and Mike certainly made a difference in my husband's healing journey. The use of best practices and attending to the real life needs of clients/patients and families fosters the creation of a world class service organization.</p>
<p><br />P.S. My husband's blood pressure is not responding to the medications very well, so a renal ultrasound was ordered. Guess what? Yep, a blocked renal artery. Getting ready for a stent!</p>
<p>Copyright&copy; 2010 LK Publications and Consulting Services. All rights reserved.</p>
<p><i>Lois Kinsella, a diploma nursing graduate and forty-year veteran of the nursing profession, has extensive experience in long term care program development. After graduating from the University of Wisconsin School of Nursing, Lois developed Cedar Acres Adult Day Center in 1987, one of the original sites in the Robert Wood Johnson Dementia Care and Respite Services Program. A pioneer in Alzheimer's adult daycare, Lois provided leadership as President of the Wisconsin Adult Daycare Associaton for several years and had many opportunities to speak at state and national conferences. Lois is the author of "The Hundred Mile Road," a parable about the acceptance of hospice care. Lois developed and managed Alzheimer's assisted living facilities, an Alzheimer's special care unit in a nursing home, hospice programs, and most recently assisted with the development of ABLE Home Health in Rockford, Illinois, a HomeCare Elite top 500 agency. As Agency Supervisor, Lois provided leadership and guidance for the staff, always emphasixing service excellence through the use of best practices to produce quality outcomes. Currently, Lois is an independent contractor providing forms development, coding and data entry services for home health and other long term care programs. </i></p>
<p><i>To learn more about Lois Kinsella and LK Publications and Consulting Services, email <a target="_blank" href="mailto:l.kinsella@comcast.net">l.kinsella@comcast.net</a>.</i></p>
<p>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="ProgId" content="Word.Document" />
<meta name="Generator" content="Microsoft Word 12" />
<meta name="Originator" content="Microsoft Word 12" />
<link rel="File-List" href="file:///C:\DOCUME~1\leslie.c\LOCALS~1\Temp\msohtmlclip1\01\clip_filelist.xml" />
<link rel="themeData" href="file:///C:\DOCUME~1\leslie.c\LOCALS~1\Temp\msohtmlclip1\01\clip_themedata.thmx" />
<link rel="colorSchemeMapping" href="file:///C:\DOCUME~1\leslie.c\LOCALS~1\Temp\msohtmlclip1\01\clip_colorschememapping.xml" />
</p>
<!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:TrackMoves />
  <w:TrackFormatting />
  <w:PunctuationKerning />
  <w:ValidateAgainstSchemas />
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
  <w:DoNotPromoteQF />
  <w:LidThemeOther>EN-US</w:LidThemeOther>
  <w:LidThemeAsian>X-NONE</w:LidThemeAsian>
  <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
  <w:Compatibility>
   <w:BreakWrappedTables />
   <w:SnapToGridInCell />
   <w:WrapTextWithPunct />
   <w:UseAsianBreakRules />
   <w:DontGrowAutofit />
   <w:SplitPgBreakAndParaMark />
   <w:DontVertAlignCellWithSp />
   <w:DontBreakConstrainedForcedTables />
   <w:DontVertAlignInTxbx />
   <w:Word11KerningPairs />
   <w:CachedColBalance />
  </w:Compatibility>
  <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
  <m:mathPr>
   <m:mathFont m:val="Cambria Math" />
   <m:brkBin m:val="before" />
   <m:brkBinSub m:val="&#45;-" />
   <m:smallFrac m:val="off" />
   <m:dispDef />
   <m:lMargin m:val="0" />
   <m:rMargin m:val="0" />
   <m:defJc m:val="centerGroup" />
   <m:wrapIndent m:val="1440" />
   <m:intLim m:val="subSup" />
   <m:naryLim m:val="undOvr" />
  </m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"
  DefSemiHidden="true" DefQFormat="false" DefPriority="99"
  LatentStyleCount="267">
  <w:LsdException Locked="false" Priority="0" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Normal" />
  <w:LsdException Locked="false" Priority="9" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="heading 1" />
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2" />
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3" />
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4" />
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5" />
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6" />
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7" />
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8" />
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9" />
  <w:LsdException Locked="false" Priority="39" Name="toc 1" />
  <w:LsdException Locked="false" Priority="39" Name="toc 2" />
  <w:LsdException Locked="false" Priority="39" Name="toc 3" />
  <w:LsdException Locked="false" Priority="39" Name="toc 4" />
  <w:LsdException Locked="false" Priority="39" Name="toc 5" />
  <w:LsdException Locked="false" Priority="39" Name="toc 6" />
  <w:LsdException Locked="false" Priority="39" Name="toc 7" />
  <w:LsdException Locked="false" Priority="39" Name="toc 8" />
  <w:LsdException Locked="false" Priority="39" Name="toc 9" />
  <w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption" />
  <w:LsdException Locked="false" Priority="10" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Title" />
  <w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font" />
  <w:LsdException Locked="false" Priority="11" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Subtitle" />
  <w:LsdException Locked="false" Priority="22" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Strong" />
  <w:LsdException Locked="false" Priority="20" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Emphasis" />
  <w:LsdException Locked="false" Priority="59" SemiHidden="false"
   UnhideWhenUsed="false" Name="Table Grid" />
  <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text" />
  <w:LsdException Locked="false" Priority="1" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="No Spacing" />
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading" />
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List" />
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid" />
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1" />
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2" />
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1" />
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2" />
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1" />
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2" />
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3" />
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List" />
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading" />
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List" />
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid" />
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 1" />
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 1" />
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 1" />
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1" />
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1" />
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 1" />
  <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision" />
  <w:LsdException Locked="false" Priority="34" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="List Paragraph" />
  <w:LsdException Locked="false" Priority="29" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Quote" />
  <w:LsdException Locked="false" Priority="30" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Intense Quote" />
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 1" />
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1" />
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1" />
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1" />
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 1" />
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 1" />
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 1" />
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 1" />
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 2" />
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 2" />
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 2" />
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2" />
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2" />
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 2" />
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 2" />
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2" />
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2" />
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2" />
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 2" />
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 2" />
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 2" />
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 2" />
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 3" />
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 3" />
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 3" />
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3" />
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3" />
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 3" />
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 3" />
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3" />
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3" />
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3" />
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 3" />
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 3" />
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 3" />
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 3" />
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 4" />
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 4" />
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 4" />
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4" />
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4" />
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 4" />
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 4" />
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4" />
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4" />
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4" />
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 4" />
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 4" />
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 4" />
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 4" />
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 5" />
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 5" />
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 5" />
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5" />
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5" />
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 5" />
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 5" />
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5" />
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5" />
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5" />
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 5" />
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 5" />
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 5" />
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 5" />
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 6" />
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 6" />
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 6" />
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6" />
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6" />
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 6" />
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 6" />
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6" />
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6" />
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6" />
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 6" />
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 6" />
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 6" />
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 6" />
  <w:LsdException Locked="false" Priority="19" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis" />
  <w:LsdException Locked="false" Priority="21" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis" />
  <w:LsdException Locked="false" Priority="31" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference" />
  <w:LsdException Locked="false" Priority="32" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Intense Reference" />
  <w:LsdException Locked="false" Priority="33" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Book Title" />
  <w:LsdException Locked="false" Priority="37" Name="Bibliography" />
  <w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading" />
 </w:LatentStyles>
</xml><![endif]-->
<p>
<style><!--
&lt;! 
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:roman;
	mso-font-pitch:variable;
	mso-font-signature:-1610611985 1107304683 0 0 159 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	mso-fareast-font-family:"Times New Roman";}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	font-size:10.0pt;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
 &gt;
--></style>
</p>
<p><i><a target="_blank" href="http://www.youtube.com/weskillyou"></a></i></p>
        ]]>

      </description>
      <dc:subject>Featured&#45;writers</dc:subject>
      <dc:date>2010-02-17T20:00:22+00:00</dc:date>
    </item>


    <item>
      <title>Reporting Closed Stage III and Stage IV Pressure Ulcers on OASIS&#45;C</title>
      <link>http://ppsplus.com/news/reporting-closed-stage-iii-and-stage-iv-pressure-ulcers-on-oasis-c/</link>
      <guid>/news/reporting-closed-stage-iii-and-stage-iv-pressure-ulcers-on-oasis-c/</guid>
      <description>

        <![CDATA[ 
          <h3>by Ann Giles, RN, BSN, HCS-D, COS-C<br /></h3>
<p>With the implementation of OASIS-C, reporting of pressures ulcers has changed.  Today, I want to focus on the reporting of closed stage III and stage IV pressure ulcers. These two stages of ulcers are considered "full thickness" ulcers, which according to the WOCN guidelines, means there is total loss of epidermis and dermis and damage extends into the subcutaneous tissue and possibly into the muscle or bone.   An important point to remember is that stage III and stage IV pressure ulcers can be considered closed when they are fully granulated, but never "fully healed."  M1308 asks the clinician to report the current number of unhealed (non epithialized) pressure ulcers at each stage. Because stage III and stage IV pressure ulcers never fully heal as discussed above, it is still appropriate to report closed stage III and stage IV pressure ulcers in M1308.  Also remember that reverse staging of stage III and stage IV pressure ulcers is not an appropriate clinical practice according to the National Pressure Ulcer Advisory Panel (NPUAP).  Stage III and stage IV pressure ulcers should continue to be reported at its worst stage, even if re-epithelialized. The next items on the OASIS ask the clinician to report the measurements of stage III or stage IV pressure ulcer with the largest surface dimensions.  Guidance in the OASIS manual tells the clinician to report 00.0 for all of these items for closed stage III and stage IV pressure ulcers.  The final question asked relating to these pressure ulcers addresses the status of the ulcer.  Again, the OASIS manual should be referenced for guidance.  It tells assessing clinicians that response 0 (newly epithelialized) is the appropriate response for pressure ulcers that have re-epithelialized.  As always, the key to ensuring OASIS accuracy is being familiar with the guidance in the OASIS manual and other OASIS resources.  </p>
        ]]>

      </description>
      <dc:subject>Coding, Education</dc:subject>
      <dc:date>2010-02-05T22:43:47+00:00</dc:date>
    </item>


    <item>
      <title>Five Revisions to OASIS&#45;B1 Items You Need to Know for Success with OASIS&#45;C</title>
      <link>http://ppsplus.com/news/five-revisions-to-oasis-b1-items-you-need-to-know-for-success-with-oasis-c/</link>
      <guid>/news/five-revisions-to-oasis-b1-items-you-need-to-know-for-success-with-oasis-c/</guid>
      <description>

        <![CDATA[ 
          <h3>by Jennifer Warfield, RN, BSN, HCS-D, COS-C</h3>
<p>A large part of OASIS-C B1 was revised to reflect comments, suggestions and changes we have seen since its inception in 1999. With the exception of the process measures that were added to account for changes made in research and other studies, most of the OASIS looks as it always did. A clinician that did an OASIS in December last year should have very little difficulty with the layout of the new form. On the other hand, there are several items which were revised to reflect comments and suggestions from the same clinicians. These items (i.e. pain, bathing, transferring) were expanded to include additional options.</p>
<p><br />&bull;<b>	M1220 (Pain)</b> separated option 0 into one option for "pt has no pain" and one option for "pain does not interfere with activity"<br />&bull;	<b>M1830 (Bathing) </b>added an option for a patient unable to utilize tub or shower but could bathe independently at the sink<br />&bull;	<b>M1840 (Toileting transferring)</b> totally removed hygiene and clothing from the previous toileting item<br />&bull;	<b>M1860 (Ambulation/locomotion)</b> separated option 0 into an option for "one handed" device and "two handed" device<br />&bull;	<b>M2020 (Medication) </b>now includes wording for all medications as opposed to all prescribed medications</p>
<p><br />All of these items have some effect on either reimbursement or outcome measures, so if your clinicians are not yet aware of these changes, now is the time to bring these to their attention.</p>
        ]]>

      </description>
      <dc:subject>Coding, Education</dc:subject>
      <dc:date>2010-02-05T21:54:20+00:00</dc:date>
    </item>


    <item>
      <title>Coding Tip of the Month &#45; February 2010</title>
      <link>http://ppsplus.com/news/coding-tip-of-the-month-february-2010-1/</link>
      <guid>/news/coding-tip-of-the-month-february-2010-1/</guid>
      <description>

        <![CDATA[ 
          <p>Abnormality of Gait vs. Difficulty in Walking</p>
        ]]>

      </description>
      <dc:subject>Coding, Education</dc:subject>
      <dc:date>2010-02-01T17:12:04+00:00</dc:date>
    </item>


    <item>
      <title>Detailed OASIS Review Now More Important than Ever</title>
      <link>http://ppsplus.com/news/detailed-oasis-review-now-more-important-than-ever/</link>
      <guid>/news/detailed-oasis-review-now-more-important-than-ever/</guid>
      <description>

        <![CDATA[ 
          <h3>by Mark Scott, RN, HCS-D</h3>
<p>A detailed review of your OASIS data before submission has always been vitally important. Undetected coding and OASIS errors dramatically affect a homecare agency's reimbursement and outcome percentages.</p>
<p>With the advent of OASIS-C we now have process measures that will be publicly reported in addition to the quality measures previously reported. These new measures will require monitoring as well. Even the most n=highly trained OASIS review professionals are unable to find and correct every mistake in documentation.</p>
<p>Fortunately, there are tools to enhance the review process. Electronic OASIS review software is available that will quickly and thoroughly review your OASIS assessments for coding errors and clinical inconsistencies. It will direct you to specific OASIS items with suggestions for corrections. Review staff can then determine what corrections should be made.</p>
<p>This can dramatically reduce the amount of time it takes for the review process and will make a significant impact on Medicare reimbursement, outcomes and other quality measurs.</p>
        ]]>

      </description>
      <dc:subject>Software</dc:subject>
      <dc:date>2010-01-28T13:53:01+00:00</dc:date>
    </item>

    
    </channel>

</rss>