​
Overview

In the Corti API, Templates define the structure for document that are generated by Corti Ensemble and Corti Symphony foundation models from various inputs, such as conversational transcripts, facts, or other medical documents. Templates are available in different languages and can be specific to your organization. Each template includes sections that set the structure (e.g., SOAP Note template consists of the four sections Subjective, Objective, Assessment and Plan), and a writing style and documentation format is defined for each section. This ensures consistency, clarity, and control in use of AI to support medical reporting. This page explains the standard workflow for generating documents from facts or transcripts.

​
Using Templates to Generate Documents

Steps to Generate a Document
  1. Review and Finalize Data: After the live session, the client can review and make final edits to the facts collected during the interaction. These finalized facts will be used to generate the document.
  2. Make a POST Request: Send a POST request to the /interactions/{id}/documents endpoint, and include the finalized facts, templateKey, and language in the request payload.
    • The ‘templateKey’ parameter defines the format of the output document.
    • The ‘language’ parameter defines the language the output note will be written in.
    • Please see this page for a list of supported language codes.
    • Use the GET /templates request to see available templates; add ?lang= to the request to filter for available languages.
  3. Processing the Request and Receiving the Document: The API processes the submitted data, applying the specified template to generate the structured document. If the request is successful, the API returns a 200 OK status along with the formatted document.
  4. Mark Interaction as Completed (optional): If this marks the end of the encounter, the client can update the interaction status by sending a PATCH request to /interactions/{id}, setting the interaction state to "completed".

This sequence diagram refers to using the live, real-time fact generation workflow and generating a document from the final facts list. You can also use the final transcript as input context, see further below for more details.

​
Generate document from facts vs. from transcript

For the typical ambient documentation workflow, summary documentation can be generated either on the basis of facts or the transcript. If your integration is centered around facts, those would typically have been generated automatically during the live stream (source: core) but you might have also created facts to pipe over relevant pre-chart information, e.g. demographics (source: system), or have given the clinician the ability to add and edit live notes (source: user). In the end, you decide which facts to use as the basis to generate a document. Let’s look at the differences in the request payload when generating a document on the basis of facts vs. a transcript: 
  curl --request POST \
  --url https://api.$environment.corti.app/v2/interactions/$id/documents \
  --header 'Authorization: Bearer <token>' \
  --header 'Tenant-Name: <tenantname>' \
    --header 'Content-Type: application/json' \
    --data '{
    "context": [
      {
        "type": "facts",
        "data": [
          {
            "text": "32 year-old female",
            "group": "demographics",
          "source": "system" # example of a fact that was created via REST
          },
          {
            "text": "itchy rash, started last week",
            "group": "history-of-present-illness",
          "source": "core" # fact generated by Corti LLM during stream
          },
          {
            "text": "allergic to birch pollen since childhood",
            "group": "allergies",
            "source": "core"
          },
          {
            "text": "typical eczema appearance",
            "group": "assessment",
            "source": "core"
          },
          {
            "text": "corticosteroid treatment, follow-up in 4 weeks",
            "group": "plan",
          "source": "user" # a fact edited by the end user
          }        
        ]
      }
    ],
    "templateKey": "soap",
    "name": "Soap note summary: itchy rash",
  "outputLanguage": "en-US" # BCP-47 code
  }'