Clinical Edify web app video

Clinical Edify delivers continuing medical education to healthcare professionals. The brief was a platform that could scale to that audience and track continuing education credits against compliance requirements, which is where most of the difficulty lay.

Three challenges defined the project. First, CE credit rules are not uniform: requirements differ across medical specialties, so the platform had to model several credit regimes rather than one. Second, the course video is the product, so it had to be protected against unauthorized sharing. Third, completions had to connect to the systems that actually count them, meaning healthcare credentialing systems and state boards.

The result is a full learning management system. Clinicians watch video courses with their progress tracked through each one. When they finish, the platform generates a certificate automatically, and each certificate can be verified, so a third party can confirm it is real without phoning anyone. Credit tracking and reporting sit underneath, recording what each professional has completed and how it counts toward their requirements.

Integrations with healthcare credentialing systems are what turn the platform from a video library into a compliance tool. A clinician who completes a course should not have to re-enter it somewhere else, and an administrator should be able to report on completions in a form the receiving body accepts.

The platform supports thousands of concurrent users with enterprise-grade security. For education sold to healthcare professionals, both matter. Usage tends to spike around renewal deadlines, and the records the system keeps are the evidence a professional relies on when their licence is reviewed.

The web application is React with TypeScript on a Node.js backend, with PostgreSQL as the database. A relational database suits this domain: courses, modules, completions, credits, specialties and certificates are tightly linked records, and reporting across them is exactly the kind of query PostgreSQL handles well.

Video is hosted on Vimeo, chosen for secure delivery, which addresses the unauthorized sharing problem without building a streaming stack from scratch. Payments run through Stripe. Custom APIs handle the credentialing integrations, since those connections differ from one body to the next and rarely come with an off-the-shelf connector.

It is tempting to judge an education platform by its video experience, because that is what a demo shows. For continuing education, the part that decides whether the product succeeds is less visible. A clinician needs proof of completion that holds up. An administrator needs to answer the question of who has finished what, and by when, without exporting spreadsheets. A credentialing body needs data in the format it expects.

That is why we treat certification and reporting as core features on projects like this, designed and tested with the same care as the learner interface. A certificate that cannot be verified, or a credit that is recorded against the wrong specialty, is a failure that surfaces months later at the worst possible moment.

Video security was one of the three challenges named at the outset, and it is a problem every paid education product meets sooner or later. When the course itself is what the customer pays for, a single shared download can undercut the business. Clinical Edify addressed it by hosting video on Vimeo for secure delivery rather than serving raw files, so playback happens inside the platform for signed-in learners.

No protection is absolute, and we say so when scoping. The practical goal is to make casual sharing difficult and to tie viewing to an account, so that access can be granted, tracked and withdrawn. For certification products there is a second layer of protection built in: watching a leaked copy earns nobody a credit, because credit only comes from completing the course inside the platform.

The people using a continuing education platform are busy professionals fitting courses around clinical work. That shapes small decisions. Progress tracking has to be reliable, so a clinician can stop partway through a module and pick up in the same place on another device. The path from finishing a course to holding a certificate should be immediate, with no waiting for manual approval. And the record of what has been completed has to be easy to find when a renewal comes due.

These details rarely appear in a feature list, yet they decide whether professionals return to the platform for their next course or look elsewhere.

Payments follow the same principle. Stripe handles checkout, so a clinician can buy a course and start it in one sitting, and an organisation paying for its staff gets receipts it can file without chasing anyone.

If you run training that people must complete for a licence, a certification or an internal compliance programme, the same pattern applies: secure content, progress tracking, verifiable certificates and reporting that the receiving body accepts. Our SaaS development and portal development services cover this kind of build, and every engagement starts with a written scope and a fixed price per phase.

The video above shows the Clinical Edify web application in use. The case study covers the challenges, the solution and the stack in more detail.