Skip to main content
One <script> tag drops Telepatia’s clinical AI into your own EMR page. One config composes what the doctor sees — Scribe to record the visit and return the structured note, Telepatia Intelligence as the in-consultation copilot, and CDSS to review the note against the institution’s guidelines. The doctor never leaves your product. The panel mounts in its own Shadow DOM, so your CSS and the embed’s styles don’t affect each other. It is more than audio. New capabilities ship through the same CDN bundle, so you integrate once and turn them on with a flag — no second integration.

The capabilities

One config, window.TelepatiaEmbedConfig, composes three capabilities. Each is a { show } flag, and each renders only when your institution is also granted it.

Scribe

scribeContext — records the visit, transcribes it, generates the structured note, and returns it to your EMR.

Telepatia Intelligence

intelligence — the clinical copilot: streaming chat, scales, attachments (image / PDF) and memories, scoped to the consultation.

CDSS

cdss — corrective clinical alerts on the finished note, reviewed before it reaches the chart.

How it works

  1. You pass the context — patient, template, consultation id — to init().
  2. The doctor records the visit and works the copilot in the panel.
  3. Telepatia transcribes the audio, generates the note, and raises CDSS alerts.
  4. Your backend fetches the structured record and writes it to the chart.

Where to go next

Quickstart

Set up the keys, drop the script, record your first note.

Reference

init() config, capabilities, methods, callbacks, and errors.

Examples

A full page to copy, and what the panel looks like.