Hi Caity,
Thanks for submitting this excellent question! In my time here at Cayuse as a Professional Services Consultant and Product Manager, I have seen this handled in various ways by different institutions.
At OHSU, where I worked as an IACUC administrator, we did the first option you mentioned. We had the PI add all core procedures, locations, personnel, and drugs etc. to their protocol. The core had their own more general protocol as well. All work would be done under the original PI's protocol without transferring the animals. The OHSU IACUC felt that the protocol PI was ultimately responsible for all work done under their protocol for their experimental aims.
Another institution I'm working with opted to have a page in the protocol dedicated to collecting information about core work. The downside to this option, is that the information is not currently easily accessible in out-of-box reports. The product team is working on enhancing reporting tools. More info on that to come. :)
Things to consider:
- Animal oversight - who is ultimately in charge of the welfare of the animal during the core procedures? If an adverse event occurred during the core procedure, who would be responsible?
- Reducing administrative burden - We always want to reduce burden whenever possible for researchers, while balancing compliance risks, etc. Ways to reduce the burden of option 1 for PIs could be including core procedures, core agents, and other core details as pre-populated standard options for selection in the protocol form.
- Reducing risk - At OHSU, we felt that transferring animals between protocols could introduce compliance risk. The transfer to the core protocol and back to the PI's protocol must be clearly and accurately documented. If the animals suffered adverse consequences while under the core protocol, the core PI would presumably be the responsible party. Each institution needs to weigh this.
I'll keep you posted if I learn more about how other institutions handle this. From a Product Management perspective, I would also appreciate any ideas on how we can improve the applications to better and more efficiently handle core work.
Please always feel free to reach out to me directly. Again, many thanks for the great question!
Best,
Sarah
------------------------------
Sarah Josway
Professional Services Consultant
Cayuse
------------------------------
Original Message:
Sent: 06-27-2023 10:55
From: Caity Conley
Subject: Animal Oversight - How to describe adding shared equipment facility procedures to protocols?
Hi All,
Would anyone using Animal Oversight be willing to share how you deal with procedures at a core facility in terms of how they're described on protocols? We have a small shared equipment facility for imaging (not quite a core), which does non-invasive in vivo imaging. We are trying to develop a new process for how PIs with existing AO/IACUC protocols can add the imaging procedures to their studies. They would pick an appropriate time in their study timeline to transfer animals to the facility, have them imaged by an expert, then transfer them back to the animal facility to resume the original study.
Two potential models we've come up with for how to handle this are:
- Have all participating PIs add standard language for the imaging non-surgical procedures, drugs, use location, personnel, etc. to their original study protocols. This would be done as a comprehensive amendment for each protocol. (The standard language could be submitted to the IACUC as a stand-alone protocol by the imaging facility in advance, to get approval, but all relevant language would have to be added to the individual protocols of anyone having imaging done.)
- Have the imaging facility submit a stand-alone protocol for all the available imaging procedures. Any participating PIs who are interested in having their animals imaged would transfer animals to the imaging protocol and then have the animals transferred back to their original protocol afterwards. They would still need to submit an amendment to add the transfer to their study timeline. The stand-alone protocol would have to use general enough language to cover multiple strains, personnel, etc.
Each model has pros and cons, and we can't find much in the way of references to support or rule out either. Do you all use one or the other, or some other model entirely? Any advice would be appreciated. Thanks.
------------------------------
Caitlyn Conley
Administrative Support
Oakland University
------------------------------