Healthcare UX design that patients, clinicians and admin teams can rely on

It depends on the number of user roles, the core flows, the platforms, how much research the product needs, the compliance and clinical safety reviews, and whether my team builds it too. A patient app with a clinic dashboard is two products on one data model, and the scope says so. After a free 30 minute intro call I write a scope and give you one fixed quote for the whole project. No retainer and no hourly billing.

There is no HIPAA certification for a design or a designer. HIPAA binds covered entities and their business associates. What I do is design the parts of the rule that show on screen: access control, audit history, sign-in for each person and session warnings that keep the draft. Your counsel decides how the rule applies to you, and I make sure the design can follow that decision.

An agency suits you if you need many people across several large products at once, or in-house regulatory staff. If you want senior people on one product, a fixed quote and the same team designing and building, my team fits better. You work with me directly, and in reviews with the designers and developers doing the work. Book a free intro call and I will tell you honestly which fits your project.

Yes. When your API exposes FHIR resources such as Patient, Appointment, Schedule and Observation, I name the screens, fields and states the way those resources do, so the design and the integration agree. My team builds front ends in React and Next.js that connect to your APIs. The integration with a specific EHR is planned with your engineers, because each vendor's access and limits differ.

It might be. The FDA uses the IMDRF definition of software as a medical device: software intended for one or more medical purposes that performs them without being part of a hardware device. Intended use is the key, and screen copy can change it. Ask a regulatory specialist early. If the answer is yes, I design with IEC 62366-1 usability engineering in mind and work with your regulatory lead on use scenarios and testing.

It depends on the number of roles and screens, how much research the product needs and how many review rounds your clinical and compliance leads want. A focused dashboard is usually a matter of weeks, not months. Your written scope after the intro call sets out the timeline flow by flow, with the review checkpoints marked, so you can plan a launch on a real schedule rather than a guess.

Always. WHO estimates that 1 in 6 people experience significant disability, and many patients are older or unwell when they use the product. Every patient screen meets WCAG 2.2 level AA: text that resizes to 200%, targets of at least 24 by 24 CSS pixels, time limits people can extend and sign-in without a memory test. I write patient words first and test the booking flow at 200% text.

Yes. For the NHS, I design with the DTAC in mind, especially its usability and accessibility area, so your answers have evidence behind them. For Europe, the GDPR treats health data as a special category, so consent rows are separate, unticked and say who sees the data. I work remotely from Dhaka with teams in the UK and Europe, and native speakers on your side approve the words.