ºìÁì½í¹Ï±¨

Ensure the vendor is using the Canadian version of the interRAI standard and determine how specification updates will be reflected in the vendor software solution (including frequency, timelines for incorporating changes and whether changes are included in the contract or are an additional cost). 

Outline the reports that are required to meet your business needs. Ensure that the vendor can manage the process for reporting and extracting data based on CIHI’s submission specifications.

There is a subset of data available through the query functionality in IRRS. It is recommended that jurisdictions build data quality reports that use the query data to meet their business needs. This includes the following types of reports:

• A report that lists which validations have been triggered and how often. Use this information to enhance or modify training for assessors on coding.
• A report that lists which assessment data has not yet been submitted to IRRS. This enables your jurisdiction to identify unsubmitted assessment data and investigate the reason (e.g., incomplete data, error triggered during initial submission and not fixed).
• A report that flags missing longitudinal records (i.e., no assessment or discharge information for a person for a specified period).
   

Consider any additional data elements you may be interested in collecting outside the interRAI assessments; there may be an additional cost if this is not included in your vendor contract. 

For additional functionality, consider the following: 

• The ability to retrieve metadata from IRRS for previously submitted assessments and the ability to delete submitted data by using CIHI-issued resource identifiers. This is particularly useful when trying to reconcile submissions and when performing system migrations.
• Inclusion of local validations and reporting to meet business needs.
   

It is recommended that the selected software vendor build in local validations so that data is validated prior to submission to IRRS. These local validations might include hard edits or warnings to prevent incomplete or inaccurate data submissions to IRRS. 

It is recommended that the vendor software solution include an offline option for data collection and validation. This is so that the system will still function in times of poor connectivity or lack of internet access.

Confirm that the vendor software solution has local validation checks that allow the assessor to make corrections in real time as opposed to needing to address errors upon reconnection. 

Ensure that the outputs (e.g., Clinical Assessment Protocols, outcome scales, quality indicators, resource allocation, screening and risk algorithms) are included in your vendor solution package. 

Discuss the ability to retrieve metadata for previously submitted assessments from IRRS and the ability to delete submitted data by using CIHI-issued resource identifiers. This is particularly useful when trying to reconcile submissions and when performing system migrations.