Skip to main content

Feature requests

Feedback & Support → Feature Request.

Feature requests from clinicians are the single most useful signal we get, which is why the AI help around them is not behind Premium — free accounts get the whole thing.

The optional interview​

When you start a feature request, MedJot offers an AI interview: a few grounded follow-up questions about what you are trying to do, then a properly structured write-up of the request.

You review and edit the draft before it is sent. Nothing goes anywhere until you approve it, and every failure path in the interview ends at "send it as I wrote it" — a feature request must never be lost to a broken AI.

The interview is optional. Typing a sentence and sending it works perfectly well.

Why it helps​

The interview is grounded in what MedJot already does, so it can tell you when the thing you want exists — occasionally the fastest possible resolution — and it asks the questions we would otherwise have to email you about, which is usually the difference between a request being actionable now and in three weeks.

What happens next​

Every feature request is assessed automatically, whether or not you used the interview, and lands in a queue a person reads.

Requests are triaged for feasibility, value and effort, and duplicates are grouped — so a request that has been made before adds weight to it rather than being lost.

What makes a good request​

Describe the problem, not only the solution. "I need a button that does X" tells us less than "at the end of a job I have to retype the obs into our ePRF because…". The second lets us solve it a way you had not thought of, which is sometimes better and sometimes much simpler.

Say how often it bites and how much time it costs. Frequency is what moves things up a list.

Say what you do instead now. The workaround usually reveals the real constraint.

Things MedJot will not do​

Some requests are impossible by design rather than by priority, and knowing which saves you writing them:

  • Storing patient data on our servers. Clinical data stays on the device. This is architectural. See Data flows.
  • Integrating with trust systems. No ePRF, PAS or SCR integration.
  • Anything requiring a native app. MedJot is a PWA.
  • Drug dose data or a dosing calculator. See Overdose calculator for why.

Offline-first working also constrains anything that would need a live connection mid-report.

Following your request​

It is a ticket like any other — visible in My tickets, with a reply when there is something to say.