What is Medisa
The problem Medisa solves and how a conversation becomes a SOAP note.
Medisa is a voice-to-EMR platform: a doctor records the consultation, and AI turns it into a structured medical note in SOAP format — Subjective, Objective, Assessment, Plan.
The problem it solves
Writing up a medical record eats time that belongs to the patient. Doctors type while listening, or postpone documentation until the end of clinic when the details have already faded. Both cost something: the first splits attention, the second costs accuracy.
Medisa moves the typing to the AI. The doctor talks to the patient as usual, then reviews a draft that is already structured.
How it works
SATU SEHAT is Indonesia-only
Submission to SATU SEHAT applies only to health facilities registered in Indonesia that hold credentials from the SSP / REGFASYANKES portal. Everywhere else the rest of the flow — recording, transcript, SOAP, and the on-chain integrity proof — works exactly the same. See SATU SEHAT Integration.
Record. The doctor starts recording in the app. Audio is written to the device first, and is saved automatically every 30 seconds while the recording runs.
Transcribe. Once the recording is finished and uploaded, the AI transcribes the conversation. The spoken language is detected automatically, so the transcript follows what was actually said.
Compose the SOAP note. The transcript becomes a structured SOAP note, with citations back to the part of the transcript each point came from, and ICD-10 codes where they can be detected.
Review. The doctor reads the draft, corrects what needs correcting, and saves it. This step cannot be skipped — an AI draft is not a final document.
What sets it apart
It works without a connection
Recordings go to device storage first, not straight to the server. If the connection drops mid consultation the recording is still safe; upload and processing resume on their own once the device is back online. Re-sending the same recording does not consume quota twice.
The transcript follows the spoken language
The transcript is always in the language of the conversation and is never translated or overwritten. Only the SOAP content is translated, and that happens in the background so it never holds up saving the record. Any translated SOAP view carries its translation status and an AI disclaimer.
One account, many devices
Medisa runs as a web app at app.medisa.io, as an Android app on Google Play, as an installable PWA on iOS, and as a browser side panel extension for pasting results into an existing hospital system. A standalone desktop app is coming soon. Details in How to Access Medisa.
Built for compliance
- Medical records and patient identities are encrypted at rest.
- Every significant action is written to an audit log that cannot be altered.
- Each medical record can carry an on-chain integrity proof, so silent changes are detectable.
- Outpatient consultations can be submitted to SATU SEHAT as FHIR R4.
For clinics and hospitals
Beyond individual accounts, Medisa supports clinic organizations on a per-seat model: the owner buys seats, assigns them to doctors, and controls who can see what. See Creating an Organization.
For integrators
Other systems can use Medisa's voice-to-SOAP capability through the developer API, with API key authentication, webhooks, and usage metering. API access is granted per institution — talk to the Medisa team for credentials and the technical documentation.
Architecture at a glance
Medisa has four layers: the apps a doctor uses, the API that serves them, the AI layer that turns speech into text, and the storage and integration layer behind it.
A few design decisions shape how Medisa behaves:
- Device first, server second. Recordings are written to device storage before they are sent. The server is never a single point of failure during a consultation.
- Processing is asynchronous. An upload returns a receipt immediately, and transcription progress is streamed to the app. The doctor never waits on a blank screen.
- Translation and SATU SEHAT submission run through queues. Both happen in the background, so neither ever holds up saving a medical record.
- Encryption is per data category. Medical records, patient identities, and payment data use separate keys, so one exposure does not open everything.
- The integrity proof is separate from the content. What goes on-chain is a fingerprint of the record, not the record. Patient data never reaches a public network.
Subscription and billing
Medisa subscriptions are based on a monthly recording-hour quota. Quota is counted from the duration of processed audio and resets at the start of each period.
Pick a plan. Each plan carries a monthly allowance of recording hours. Choose the one closest to your consultation volume.
Pay. An invoice is issued through the payment gateway, and the subscription activates once payment is confirmed. Monthly and annual cycles are available; the prices that apply are shown on the subscription page inside the app.
Use it. Remaining quota is visible in the app, and you are notified as usage approaches the limit.
Renew or upgrade. Reminders go out before the period ends. If quota runs out early, you can add hours or move up a plan.
Also worth knowing:
- Organization quota is per seat. A clinic buys seats and assigns them to doctors. See Adding Organization Seats.
- Vouchers can be applied at payment when available.
- The price you lock in stays yours for as long as the subscription runs, even if the plan price rises for new customers.
For institutions
Hospitals, clinic groups, and health-system vendors are rarely served well by the standard plans. Three routes exist, and they stack — start with the lightest and go deeper once the value is proven.
| Route | What it is | Best for |
|---|---|---|
| The free plan | An ordinary account at no cost — every new signup starts here | Trying it yourself — judging the result before talking to anyone |
| A custom quota | Extra hours granted on top of the free plan by the Medisa team | A small-scale rollout — one department or a handful of doctors running without a subscription |
| API access | Medisa's capability called from your own system | Institutions that already run a HIS/EMR and want doctors to stay inside it |
| Medisa Enterprise | A dedicated environment, with negotiated quota and seat counts | Institutions with data isolation, compliance, or whitelabel requirements the shared service cannot meet |
Start on the free plan
The fastest route, and it asks nothing of you. Sign up a few doctors, record some real consultations, and judge the result yourself. No integration, no installation, and no need to talk to anyone first.
Use it to answer the decisive question before any other: will your doctors actually use it, and are the notes good enough for your practice? If the answer is no, you have spent nothing.
Once it is proven, move up to a paid plan for more quota, or on to one of the routes below.
A custom quota on top of the free plan
The free plan's allowance is enough to try Medisa, but not to work in it daily. For that, the Medisa team can grant custom quota on top of the free plan — no subscription required first.
This is the usual route for a small-scale rollout: one department, one unit, or a handful of doctors genuinely using Medisa in day-to-day practice, with the hours sized to their volume. It also suits a proof of concept that worked and needs to keep running while the institution decides on a larger arrangement.
Mention the rough number of doctors and their monthly consultation volume when you get in touch.
API access
Medisa runs behind the scenes. Your system does the recording and the display; Medisa returns the SOAP note, the ICD-10 code, and the FHIR bundle over the API.
This fits when your doctors already live in one system and moving them to another would only add friction. It needs engineering work on your side.
API documentation is issued per institution
The technical reference, credentials, and sandbox keys are not published on this site. They go to institutions that have agreed to the integration route — talk to the Medisa team to get started.
Medisa Enterprise
A Medisa instance that stands alone: a separate database, your own domain, and configuration that can extend to your institution's branding. This is also the route where quota and seat counts are negotiated around your needs rather than taken from a published plan.
It is the answer when data must not share infrastructure with other tenants — usually because of internal policy, audit requirements, or a third-party agreement. It is provisioned by the Medisa team rather than through self-service signup, and comes with its own SLA.
The three combine
The usual order: start on the free plan to prove the value in one department, add the API integration once the doctors are comfortable, then move to a dedicated environment when the rollout reaches the whole institution. You do not have to decide it all up front — talk to the Medisa team about a sensible starting point.
Referral program
Medisa runs a partner program: you introduce Medisa to other doctors or clinics and earn a commission on the subscriptions they start.
| Terms | |
|---|---|
| Commission | 7% of subscription value for your first 25 conversions, 5% from the 26th onwards |
| Annual subscriptions | Commission is paid up front in the first month, calculated on the annual value |
| Payout | End of each quarter, by bank transfer, within 14 working days |
| Minimum payout | Rp 500,000 |
How it works, briefly: register as a partner and provide your bank details, receive a unique referral code, then share it. Anyone who signs up with that code and becomes a paying customer is recorded as your referral.
Worth reading closely
Commission applies only to active paying customers — free-plan users and anyone who cancels within the month do not count. The rate is locked per referred user at their first conversion: your first 25 stay at 7% for as long as they subscribe, even once later conversions have moved to 5%.
The full guide — joining, KYC, how commission is calculated, and payouts — is in Referral Partner.
Limits worth knowing
Medisa is not a diagnostic tool
Medisa documents what was said during a consultation. It does not make diagnoses, does not recommend treatment, and does not replace clinical judgement. Every medical decision stays with the doctor.
- Transcript quality follows audio quality. A very noisy room or a distant microphone will reduce accuracy.
- A SOAP draft can mishear or miss detail. That is exactly why the review step is mandatory.
- SOAP translations are AI-generated and labelled as such; for legal purposes, refer to the original language version.
Next steps
- Common questions: FAQ
- Terms used across this documentation: Glossary
- Straight into the app: Creating a New EMR