Radiology report screen

A radiology product needed the screen where a radiologist reads a study and signs the report. I am the sole front-end developer and the client’s day-to-day contact.

Client
A medical-imaging company
My role
Sole front-end developer and client contact
Timeline
2026
Path
FDA 510(k) submission planned for 2027
Report · Chest PA Sample study
Sample chest X-ray in the viewer W 1500 · L −600
End-to-end 91 / 91Sign report

The problem

The screen shows medical images beside a structured report, so every field has to be correct, traceable and tested.

The product is on the FDA 510(k) path, so the front end needed written code standards that match what the code really does.

The API comes from another team, so the contract between the two had to be settled early and checked in code.

A chest X-ray, the kind of study the report screen displays

What it does

  • DICOM image viewing with Cornerstone3D
  • A structured report beside the image
  • Sign-in with DPoP-bound tokens
  • A typed API client checked with zod
  • End-to-end tests against the client’s API

My role

I own the front end and I am the client’s main contact. I worked from an 88-requirement spec and sent 29 written questions to the API team before writing code against it.

I also wrote the IEC 62304-style front-end code standards for the submission.

Decisions

  • Ask before building

    Before any integration code, I sent the API team 29 written questions on the spec, so gaps could show up on paper, where they are cheap to fix.

    Time spent before the first line of integration code.

  • Nine small pull requests, not one large one

    I shipped the integration as nine stacked pull requests, from DPoP sign-in to the typed API client, so each one could be reviewed on its own.

    More branches to keep in sync as review comments came in.

  • Check every response at the boundary

    A typed API client with zod schemas checks what the server sends before the screen uses it, so a contract change fails loudly in a test, not quietly in front of a radiologist.

    Schemas to maintain alongside the API.

  • Write standards that are true

    In the front-end code standards for the submission, I removed 14 claims that were not true.

    A shorter document, in which every line can be shown in the code.

Results

  • 91/91end-to-end tests pass against the client’s API
  • 88requirements in the spec I worked from
  • 9stacked pull requests for the integration
  • 14untrue claims removed from the code standards

Tech

Front end
Vue 3, Vite, TypeScript
Imaging
Cornerstone3D for DICOM
Contract
zod schemas and a typed API client
Auth
OAuth with DPoP-bound tokens
Testing
Vitest and end-to-end tests

Next case study

Two digital health platforms

A sleep-therapy platform and an AI mental-health companion, each built on AWS in Canada for a different client.

Read the case study

Hiring for a remote role in Canada? Tell me about it.

This opens your email app with your note, addressed to me.

Email
ekamxjot@gmail.com
Resume
Full-stack engineer resume (PDF)
Elsewhere
LinkedIn · GitHub