RAST 101

From Guide to YKHC Medical Practices

Revision as of 22:34, 23 August 2021 by JenniferH (talk | contribs) (→‎PRAST)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

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

YKHC RAVEN Application Sub Team (RAST)Electronic Health Records Change Management Policy (linked to Policy Manager (MCN))

PRAST

Any provider related changes requested in the EHR must go through the PRAST process to ensure appropriate consensus and to avoid unintended consequences. The PRAST committee meets from 8 to 9am the third Thursday of each month and all providers and/or interested parties are encouraged to attend. 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 all the 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.

  • for RAST Type: select "Provider RAST"
  • for Help with the "Priority Level," click the blue "?" next to the box for details of Level 1-4.
    1. Financial, regulatory, or patient safety issue without a workaround.
    2. Financial, regulatory, or patient safety issue with a workaround.
    3. New or improved workflow for all users within a single department or multiple departments.
    4. New or improved workflow for some users or the majority of users within one department
  • 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:

  1. If it is an urgent issue affecting patient care, call ext. 6070, option 3 to speak with the RAVEN on-call person.
  2. 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.


Electronic Health Record (EHR) Main Page