Amela
Operator of a case-sharing service for doctors — platform build story
For confidentiality, company names, project names and system images have been replaced with pseudonyms and mock-ups.

A doctors-only case discussion platform, built in-house from scratch.

CaseLink is a closed community where only credential-verified doctors share and discuss clinical cases — a SaaS platform for doctors with around 10,000 registered members covering every specialty.

A space of trusted doctors only, protection of patient information, structured clinical presentation and accumulated knowledge — a platform meeting all four axes a doctor community needs, built in-house from scratch in 6 months. This is the story of that launch.

Credential verification
100%
Identity verified under invitation and review
Structured cases
30,000 +
Chief complaint through course, structured
Average reply
hourswithin
Threaded specialist discussion
Specialties covered
8 +
From cardiology to emergency medicine
01
CLIENT
About the client

One of the country's leading operators of SaaS for doctors, running a case-sharing service.

They operate a platform for sharing and discussing clinical cases, open only to doctors whose credentials have been verified. Doctors post cases in structured, de-identified form and other specialists advise in threads, so everything from consulting on a difficult case to accumulating clinical knowledge happens in one trusted place.

Connecting knowledge that is limited within one hospital to specialists across the country is the core of the business. Unlike a general social network, invitation and review assure the trustworthiness of participants, read-tracking stops discussion being lost, and the system itself protects patient information — a closed professional network for clinicians.

10,000+
Registered doctors, all specialties
30,000 +
Clinical cases shared
100%
Credential verification
BUSINESS FLOW — how the platform works
STEP 1
Credential verification & review
Credentials verified under an invitation-only model
STEP 2
Post cases in structured form
Post chief complaint through examination and images, anonymised
STEP 3
Specialists discuss in threads
Comment with differentials and advice, tracked by read status
STEP 4
Clinical knowledge accumulated and searchable
Discussion turned into a reusable asset
02
CHALLENGE
Design problems to solve

The four structural requirements the platform had to meet.

None of these were questions of technology choice; they were business requirements tied directly to trust, compliance, expertise and the accumulation of knowledge. Building from scratch demanded a design that satisfies all of them at once.

Create a space of trusted doctors only

If participants' credentials cannot be verified, the very trustworthiness of the discussion collapses. Where you cannot tell who is advising, no clinical decision can be entrusted.

Share while protecting patient information

Without anonymisation built into the system, case sharing becomes Personal-data and compliance risk. A design that relies on the goodwill of posters alone will fail.

Structure the clinical presentation

Leaving chief complaint through examination to free text means cases cannot be compared or searchedDiscussion never deepens, and what accumulates never becomes an asset.

Turn discussion into an asset instead of letting it wash away

Get the design of threads and read-tracking wrong and Valuable knowledge washes away. You lose track of who has read what and where the discussion stalled.

03
ARCHITECTURE
The architecture we built together

Case discussion, on a foundation you can trust, across four areas.

Credential verification, structured cases, privacy protection and the discussion platform — the four areas essential to trustworthy case discussion, all built in-house from scratch. Together with the client we delivered a design where doctors can consult on difficult cases with confidence and accumulate clinical knowledge while protecting patient information.

Amela
EXECUTION
6 months
Duration
42 man-months
Total effort
Area ①
Credential verification & review
Challenge

Design a mechanism that reliably verifies medical credentials under an invitation-only model.

Solution

Invitation, identity check and review of credentials and affiliation earn the verification badge

A closed design assures the trustworthiness of everyone taking part.

Area ②
Structured cases
Challenge

Clinical presentations need to accumulate in a form that can be compared and searched.

Solution

Diagnosis, age, sex, chief complaint, history, examination and images stored in a structured form

Cases can be compared and searched, giving discussion a base to deepen on.

Area ③
Privacy protection
Challenge

A mechanism that reliably strips identifying patient information is needed.

Solution

An anonymisation guide at posting time and automatic masking of attached images

Cases can be shared while the system protects patient information.

Area ④
Discussion & notifications
Challenge

Specialist discussion needs to be tracked without anything being lost.

Solution

Threaded comments, read-tracking and asynchronous notification

Discussion made visible and turned into an asset, so knowledge is not washed away.

BACKEND
Ruby on Rails Devise + OAuth + JWT PPundit SSidekiq
DATA
MySQL AWS S3 (ActiveStorage) KKaminari
FRONTEND
HStructured case form Verification badge UI
04
IMPACT
The value the platform creates

The circulation of clinical knowledge at the service operator, accelerated.

This foundation continuously produces business outcomes — better diagnosis, a space where sharing feels safe and a growing body of knowledge — rather than technical metrics.

A foundation for discussion you can trust

Because only verified doctors take part, the advice gathered can be trusted for clinical decisions.

Share while protecting patient information

Anonymisation and automatic masking make it possible to share cases while staying compliant.

A foundation that accumulates and reuses clinical knowledge

Structure and read-tracking keep discussion from washing away, so it can be reused as an asset.

Specialist knowledge within hours

Specialists across the country reply in threads, so difficult cases move quickly.

🩺
STAKEHOLDER
Posting doctor
Typically

Difficult cases tend to be carried alone on in-house knowledge.

On this service

Structured consultation with specialists nationwide.

Business impact

Diagnosis and treatment decisions improve

💬
STAKEHOLDER
Doctors in the discussion
Typically

On a general social network, neither credentials nor truth can be confirmed.

On this service

Professional discussion happens only with verified doctors.

Business impact

Knowledge can be shared with confidence

🔒
STAKEHOLDER
Patient and compliance perspective
Typically

Sharing cases easily becomes a personal-data risk.

On this service

Sharing with anonymisation guaranteed by the system.

Business impact

Learning while staying compliant

🏛️
STAKEHOLDER
Operations
Typically

Assuring the trustworthiness of participants and stopping knowledge from scattering are the usual problems.

On this service

Verification and read-tracking deliver trust and accumulation together.

Business impact

The value of the community keeps rising

05
DEMO
Three scenarios

Experience the case-sharing service for doctors through a working demo.

FLAGSHIP
Case feed & Discussion

A case feed filtered by specialty → structured clinical fields in detail → threaded comments with verification badges, read counts and posting.

Launch demo
Post a case

A structured form from chief complaint to physical findings, attachments and publish/draft status, with live preview and a reminder to anonymise patient information.

Launch demo
Doctor profile & verification

Verified profiles of credentials and career, with a verification badge, review status and a directory of verified doctors filterable by specialty.

Launch demo