Skip to content

Collaboration Education

mdBriefCase

Medical education platform, first version

The first version of an accredited continuing-education platform for doctors.

Visit site
Client
mdBriefCase
Industry
Education
Year
2022–2023
Status
Delivered
doctors registered on the first version
5,500 doctors registered on the first version
accredited courses running on it
15 accredited courses running on it

Context

For a doctor, continuing education is not optional. Credits are what keep a licence current, which means the certificate at the end of a course is the product, and the videos are how you get there. mdBriefCase delivers that education online, and in 2022 it needed a first version: the one that had to show the model worked before anyone would fund making it bigger.

The problem

The machinery behind an accredited course is not small. Enrolment, video, an exam, a pass mark, proof that this doctor finished this course on this date, a certificate that stands up afterwards, and separate roles for the doctors and the people running it. Built from scratch, that is most of six months, and none of it answers the question the first version actually existed to answer, which was whether doctors would sign up and pay. The harder problem was that the business model itself was still moving. Subscriptions, registration types, payments: a first version that has to prove a model is being built while the model is still being decided, and the scope moves under you. That is normal, and pretending otherwise is how these projects are lost.

The solution

Two systems, each doing the thing it is actually good at. Moodle runs the teaching: the course catalogue, the enrolments, the video, the exams, the pass marks and the certificates. WordPress, used headless, is the product the doctor meets: the face of it, the registration types, the subscriptions and the payments. A REST API joins them, so a doctor signs up and studies in one place and never knows Moodle is there.

That split is the whole decision. A raw Moodle looks like a university LMS, which is the wrong thing to sell to a practising physician. A platform built from nothing would have spent the six months rebuilding accreditation machinery that already exists and is already trusted, to answer a question about the business instead. Picking the boring component for the regulated half is what left the budget for the half that was genuinely unknown.

The existing data was exported and migrated in, so the first version launched with the catalogue already on it rather than empty.

What it does

  • Course catalogue, with registration types, subscriptions and payments
  • Doctor sign-up, with the teaching served from Moodle behind a WordPress front
  • Online video, end-of-course exams and the certificate that follows a pass
  • Separate roles for doctors and for the people administering the platform
  • REST API between the headless WordPress front and the Moodle engine
  • The existing catalogue exported and migrated in, so it launched with content

What happened to it

It has been developed well beyond that version since, by other hands. That is the outcome a first version is for: it earned the investment that replaced it.

I am named here for six months of 2022 and 2023, as the developer on a team of three, a project manager and a UI designer and me, working through AdhocWorks rather than under a direct contract. The platform doctors use today is not the one I wrote, and it would be easy to let that blur.

My role

Full-stack developer, and the only one on it, in a team of three at AdhocWorks with a project manager and a UI designer. Six months, delivered through AdhocWorks rather than as a direct contract with mdBriefCase.

Built with

MoodleWordPress (headless)PHPREST APIs
Web DevelopmentCustom SoftwareSaaS

Related services

Other work

Built, shipped, and still running.

View the full portfolio

Something similar on your side?

If this looks like the problem you have, the first conversation costs nothing.