DermaScope

● live in clinics

Clinical photography with before/after comparison.

In plain words: Before/after clinical photos, with consent.

Clinical · Full PHI · Dermatology · Plastic & Cosmetic Surgery

What DermaScope does

Consented clinical photos with before/after side by side, organised by body site across visits. The consent is structural: the consent-engine check and the photo commit in one transaction, and the consent record id sits NOT NULL on every photo row. Built for dermatology and aesthetics, where the photograph is the outcome measure.

How you actually use it

  1. Record the consent firstFind the patient and record photography consent. Without it there is no photo: the consent id is a NOT NULL column on the image row, not a policy somebody remembers.
  2. Name the body siteLeft cheek, scalp, right forearm — the site is what every later comparison hangs on, so the screen asks before it takes anything.
  3. Take the photoIt uploads, is checked, and lands on the visit under the tenant’s own storage prefix.
  4. Compare side by sideTwo dates of the same site sit next to each other with a divider you drag — which is the whole outcome measure in dermatology and aesthetics.
  5. Withdraw when askedA withdrawal is recorded with its reason and stops new photos on the spot; the ones already taken stay in the record.
See it on screen
Live product
01Photos — Before/after clinical photos, with consentCaptured from the running demo clinic
DermaScope — Photos — Before/after clinical photos, with consent
1 of 1

Connected to

Read out of the code, not the brochure: each app below is here because one service queries the other’s tables. Install either side and the hand-over is already wired.

Reads from · 1
Hands to · 1
See the whole clinic →

What it reads

visitsconsent

What it writes

imagescomparisons
Same patient record as every other app — nothing is copied into a silo. Data class: Full PHI.

What it does not do

No photo without a consent record — the database column refuses, not a policy. Withdrawn consent stops new photos on the spot. No photo leaves the tenant: object keys live under the tenant prefix and downloads are short-lived signed URLs.

Every app page carries this section. A listing with only benefits is an advertisement.

Questions clinics ask

What data does DermaScope read and write?

DermaScope reads visits, consent and writes images, comparisons. Its data class is Full PHI. Every app works on the same patient record — nothing is copied into a silo.

What does DermaScope deliberately not do?

No photo without a consent record — the database column refuses, not a policy. Withdrawn consent stops new photos on the spot. No photo leaves the tenant: object keys live under the tenant prefix and downloads are short-lived signed URLs.

What happens to our data if we uninstall DermaScope?

Images stay under retention policy; export on request.

Is DermaScope available today?

Yes — DermaScope is live in clinics today. Set up your practice on MedAppz and install it from your dashboard.

Ask about DermaScope

Want to see DermaScope running on your own patients?

Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.

We use your name, phone number and clinic name for one thing: to answer this enquiry about MedAppz. It is stored on our own server, in the single region our trust centre names, and it is not sold or passed to anyone else.

Email us

You can withdraw either at any time: write to hello@medappz.com, or tell whoever calls you, and we will delete what you gave us.

Runs alongside — same specialty, same record
More clinical apps
Featured inDermatologyPlastic & Cosmetic Surgery