Articles in this section

OUD Query (BOOST List)

  • Updated

Overview
Historical Context
Query Logic and Data Fields
Approved POS's
Approval/Change Request Process
Sample Email that Gets Sent to Recipients

Overview

The OUD Query, also known as the BOOST List or simply BOOST, is a tool used to support the management of clients receiving Opioid Agonist Therapy (OAT). It provides authorized users with a list of clients who are actively receiving OAT at their POS, helping care teams monitor and coordinate ongoing treatment.
 

Historical Context

The OUD Visit form (also known as the OUD Form) and OUD Query were developed as part of the Best Practices in Oral Opioid Agonist Therapy (BOOST) Collaborative, a joint initiative launched by Vancouver Coastal Health (VCH) in partnership with the BC Centre for Excellence in HIV/AIDS (BC-CfE). The collaborative aimed to enhance the quality, effectiveness, and accessibility of substance use care, ultimately improving outcomes for individuals living with opioid use disorder (OUD) in the Vancouver community.

Initially, the OUD Query was designed to support data tracking and reporting for the BOOST Collaborative metrics. Although the formal initiative has since concluded, the query has been repurposed as an operational tool to help clinics track and manage clients actively receiving OAT.

Over time, there has been no formal process to regularly review or update user access. As a result, some clinics may still be receiving the OUD Query despite no longer using it. Currently, recipients are only removed upon request, highlighting the need for a periodic review and cleanup process to ensure the distribution list remains accurate and relevant.

A ticket (EMR-10688) has been opened to explore the development of resources to support the use of the OUD Query and the management of related requests, as well as any changes to existing processes related to the OUD Query.
 

Query Logic and Data Fields

The OUD Query went through a redesign in April 2026. The logic was updated so that the query:

  • Displays the client's most recent Primary OAT, Supplementary 1, and Supplementary 2 prescription from Scripts module, not the most recent OUD Form
    • This is important because clinicians sometimes use the OUD Form to document information such as urine drug screening results without adding a new OAT prescription. This change in logic ensures that prescription information is not missing in the OUD Query
  • Only pulls Primary OAT, Supplementary 1, and Supplementary 2 prescriptions with an end date within the last 3 months
    • This change was made to decrease clutter within the query and remove any historical client records that were no longer relevant
Data Field Description
Primary OAT Site Primary POS where client receives OAT (pulled from OUD Form)
Last Name Client's last name
First Name Client's first name
PARIS ID Client's PARIS ID
Primary OAT Primary OAT medication name (pulled from Scripts)
Rx Start Primary OAT prescription start date (pulled from Scripts)
Rx End Primary OAT prescription end date (pulled from Scripts)
Daily Dose Primary OAT daily dose (pulled from Scripts)
Treatment Stage Primary OAT treatment state (pulled from OUD Form)
Supp1 Rx Supplementary 1 medication name (pulled from Scripts)
Supp1 Rx Start Date Supplementary 1 prescription start date (pulled from Scripts)
Supp1 Rx End Date Supplementary 1 prescription end date (pulled from Scripts)
Supp2 Rx  Supplementary 2 medication name (pulled from Scripts)
Supp2 Rx Start Date Supplementary 2 prescription start date (pulled from Scripts)
Supp2 Rx End Date Supplementary 2 prescription end date (pulled from Scripts)
OAT Duration Number of days client has been receiving OAT (pulled from OUD Form)
PC POS Client's PC POS (pulled from client's record - see yellow banner)
Alt POS Client's Alt POS (pulled from client's record - see yellow banner)
MRP Client's MRP (pulled from client's record - see yellow banner)
AP Client's alternate providers (pulled from client's record - see yellow banner)
Form Date Date that OUD Form was created
Creator Username of user who created the OUD Form
Form POS POS that form creator was logged into when they created the OUD Form
Contact Method Pulled from "How to Contact" field in the OUD Form
MRSD Most recent start date for OAT (pulled from "Most Recent" field in OUD Form)
Duration Number of days client has been receiving OAT (pulled from OUD Form)

Approved POS's

The following POS's have been approved to receive the OUD Query:

POS Code POS Name
DCH Downtown Community Health Centre
GSG Groundspring Primary Care (Green Team)
GSO Groundspring Primary Care (Orange Team)
GSP Groundspring Primary Care (Purple Team)
GWM Grandview Woodland Mental Health and Substance Use Services
HCC North Shore HealthConnection Clinic
HLY Heatley Community Health Centre*
ICM Innercity Intensive Case Management
JRC John Ruedy Clinic
PEN Pender Community Health Centre*
RAA Rapid Access Addictions**
RAB Raven Song Primary Care (Blue Team)
RAG Raven Song Primary Care (Green Team)
RAY Raven Song Primary Care (Yellow Team)
RSG Raven Song*
RSM Raven Song MHSU 
SOM South MHSU
SSC Stepping Stones
STR START: Substance Use Treatment and Response Team
SWY Sheway
TBR Three Bridges Primary Care

*indicates decommissioned POS's 
**indicates program has transitioned to CST Cerner

Note: We need to explore if we should remove these POS's from OUD Query recipient list
 

Approval/Change Request Process

A.) Adding Recipients for Already Approved POS's

Adding new recipients for the OUD Query for POS's that have already been approved is a Standard Order. See Standard Order SO037 Report/Extract Recipients.

B.) Adding Recipients for Not-Yet-Approved POS's

At this time, requests to add recipients for POS's that haven't been approved to receive the OUD Query yet must go through CIS as a change request. After the request has been approved, use the steps below to update the config file:

  1. Ask SA for most recent config.xml file from \\10.251.219.3\kdc-temp\Paris\EMR\BOOST_LIVE\script.ps1

  2. Familiarize yourself with the sample below (this is just a portion of the config):


          

  3. Modify xml file directly in Notepad:
    • Update Recipient List (see Standard Order SO037 Report/Extract Recipients):
      • Update email addresses as needed within the applicable POS segment (each email address separated by semicolon)
    • Modify POS Code (e.g. when POS's code has changed): (use 'Find' function to find all SIX areas with POS code per segment)
      • Modify the affected segment's POS codes
    • Add New POS:
      • Copy the POS segment (refer to screenshot above, example of one POS segment is indicated by red bracket), modify all six POS codes, and add email addresses of recipients 
    • Decommission POS: 
      • Remove the entire POS segment
         
  4. Fill out DRT tab of sysconfig

Sample Email that Gets Sent to Recipients

The OUD Query is sent out daily. Recipients receive two emails from DoNotReplyProfileEMR@vch.ca:

  1. Email with the report attached

  2. Email with the report password