| Standard Order Category: | Various (see below) |
| Who should fulfill this SO? | SO Analyst (with Tech consultation for subset of codes - see below) |
| Requires CIS involvement? | No |
| Link to the SO request form: | N/A |
Reminder to please follow the Standard Order Guidelines on top of the specific instructions outlined below.
Background
SO Nominations for Short Code Types
Prerequisite: Determine the Short Code Type Eligibility
Approved for SO Process
Approved for SO Process (with Tech Consultation)
Excluded from SO Process
Short Code Types not specified in this Zendesk
Fulfillment Instructions
Background
Short Codes changes can vary in complexity in terms of impact on the system and amount of work required. Due to this, the Short Code Types have been reviewed and grouped based on if it is in scope for SO process and if so, whether it requires a technical consultation.
SO Nominations for Short Code Types
All existing Short Code Types have been reviewed. If an analyst would like to nominate a new Short Code Type to become an SO, a technical resource would need to give advice first on whether it can become one, and if so, if it requires tech consultation. This is the general guideline on how to approach this:
- Analyst asks advice from the developer that worked on the request that involved creating the new Short Code Type.
- The developer provides their technical advice on whether or not it can be an SO, and if so, if it requires dev consultation. They will not provide feedback regarding feasibility based on business or clinical workflow. The developer will have to consider:
- usage/impact across the system (ex: are all areas its used safe to change by SO?)
- ease of change (ex: could those on SO duty do it independently or requires dev consultation?)
- likeliness of the Short Code can be changed independently from other work (ex: if the Short Code change always requires other components that require a CC, it's best it is not an SO)
- add/modify/delete actions (ex: could all three be consider SOs, or only add/modify?)
Note: if the developer needs guidance to make these decisions, they can contact the developer that did their tech review. If more guidance is required, the developer can email the whole development group for assistance, or raise it in the next monthly dev meeting if it's scheduled soon.
- Based on the developer's advice, the analyst can nominate it for an SO in an upcoming ATP. The analyst should note the technical advice on whether or not it can be done independently or must have dev consultation before changing. The rest of the SO nomination process proceeds as usual.
Prerequisite: Determine the Short Code Type Eligibility
Only a subset of Short Codes are approved to be updated through the Standard Order Process. Of this subset, some must be changed by the SO Analyst with a technical consultation. Review the following sections that outline which Short Code Type below to which category before proceeding.
Approved for SO Process
The ones listed below can be done using usual Standard Order process.
| Short Code Type | Notes |
| Clinical Tag | Adding only is SO. Removal is not an SO. Feature is only used in some YCA forms |
| Excluded Next Appointment Types | Add, Modify and Delete are approved to be SO. Used in Patient Info Bar (Yellow Bar) and next appointment |
| Form Links | For more details, see article specific to Form Links short code |
| Form URL Links | For more details, see article specific for Form URL Links |
| OAT Medications (Used by OUD Form) |
Adding only is SO. Removal is not an SO. Addition of new medication must be first approved by Clinical Informatics SO instructions are located in the OAT Medications SO Folder ('OAT Medications Short Code_INSTRUCTIONS AND MAIN LIST' excel spreadsheet): \\vch\departments\PCAC_EMR\01 - PCCEMR\Work Items\00 - All Items (JIRA)\01-Standard Orders\User Requests\Short Codes\OAT Medications See OUD Form Tab on spreadsheet. |
|
OAT Medications DUP (Used by DUP Form) |
Same as OAT Medications above See DUP Form Tab on spreadsheet. |
| Primary Care POS List | Add, Modify and Delete are approved to be SO. Used only in Update POS form |
| Religion | Add, Modify and Delete are approved to be SO. Only used in Alter Patient. Tied to a single field and doesn't affect anywhere else in the system. |
Approved for SO Process (with Tech Consultation)
These can be done using the SO process however a developer/technical resource should be consulted first. This is because these short codes aren't straight forward changes. There can be a slight level of complexity to it.
| Short Code Type | Notes |
| Language | PCIS_EMR_Language is tied to Language short codes, they should be updated at the same time. Paris Update macro will update this SC automatically too. Best to consult with dev first |
| EMR_FHIR_Country | SO if Panorama reaches out to us and says it's integrated on their side already. Needs a matching value on the FHIR/Panorama side |
| EMR_FHIR_Display Values | SO if Panorama reaches out to us and says it's integrated on their side already. Needs a matching value on the FHIR/Panorama side |
| EMR_FHIR_SYSTEM_URL | SO if Panorama reaches out to us and says it's integrated on their side already. Needs a matching value on the FHIR/Panorama side |
| EMR_PAN_Ethnicity | SO if Panorama reaches out to us and says it's integrated on their side already. Needs a matching value on the FHIR/Panorama side |
| EMR_PAN_Language | SO if Panorama reaches out to us and says it's integrated on their side already. Needs a matching value on the FHIR/Panorama side |
| PCIS _EMR_Language |
SO if PCIS reaches out to us and says it's integrated on their side already. Needs matching value on the PCIS side
PCIS_EMR_Language is tied to Language short codes, they should be updated at the same time.. Best to consult with tech first |
| PCIS_EMR_Relationship | SO if PCIS reaches out to us and says it's integrated on their side already. Needs matching value on the PCIS side |
| PCIS_EMR_Religion | SO if PCIS reaches out to us and says it's integrated on their side already. Needs matching value on the PCIS side |
| UBC Doctors |
Pulled into some UBC forms via macro - used in in a standard dropdown/text field pairing for all those UBC forms https://imitspccs.zendesk.com/hc/en-us/articles/360053674891-UBC-Forms-Neurologist-Dropdown-Request |
Excluded from SO Process
These were reviewed and explicitly deemed unable to user the SO process. They were identified to fit one of these categories:
- Require more effort/complexity during analysis compared to other SOs
- May require additional changes outside of the Short Code change to work
- Not used by any of our workflows or processes
| Short Code Type | Notes |
| Iwi | ANZ Tribal names - not revelvant to Canada. We should never get this request |
| Occupation | Largely unused, this is client occupation |
| Accession Client Question | We don't use, tied to IH patient web portal |
| Admin Forms | Needs to be deployed with form changes (access/role-based related too) |
| Approved PARIS Alerts | Requires more than just short code. Requires approval by PARIS and analysis. But potentially in future if the macro that uses this is changed to handle updates to this short code better |
| Care Team roles | Requires more complex analysis & informatics involvement |
| Client Gender Identity | Used for Client Registration form and Update Gender Identity form. More complex analysis is required. |
| Client Pronouns | Used for Client Registration form and Update Pronoun form. More complex analysis is required. |
| Client reg Form Record Type | Used for Registration form. More complex analysis is required. |
| Contacts | Related to Appointment Preferences. Many other areas to change if this changes |
| Data Environment | Is used by macros and if needs to change, more than just short code needs to be changed too |
| Database Map | Is used by macros and if needs to change, more than just short code needs to be changed too |
| P2P Admin | Tied to PARIS Interface |
| P2P Interface | Tied to PARIS Interface |
| Pregnancy Nature | Complex analysis required; Changes and removal may have impact in antenatal form |
Short Code Types not specified in this Zendesk
Any short codes not explicitly listed within this Zendesk by default should NOT be considered an SO. The developers have reviewed the full list and there were many that they did not know what it was used for or if it can be considered simple. It's best and safest to not follow the SO flow for these ones and go through regular CC process. If during that analysis phase it's discovered it is in fact simple, we can then nominate it to use the SO process.
Fulfillment Instructions
- Sign into EMR DEV using an account with a Sys Admin or Support Analyst role
- Go to Maintain > Short Codes
- In Type column, select the desired Short Code Type that the Short Code to modify belongs to. The list of short codes for this type should now display on the right side panel
- Make the update as appropriate
- To Add: Click on the Add new short code icon at the top. Fill in the Code and Description, then click on OK
- To Modify: Double-click the short code desired to change. Update the Code and/or Description, then click on OK
- To Delete: Select the desired short code, then click on the Delete current short code icon at the top. Confirm the deletion.
- To Add: Click on the Add new short code icon at the top. Fill in the Code and Description, then click on OK
- Confirm the changes/addition/deletion. Validation depends on Short Code type being affected.
- If all is good, proceed to do the same change into Profile EMR Production
- Using the generic ADMIN user account, add the changes done above to EMR VTM. This is so both Training and Self-Training environments will get this update on next refresh.