RAST 101: Difference between revisions

Revision as of 01:28, 8 October 2020

The EHR/Provider RAST (“RAVEN Application Sub-Team”) meets monthly on the 3rd Thursday. All medical providers and interested parties are encouraged to attend, especially if submitting item(s) for review.

EHR/Provider RAST submissions are requests for changes to the RAVEN system requested by, and primarily effecting providers. The EHR/Provider RAST Committee meetings allow providers (and others) the opportunity to evaluate and weigh in on the submissions for approval.

All RAST submissions should be endorsed by a direct supervisor before being sent to the committee for review.

If approved by the EHR/Provider RAST, the submissions will then usually need to be submitted the ‘Clinical/Financial RAST Committee’ for approval which meets every two Wednesdays. This offers other discipline representatives (i.e., Nursing, Registration, Scheduling, Finance, IT, CHAP, Village Ops, SRC, Behavioral Health, Diagnostic Services/Lab, Compliance, Coding, Pharmacy, and Performance Improvement) an opportunity to weigh in on the provider requests, ensuring that there are no unintended consequences from the request that may negatively impact other aspects of the organization.

Once a RAST request has been approved, the submitter will be notified via email when the request has been logged into SharePoint and throughout the lifespan of the request as updates are made to the SharePoint ticket. RAST requests with a priority of 3-4 are assigned at RAVEN’s bi-weekly change control meetings. Priority 1 and 2 requests are assigned immediately following the RAST meeting at which it was approved.

RAST requests need to be submitted along with supporting or relevant information, attachments, etc., via our HEAT system (see example below) by the FRIDAY prior to the RAST monthly meeting. Submissions will then be emailed out to all providers on the Monday prior to the monthly meeting for comments. This allows those who are unable to attend the committee meeting a chance to weigh in on the submissions.

There is a distinction between changes in the RAVEN system which need to go through RAST approval processes and a ‘correction’ or ‘fix’. If something in RAVEN is not working properly, needs to be ‘fixed’ or ‘corrected’ (e.g., the Growth Chart is freezing the screen), this should not go to RAST committee. You have two options in this case:

If it is an urgent issue impacting patient care, call ext. 6070, option 3 to speak with the RAVEN on-call person.
If it is not an urgent issue, it should go to the RAVEN team as a heat ticket.

Whenever possible, it helps to contact the RAVEN team when an error or problem is actually occurring so that they can see your screen. If not possible to report the problem in real-time, please take a screen shot or ‘snip’ of the screen to send later. It helps to provide as much detail as possible to provide context within which to evaluate the problem.

