12.07.2015 Views

RAI-MDS 2.0 Nutritional Care Resource Guide April 2011 - CCIM

RAI-MDS 2.0 Nutritional Care Resource Guide April 2011 - CCIM

RAI-MDS 2.0 Nutritional Care Resource Guide April 2011 - CCIM

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Remember:• The nutrition care team is responsible for addressing all nutrition care needs and strengths ofresidents that are not included in RAPs• Depending on individual home’s policy, non-triggered clinical problems can be documented in theprogress notesTRIGGERED RAP AND NON-TRIGGERED CLINICAL PROBLEMS REVIEW PROCESSTRIGGERED RAP REVIEW AN INTERDISCIPLINARY APPROACHTRIGGERED RAP REVIEW PREPARATIONFind out from the <strong>RAI</strong> Coordinator:1. Who will generate the RAPs and Section V (Resident Assessment Protocol Summary)?2. When will RAPs and Section V be generated?3. What RAPs will the dietary team be responsible for or contribute to?4. When will the care team get together to review the RAPs and develop care plan interventions?TRIGGERED RAP REVIEW PREPARATIONFind out from the <strong>RAI</strong> Coordinator:1. Who will generate the RAPs and Section V (Resident Assessment Protocol Summary)?2. When will RAPs and Section V be generated?3. What RAPs will the dietary team be responsible for or contribute to?4. When will the care team get together to review the RAPs and develop care plan interventions?TRIGGERED RAP REVIEW PROCESS1. Do you agree with the RAP condition triggered?2. Do you agree with the <strong>RAI</strong>-<strong>MDS</strong> <strong>2.0</strong> items associated with the triggered RAP?3. If the RAP is not accurate, notify the <strong>RAI</strong> Coordinator to correct coding and reprint the RAP.4. If you agree with the RAP and the triggered items, follow the 5-step RAP documentation process.For Information: 416.327.7625 4ltchrai@ontario.ca4

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!