Stream clinical conversations in your product.
Your backend identifies the patient and calls Doctronic. Doctronic runs the clinical conversation. Typed events tell your product what to display and which workflow state changed.
API workflow
text/event-streamPOST /users/Create the user onceStore the returned ID with the patient in your system.POST /chats/Create a clinical conversationSend the stored user ID and relevant context.POST /chats/{chatId}/stream/Send a patient turnRead the typed Server-Sent Events stream.ai_consultation.completeReceive available document IDsRetrieve each identified document when it is ready.
Conditional workflow signals
guardianGuardian eventIf emitted, follow the safety behavior approved for your integration.skill_code.ctaCare actionIf emitted, map it to a supported product action.What you can build
One API covers users, chats, consultation documents, appointments, pharmacy, and insurance coverage.
Run a clinical conversation
Create a chat, stream each patient turn, pass context, and restore the transcript.
Read the guideConnect patients to care
Book scheduled or ASAP visits, track them, read visit results, and save a pharmacy.
Read the guideHandle safety events
Act on guardian events and calls to action from the event type, never the assistant text.
Read the guideFrom access to production
Build against staging, prove the integration end to end, then roll out to production traffic in stages.
Use the docs in your workflow.
Browse endpoint details, download the OpenAPI schema, or load plain-text documentation into your coding tools.