Recently released & upcoming changes
We are now keeping track of our releases on a quarterly basis, look below to see upcoming and recent changes to the Ontario Harm Reduction Database. Released changes either apply to the NEO web application or the CAMH SAP reports. The types of changes (updates, bug fixes & new features) are defined below.
NEO
Release Date | Type | Product | Name | Description |
---|---|---|---|---|
| Minor update | Consumption & Treatment Module | 0.25 naloxone dose | Added 0.25 doses of naloxone as available option during medical emergency. |
| New feature/ Bug fix | All modules | Share Data | Previously, Transaction Sites in NEO could only see the Client History of a code for transactions logged at that specific site, even if one agency operated multiple Transaction Sites with shared staff and clients. Agencies now have the option to group Transaction Sites together in order to enable a shared view of the Client History across multiple Sites. By default, Client History will continue to be limited unless otherwise requested. This feature has also fixed a bug wherein some users of the Consumption & Treatment module could see client visits belonging to other CTS sites in their region. |
Reports
Release Date | Type | Product | Name | Description |
---|---|---|---|---|
| New report | CTS Medical Emergencies | CTS Medical Emergencies | Created a new report to more easily view the medical emergencies/overdoses that have been logged in the NEO CTS module. This report is to assist agencies with checking the number of overdose events they are reporting on the CTS Monthly Report. |
| Major update | ONP Quarterly Report | Unknown doses | Added "UNK" to "Number of individuals who reported administering or receiving naloxone". Clarified that "5 or more doses" is captured in report. Number of individuals who reported administering or receiving naloxone, unknown type (nasal vs. injectable). |
Major update | Harm Reduction Outreach Report (OCHART Section 6) | BZK Wipes | BZK wipes will be added to the SAP report version of OCHART Section 6. Agencies already tracking BZK wipes in NEO will see their totals listed. | |
| Minor update | All reports | Date filters | Date filters can now be set as a flexible range rather than by year and quarter. |
| Bug fix | NEP Activity Report | Average age of clients | Fixed following scenarios when average age is broken down by gender:
Note: This report already excluded years of birth <1920 from average age calculations, so year of birth must now be between 1920 and 2018 to be included in calculations. |
Minor update | NEP Activity Report | "Not Specified" Gender | "Not listed/Undisclosed" previously aggregated transactions belonging to both coded and anonymous clients with the gender "Other gender not listed". This category in the NEP Activity Report now also contains all transactions with the gender "Not specified". | |
Major update | Harm Reduction Outreach Report (OCHART Section 6) | BZK Wipes | BZK wipes will be added to the SAP report version of OCHART Section 6. Agencies already tracking BZK wipes in NEO will see their totals listed. |
Types of changes
The ONHRDB releases changes that vary in their level of assessment, development & impact. The categories below broadly define the changes we release to better understand how they are developed and how they may impact end users.
Category | Description |
---|---|
Bug fix | Bugs describe unexpected or erroneous behavior in NEO or SAP reports. Anything from a spelling error to a miscalculation in a report might be a bug. Bug fixes correct these errors. |
Minor update | Includes:
|
Major update | Also includes NEO configuration changes & SAP report updates. However, a major change would impact users enough to require a sector-wide communication & scheduled release. This may be due to changes that impact mandatory reporting requirements. Users are informed prior to the change & know the date of the planned release. |
New feature or report | New features & reports require development either by CAMH or our NEO vendor. Development includes the collection & refinement of user requirements, assessment of feasibility, programming the actual feature/report, and user approval testing. |