Struct ClinicalNoteGenerationSettings 

#[non_exhaustive]
pub struct ClinicalNoteGenerationSettings {
    pub note_template: Option<MedicalScribeNoteTemplate>,
}

The output configuration for clinical note generation.

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

note_template: Option<MedicalScribeNoteTemplate>

Specify one of the following templates to use for the clinical note summary. The default is HISTORY_AND_PHYSICAL.

• HISTORY_AND_PHYSICAL: Provides summaries for key sections of the clinical documentation. Examples of sections include Chief Complaint, History of Present Illness, Review of Systems, Past Medical History, Assessment, and Plan.

• GIRPP: Provides summaries based on the patients progress toward goals. Examples of sections include Goal, Intervention, Response, Progress, and Plan.

• BIRP: Focuses on the patient's behavioral patterns and responses. Examples of sections include Behavior, Intervention, Response, and Plan.

• SIRP: Emphasizes the situational context of therapy. Examples of sections include Situation, Intervention, Response, and Plan.

• DAP: Provides a simplified format for clinical documentation. Examples of sections include Data, Assessment, and Plan.

• BEHAVIORAL_SOAP: Behavioral health focused documentation format. Examples of sections include Subjective, Objective, Assessment, and Plan.

• PHYSICAL_SOAP: Physical health focused documentation format. Examples of sections include Subjective, Objective, Assessment, and Plan.

Implementations

impl ClinicalNoteGenerationSettings

pub fn note_template(&self) -> Option<&MedicalScribeNoteTemplate>

Specify one of the following templates to use for the clinical note summary. The default is HISTORY_AND_PHYSICAL.

• HISTORY_AND_PHYSICAL: Provides summaries for key sections of the clinical documentation. Examples of sections include Chief Complaint, History of Present Illness, Review of Systems, Past Medical History, Assessment, and Plan.

• GIRPP: Provides summaries based on the patients progress toward goals. Examples of sections include Goal, Intervention, Response, Progress, and Plan.

• BIRP: Focuses on the patient's behavioral patterns and responses. Examples of sections include Behavior, Intervention, Response, and Plan.

• SIRP: Emphasizes the situational context of therapy. Examples of sections include Situation, Intervention, Response, and Plan.

• DAP: Provides a simplified format for clinical documentation. Examples of sections include Data, Assessment, and Plan.

• BEHAVIORAL_SOAP: Behavioral health focused documentation format. Examples of sections include Subjective, Objective, Assessment, and Plan.

• PHYSICAL_SOAP: Physical health focused documentation format. Examples of sections include Subjective, Objective, Assessment, and Plan.

impl ClinicalNoteGenerationSettings

pub fn builder() -> ClinicalNoteGenerationSettingsBuilder

Creates a new builder-style object to manufacture ClinicalNoteGenerationSettings.

Trait Implementations

impl Clone for ClinicalNoteGenerationSettings

fn clone(&self) -> ClinicalNoteGenerationSettings

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for ClinicalNoteGenerationSettings

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl PartialEq for ClinicalNoteGenerationSettings

fn eq(&self, other: &ClinicalNoteGenerationSettings) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl StructuralPartialEq for ClinicalNoteGenerationSettings