A scribe session is created when a clinician conducts a consultation through the Telepatia interface. Once the session is finished, the structured medical record is available via the API.
Session lifecycle
| Status | Description |
|---|
in_progress | The clinician is actively recording the session |
completed | The session has ended and results are available |
cancelled | The session was cancelled before completion |
Retrieving a session
Use the consultationInternalId you provided (or received) when setting the consultation context:
curl https://synapse.telepatia.ai/v1/scribe-sessions/CONSULT-12345 \
-H "Authorization: Bearer YOUR_API_KEY"
{
"id": "session-abc-123",
"status": "completed",
"createdAt": "2026-02-20T10:00:00Z",
"completedAt": "2026-02-20T10:30:00Z",
"patientName": "John Doe",
"scribeSessionModality": "IN_PERSON",
"consultationInternalId": "CONSULT-12345",
"specialty": "Cardiology",
"medicalRecordMutable": {
"chiefComplaint": {
"title": "Chief Complaint",
"type": "text",
"status": "completed",
"content": "Patient reports headache"
}
}
}
If status is in_progress, the session is not yet finished. Poll this endpoint until status is completed before processing the results.
Medical record structure
The medicalRecordMutable object contains the structured output of the session. Each key is a section (e.g. chiefComplaint, physicalExam) with a title, type, and content field. The sections available depend on the session template used. 
