Medisa Documentation
Start here — what Medisa is, the problem it solves, and how to use this documentation.
A problem you will recognise
The consultation takes fifteen minutes. Documenting it often takes nearly as long.
Some doctors type while the patient is still talking — and lose eye contact at the moment it matters most. Others leave it until the clinic closes, then write from memory about a dozen patients who have started to blur together. Both end the same way: records thinner than the reality behind them, and time spent on administration instead of patients.
What Medisa is
Medisa listens to your consultation and drafts a SOAP note from it.
You press record when the consultation starts and stop when it ends. Moments later the draft is ready — with the conversation transcript and a suggested ICD-10 code alongside it. Your job is to read it, correct what needs correcting, and sign it off.
What Medisa does not do
Medisa does not diagnose, does not recommend treatment, and does not replace clinical judgement. It documents what happened in the room. Every note still has to be read and signed off by you — and the whole flow is built around that.
What changes
| Before | With Medisa |
|---|---|
| Typing while the patient speaks | Recording, and giving the patient your full attention |
| Writing notes from memory after clinic | The draft is already waiting to be reviewed |
| Note quality depends on end-of-day stamina | Consistent, because it comes from the conversation itself |
| Hard to trace where a statement came from | Every point traces back to the transcript and the audio |
| Retyping into the hospital system | Copy from the side panel, or integrate through the API |
| SATU SEHAT reporting done by hand | Submitted from a record you have already signed off |
Clinics get a further layer: one subscription for the whole team, central billing, and control over who can see what. Institutions that want to connect their own system can reach the same flow through the API.
Why this documentation exists
To make you good at using Medisa — not merely aware of where the buttons are.
Every guide page explains what happens behind the screen and which decisions are yours, not just the sequence of clicks. That matters because this is a clinical tool: knowing when a note deserves a second look counts for as much as knowing how to produce one.
What is in here
Two sections, readable in any order:
| Section | What it holds |
|---|---|
| Introduction | What Medisa is, plans and pricing, the FAQ, and the glossary |
| User Guide | Day-to-day workflows in the app, step by step, each with its own troubleshooting |
The API documentation for system integration is not published here — see What is Medisa.
Conventions
- Language. Available in Bahasa Indonesia, English, 中文, and Bahasa Melayu. The language picker sits at the bottom of the sidebar, and switching keeps you on the same page.
- Versions. The documentation is versioned. The picker is above the sidebar; by default you are reading the latest.
- Roles. Pages that require a particular role say so at the top, like Clinic Admin.
- Plans. Features limited to certain plans are marked too, like Clinic.
Where to start
New to Medisa. Read What is Medisa — how it works, the plans and pricing, and its limits. Then the FAQ for the questions that come up most.
You have an account and want to try it. Open Accessing Medisa, then Creating a New EMR. Those two pages are enough for your first consultation.
Running a clinic. Start with Organization Feature to understand the roles and permissions, then Creating an Organization.