> ## 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.

# Content Retrieval

> Retrieving generated clinical content, transcripts, and structured data from sessions

<Accordion title="How do I retrieve generated clinical content?">
  After ending a session, retrieve content using the session's recording ID:

  After ending a session, wait for the suggestionsGenerated event through the session delegate, then use the SDK's content retrieval methods with the session's recording ID.
</Accordion>

<Accordion title="What does the retrieved content contain?">
  The retrieved content includes:

  * **Clinical sections**: Structured documentation organized by medical sections (e.g., History of Present Illness, Review of Systems)
  * **Timestamps**: When the content was generated
  * **Session metadata**: Information about the session, patient, and provider
  * **Confidence scores**: AI confidence levels for different content sections
  * **Structured data**: Formatted clinical information ready for EHR integration
</Accordion>

<Accordion title="How long does content generation take?">
  Content generation time varies based on:

  * **Session length**: Longer sessions take more time to process
  * **Audio quality**: Clear audio processes faster
  * **Network conditions**: Affect upload and processing speed
  * **Server load**: Peak times may have longer processing

  Typical generation times range from 30 seconds to a few minutes. Use session delegates to get real-time updates.
</Accordion>

<Accordion title="Can I retrieve content multiple times for the same session?">
  Yes, you can retrieve content multiple times using the same recording ID. The content remains available on the server for a specified retention period. Each retrieval call returns the same generated content.

  Retrieve content multiple times using the same recording ID. Each retrieval call returns the same generated content during the retention period.
</Accordion>

<Accordion title="What happens if content generation fails?">
  If content generation fails, you'll receive a `contentGenerationFailed` event through the session delegate:

  If content generation fails, you'll receive a generation failed event through the session delegate. Handle this by showing appropriate error messages and potentially creating a new session.

  Common causes include poor audio quality, network issues during processing, or server errors.
</Accordion>

<Accordion title="How do I check if content is ready without retrieving it?">
  Use session status methods to check processing status:

  Use session status methods to check processing status before attempting content retrieval. This helps determine if content generation is complete.
</Accordion>

<Accordion title="Can I retrieve partial content during generation?">
  No, content retrieval returns the complete generated clinical documentation once processing is finished. Partial content isn't available during the generation process. Use session delegates to monitor progress and retrieve content only after receiving the `suggestionsGenerated` event.
</Accordion>

<Accordion title="What should I do if content retrieval fails?">
  Handle content retrieval failures gracefully:

  Handle content retrieval failures gracefully by implementing proper error handling for various failure scenarios like network issues or content not being ready.

  Implement retry logic with exponential backoff for transient errors.
</Accordion>

<Accordion title="How long is generated content stored on the server?">
  Generated content is typically stored for a defined retention period (usually 30-90 days, depending on your agreement with Suki). After this period, content may be automatically deleted. Check with your Suki partnership team for specific retention policies.
</Accordion>

<Accordion title="Can I retrieve content for offline sessions?">
  Yes, once offline sessions are uploaded and processed, you can retrieve their content using the same methods. The SDK automatically handles the upload process when connectivity is restored, and content generation begins once the upload completes.

  Monitor the upload and generation progress through session delegate events.
</Accordion>