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

# Patient Summary

> FAQs about the Patient Summary APIs

<Accordion title="Which organization ID should I use when requesting an upload URL?">
  Use your partner organization ID from your external registration with Suki. It can be a UUID or non-UUID string. But not a Suki UUID. Do not use an internal Suki organization ID. Suki maps your partner organization ID to the correct internal organization and Clinical Knowledge Graph (CKG).
</Accordion>

<Accordion title="How do I authenticate with the CKG Data Ingestion APIs?">
  Use the same Suki Token (`sdp_suki_token`) returned by the [Login](/patient-summary-api-reference/authentication/login) API.
</Accordion>

<Accordion title="How long is the upload URL valid?">
  The pre-signed Google Cloud Storage (GCS) upload URL expires after 15 minutes. If the URL expires before you upload, request a new upload URL.
</Accordion>

<Accordion title="What is the maximum upload size?">
  Each FHIR bundle can be up to 500 MB.
</Accordion>

<Accordion title="What format should the uploaded file use?">
  Upload a raw JSON file containing a FHIR Bundle of type `transaction`. Each entry should use a `PUT` request so CKG can create or update resources by id. The bundle must follow the FHIR R4 specification and include only supported resource types. For a complete sample, refer to [Example FHIR R4 bundle](/documentation/concepts/patient-summary/integrate-ckg#example-fhir-r4-bundle).
</Accordion>

<Accordion title="Can a bundle contain data from multiple organizations?">
  No. All resources in a bundle must belong to the same organization.
</Accordion>

<Accordion title="Does Suki validate resource references during ingestion?">
  No. Suki does not enforce referential integrity during ingestion. Ingestion can succeed even if a resource references another resource that has not been ingested yet.
</Accordion>

<Accordion title="When should I use a correlation ID?">
  Set the correlation ID to the original tracking identifier when uploading updates for a previous ingestion. This ensures Suki processes related updates in order and helps avoid conflicting changes.
</Accordion>

<Accordion title="Is the data available immediately after the upload succeeds?">
  No. A successful `PUT` confirms the file was stored. Suki processes the file asynchronously after upload completes. Poll the ingestion status endpoint or configure webhooks to learn when processing finishes.
</Accordion>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.