New SO Article Template

Article Settings

When a new SO is approved, use this structure to create the new SO's instruction article.

Do NOT include this section in the new SO article. These are notes for setting up the article.

• Article Title Standard: SO Type ID followed by the name of the category. Do not add action words to the title if possible. Example: use "SO027 Letter Template" and not "SO027 Manage Letter Template"
• Article Section Placement: Profile EMR > Standard Order Processes
• Article Placement within section: By SO Type ID, descending
• In this article: replace information where you see the placeholder tags < >, ensuring any replacement text's highlight colour is removed. 
• Update the Table of Contents Links - if you copy and paste them into a new article, it will point to this template instead of itself.

Standard Order Category:	<SO Category 1/SO Category 2/SO Category 3>
Who should fulfill this SO?	<SO Analyst, EMR SA and/or Tech>
<remove row if not Category 3>Requires CIS involvement?	<Yes/No>
Link to the SO request form:	<replace with URL to published fillable PDF form>

Reminder to please follow the Standard Order Guidelines on top of the specific instructions outlined below.

Background
Prerequisite: Requester to Complete the SO Request Form
Prerequisite: Approval from Clinical Informatics <remove if does not require CIS approval>
Prerequisite: Forward to <EMR SA/Tech> <remove if does a SO analyst can fulfill the request>
<insert more prerequisites section titles, if needed>
Fulfillment Instructions
     <insert subsection titles>
Resource File(s) <remove if none are required>

Background

<Add any priority notes at the top of this section. Describe the purpose (problem to solve) and/or goal (what it fulfills) of this SO>

Prerequisite: Requester to Complete the SO Request Form

If a request was received for this Standard Order but without using the SO request form, send the form's URL link to the requester. After receiving the form submission, ensure all the mandatory fields are completed before proceeding. If not, discuss further with the requester.

Prerequisite: Approval from Clinical Informatics

Clinical Informatics approval is required. Once the requester has completed the SO request form and the main SO JIRA has been created:

• Set the JIRA status to Waiting for Approval
• Attach the SO Request Form to the JIRA
• Create a subtask for <replace with SO Type ID> CIS Approval for EMR-XXXXX, where EMR-XXXXX is the JIRA ID. Assign it based on the CIS based on the Clinical Informatics Specialist (CIS) - Matrix

Prerequisite: Forward SO to <EMR SA/Tech>

Once ready for fulfillment, forward the information to [e-mail] by copying and pasting the below to an email, attaching the completed PDF, and replacing EMR-##### with the JIRA ID:

Email Subject: SO Request: <replace with SO Type ID and SO name>  (EMR-#####)

Email Body:

Hello <EMR SA/Tech>, 

Please complete the following approved SO. See attachment for details. Reminder to do the following:

1. Create the Implementation subtask and assign both this subtask and the main JIRA to yourself once you begin to fulfill the request <remove this bullet if does not require CIS approval>
2. Assign the JIRA to yourself once you begin to fulfill the request <remove this bullet if it requires CIS approval>
3. Complete this SO by following this Zendesk article: <replace with link to this article>
4. Save any related files to the SO work item folder
5. Resolve the JIRA when its completed 
6. Notify the requester with the [e-mail] email CC'd
7. Send out the SO Completed email with the [e-mail] email CC'd
8. Move any related emails of this work to the 01 Completed folder in the [e-mail] mailbox

Thanks

Prerequisite: <insert description, if more prerequisites are needed>

<Remove this section if not needed. If a prerequisite is needed and must be done in a specific order, re-arrange the sections chronologically, which may mean this should be above the prerequisite of getting Clinical Informatics approval>

Fulfillment Instructions

<if this SO required CIS Approval, keep this paragraph. If not, remove it>Create a subtask for <replace with SO Type ID> Implementation for EMR-XXXXX, where EMR-XXXXX is the JIRA ID. Assign it to yourself. Note: do not create this subtask earlier while waiting for CIS Approval; create it only once CIS has approved. If this is not followed, this will report inaccurate metrics for the monthly performance reports.

<If the SO has a single path to completion, use the suggested subsections below. If there are multiple ways request types (e.g. add, modify, delete), use those as subsection titles instead). Just ensure if you replace it with your own subsections, that it should still follow the typical cycle of dev/test, deployment (including VTM reminders) and validation.>

Development & Testing

<Insert instructions here. Remove this section if it can only be done on the fly in production/VTM>

Deployment

Reminder: complete deployment steps in VTM after completing in production. This will ensure the Self-Training environment contains this work upon next refresh. Use the generic ADMIN user account to do so. <Remove this reminder if the SO is specific to changing user account or client data that does not exist in VTM>

<Replace with instruction here> 

Validation & Post Deployment

<Replace with instruction here> After this, contact the requester regarding the request's completion.

Resource File(s)

<Remove this section if there are no attachments to this article>