Clinical Edify

The client and the market

Clinical Edify delivers continuing education to healthcare professionals. Its learners are clinicians who have to keep earning continuing education (CE) credits to stay licensed, and its larger customers are hospitals that enrol staff in bulk and need to show that the training was completed. That gives the platform two audiences with different needs: the individual who wants to finish a course on a phone between shifts, and the administrator who needs a report that will stand up to a compliance review.

The Challenge

Clinical Edify needed a scalable platform to deliver continuing medical education to healthcare professionals, with tracking for CE credits and compliance requirements. Specific challenges included:

• Managing complex CE credit requirements across different medical specialties
• Ensuring video content security and preventing unauthorized sharing
• Integration with healthcare credentialing systems and state boards

Each of these is a trust problem as much as a technical one. A certificate is only worth something if the hospital or board receiving it can check it. A paid course is only a business if the video cannot be passed around freely. And credit rules that differ by specialty have to be modelled exactly, because a learner who completes the wrong course has lost time they cannot get back.

Our Solution

We built a learning management system (LMS) with video hosting, progress tracking, automated certifications, and integration with healthcare credentialing systems.

The design choices follow from the two audiences. For learners, courses are video first with progress saved as they go, quizzes and assessments that gate completion, and a mobile app so a course can be finished away from a desk. For organisations, there is bulk enrollment so a hospital can register its staff at once, an analytics dashboard for administrators, and SCORM compliance so enterprise clients can bring the content into the systems they already run.

Credit tracking sits between the two. When a learner passes an assessment, the platform records the CE credit, generates a certificate, and makes that certificate verifiable, so the person receiving it does not have to take the learner's word for it.

How it works for a learner

1. The learner, or their employer through bulk enrollment, signs up for a course.
2. They work through the video lessons on the web or in the mobile app, with progress tracked.
3. They complete the quiz or assessment that closes the course.
4. The platform records the CE credit and issues a certificate that can be verified.
5. Administrators see completion and credit data in their dashboard and can report on it.

Key Features Delivered

Technologies Used

React with TypeScript, Node.js backend, PostgreSQL database, Vimeo for secure video hosting, Stripe for payments, and custom APIs for credentialing integration.

Each piece covers one of the challenges above. Vimeo handles secure video delivery so course content is not simply downloadable, Stripe takes payments for paid courses, PostgreSQL keeps enrollment, progress and credit records in one relational store that reporting can query, and the custom APIs connect the platform to the credentialing side.

See it

A walkthrough of the web application is on our Clinical Edify video page.

What a similar platform can take from this

In professional education, the certificate is the product. Learners pay for the credit, and employers pay for proof of completion, so verification, credit rules and reporting deserve as much design attention as the course player. Decide early which enterprise standards you will support (SCORM here) because hospital customers will ask, and treat mobile as a first class way to finish a course, not an afterthought. Our guide to educational app development for medical and health training goes deeper on these decisions, and the education industry page collects our other learning projects.

This page describes the platform only at the level already public. The domain previously linked here no longer points to the platform, so we no longer link to it.