RAST 101: Difference between revisions

Revision as of 01:41, 8 October 2020

RAST

The RAVEN Application Sub-Teams (i.e., RAST) are responsible for vetting requests for changes to the EHR.

There are two main RAST committees:
- PRAST = Provider RAST
- CRAST = Clinical/Financial RAST

PRAST

The PRAST committee meets monthly on the third Thursday to review all requests for changes to the EHR specifically requested by, and/or primarily affecting providers. The PRAST committee meetings allow providers (and others) the opportunity to discuss and weigh in on the requests. All providers and interested parties are encouraged to attend the monthly meeting, especially if submitting item(s) for review. If the requester is unable to attend, a representative should attend to address any questions that may arise in the discussion. If the requestor (or a representative) is not present at the committee meeting, the request may be placed on hold until a representative can attend the meeting.

When the PRAST committee approves a request, the request is then submitted to the CRAST committee that meets monthly on the Wednesday after the PRAST. This committee reviews all RAST requests coming from providers, as well as many others requests. The committee meetings offers representatives from a variety of disciplines (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 all requests, (including provider requests), ensuring that there are no unanticipated/unintended consequences that may adversely impact other aspects of the organization.

Submitting Requests

PRAST Requests need to be submitted along with supporting and/or relevant information, attachments, etc., via our HEAT system by the FRIDAY prior to the PRAST monthly meeting. Requests will then be emailed out to all providers for comments. This allows those who are unable to attend the committee meeting an opportunity to weigh in on the requests. See an example of a PRAST request on next page.

A direct supervisor should endorse all RAST requests before sending to the RAST committee(s) for review.
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.

Fix vs Change

There is an important distinction between a request for changes to be made to the EHR (which need to go through RAST approval processes) and a ‘FIX’.

If something in the EMR is not working properly, i.e., needs to be FIXED (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 affecting 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, taking a screen shot or ‘snip’ of the screen to send later helps to provide a context within which to evaluate the problem.

@@ Line 1: / Line 1: @@
-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.
+===RAST===
+The RAVEN Application Sub-Teams (i.e., RAST) are responsible for vetting requests for changes to the EHR.
+*There are two main RAST committees:
+**'''PRAST''' = Provider RAST
+**'''CRAST''' = Clinical/Financial RAST
+===PRAST===
+The PRAST committee meets monthly on the third Thursday to review all requests for changes to the EHR specifically requested by, and/or primarily affecting providers. The PRAST committee meetings allow providers (and others) the opportunity to discuss and weigh in on the requests. All providers and interested parties are encouraged to attend the monthly meeting, especially if submitting item(s) for review. If the requester is unable to attend, a representative should attend to address any questions that may arise in the discussion. If the requestor (or a representative) is not present at the committee meeting, the request may be placed on hold until a representative can attend the meeting.
-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.
+When the PRAST committee approves a request, the request is then submitted to the CRAST committee that meets monthly on the Wednesday after the PRAST. This committee reviews all RAST requests coming from providers, as well as many others requests. The committee meetings offers representatives from a variety of disciplines (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 all requests, (including provider requests), ensuring that there are no unanticipated/unintended consequences that may adversely impact other aspects of the organization.
-''All RAST submissions should be endorsed by a direct supervisor before being sent to the committee for review.''
+===Submitting Requests===
+PRAST Requests need to be submitted along with supporting and/or relevant information, attachments, etc., via our '''HEAT system''' ''by the FRIDAY prior to the PRAST monthly meeting''.  Requests will then be emailed out to all providers for comments. This allows those who are unable to attend the committee meeting an opportunity to weigh in on the requests. See an example of a PRAST request on next page.
+*A direct supervisor should endorse all RAST requests before sending to the RAST committee(s) for review.
+*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 to 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.
+===Fix vs Change===
+There is an important distinction between a request for changes to be made to the EHR (which need to go through RAST approval processes) and a ‘FIX’.
-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.
+If something in the EMR is not working properly, i.e., needs to be FIXED (e.g., the Growth Chart is freezing the screen), this should not go to RAST committee.
-'''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.'''
+You have two options in this case:
+#If it is an urgent issue affecting patient care, call ext. 6070, option 3 to speak with the RAVEN on-call person.
-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.
+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, taking a screen shot or ‘snip’ of the screen to send later helps to provide a context within which to evaluate the problem.