RAST 101 - Revision history

JenniferH: /* PRAST */

2021-08-23T22:34:25Z

PRAST

← Older revision		Revision as of 22:34, 23 August 2021
Line 6:		Line 6:
	[https://ykhc.ellucid.com/documents/view/18991 YKHC RAVEN Application Sub Team (RAST)Electronic Health Records Change Management Policy] (linked to Policy Manager (MCN))		[https://ykhc.ellucid.com/documents/view/18991 YKHC RAVEN Application Sub Team (RAST)Electronic Health Records Change Management Policy] (linked to Policy Manager (MCN))
	===PRAST===		===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 ~~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.		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.		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.

JenniferH: /* PRAST */

2021-08-23T22:33:29Z

PRAST

← Older revision		Revision as of 22:33, 23 August 2021
Line 6:		Line 6:
	[https://ykhc.ellucid.com/documents/view/18991 YKHC RAVEN Application Sub Team (RAST)Electronic Health Records Change Management Policy] (linked to Policy Manager (MCN))		[https://ykhc.ellucid.com/documents/view/18991 YKHC RAVEN Application Sub Team (RAST)Electronic Health Records Change Management Policy] (linked to Policy Manager (MCN))
	===PRAST===		===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.		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 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 all the requests, (including provider requests), ensuring that there are no unanticipated/unintended consequences that may adversely impact other aspects of the organization.		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.

JenniferH at 08:24, 2 January 2021

2021-01-02T08:24:31Z

← Older revision		Revision as of 08:24, 2 January 2021
Line 8:		Line 8:
	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.		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.		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===		===Submitting Requests===

JenniferH: /* Fix vs Change */

2020-11-21T04:34:44Z

Fix vs Change

← Older revision		Revision as of 04:34, 21 November 2020
Line 31:		Line 31:

	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.		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.


			[[:Category:RAVEN\|Electronic Health Record (EHR) Main Page]]

JenniferH at 21:12, 8 October 2020

2020-10-08T21:12:18Z

← Older revision		Revision as of 21:12, 8 October 2020
Line 4:		Line 4:
	**'''PRAST''' = Provider RAST		**'''PRAST''' = Provider RAST
	**'''CRAST''' = Clinical/Financial RAST		**'''CRAST''' = Clinical/Financial RAST
			[https://ykhc.ellucid.com/documents/view/18991 YKHC RAVEN Application Sub Team (RAST)Electronic Health Records Change Management Policy] (linked to Policy Manager (MCN))
	===PRAST===		===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.		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.

JenniferH: /* Submitting Requests */

2020-10-08T01:47:19Z

Submitting Requests

← Older revision		Revision as of 01:47, 8 October 2020
Line 10:		Line 10:

	===Submitting Requests===		===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~~.		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.
			*#Financial, regulatory, or patient safety issue without a workaround.
			*#Financial, regulatory, or patient safety issue with a workaround.
			*#New or improved workflow for all users within a single department or multiple departments.
			*#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.		*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.		*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.

JenniferH at 01:41, 8 October 2020

2020-10-08T01:41:16Z

← Older revision		Revision as of 01:41, 8 October 2020
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.		#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.

JenniferH at 01:33, 8 October 2020

2020-10-08T01:33:32Z

← Older revision		Revision as of 01:33, 8 October 2020
Line 5:		Line 5:
	''All RAST submissions should be endorsed by a direct supervisor before being sent to the committee for review.''		''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.		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.

	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.		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.

JenniferH at 01:28, 8 October 2020

2020-10-08T01:28:30Z

← Older revision		Revision as of 01:28, 8 October 2020
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.		#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.

JenniferH: Created page with "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,..."

2019-09-18T10:44:22Z

Created page with "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,..."

New page

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 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 affecting providers. Please make sure to discuss any RAST submissions with your direct supervisor before sending 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.

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.'''''

;''Example of incomplete RAST request:''
: "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:''
: 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
: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”).