Skip to content

Clinical Documentation AI

Draft the note. Let the clinician sign it.

Transform conversations and intake data into structured, editable draft documents. Clinicians review, edit, and approve every final note.

Get API AccessAPI reference
POST /v1/documentation/draftSynthetic example
response.json
{
  "draft_id": "doc_demo_1p1z3r",
  "status": "draft_pending_approval",
  "template": "soap",
  "source": {
    "type": "transcription",
    "id": "tr_demo_001"
  },
  "sections": {
    "subjective": "Headache since yesterday evening, rated 6/10, worse with bright light. Nausea since this morning. Took ibuprofen last night. Denies noticed fever.",
    "objective": "Not captured in conversation. To be completed by clinician.",
    "assessment": "To be completed by clinician.",
    "plan": "To be completed by clinician."
  },
  "normalized_terms": [
    {
      "text": "headache",
      "attributes": {
        "onset": "yesterday evening",
        "severity": "6/10"
      }
    },
    {
      "text": "nausea",
      "attributes": {
        "onset": "this morning"
      }
    },
    {
      "text": "photophobia",
      "source_phrase": "worse when I look at bright light"
    },
    {
      "text": "ibuprofen",
      "category": "medication_taken"
    }
  ],
  "requires_approval": true,
  "disclaimer": "Decision-support draft for clinician review. Not a diagnosis."
}

Responsible use

Documentation drafts are generated for clinician review. Clinicians are responsible for reviewing, editing, and approving final clinical documentation.

Capabilities

Draft notes clinicians edit and approve.

Status labels show what is in development today and what is planned.

  • Draft clinical notes

    In development

    From transcripts, intake sessions, or both.

  • SOAP-style documentation

    In development

    Subjective, objective, assessment, plan sections.

  • Structured summaries

    In development

    Concise summaries for referrals and handovers.

  • Terminology normalization

    In development

    Patient phrases mapped to clinical terms.

  • Editable output for approval

    In development

    Drafts stay drafts until a clinician approves them.

  • JSON export & EHR integration

    Planned

    Structured sections mapped to your record schema.

Workflow

How it fits your product

Key output fields
sections.subjectivenormalized_terms[]statusrequires_approval
Typical host systems
EMR/EHRClinic management systemsReferral workflows
  1. 1

    Source selected

    A transcript or intake session.

  2. 2

    Draft generated

    Template sections with normalized terms.

  3. 3

    Clinician approves

    Edited and signed in your EHR, not ours.

Playground

Try the request and response

All examples on this site use synthetic data. No real patients, recordings, or inference requests are involved.

Demo mode · syntheticProposed
POST/v1/documentation/draft
Examples

Valid JSON

ResponseAwaiting request

No response yet.

Run the request to inspect the structured JSON response.

Responses are generated in your browser by deterministic demo rules over your request. They show the response schema — they are not results of a real inference request. Do not enter real patient data.

Compose with other modules

Clinical Documentation AI shares authentication, sessions and webhooks with every AKIRAMO module.

Your healthcare software deserves intelligence.

Integrate medical AI into the systems you already use.

Get API AccessTalk to Our Team
AKIRAMO AI — Medical Intelligence InfrastructureDeveloped by ZhanCare.