Clinical Note Execution

The document explains the process of generating and executing notes through a system involving template selection, server-side actions, and template processing.

Note Generation/Execution

Upon recording a visit, users select the note template via dropdown. Only the template ID is sent in requests, and the server constructs the template.

Server-side actions:

1. Retrieve the template JSON from Firebase using templateId.

2. Access the template JSON from GCS using templateId or gcsPath.

3. Process voice-triggered templates from their GCS paths, ready to be converted to an LLMChain.

Template: LLMChain Structure

{
  "chainId": "template.id",
  "name": "template.title",
  "execution": "parallel",
  "tasks": [...] // tasks can be LLMChain or LLMTask
}

Section: LLMTask/LLMChain Structure

{
  "chainId": "section.id",
  "name": "section.title",
  "execution": "sequential",
  "tasks": [...]
}

A section-level LLMChain identifies which template to trigger based on voice prompts and executes necessary tasks sequentially.