> ## Documentation Index
> Fetch the complete documentation index at: https://developer.suki.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# General

> Frequently asked questions about the Suki Developer Platform and integration benefits

<Accordion title="What Types of Organizations Can Benefit from Using the Suki for Partners?">
  Healthcare solutions, including electronic health records (<Tooltip tip="Electronic Health Record. The longitudinal digital chart for a patient across care settings. Partners integrate Suki so generated notes and structured clinical data can flow into the EHR clinicians already use." cta="View in Glossary" href="/Glossary/e">EHR</Tooltip>s), telehealth applications, medical devices, and more, can now easily incorporate AI voice features directly into their offerings using the Suki APIs and <Tooltip tip="Software Development Kit. A collection of tools, libraries, and documentation to help developers build applications for a specific platform." cta="View in Glossary" href="/Glossary/s">SDK</Tooltip>s.

  **Best for:**

  * Electronic Health Record (EHR) systems.
  * Telehealth platforms.
  * Medical device manufacturers.
  * Healthcare mobile app developers.
  * Clinical workflow software providers.
</Accordion>

<Accordion title="What Kind of Analytics and Reporting Capabilities Does the Suki Platform Provide?">
  Currently, the Suki platform does not offer built-in analytics and reporting capabilities. However, this is planned for an upcoming release. Stay tuned!

  **Coming soon:**

  * Usage analytics and insights.
  * Integration performance metrics.
  * Clinical documentation quality reports.
</Accordion>

<Accordion title="What Kind of Support Does Suki Offer During the Implementation Process?">
  Suki offers 24/7 support for critical issues and is available to assist in any way we can. During the initial phase, we will hold regular check-in meetings to ensure any blockers are addressed promptly.

  **Support includes:**

  * 24/7 critical issue support.
  * Regular implementation check-ins.
  * Technical integration assistance.
  * Documentation and training resources.
</Accordion>

<Accordion title="What Is the Typical Implementation Timeline for the Platform?">
  Overall, the typical implementation timeline ranges from 4 to 6 weeks.
  However, this can vary based on specific project requirements and resource
  availability. For a more accurate timeline tailored to your project, contact
  our [support team](/documentation/references/support).
</Accordion>

<Accordion title="What Versions Do Partners Need for Ambient Interoperability?">
  Ambient interoperability lets clinicians continue the same clinical note across Suki ambient products. Use product versions that support the shared `emr_encounter_id` workflow:

  * **Ambient APIs:** Pass `emr_encounter_id` when you [create an ambient session](/api-reference/ambient-sessions/create).
  * **Mobile SDK:** **v2.7.0** or later. Refer to [Mobile SDK interoperability](/mobile-sdk/ambient-guides/ambient-interoperability).
  * **Web SDK:** **v3.2.0** or later. Refer to [Web SDK ambient interoperability](/web-sdk/guides/ambient-interoperability).
  * **Headless Web SDK:** Interoperability support is coming soon.

  For the platform overview, use cases, and identifiers, refer to [Ambient interoperability](/documentation/concepts/ambient-clinical-notes/ambient-interoperability).
</Accordion>