Quickstart - Telepatia Integration Hub

Set up (once, via the Scribe API)

Do this once per doctor through the Scribe API (institutional), with your institutional API key. Don’t have one? Ask your Telepatia contact.

Create a doctor account. The response returns two keys, shown once: publishableApiKey (pk_…) goes on the page; apiKey (sk_…) is the secret — backend only, never the browser.

Create a smart template — save its id

Create a smart template. Save the returned mrc_… id; you pass it to init().

Create a webhook

Subscribe to scribe_session.completed. Save the signingSecret to verify the calls. This is how your backend learns a note is ready.

Add the script

Put the config block before the CDN tag. Serve the page over https or localhost — the microphone needs a secure context.

<script>
  window.TelepatiaRecorderConfig = {
    apiKey: "pk_…",              // publishable key — never the sk_
    branding: { name: "Your Brand" },
    locale: "en",                // "en" · "es" · "pt"
  };
</script>
<script src="https://cdn.telepatia.ai/telepatia-embed/v0/embed.js"></script>

Use a test key while you build (no real data) and your production key to go live. Same code, no environment flag.

Open the panel

Call init() when the doctor clicks record — it mounts and opens the panel. Pass the context your app already has (the patient and the doctor’s template) so the note comes back linked to the right consultation.

document.getElementById("record").addEventListener("click", () => {
  window.TelepatiaRecorder.init({
    patient:      { name: "Maria Gómez", idCountry: "CO", idType: "CC", idValue: "55544433" },
    template:     { medicalRecordConfigurationId: "mrc_…" },
    consultation: { externalConsultationId: "CONSULT-12345" }, // your encounter id
  });
});

Always pass your own externalConsultationId — it’s how you fetch the result later. Without it Telepatia generates one you can’t see. And use init() to open: show() only expands a panel that’s already mounted.

Get the result

Your externalConsultationId is the Scribe API’s consultationInternalId — same value, different name. When the scribe_session.completed webhook fires, fetch the record on your backend with the secret key (sk_), never the browser:

Look up the session — GET /v1/scribe-sessions/{consultationInternalId}
List the record documents — GET /v1/scribe-sessions/{consultationInternalId}/medical-record-documents

The full record schema and error format live in the Scribe API product in this Hub.

​Set up (once, via the Scribe API)

​Add the script

​Open the panel

​Get the result

Set up (once, via the Scribe API)

Add the script

Open the panel

Get the result