Loading benchmark…
CEM Benchmark
Release 2026.4 · Reviewed October 1, 2026
Loading benchmark…
Publisher. The Clinical Education Management (CEM) Benchmark is published and maintained by HealthTasks. All vendors, including HealthTasks, are evaluated using the same published methodology and evidentiary standards based on publicly available primary sources. The benchmark is provided for informational and research purposes only and does not constitute an endorsement, certification, warranty, or guarantee regarding any vendor, product, or service.
Methodology. Scores reflect documented capability coverage based on publicly available primary vendor sources, including product documentation, help centers, knowledge bases, API documentation, and other primary-source materials available at the time of review. Scores are intended to measure documented capability coverage under the published methodology and should not be interpreted as measures of product quality, customer satisfaction, usability, market share, or overall suitability. A capability marked as not supported indicates that HealthTasks did not identify sufficient publicly available evidence to verify support under the published methodology. It does not necessarily mean the capability is absent or unavailable.
Process. Research is produced using AI-assisted analysis together with human review and is refreshed periodically. While reasonable efforts are made to ensure accuracy and consistency, errors or omissions may occur, and vendor documentation may change over time. Users should independently verify information before making purchasing, procurement, or business decisions. Machine-readable benchmark data and methodology are available at /benchmark/dataset.
Updates and Corrections. Vendors and members of the public may submit corrections or additional primary-source documentation for review. Submissions are evaluated using the same published methodology and evidentiary standards applied to all vendors. Accepted corrections may be incorporated into the current release, published in the benchmark changelog, or included in a subsequent benchmark release.
Trademarks. All company names, product names, logos, and trademarks are the property of their respective owners and are used solely for identification, comparative research, and informational purposes. Their use does not imply any affiliation with, sponsorship by, or endorsement from their respective owners.
How we score clinical tracking and clinical education management platforms: binary rubric, cited primary sources, semantic proof matching, and a public capability specification.
Capabilities
37
Binary scored
Modules
7
Functional areas
Vendors
7
Release 2026.4
Scale
Cited or not
Every capability is either cited or not — no partial credit, no inferred features.
Score = 1
Public vendor documentation with a direct URL and quotable excerpt that substantiates the capability.
Score = 0
No verifiable primary-source proof, or marketing copy too generic to document the specific feature.
module = supported ÷ total in module
overall = supported ÷ 37 capabilities
Unweighted. No popularity or market-share inputs.
What counts as proof, and how each capability is verified.
Product pages, help centers, or API docs — never third-party reviews alone.
Does the excerpt substantively satisfy the capability definition, even with different wording?
Store URL, verbatim quote, interpretive note, and match type (semantic or literal).
Semantic equivalence with verbatim excerpts — not keyword bingo.
Each supported capability requires a public URL and a verbatim excerpt. Proof is evaluated semantically— not by keyword matching alone.
Example citation
placement.site-directory
Click to expand — same pattern used in comparison tables.
Design choices that limit bias and over-scoring.
A capability scores as supported only when a public source URL is attached with a verbatim excerpt. No quotable proof, no score.
Evidence is matched on functional equivalence to the capability definition, not exact keywords. The quoted excerpt and a brief note must substantiate the claim.
A capability scores as supported only when the vendor documents the feature as native to their platform or as a vendor-operated service. Third-party partner products, integrations, or add-ons that require a separate vendor subscription or contract do not count.
Automated assistance is evaluated within each functional module (not as a separate platform category), preventing disproportionate overall credit for automation-heavy vendors.
Scores are derived exclusively from the capability rubric. Market share, search frequency, and brand recognition are not inputs.
Capabilities that cannot be verified from public documentation receive a score of not supported. The benchmark does not infer undocumented features.
Each release is immutable and dated. Score changes require documented evidence updates and a new release version. Expanding the rubric raises the bar instead of inflating leader scores.
All vendors are evaluated against the same feature definitions using the same evidence criteria, regardless of vendor size or tenure.
Release 2026.4 — 7 clinical education management platforms evaluated against the same rubric.
Canonical capability specification used for evaluation. Internal IDs are omitted from this view.
Manage multiple programs or tracks within one tenant.
Evidence bar: Public documentation of multi-program or multi-track administration.
Documented LMS, SIS, or other native product connectors.
Evidence bar: Public LMS, SIS, or connector documentation. A programmatic REST API with schema is scored separately.
SSO, security policies, or enterprise auth controls.
Evidence bar: Public SSO, security, or authentication documentation.
Public, authenticated REST (or equivalent) over core CEM objects with at least one write operation and vendor-hosted signed webhooks.
Evidence bar: Public API documentation an IT team can review covering reads, writes, and signed webhooks. LMS connectors, contact-sales “Open API,” or marketing “REST API Framework” copy with no schema do not count.
Automated account create/update from SCIM, just-in-time IdP claims, or a recurring IdP/SIS directory or roster sync.
Evidence bar: Public SCIM, JIT, or automated directory/roster-sync documentation. SSO into a pre-created account, one-time CSV import, or professional-services migration do not count.
Native agents that propose or execute mutations on live records with human review and an audit trail, including in-product tool-calling or MCP.
Evidence bar: Public documentation of human-in-the-loop agent actions on live CEM records. Chatbots, help assistants, or generative Q&A without record mutations do not count.
A product control that prevents or gates protected health information from entering the CEM, such as a scanner that blocks save or submit until identifiers are cleared.
Evidence bar: Public documentation of a native PHI gate or scanner. HIPAA policy copy, student HIPAA training requirements, BAAs, or encryption alone do not count.
The CEM can require MFA or 2FA for users as a product control.
Evidence bar: Public product or help documentation that the CEM can require TOTP, authenticator, SMS, or email OTP. IdP MFA via SSO alone does not count.
Students or preceptors can complete a core CEM workflow from a phone or tablet.
Evidence bar: Public documentation of a PWA, native app, or first-party mobile/any-device workflow (logging, clock-in, evaluations, or checkoffs). Desktop-only installers do not count.
CEM here includes clinical tracking, placements, evaluations, compliance, curriculum, and reporting.
Clinical education management (CEM) is the category name for the software nursing, medical, and allied health programs use to run clinical education. Buyers usually search the same market as clinical tracking, clinical placement or rotation software, student clinical logs, preceptor management, and competency tracking. CORE Higher Ed’s product is CORE ELMS (experiential learning management), so some programs search that name too. This benchmark is the public comparison dataset for those products.
HealthTasks product pages: experiential tracking · clinical placements · nursing. Machine-readable scores: dataset.