Grant Dyer: Hello everyone, thank you for joining today. I really appreciate you making the time. For anyone I haven't met, my name is Grant Dyer and I lead our Customer Success team here at Orah. Our team owns onboarding, ongoing enablement, adoption, and support — basically everything that happens after you've partnered with us, to make sure you're getting real value out of the platform.
Today's session is a practical one: medication management. We're going to walk you through the setup and safe administration of the new module. The goal is to make sure you leave with a clear, step-by-step understanding of how to configure it in a way that fits your on-the-ground process, and how to use it confidently day to day to support safe, consistent medication administration.
A little context on why we're running this: we've heard from a lot of schools that medication workflows are one of those areas where almost working isn't good enough. It needs to be clear, auditable, and easy for teams to follow — especially when you have shift changes and multiple staff involved. This webinar is part of how Customer Success supports you beyond the initial rollout. We'll run targeted training sessions like this to help you strengthen specific workflows and get more value out of Orah.
With that, I'll pass it over to Emily DeRoche, one of our Customer Success Managers, who will be running today's session. We also have Zoab and Ram from our onboarding team, and Alexis, another Customer Success Manager. Take it away, Emily.
Emily DeRoche: Thanks, Grant. Today will be a 45-minute session with about 15 minutes at the end for Q&A. I see a lot of familiar names on the call, so great to have so many of you here. Good morning, good afternoon, or good evening depending on where you're joining from — and hello if you're watching the recording.
This session is for anyone who could be involved with medication management: health center teams, boarding staff, admins, and IT staff who will be helping with setup and access. The goal is to provide the initial training to get you started, and of course our team and support desk are available for anything that comes after.
We'll start by talking about why medication management matters, what led us to build this module, and a high-level overview of what it includes. Then I'll hand it over to Zoab for a live demo, and we'll close with dedicated Q&A.
Emily DeRoche: When we talk to schools about medication, we hear a consistent theme: the stakes are high, the environment is busy, and the systems are often pieced together. Maybe it's a binder, a spreadsheet updated between shifts, sticky notes, handoffs, or a pastoral note in Orah. We know that's how a lot of schools track medication administration, and it can work — until it doesn't.
For instance, a student shows up during shift change with a line at the door, or a student with a daily prescription forgets to come in and staff don't catch it because it's too busy. It's easy for things to fall through the cracks, and it's critical that they don't. It's a matter of safety, compliance, and trust with families.
That's the gap the Orah Medication Management Module is built to solve — bringing structured, safety-first workflows into the day-to-day reality of school life without adding administrative burden.
It's not just about logging a dose. It's about making sure the right student receives the right medication in the right amount at the right time, with the right context. It's about being able to confidently answer questions like: What was given? Who gave it? When was it given? What changed afterward? Are we running low on stock?
Instead of isolated logs and manual reconciliation, we built one connected workflow that ties together the medication catalog, prescriptions, over-the-counter inventory, and administration records — all in one place.
When a school adopts the Medication Management Module, the goal is simple: make medication administration safer and easier every day. There are four outcomes we aim for:
1. Safety-first administration. Reduce missed steps and avoidable errors by giving staff a consistent workflow every time. The module brings student context forward, supports warnings, and makes administration feel like a guided safety process — not an informal checkbox.
2. Audit-ready records. Schools should always be able to see who administered what, when, and what changed afterward. The module preserves full history so records are complete and defensible without any extra preparation for audits.
3. Less operational overhead. Fewer paper logs, fewer spreadsheets, fewer risky handoffs between staff and shifts. When the workflow is centralized, staff spend less time tracking things down and more time caring for students.
4. Better visibility at a glance. Staff should be able to see what's due, what's overdue, and what's running low. That visibility reduces last-minute surprises and helps schools stay on top of things.
So what does that look like in practice?
The module starts with a medication catalog — the single source of truth where the school defines medications once, with consistent details: names, types, units, strengths, and directions. Validation rules keep the catalog clean, because everything downstream depends on it.
For over-the-counter medications, we support inventory tracking — a live medicine cabinet view where stock updates as administrations are recorded. Staff can see low and out-of-stock indicators, which means fewer surprises.
For prescriptions, the school manages prescribed medications, schedules, and workflows. Active prescriptions are organized by overdue and upcoming, supporting daily, multi-dose, and custom schedules.
And then there's the dispensary — the day-to-day operational view where staff record administrations and review a chronological log. Edits are tracked with full history for compliance and accountability. Individual student profiles also show a complete history of prescriptions and administrations.
The goal is not to add complexity. It's to reduce risk, reduce overhead, and increase confidence. When medication management is structured and fully traceable, staff feel supported, leadership has clarity, and students are safer.
I'll now hand it over to Zoab, who will walk through the module and share best practices for setup.
Zohaib Siddiqui: Thank you, Emily. Let me share my screen.
Let's approach this from the perspective of someone who's just been introduced to the module and wants to get started as simply as possible. You're on your Orah account, you go to Student Care, and you see Medication. Open it up and you'll see Dispensary, Prescriptions, and other options we'll explore. But first, let's just administer a medication to a student who's just walked in.
Click Administer Medication. You'll see a list of all students. Select the student — let's say Adam Norton. Then choose whether it's an over-the-counter medication or a prescribed medication. If he's just come in for something like Dolol because he's not feeling well, you select the medication, click Administer Medication, add any relevant notes, confirm the dose and time, and save. That's it. The timestamp, who gave it, what was given — everything is captured automatically.
The same process applies for prescribed medications. You select the student, choose from their active prescriptions, add notes, and administer. Simple and fast.
Now let's look at the setup side. In the top right corner of the screen, you'll see Medication Settings. Click that to access the catalog — a list of all your medications, filterable by type: OTC or prescribed only.
To add a medication, click Add Medicine. Give it a name, add the manufacturer, select the type, specify the unit (liquid, tablet, capsule, etc.), add the strength, a description, dosage restrictions, and any other relevant details. Save, and it's in your catalog.
A useful tip: at the start of the school year, go through your existing medication list and add everything to the catalog so you're ready to go.
From the Dispensary view, you can see a log of every medication administered across the school. You can search by student name or medication, and filter by various criteria to narrow things down.
In Prescriptions, you can see all active and past prescribed medications. Open any student to see the full details of their prescription — when it was created, who created it, and the full administration history. To add a new prescription, select the student, add the prescribing doctor, set the course duration, select the medication, fill in the details, and optionally attach a photo of the prescription. You can also restrict who is authorized to administer that specific medication — for example, limiting it to the chief nursing officer or specific named staff.
In Inventory, you can see all OTC medications and their current stock levels. One thing to note: in this first version of the module, stock is organized by house or dorm. For day schools without houses, we can set up a common "Schoolhouse" so you can still use the inventory feature. We're also working on the ability to manage inventory independently of houses, and feedback on that is welcome.
To view medication history for an individual student, go to their profile and select the Medication tab. You'll see their active prescriptions and a full administration history — every dose recorded, with timestamps and details of who administered it.
Grant Dyer: On permissions: access in Orah is role-based. For medication management, we typically recommend splitting access into a few groups. First, staff who administer medications — they can view student medication details and record administrations. Second, supervisors and health center leads — they can also edit medication setup and review history for oversight. Third, broader staff — in most schools, you'd either restrict access entirely or give view-only access to those who need awareness but shouldn't be recording anything.
The key point is that not everyone needs access to everything. We can keep it tight so only the right staff see sensitive information and only authorized people can make changes, while still maintaining a full, auditable record of every administration. We're happy to help you configure this based on your roles.
Q: Is this module available on the mobile app?It's fully functional on desktop for now. Mobile app support is coming and we'll update you when it's released.
Q: Will it integrate with medication modules from other systems like iSAMS or Magnus?Not at this stage. It's currently an independent feature within Orah. We can pull allergies and conditions from Magnus, but not medication data. We'd encourage you to submit that as a feature request through Feature Base.
Q: How does this work for off-campus trips, sports, and weekends?You assign trip or duty staff the appropriate permissions so they can view student medications and record administrations while off campus. The key benefit is that everyone sees the same up-to-date medication history — nothing relies on paper notes or memory. A simple handoff workflow before the trip confirms what's due, who's carrying it, and any special instructions.
Q: What's the audit trail like?You can view the audit trail at two levels. At the student level, open their profile and go to the Medication tab — you'll see a full history of every administration, including timestamps and who recorded it. At the school or dorm level, the Dispensary view shows a chronological log of all administrations across the school. You can filter by dorm, student group, or administration status.
Q: What about compliance with school inspection bodies?All features we build operate within our existing security and compliance framework, which covers GDPR, HIPAA, and related certifications. If there's a specific inspection authority you need to verify against, reach out and we can look into it.
Emily DeRoche: That looks like all the questions for today. If anything comes up after this, our chat support is available in the bottom right corner of your Orah account, and our team is always happy to help. You can also submit feature requests directly through Feature Base — accessible via the Orah logo at the bottom right of your screen. Requests can be upvoted and commented on by other users, so it's a great way to have your voice heard as the module develops.
Grant Dyer: Thank you everyone for attending. You can also reach us at support@orah.com, and if you'd like a hand getting this module set up, don't hesitate to reach out — we're happy to jump on a quick call. Bye everyone.
Zohaib Siddiqui: Thank you all.
‍
