N
| Term | Definition |
|---|---|
| Natural Language Voice Interaction | Technology that allows users to interact with systems using spoken natural language commands and queries. |
| NLP | Natural Language Processing. AI technology that helps computers understand, interpret, and generate human language. |
| Note | In ambient interoperability, the clinical documentation artifact that groups ambient sessions under an EMR encounter. Create Session returns composition_id; use that value as note_id with note-level Ambient APIs. After finalize and submit to the EMR or EHR, the composition is treated as a finalized note. |
| Note Archive | A Web SDK component that allows users to view and manage both current and historical clinical notes associated with a patient. |
| Note Editor | A rich-text editing component in the Web SDK designed specifically for AI-generated clinical content, supporting editing, formatting, and section-level interaction. |
| Note Generation | Suki’s AI process that turns encounter audio and session context into a structured clinical note. Output follows the LOINC sections you configured for the ambient session. |
| Note ID (Ambient APIs) | Unique identifier for an interoperable ambient note. Create ambient session returns composition_id; pass that value as note_id to note-level ambient endpoints such as note content, note context, and note structured data. |
| Note ID (Web SDK) | The unique identifier for the generated note in the Headed Web SDK. It appears in the payload for the onNoteSubmit prop (React) and the note-submission:success event (React and JavaScript) when you complete Note Submission. |
| Note Section | A labeled part of a clinical note identified by a LOINC code, such as HPI, Physical Exam, or Assessment and Plan. In Suki, you choose which note sections to generate by passing their LOINC codes in ambient session configuration. |
| Note Submission | The step where a completed clinical note is finalized and handed to the partner application for EHR write-back or downstream storage. In SDKs, this is typically surfaced through note-submission callbacks or events. |
| Non-Generated Values | Form filling API structured-data field (non_generated_values) listing form_template_id values for which Suki did not generate structured output in that Form filling Session. |
| Notification Webhook | A server-to-server HTTP callback from Suki to a partner’s registered endpoint, triggered by events such as note generation completion or session status changes. |