Clinical scribe with verified codes

From your dictation to a record ready to sign.

You dictate the consultation; VozMedica structures the clinical record and proposes ICD-10 and CUPS codes that are checked against a catalog. Only the doctor signs.

  • Codes checkedEvery CUPS and ICD-10 code is checked against the catalog before you see it
  • No signing with open codesYou approve, replace, or remove each code
  • Built for Colombia10,024 CUPS codes, 12,545 ICD-10 codes, and the clinical record in Spanish

Conceptual view with synthetic data.

AI scribe vs. healthcare agents

A scribe writes the note. An agent carries the work through to review.

Documenting the consultation is the first step and is what is in production today. WhatsApp reception and follow-up are in development.

01Visit
02Record
03Coding
04Reception
05Follow-up
06Approval
AI scribeA short job.Listens to the consultation and writes the note. Everything else stays manual.
Listens to the visit
Drafts the note
Manual
Manual
Manual
Manual
VozMedicaDocumentation today; more work later.Today: dictation, record, and verified coding. In development: reception and follow-up.
Transcribes the visit dictationAudio is not stored.In production
Structures the clinical recordEditable until professional signing.In production
Suggests ICD-10 and validates CUPSEvery code is checked against the catalog; unconfirmed, it cannot be signed.In production
Will receive patients on WhatsAppCLARA: reception in development.In development
Will prepare follow-ups from signed plansIn development; not yet available.In development
Signing is the doctor’s aloneSigning, prescribing, and finalizing a diagnosis are doctor-only actions.Always

VozMedica includes this scribe, in production. Reception and follow-up are in development.

The agent prepares. The professional decides.AI supports the work; it does not replace clinical judgment.
A work system, not another chatbot

From a dictation to a reviewable record.

VozMedica turns the dictation into a structured record with verified codes and leaves the decision to the professional.

In
Consultation dictationSpeech to text; audio is not stored
WhatsAppIn development: questions and new contacts
Clinical eventIn development: results and follow-ups
VozMedica

Clinical documentation layer

Each step has a limited scope; signing, prescribing, and finalizing a diagnosis are the doctor’s alone.

Speech-to-text + clinical AIICD-10 and CUPS catalogsOnly the doctor signsCodes checked
Out, for your review
Clinical recordEditable before signing
Reception caseIn development
Proposed codesChecked against catalog; you confirm

How it works, in four steps

  1. 01
    CaptureConsultation dictation. WhatsApp and clinical events: in development.Who acts: Agent
  2. 02
    PrepareTranscription, record structure, and ICD-10 / CUPS codes.Who acts: Agent
  3. 03
    ReviewYou review the record and confirm each code. Everything is editable.Who acts: You
  4. 04
    Approve and signOnly the doctor signs; with an unconfirmed code, signing is blocked.Who acts: You
What exists today and what is next

One clear healthcare role at a time.

The clinical scribe is in production today. WhatsApp reception and follow-up are being built and are marked as in development.

In production

Clinical scribe

Turns the consultation into a structured, editable record.

  • Medical transcription
  • Structured clinical AI
  • CIE-10 + CUPS validated
  • Review and signing
In development

CLARA

WhatsApp receptionist in development. It is not yet part of the production product; the planned design is:

  • Private conversation per contact
  • Structured questionnaire
  • Alerts and summaries
  • Connected follow-up
In development · not yet available

Follow-up

In development

Planned: reminders and communication from approved plans.

  • Pending follow-ups
  • Message drafts
  • Team escalation

Operations

Idea in design

Not built yet: a panel to see the clinic’s status.

  • Unsigned records
  • Incomplete information
  • Integration failures
The workspace

Dictate, review, and sign in one place.

Dictations, records pending signature, and codes to confirm, with whatever needs your attention always on top.

Illustrative view with synthetic data. CLARA elements are a concept in development.

WhatsApp reception · In development

A WhatsApp receptionist, in development.

In developmentNot in production yetPlanned design

Planned design: an assistant with its own name, tone, information, and questionnaire that answers general questions, collects each case, and alerts the team. It will not diagnose or prescribe. It is not yet part of the production product.

Private session per personHistory and attachments isolated by contact.
Clinic instructions and safetyApproved information, tone, questionnaire, and clinical limits.
Team informedNew-contact alerts and completed-case summaries.
Archive and follow-upDesign: keep the authorized history and pass qualified cases to the team.
Case collected by CLARAFor team review
Review
Name
Andrea Pérez
Type
First visit
Reason
Skin allergy
Location
Pending
  1. T+0Private conversation · contact-isolated session
  2. T+1Team alert · new contact
  3. NEXTPlanned · qualified case to the clinical system
Will not diagnose or prescribe

Design: answer general questions and record the reason for the team.

Designed for each clinic

In development. The current application serves a single clinic per installation; a multi-clinic model is not available yet.

Example conversation of a concept in development, with synthetic data.

Control before autonomy

The agent prepares. The professional decides.

Autonomy follows risk. A lookup may run; a clinical record needs review, confirmed codes, and the doctor’s signature.

Low riskA lookupMay run
Medium riskA codeNeeds confirmation
High riskA clinical recordNeeds review and signing
Clear origin

The record comes from your dictation. Audio is not stored.

Doctor-only actions

Only the doctor can sign, prescribe, and finalize a diagnosis.

Explicit approval

No irreversible clinical actions in the background.

Confirmed codes

With an unconfirmed code, signing is blocked.

Integrations

REST API and FHIR push to CareCompile.

Today VozMedica offers a REST API and, on signing, pushes the record to CareCompile as a FHIR DocumentReference. There are no HL7 or third-party records-system connectors.

Channels

WhatsApp · in development

Clinical operations

CareCompile · FHIR push on signing

Standards

FHIR DocumentReferenceREST API

Models and catalogs

Local modelCIE-10CUPS Colombia

The code-system layer starts with Colombia (CUPS and ICD-10) and is designed to add other countries’ code systems. Roadmap: not live yet.

Guided trial

Test the coder on your own dictation.

15-minute session with synthetic data. No patient data.

What happens after you request access

  1. 1We start with one concrete task.
  2. 2We measure the result.
  3. 3We expand permissions only when the workflow is safe.

Test the coder on your own dictation

15-minute session with synthetic data. Leave your details and we will contact you.

Do not include patient data in this form.

Thank you. We received your request and will contact you using the details you left.