sdp_suki_token). Critically, wait until summary generation status is COMPLETED before you treat summary content as final. Use patient_summary_id when you stored it from a generation response, or pass your fhir_encounter_id and fhir_practitioner_id when you resolve summaries by partner identifiers.
Available endpoints
Patient Summary (ID)
Retrieve the full Patient Summary using
patient_summary_idPre-Visit Summary (ID)
Retrieve the pre-visit section using
patient_summary_idPatient Summary (Partner IDs)
Retrieve the full Patient Summary using encounter and practitioner identifiers
Pre-Visit Summary (Partner IDs)
Retrieve the pre-visit section using encounter and practitioner identifiers
Related guides
Retrieve Patient Summaries
Learn when to retrieve full and pre-visit summaries
Generate Patient Summaries
Learn how generation jobs complete before you retrieve content
Patient Summary Basic Usage
Learn the upload, generate, poll, and retrieve Patient Summary flow
Common use cases
Show a full summary during chart review
Retrieve the comprehensive Patient Summary object and present About Visit, Patient Summary, Previous Visit, and Problems sections before or during the encounter.
Display pre-visit previews in schedule views
Load the pre-visit section for each appointment to display a preview to the provider directly in the schedule or appointment list interface.
Look up summaries with your own encounter IDs
Use encounter and practitioner identifiers from your EHR when you do not persist
patient_summary_id in your scheduling or charting workflow.Integrate summary sections into your EHR UI
Map structured summary sections and snippets into your review screens, dashboards, or handoff workflows after generation completes.