Stakeholders are able to request various types of changes to DATIS product, for example:
- Updates to existing report templates,
- Entirely new reports,
- Refinement of permissible options within applications, e.g. adding "Fentanyl" as a substance option
- Changes to application features/functionality, e.g. changing the workflow of a module
- It may not always be clear when a request is simple or difficult, which makes it challenging to plan expected timelines
To submit a Product Change Request, select the option within the Service Desk.
Fill out the details of your request, keeping in mind the following considerations:
- Providing as much detail as possible is always appreciated.
- We will resolve “bugs” as soon as we can, dependent on resourcing, the nature of the issue and whether we need to involve external vendors.
- Major updates take longer than minor updates. New features & reports will generally require the most time to complete.
- Consider how a change you request in may impact corresponding mandatory reporting requirements for agencies, and vice versa.
- If you do have a target deadline in mind, please let us know so we can prioritize the request against others in the queue.
We recommend you keep Product Change Requests shared with your organization. Once you're done, hit submit.
What happens after I submit a request?
When you submit a request CAMH will respond within 5 business days with an assessment of the scope of your request as defined by one of these four categories. After this initial assessment, CAMH will investigate the change further in order to confirm requirements, feasibility and timeline.
Category | Description |
|---|---|
Bug fix | Bugs describe unexpected or erroneous behavior in an application or report. |
Minor update | Includes:
For an update to be considered minor it must also be simple enough as to not require a sector-wide alert of the change. |
Major update | Also includes application configuration changes & report updates. However, a major update would be significant to users as to require a sector-wide communication & scheduled release. This may be due to changes that impact mandatory reporting requirements. Users must be informed prior to the change & know the date of the planned release. |
New feature/ report | New features & reports require development either by CAMH or our vendors and must be assessed on a request-by-request basis. |
