From the outset with the CMIRPS project, the vision was that it wasn't to be built in silos. So if you look at the organizations that have been involved in the product from the beginning, Health Canada is certainly up front, as is the Canadian Patient Safety Institute, within their mandate of safety within the country, and the Institute for Safe Medication Practices Canada, or ISMP, has also been involved in the field.
If you look at the components of the data we're managing to collect, there will certainly be incidents or errors that will occur that are essentially associated with the product. So we have naming, packaging, labelling, look-alikes, and sound-alikes. Certainly that's data that Health Canada is very interested in, in their legislative role, so we would look at making sure that data is available.
We talk of the entire environment of reporting. This is not a mandated reporting area, so this is a cultural change. This is a change from a reporting culture of naming and blaming to one of learning and sharing. The system design is really there to share the data. We want to be able to share the incidents or errors that occur back with the institutions where they occurred, do that in an aggregate way so that they can look at other institution incidents, and then use that data to put in place safety strategies.
CMIRPS, from the beginning, is a cooperative venture. We have most of the players at play. Certainly in our initial consultations we include health care practitioners—nurses, physicians, pharmacists—those involved with the delivery of medications within the institutions.
So from our perspective, it's well linked right from the outset. It's a good concept of sharing that data. We're the data gatherer and we're to make sure that the data we gather is valuable, that the data set is useful, and that we find mechanisms to share that in a privacy-sensitive way.