F
| Term | Definition |
|---|---|
| Family History | A clinical note section (LOINC: 10157-6) for relevant conditions among the patientβs biological relatives. In Suki, pass this LOINC code when you want family history captured in the generated note. |
| Federated Authentication | An authentication model where multiple systems trust a single identity provider, allowing users to access multiple services with one set of credentials. |
| FHIR | Fast Healthcare Interoperability Resources. An HL7 standard for exchanging healthcare data as structured resources (for example Patient or Encounter). Partners use FHIR-oriented patterns when integrating Suki outputs with modern health IT systems, and upload FHIR data into CKG for Patient Summary. |
| FHIR Bundle | A FHIR resource collection partners upload during CKG Data Ingestion so Suki can store encounter, patient, practitioner, and history data for Patient Summary generation. Keep identifiers in the bundle consistent with the IDs you pass when you generate and retrieve summaries. |
| Form filling | AI-powered workflow that populates Suki Medical form templates from visit conversation. Use Form filling for the capability; use Form filling API for the REST product. |
| Form filling API | REST APIs for voice-driven medical form sessions: create and manage sessions, stream audio over the Partner WebSocket, and retrieve structured form output. |
| Form filling SDK | JavaScript and React library that embeds Form filling in your web app with a hosted iframe. Handles sign-in, the Form filling UI, and SDK callbacks so you do not build the full Form filling API workflow yourself. |
| Form filling Session | A time-bound visit session for capturing conversation and generating structured medical form output. REST responses return its ID as ambient_session_id. That value is not the same as an ambient session ID from the Ambient API even though the field name matches. |
| Form filling Session Context | Patient, provider, encounter, and Medical form template metadata you seed or update for a Form filling session through Form filling API context endpoints. |
| FormFillingClient | Main class in the Form filling SDK. Create it with a configured auth manager, then call start() to open a Form filling session in a container on your page. |
| Full Summary | The complete Patient Summary object returned after a summary job finishes. Use it for chart review; use Pre-Visit Summary when you need only the schedule-preview section. |