Templates & schemas

A Studio API's schema defines what JSON it returns. The shape mirrors OHM's built-in clinical templates so cloning a starter is a deep copy with no transformation.

Anatomy

{
  "version": 1,
  "label": "OPD Prescription",
  "specialty": "general",
  "sections": [
    {
      "key": "complaints",
      "title": "Complaints",
      "fields": [
        { "key": "chiefComplaint", "type": "text", "label": "Chief Complaint" },
        { "key": "presentIllness", "type": "rich-text", "label": "HPI", "mentions": ["dx"] }
      ]
    },
    {
      "key": "examination",
      "title": "Examination",
      "fields": [
        { "key": "vitals", "type": "vitals-block", "label": "Vitals" }
      ]
    }
  ]
}

The output JSON has the field keys as object keys, not nested by section:

{
  "chiefComplaint": "Fever 3 days",
  "presentIllness": "- Fever × 3 days...",
  "vitals": { "bp": { "systolic": 130, "diastolic": 85 }, "hr": 92 }
}

Built-in starters

When you create an API, you can clone any of these as a baseline. The list is always served live from /api/templates so it stays in sync with OHM's shipped catalog:

OPD prescription · SOAP note · Discharge summary · ICU daily · Psychiatry consultation (with insights) · Psychiatry follow-up · Cardiology · Pediatric · Antenatal · Emergency triage · Operative note · ENT · Ophthalmology · Dermatology · Orthopedic · MLC.

After cloning, edit fields, prompts, and inputs freely — your changes don't affect the starter or any other API.

Versioning

Every Publish creates a new version. Callers always hit the latest published snapshot. Drafts edit freely; only Publish promotes them to production.

DRAFT edits never break callers — they only see what's published.