Writing Ends With the Encounter
The physician talks with the patient; the report is ready as the encounter ends. The burden of writing notes after the encounter, trying to remember, and closing files at the end of the shift disappears.
Encounter Decision Support System
Ssemora listens to the encounter and prepares a draft report that fits your template. Every sentence extracted from the recording is linked to its source in the conversation and to its second in the audio. It does not guess information that was not said; anything missing is flagged for you.
Cloud service, no installation · Separate, isolated setup per institution · Compliant with KVKK (Turkish data protection law)
The Problem
Which sentence a note is based on is not visible afterwards; a skipped question is never visible at all. Ssemora's real job is not writing notes but making you notice what is missing.
Typing notes into a screen takes attention away from the patient. Encounter time and eye contact suffer as a result.
Questions such as allergy history or current medications can be skipped in a busy clinic, and when the report is written the gap stays invisible.
It is hard to verify afterwards whether a written sentence was actually said in the conversation.
How It Works
Record the encounter from the browser, on a computer or a phone. You can also upload a ready-made audio file. If needed, photograph a wound, lesion, ECG or lab printout and upload it.
By default, the audio is converted to text with locally running speech recognition. In the transcript, speakers are labelled Physician, Patient and Companion.
The de-identified transcript is turned into a report and reasoned suggestions according to the institution's template. Every sentence extracted from the recording comes with its source.
You review the red and grey items in the Verification tab and approve the report. The approved report is locked.
Quick Demo
Read the sample scenario below aloud as if it were a short encounter conversation; Ssemora uses its real engine to produce the transcript, place the report into the template and build the evidence links. The texts are fictional; do not say any real patient information.
Audio is transcribed → speakers are separated → the report is placed into the template, with every sentence linked to the audio recording. In this demo you see these steps with the real engine and download the draft as Word; in real use, the verification panel, suggestions and approval step follow.
The live demo is currently closed. Write to us for a demo planned around your institution's templates.
Evidence Display
Select one of the report fields. If it has a basis, the sentence in the conversation and its second in the audio recording are highlighted; if not, the reason is written.
Draft Report (Example)
Conversation Transcript
Audio Recording
Why Ssemora
Writing time after the encounter, skipped questions, manual entry into the HIS, illegible file notes, and the medicolegal risk of unsupported records. Ssemora reduces these items; the physician looks after the patient, and the record looks after itself.
The physician talks with the patient; the report is ready as the encounter ends. The burden of writing notes after the encounter, trying to remember, and closing files at the end of the shift disappears.
Information not mentioned in the conversation is not guessed; a missing history is flagged in red (e.g. an allergy history that was not asked). The file is closed complete and consistent.
The documentation minutes per patient return to the encounter; the same outpatient team keeps records of the same quality for more patients.
The approved report is written to the patient file; the test and medication orders you select are transferred to the HIS. There is no need to type the same information a second time.
Every sentence of the report is linked to its second in the audio recording; the basis is ready for objections and audits. Approval, deletion and sharing are also in the audit log.
The microphone of a computer or phone is enough. No special recording device, device-bound licence or soundproofed room is required.
Even on the busiest outpatient day and on night duty: the same template, the same checklist, the same completeness. Record quality does not drop with fatigue.
Highlights
Every statement extracted from the recording is linked to its character range in the transcript and its second in the audio recording. Tap, listen to the audio, verify.
Red and grey items are collected in a single list. Depending on the institution's setting, the report cannot be finalised while there are unapproved items; this rule is also enforced on the server.
Questions that could be asked, tests that could be requested, medications that could be prescribed, and general recommendations. Each comes with a one-line rationale and a source; none is pre-selected.
Photograph a wound, lesion, ECG printout or lab result with the rear camera and attach it to the encounter. A finding in the photo appears in the report with a "From image" label and is reflected in the suggestions. A photo without the "No face/identity visible" confirmation is not sent to the AI.
The approved report is exported as Word or PDF; the PDF carries a signature block and a verification QR code. A sharing text for WhatsApp and email is prepared with consent confirmation and a log.
Preview, test and version institution templates; manage your abbreviation dictionary. Users and roles, statistics, logs, backup and export are in the same place.
Channels and Integration
Record on a computer or phone with microphone permission; pause, resume, finish or start over. An unfinished recording is kept on the device.
Upload a recording made on another device; it goes through the same flow and becomes a report.
Besides findings such as wounds and lesions, photograph an ECG printout, lab result or imaging report with the rear camera and attach it to the encounter. Photos you approve contribute to the report and suggestions; location and device information is deleted.
Physicians record the encounter on the phone, take the photo with the rear camera and verify the result on the same screen. The app connects to the institution's own address with an institution code.
External systems such as the HIS upload the encounter via the API, track its status and retrieve the physician-approved report as JSON or Word.
Add it to your phone or tablet like an app. There is an information page that opens while offline.
Architecture Workflow
Whichever channel the audio comes from, it passes through the same engine: transcription, speaker separation, evidence links, template placement, attention flags, suggestions, approval and HIS transfer.
For the endpoint list, authentication and error contract, see the Integration page.
The Decision Stays With the Physician
Security and Privacy
What follows is what the software does. Legal compliance is a property of your institution's processing activity as the data controller; Ssemora provides tools that make it easier for you to meet that obligation.
In the text sent to the AI model, names, national ID numbers, file numbers, phone numbers, email addresses, addresses, institution names and exact dates are replaced with placeholders. Age, sex and clinical content are preserved.
Cloud allowed, de-identified data only, or local model only. The choice applies to speech recognition as well as to the report model.
Speech recognition runs locally by default; raw audio is not sent to AI providers. Cloud speech recognition can be used only under the "cloud allowed" policy and with explicit consent.
Each institution runs on its own isolated instance and database. There is no data sharing between institutions.
Approvals, deletions and setting changes are written to the audit log; even deleting the log is recorded. Personal data is masked in application logs.
Audio recordings are deleted after 7 days by default (at most 30 days by institution setting). The transcript and report remain. National ID numbers are not stored in plain text.
Physician, administrator and auditor roles; a limit on login attempts. API keys are shown only once and stored as a hash.
Per-patient export and deletion, export of institution data, consent confirmation for sharing, and a record of every share.
Who It's For
Focus on the encounter; the draft report, verification list and suggestions are ready as soon as the encounter ends. Set up your templates and abbreviations to suit yourself.
Manage users and roles; monitor statistics and review system logs.
API keys authorised by scope, IP restriction, rate limiting and a detailed error contract. The HIS connector is planned according to the institution's system.
Frequently Asked Questions
No. Ssemora is decision-support software: it turns the conversation into a report, flags missing information and offers reasoned suggestions. It does not suggest a single diagnosis, does not produce probabilities or risk scores, and does not pre-select any suggestion. Responsibility for the report and for clinical decisions rests with the physician who approves the report.
Every statement extracted from the recording is linked to its character range in the transcript and its second in the audio recording. When you select a sentence, you see its source and verify it by listening to the audio. A statement with no basis in the recording is not shown in yellow: if it is a model interpretation it is marked grey, and if it is missing or uncertain it is marked red.
It works through the browser. On a computer or phone you can record the encounter or upload a ready-made audio file. You can add it to the home screen of your phone or tablet and open it like an app. Unfinished recordings are kept on the device; when the connection returns you can continue, send or delete them.
Yes, up to 6 photos per encounter: findings such as wounds, skin lesions and rashes, and documents such as ECG printouts, laboratory / test results, imaging reports or discharge summaries. The photo is downscaled on the device, and location and device information is deleted on the server. Only photos that the physician has confirmed as "no face/identity visible" go to AI analysis, if the institution setting is enabled; sentences that come from a photo are shown in the report with a "From image" label. Photos are also included in the Word and PDF output.
Each institution runs on its own isolated instance. Audio recordings are deleted after 7 days by default; by institution setting this can be extended to at most 30 days. After deletion, the transcript and report remain. National ID numbers are not stored in plain text.
Text sent to the AI model is always de-identified first: names, national ID numbers, file numbers, phone numbers, email addresses, addresses, institution names and exact dates are replaced with placeholders. In addition, one of three policies is chosen for each institution: cloud allowed, de-identified data only, or local model only; with the last one, the text never leaves for an external provider. Speech recognition runs locally by default.
Compliance is a property not of software but of the processing activity of the institution acting as data controller; for this reason we make no claim such as "KVKK-compliant" or certified. Ssemora provides tools that make it easier for the institution to meet its obligations: de-identification, retention period, audit log, sharing consent and its log, and per-patient export and deletion. Even though direct identifiers are removed, the risk of indirect identifiability in very small patient populations cannot theoretically be reduced to zero; this is why the AI policy is chosen at the institution level.
Sending to the HIS is designed to go through a connector written specifically for each institution; we do not currently publish a ready-made HIS connector. Instead, external systems can upload encounters and retrieve the physician-approved report through the REST API. Nothing is sent to the HIS without physician approval.
The physician approves the report. The approved report is locked and the action is written to the audit log. Every edit before approval is kept in the version history; you can compare versions and return to an unapproved version.
Demo
Let's plan a live demo with your institution's templates and your own encounter examples. No installation is needed; an instance dedicated to your institution is opened the same day.
Demo requests are not currently being accepted through this form. Please write to us by email: info@semora.com.tr