The physical therapy program down the hall already runs CORE ELMS. So when an administrator asks why the speech clinic can't just use the same system and save the department a line item, it's a fair question. The answer takes a minute to explain. CORE holds your students' placements, evaluations, and clock hours. It doesn't hold anything that functions as a patient's chart. If you're looking for a CORE ELMS alternative for university clinics, some version of that conversation is probably why.
Here's the part most comparison pages skip. CORE ELMS is good software doing a real job, and it earns a 4.7 out of 5 across 36 verified reviews on Capterra.3 The problem usually isn't quality. It's that a lot of directors typing "alternative" don't need a replacement at all. They need the other half of the system.
This post covers what CORE actually does, where the gap opens once your program treats patients on campus, what to ask about pricing, and how to tell which layer is the one failing you.
What CORE ELMS Actually Does
CORE ELMS is an experiential learning management system from CORE Higher Education Group, built around the externship and fieldwork process. It runs more than 30 modules.1
The list is specific, and worth knowing before you go shopping:
- SmartMatch scheduling that matches students, sites, and preceptors against customizable rules
- Student, self, and preceptor evaluations with automated reminders, grade calculation, and low-score alerts
- Affiliation agreement tracking with expiration alerts, plus preceptor license verification
- Student requirement tracking for immunizations, CPR, background checks, and HIPAA training
- Timesheets and absence tracking, with optional GPS and preceptor confirmation
- A document library, incident reports, reporting, surveys, and a messaging center
For a program whose students go out to placement sites, that's most of the job. The reviews reflect it, and clinical coordinators who spend their fall chasing expiring immunization records and matching 40 students to sites are not wrong to like it.
One detail worth checking for yourself. CORE's allied health page names occupational therapy and physical therapy, along with nursing, pharmacy, physician assistant, social work, psychology, counseling, dental, and several others. Speech-language pathology and audiology aren't on that list.2 That doesn't mean CORE won't work with a communication sciences and disorders program, and coverage changes, so ask them directly rather than taking a blog post's word for it. But it does explain a pattern: the SLP clinic is usually the program that inherits CORE from a neighbor instead of choosing it.
None of this is a criticism of the software. It's a description of the job it was built to do.
The Line Between an Education Record and a Patient Chart
Every accredited program keeps two records.
One is about the student. Where were they placed, which competencies did they meet, how many clock hours did they log, was their TB test current. The other is about the patient. Who are they, what happened in Tuesday's session, which diagnosis and service codes apply, who approved the note, what got billed.
CORE ELMS is built for the first record. A program that treats patients on campus runs on both.
Worth being precise here, because a director who actually uses CORE will spot a dodge. CORE's field experience logging does accept student-submitted work, including reflections, journals, assignments, and SOAP notes.1 That's genuinely useful for coursework and for showing an accreditor that a student produced clinical writing. But a SOAP note filed as a student's field-experience artifact isn't the same object as a note filed in a patient's chart: linked to a diagnosis and a service code, locked by a supervisor's approval, and readable by whoever treats that patient next.
Here's the test worth running on your own setup. A client finishes spring semester with one student clinician and comes back in the fall to a different one. Where does the new student read what happened last spring? If the honest answer is "the previous student's coursework folder," or "a shared drive," or "she'd have to ask the supervisor," you've found the gap. And it isn't a CORE problem. It's a missing record.
Everything else on the patient side has to live somewhere too. Appointment scheduling, therapy room reservation, copays, superbills, insurance claims. For a lot of programs that somewhere is a spreadsheet, or a private-practice EMR nobody designed with student clinicians in mind.
Where the Gap Shows Up in a Teaching Clinic
Most of the friction lands in the same five places.
A supervisor reviewing the note, not just grading the student. CORE's evaluation modules assess student performance and they do it well. A teaching clinic needs something else on top of that: a supervisor who opens a draft session note, leaves feedback inside it, and approves it before it becomes part of the patient's permanent record. ASHA requires direct supervision to be no less than 25% of the student's total contact with each client, occurring periodically throughout the practicum, with practicum time documented and verified by the program.4 Verifying the hours is an education-record job. Reviewing the note behind them isn't.
Caseload-level privacy. A student should see only the patients assigned to them. Placement systems are built around a student roster, not a patient roster with per-student access limits. That's the practical difference between a placement system and a university clinic EMR with student supervision built into the permission model instead of into your policies and procedures.
Two systems, one site visit. When CAA or another accreditor asks for hours and the documentation behind those hours, pulling from two systems that don't talk is how the semester-end spreadsheet gets born.
Double entry. A student logs 1.5 hours in one place and writes the session note in another. Nothing reconciles the two except a person with a free afternoon.
Setup friction, reported honestly. Reviewers who rate CORE highly overall still flag the same things. Settings live in "MANY different locations" that overlap and make troubleshooting confusing. Reporting draws "recurring difficulties/hurdles." SmartMatch configuration is complex without clear documentation.3 For a coordinator onboarding a cohort twice a year, hunting for a setting comes straight out of the morning she'd blocked for orientation.
What About CORE ELMS Pricing?
Straight answer: CORE ELMS pricing isn't published anywhere. Every review-aggregator listing routes to a quote request. That's normal for this category, and ClinicNote doesn't publish list pricing either, so this isn't a gotcha.
Since there's no number to compare, ask better questions instead:
- How does the price move when a cohort grows from 20 students to 35?
- Is it priced per student, per module, or per program?
- What does a second discipline on the same campus add?
- What's included in implementation, and what does onboarding each new cohort cost every term?
Then there's the cost that never appears on an invoice. Coordinator hours spent reconciling two systems. Student accounts rebuilt by hand every August. Accreditation evidence assembled from three places the week before a site visit. That's real budget, just spent in people's time instead of a line item.
Confirm current numbers and module inclusions with the vendor before you plan anything. Pricing changes, and the shape of the cost matters more than any figure you'll find secondhand.
If You Do Want a Different Placement System
Some readers genuinely do want a straight replacement, and it'd be unhelpful to pretend that question doesn't exist.
If your actual problem is placement matching and site coordination, the CORE ELMS alternatives worth putting on the list are Exxat, Typhon, HealthStream's myClinicalExchange, and Rotation Manager. For SLP programs specifically, CALIPSO is the system most programs already use for student clinical hours tracking software and KASA competency documentation, and it's built around CAA standards.5
ClinicNote isn't on that list and we're not going to pretend otherwise. We don't manage affiliation agreements, immunization compliance, or preceptor license verification.
What we'd say on a call is this: work out which layer is failing before you shop. Replacing the placement system won't produce a patient chart. Adding a patient chart won't fix broken placement matching. Programs that run their own clinic usually need both, working side by side.
What ClinicNote Covers Instead
ClinicNote is the clinical documentation and practice management layer. It produces the session records your clock hours are built on, and it works alongside CORE ELMS or CALIPSO rather than replacing them.
Supervision works the way a teaching clinic needs it to. Supervisors review student documentation in real time, leave feedback inside the document, and verify completion across a whole cohort before notes finalize. A director can see which notes are still sitting in draft without asking anyone.
Access controls are the ones university IT asks about by name: patient-level caseload restrictions so students see only assigned patients, multi-factor authentication, IP address restrictions, and role-based permission sets. ClinicNote is HIPAA compliant, and for programs holding both kinds of records, the permission model was designed with the FERPA side in mind too.
The patient-side operations an education record was never meant to cover are here as well. Appointment scheduling with room reservation. Superbills and invoices. Electronic claims through a clearinghouse. Patient portal intake forms. Real practice with CPT and service codes, which is the part students tend to arrive at their first job without.
Your templates come with you. Faculty send the SOAP notes, evaluations, progress reports, lesson plans, and treatment plans they already teach with, and we rebuild them as fill-out forms. You shouldn't have to change how you teach documentation to adopt software.
Thirteen disciplines run on one system, including SLP, audiology, OT, and PT. That matters when the same building holds three programs and your placement system names only two of them.
For proof rather than promises: 175+ clinics and 7,000+ users, including 117 speech clinics. When the University of Wisconsin-Milwaukee needed a custom compliance report on short notice, it was built in under a week, and thousands of diagnosis codes were added at the clinic's request. Full implementation runs about 60 days, the basics take one to two hours of virtual training, and every incoming cohort gets onboarding so the process doesn't live in one faculty member's memory.
Which Record Are You Missing?
The question was never whether CORE ELMS is good software. It is, for the job it was built to do. The question is which of your two records is missing, and a placement system was never designed to be the second one.
So before your next demo, write down two things: which system holds your students' hours, and which one holds your patients' charts. If the answer to the second is a shared drive, a stack of paper, or a private-practice EMR you're bending into shape, that's the gap to close first, whoever you end up closing it with.
Want to see what the clinical layer looks like when it's built for a teaching clinic? ClinicNote handles student documentation, supervisor review, scheduling, and billing for university SLP, audiology, OT, and PT programs. See how it works for university clinics and we'll walk through your program's setup, not a generic demo.
Sources
- https://corehighered.com/elms
- https://corehighered.com/core-for-allied-health
- https://www.capterra.com/p/265422/CORE-ELMS/reviews/
- https://www.asha.org/certification/2020-slp-certification-standards/
- https://www.calipsoclient.com/clinical-assessment-of-learning.html