Safety and responsibilities

Doctronic sends clinical content and typed control events. Your integration decides how those events appear in its interface, how users move between systems, and how operational teams respond when a workflow cannot continue.

Doctronic provides

• Assistant content through message.* events.
• A guardian event when a documented safety condition is emitted.
• Explicit conversation, call-to-action, error, and consultation-completion events.
• Organization and user scoping on API resources.
• Consultation documents identified by the IDs in the completion event.
• A staging environment for approved integration testing.

Your integration owns

• Authenticating the current patient before selecting a Doctronic user ID.
• Keeping the organization token and webhook secret on trusted infrastructure.
• Rendering clinical content and events without changing their meaning.
• The patient-facing fallback when a stream, appointment, or document workflow fails.
• Mapping supported call-to-action values to approved product behavior.
• Operational monitoring, local audit records, and access controls in your systems.
• Testing the complete user experience before production traffic is enabled.

Decide together

Document these items with your Doctronic implementation contact:

• Guardian presentation and escalation behavior.
• Supported CTA values and fallback behavior.
• Patient messaging and support ownership.
• Permitted clinical context and data destinations.
• Webhook events and operational contacts.
• Integration-specific evaluation cases and launch evidence.
• Rollout, pause, and rollback controls.

The public API does not define an external emergency-service integration, a guardian acknowledgement endpoint, or a general-purpose escalation destination. Do not invent one by parsing assistant text or replaying a patient turn.

Use explicit state

Treat these signals independently:

See Handle safety and escalation for event handling examples.