If you've setup a study in Slope, then you're familiar with the concept of inventories, items, and low inventory alerts. For example, we might have a "Visit 1 Kit" (which is an inventory), which has many different items, each with their own serial, lot, and expiration date. If we set a low inventory alert of 12, Slope will trigger an alert when the available quantity of kits falls below that threshold.
Managing your inventory this way using Slope will make sure that you never run out of a specific type of kit. For most sites that start using Slope, this approach works out great and helps keep their inventory organized. However, there's an outlying problem that all sites will eventually run into: figuring out how much of a specific inventory they need for upcoming visits. While Slope has a great manual reorder tracking feature, sites still have to figure out how much to order, and it can be very difficult to estimate when there is no way to measure demand across all your inventory.
So that's where our new subject visit scheduling feature comes in. We've designed a simple and easy way for you to model the visit schedules for your study protocols within Slope, then associate the inventories you've already setup with specific visits in a schedule. Slope does all the number crunching and can keep track of what you have on hand versus what your subjects will need in the future, helping you know exactly how much to order from suppliers.
Our subject visit scheduling feature is in "beta" and will only make sense if you've already setup your inventories in Slope. Due to the nature of the data that's required, there's some setup time that is required to get it configured for your specific study protocol. We are encouraging our beta users to try it out on a "practice" workspace first, then once you're comfortable with the mechanics, trying it out on one of your smaller studies, or a study that is starting up soon.
To access this feature, you'll need to reach out to the Slope team and ask nicely, then we'll set it up for your user account. Please note that if you have other members on your team, they won't have access to it unless they're on the beta as well.
Let's get started
Ready to get this going? The first step is to create a subject visit schedule.