How it works

An Interaction is the fundamental unit within the Corti API that encapsulates the entire conversation or session between a medical professional and a patient. It ties together all related data and operations, enabling a cohesive workflow from the start of the interaction to the generation of final documentation. The Interaction endpoint allows you to discover all interactions available for your organization, create a new interaction, and update existing ones. When creating an interaction you’ll receive an InteractionId as well as a Web Socket URL that can be used for real-time, streaming workflows.

Within an interaction, the Corti API extracts Facts, atomic pieces of information that are critical for documenting an interaction accurately. These facts can include details such as the patient’s name, height, blood pressure, symptoms, and other clinically relevant data. Facts are designed to help clinicians quickly identify the salient points of an interaction, making it easier to draft complete and truthful clinical documents.

Key features of Facts:

• Relevance and Precision: Facts are distilled from the conversation in real-time, ensuring that every crucial piece of information is captured as the interaction unfolds.
• Customizability: Clinicians can easily add, remove, or modify facts to ensure that the documentation reflects the true nature of the interaction.
• Integration with Documentation: These facts form the building blocks of clinical documents, ensuring that every relevant detail is included without overwhelming the clinician with unnecessary information.

The streams endpoint enables real-time workflows, designed for scenarios requiring immediate processing and feedback during live interactions. It works by establishing a WebSocket connection after initializing an interaction through the /interactions endpoint. Once connected, the client streams audio packets to the API, which responds with live transcripts and fact updates in real-time. This continuous data flow allows for instantaneous capture and processing of information, making it ideal for situations where immediate action is crucial. The stream can be updated with new facts during the interaction, and it concludes when the client sends an “end” message, formally closing the live session.

The recordings endpoint in the Corti API allows clients to manage audio recordings associated with interactions. It is part of a larger workflow that includes initializing interactions, uploading recordings, generating transcripts, and creating documents based on the interaction data.

As an example, after initializing an interaction, clients can upload an audio file by sending a POST request to /interactions/:interactionId/recording. The API responds with a 200 status code and returns a recordingId, confirming that the audio file has been successfully uploaded and linked to the specific interaction. Use the ‘recordingId’ in your next step, such as generating Facts or Documents.

The transcripts endpoint in the Corti API is part of the workflow for processing recorded interactions. After uploading an audio recording, clients can initiate the transcription process by sending a POST request to /interactions/:interactionId/transcripts. The API then processes the audio and returns a 200 status code along with the generated transcript. This transcript contains the text version of the recorded interaction, extracted and formatted for review. The transcripts endpoint plays a crucial role in converting speech to text for clinical conversations and dictations, enabling further processing and documentation creation based on the interaction data.

Templates in the Corti API allow users to specify the output of medical documents generated from various inputs, such as transcripts, facts, or other medical documents. They enable the definition of specific sections, structure, language, and writing style for documentation, ensuring consistency and clarity in medical reporting.

For more information on how to find and use existing templates, or to request custom templates, please see details on the Templates page or contact us for more information.

The documents endpoint in the Corti API is an essential part of the workflow for processing recorded interactions. After initializing an interaction, uploading a recording, and generating a transcript, clients can create the necessary documentation by sending a POST request to /interactions/:interactionId/documents. This request includes the previously generated transcript and a templateId to specify the desired format of the output document. The API then processes the request and returns a 200 status code along with the final document, which is ready for use or further editing. This endpoint allows for the generation of documentation tailored to specific needs, such as clinical notes or referral letters, based on the interaction data and predefined templates. The endpoint can be called multiple times for a given interaction if multiple document outputs are desired.

The codes endpoint in the Corti API provides access to the Corti Coding Expert Model, which includes support for ICD-10 diagnosis and procedure codes as well as CPT code with modifiers. The API provides the ability to generate codes for a text that is defined in the request or documents associated with the interaction. In addition to using out of the box coding model, organizational-specific model training is available so that coding output is tuned for client note styles and requirements.

The inquiry endpoints in the Corti API provide the ability to execute contextual searches and knowledge retrieval. Public reference material is widely supported; however, organizations can customize information sources for their standards of care. Furthermore, alignment and explainability models are available to compare resources to identify overlaps or gaps between two assets.