@@ Line 1: / Line 1: @@
-The EHR/Provider RAST (“RAVEN Application Sub-Team”) meets monthly 3rd Thursday in Outpatient Conference Room (OPCR) 8-9am. All medical providers are encouraged to attend, especially if submitting item(s) for review.
+The EHR/Provider RAST (“RAVEN Application Sub-Team”) meets monthly on the 3rd Thursday. All medical providers and interested parties are encouraged to attend, especially if submitting item(s) for review.
-The EHR/Provider RAST Committee meetings allow providers (and others) the opportunity to evaluate and weigh in on the submissions for approval. Once approved by the EHR/Provider RAST, the submissions will then often need to be submitted to the ‘Clinical/Financial RAST Committee’ for approval which meets every two Wednesdays.
+EHR/Provider RAST submissions are requests for changes to the RAVEN system requested by, and primarily effecting providers. The EHR/Provider RAST Committee meetings allow providers (and others) the opportunity to evaluate and weigh in on the submissions for approval.
-EHR/Provider RAST submissions are requests for changes to the RAVEN system requested by, and primarily affecting providers. Please make sure to discuss any RAST submissions with your direct supervisor before sending to the committee for review.
+''All RAST submissions should be endorsed by a direct supervisor before being sent to the committee for review.''
-Once a RAST request has been approved, you’ll be notified via email when the request has been logged into SharePoint and throughout the lifespan of the request as updates are made to the SharePoint ticket. RAST requests with a priority of 3-4 are assigned at RAVEN’s bi-weekly change control meetings. Priority 1 and 2 requests are assigned immediately following the RAST meeting at which it was approved.
+If approved by the EHR/Provider RAST, the submissions will then usually need to be submitted the ‘Clinical/Financial RAST Committee’ for approval which meets every two Wednesdays. This offers other discipline representatives (i.e., Nursing, Registration, Scheduling, Finance, IT, CHAP, Village Ops, SRC, Behavioral Health, Diagnostic Services/Lab, Compliance, Coding, Pharmacy, and Performance Improvement) an opportunity to weigh in on the provider requests, ensuring that there are no unintended consequences from the request that may negatively impact other aspects of the organization.
-RAST requests need to be emailed fully completed in the following format by the FRIDAY prior to the RAST monthly meeting. Submissions will be emailed to all providers on the Monday prior to the monthly meeting for comments. '''''Only completed RAST requests will be presented to the committee.'''''
+Once a RAST request has been approved, the submitter will be notified via email when the request has been logged into SharePoint and throughout the lifespan of the request as updates are made to the SharePoint ticket. RAST requests with a priority of 3-4 are assigned at RAVEN’s bi-weekly change control meetings. Priority 1 and 2 requests are assigned immediately following the RAST meeting at which it was approved.
-;''Example of incomplete RAST request:''
+'''RAST requests need to be submitted along with supporting or relevant information, attachments, etc., via our HEAT system (see example below) ''by the FRIDAY prior to the RAST monthly meeting''. Submissions will then be emailed out to all providers on the Monday prior to the monthly meeting for comments. This allows those who are unable to attend the committee meeting a chance to weigh in on the submissions.'''
-: "Hey could someone please add a better drug to our ED Power Plan? The one we have isn’t working and it’s embarrassing. Thanks. B. Bugs”
-;''Example of complete RAST request:''
+There is a distinction between changes in the RAVEN system which need to go through RAST approval processes and a ‘correction’ or ‘fix’. If something in RAVEN is not working properly, needs to be ‘fixed’ or ‘corrected’ (e.g., the Growth Chart is freezing the screen), this should not go to RAST committee. You have two options in this case:
-: REQUEST: Can we add a new medication called ‘nodoflopsie’ to the ‘Earectile Dysfunction Power Plan’? Sentences include: 50mg 1 tablet PO q 4 hours PRN; 25mg 1 tablet PO q4 hours PRN
+#If it is an urgent issue impacting patient care, call ext. 6070, option 3 to speak with the RAVEN on-call person.
-:REQUESTOR: Bugs B. Bunny, PA
-:REASON/BENEFIT: Will improves overall bunny patient care and prevents shame and embarrassment d/t excessively floppy earpendeges.
-:IMPACT: Power Chart
-:INTERESTED PARTY: Mrs. Bugs B Bunny, PA
-:PRIORITY: 1 (no work around for poor Bugs)
-:STATUS:
-;''RAST Request Template:''
-: REQUEST: (What change or enhancement are you requesting?)
-:REQUESTOR: (your name goes here)
-:REASON/BENEFIT: (Why is this change important? What is the benefit of making the change? How will it improve care / workflow / documentation / compliance / finance?)
-:IMPACT: (Which solution(s) or department(s) would benefit from this change? If this request impacts more than just your department, are all parties in agreement with this request?)
-:INTERESTED PARTY: (Who is ONE PERSON who has a vested interest and/or is able to test and/or communicate about this request if you are unavailable?)
-:PRIORITY: (Select the priority level that matches your request.)
-:*1=financial, regulatory, or patient safety issue without a workaround
-:*2=financial, regulatory, or patient safety issue with a workaround
-:*3=new workflow improvement that will improve workflow for all users within a department or multiple users from multiple departments
-:*4=new workflow improvement that will improve workflow for majority of users within one department
-There is a distinction between changes in RAVEN (which need to go through RAST approval processes) and a ‘fix’. If something in RAVEN is not working properly, needs to be ‘fixed’ or ‘corrected’ (e.g., the Growth Chart is freezing the screen), this should not go to RAST committee. You have two options in this case:
-#If it is an urgent issue interfering with patient care, call ext. 6070 and ask to speak with the RAVEN on-call.
 #If it is not an urgent issue, it should go to the RAVEN team as a heat ticket.
-Whenever possible, it helps if you can contact someone when an error or problem is actually occurring so that they can see your screen. If not possible, please take a ‘snip’ of the screen to send them so they can see what the error looks like (See ‘Learning Live’ for instructions on “How To Use The ‘SNIPPING’ Tool”).
+Whenever possible, it helps to contact the RAVEN team when an error or problem is actually occurring so that they can see your screen. If not possible to report the problem in real-time, please take a screen shot or ‘snip’ of the screen to send later. It helps to provide as much detail as possible to provide context within which to evaluate the problem.