Case Study · Healthcare · Education

ECAMS
A clinical system, not a course shop

European College of Aesthetic Medicine and Surgery — cadaveric anatomy, live models, fellowships, Clinical Club vs Associate Club. The software problem is progression and case logs, not a pretty brochure.

What shipped: public web catalog and membership (as on ecamedicine.com), delegate portal for pathways and case documentation, faculty assessment. Node.js API, PostgreSQL for membership, enrolments, ISO-aligned training records, fellowship cases. Payments and applications are data, not a mailto.

Web catalog Case logs ISO 29993/94/95
What we built Technology Live site
Clinical aesthetic medicine training environment
Clinical Club
Case logged
Fellowship stage
Cremona cadaver module · facial anatomy
Attendance is not completion — the case log is
ecamedicine.com
Web Catalog + membership
Postgres Club, pathway, cases
Node.js Applications API
ISO 29993 / 94 / 95
What we shipped

Public site + delegate portal. Faculty is a role.

Doctors do not get a native hunting-style app. They get a portal that survives a three-year fellowship.

Public web

Departments, faculty, Clinical vs Associate Club, apply. Matches ecamedicine.com.

Shipped

Delegate portal

Pathway stage, cadaver vs live vs immersion, upload cases, see faculty feedback.

Shipped

Faculty / admin

Assess, unlock next stage, ISO evidence pack. Not a shared inbox.

Shipped
The problem

A certificate PDF is not a pathway.

Standalone weekend courses left doctors with a badge and no return path. Applications sat in email. Fellowship case books were Dropbox.

  • No club stateClinical vs Associate was a sentence on a page.
  • No case objectBlepharoplasty photos lived on a phone.
  • No ISO trailWhen a standard was cited, nobody could export the evidence.
One real run

Dr. A. · Facial surgery pathway

  1. Apply — Clinical Club application. PostgreSQL membership_status = pending.
  2. Cadaver weekend — Attendance logged. Not marked complete.
  3. Clinic — Uploads supervised cases. Faculty comments on the same record.
  4. Return — Next Cremona date is a refinement, not a new random SKU.
Topic by topic

Education system, point to point

01 · Club

Clinical vs Associate

Before

Same mailing list.

After

Two membership objects. Hands-on only after Clinical.

02 · Pathway

Departments

Before

A grid of courses.

After

Medicine, face, breast, body, hair, genital, regenerative, AI — as on the site.

03 · Cadaver

Foundation first

Before

Inject on Monday.

After

Anatomy module is a prerequisite flag.

04 · Cases

Documented

Before

Phone camera roll.

After

Case log + assessment. Fellowship needs this.

05 · Mentorship

After the weekend

Before

Silence.

After

Faculty notes on the delegate record.

06 · ISO

Evidence

Before

A logo in the footer.

After

Records shaped for 29993/94/95 learning-service requirements.

Technology (from the live product)

Web + portal. Node.js and PostgreSQL for the clinical record.

The live site is the catalog and club story. The work we shipped is membership, applications, pathway stages, and case documentation — the difference ECAMS claims versus “conventional course providers.”

Source: ecamedicine.com (Clinical/Associate Club, cadaver + live + immersion, fellowships, ISO 29993/29994/29995, Dublin entity).

Web catalog Delegate portal Node.js PostgreSQL ISO records Fellowship cases
Public web

Departments, faculty, apply, ISO copy — the campus front door.

Delegate portal

Stages, cases, faculty review.

Node.js API

Applications, payments metadata, unlock next stage.

PostgreSQL

Members, pathways, case reports, assessment events.

Outcomes

What changed after go-live

Progression is a state

Return training is a row, not a vibe.

Cases are auditable

Fellowship assessment has files.

ISO is exportable

Evidence pack, not a footer badge.

Build yours

Need education that is a system?

Catalog + portal + PostgreSQL case logs — the ECAMS shape.

Start a conversation Back to portfolio