E/M Coding Overview

Learn how Suki generates E/M code recommendations, supports revenue cycle workflows, and integrates with Ambient or standalone APIs

E/M Coding is supported by: E/M Coding APIs and Ambient APIs

Suki’s E/M Coding capability recommends Evaluation and Management (E/M) codes based on the clinical documentation for a visit. E/M codes are used to describe the level of care provided during an encounter and help determine how that visit is billed for payment.

When you use E/M Coding capability, it enables you to recommend E/M codes after the note is ready, so clinicians or coding teams can review and accept a starting point instead of coding from scratch.

You can request recommended E/M codes from Suki in two ways:

• With an existing Ambient workflow:

  If your application already uses Suki Ambient APIs to capture patient-provider conversations and generate clinical notes, enable E/M Coding when creating the ambient session by setting artifacts: ["EM_CODES"]. Include the patient, provider, and visit details as usual.

• With a completed clinical note that you already have:

  If your application or EHR already has a completed clinical note, send its sections to Suki using the standalone E/M Coding APIs. Suki analyzes the note and returns the recommended E/M codes without requiring an Ambient session.

Suki analyzes the clinical note along with available visit details, such as patient information, diagnoses, and encounter context. It returns recommended E/M codes with supporting information that explains why each code was selected, when that information is available.

Your application can display these recommendations for clinician or coding review. Once a reviewer accepts a recommendation, your application can pass the selected code into your existing billing workflow.

• Suki only provides coding recommendations. Your application remains responsible for the review, code selection, and subsequent billing process.
• Supporting rationale or evidence is included only when applicable for the coding path Suki used. For example, MDM-based codes can include rationale, and time-based or wellness codes can include evidence.
• E/M Coding is in Beta. Behavior and response fields can change based on user feedback.
• E/M Coding must be enabled for your organization. Contact support or the Partnership team to enable the capability.

​

How E/M Coding supports revenue cycle management

Clinical documentation is only one part of the post-visit workflow. Once a note is complete, clinicians or coding teams must determine the appropriate visit code before the encounter can move through billing.

E/M Coding helps with this step by analyzing the completed note and available encounter details to recommend an appropriate Evaluation and Management code. It also provides supporting rationale to help reviewers understand the recommendation.

With Suki’s E/M Coding capability, you can:

Move from Documentation to Coding

Extend your existing Ambient or Dictation workflows beyond note creation. Generate E/M code recommendations once the clinical documentation is ready.

Give Reviewers a Starting Point

Present recommended codes with supporting rationale so clinicians and coding teams can review the results instead of starting the coding process from scratch.

Keep Your Existing Billing Workflows

Integrate code recommendations into your EHR or RCM application. Your application controls code review, acceptance, and submission.

Support Different Integration Needs

Generate codes as part of an existing ambient session or use the standalone APIs to process notes already available in your application.

• E/M Coding recommends office and outpatient E/M codes from a completed clinical note. If you bill by time, include the total minutes (total_time_minutes) as a number greater than 0.
• For a preventive or wellness visit, include the patient’s date of birth, the date of the visit, and a visit type Suki supports. This helps Suki apply the right criteria for the recommended code.

​

Common use cases

E/M Coding for Ambient Visits

Your application already uses Ambient APIs to document patient visits. Enable E/M Coding on that session with artifacts: ["EM_CODES"], then read the recommended E/M code and the reason after the note is ready. You do not call a separate generate E/M codes API.

E/M Coding for Existing Clinical Notes

Your EHR already creates clinical notes, and you are not using Suki Ambient APIs for this visit. Submit the completed note with Suki’s standalone E/M Coding APIs, then read the codes with the coding session_id Suki returns. This does not change how you create or store the note.

Time-Based Visit Coding

Your clinicians bill based on the time spent with patients. Include the total visit time as total_time_minutes on the Ambient session or the standalone encounter, using a number greater than 0.

Preventive and Wellness Visit Coding

Your application handles preventive care and wellness visits. Include the visit type, the patient’s date of birth, and the date of service when you ask Suki to recommend an E/M code. The visit type must be one Suki supports.

If the visit has not yet been documented, use Ambient or your existing documentation workflow first.

E/M Coding works with clinical notes; it does not independently record or transcribe patient conversations.

​

How E/M Coding works

The integration follows the same general process whether you use Ambient or the standalone APIs:

Choose the integration path that matches your existing workflow. Refer to Choose Ambient or standalone for a detailed comparison of both approaches.

​

Information you need to provide to Suki for E/M Coding

E/M Coding uses the completed clinical note and available encounter details to generate code recommendations. Providing relevant patient, provider, and visit information helps Suki evaluate the appropriate coding criteria.

Information	What to provide and why
Clinical note	Provide the clinical note that Suki should use for E/M coding. Each note section must include a LOINC code (loinc) and its text in content.text. For Ambient sessions, Suki generates the note sections. For standalone coding, your application must send them. At least one section must contain text.
Patient type	Specify whether the patient is new or established. Suki uses this information to determine which E/M codes apply to the visit.
Date of birth, date of service, and visit type	Provide these details for preventive and wellness visits. The visit type must match one of the Visit types supported by Suki.
Total visit time	If the visit is billed based on time, provide the total time in minutes using total_time_minutes. Pass this value with the Ambient session or standalone encounter. The value must be a number greater than 0.
Existing diagnoses	Optionally provide diagnoses already recorded for the patient. Suki uses supported diagnosis information as additional context when recommending E/M codes. See Provide existing diagnoses.
Clinician NPI and insurance	Provide the clinician’s NPI and insurance information to give Suki additional context for the coding recommendation.

​

Provide existing diagnoses

Diagnoses and E/M codes describe different aspects of a visit. A diagnosis identifies a patient’s medical condition, such as hypertension. An E/M code, such as 99214, represents the level of service provided during the visit.

If you already have diagnoses for the encounter, include them in diagnoses.values, with a code and short description for each diagnosis. Suki uses ICD-10 and IMO diagnoses alongside the clinical note when recommending an E/M code. Your existing diagnoses remain unchanged.

​

Supported diagnosis types

An E/M Coding request treats these diagnosis types as follows:

• ICD-10: Used when evaluating the encounter and recommending an E/M code.
• IMO: Used when evaluating the encounter and recommending an E/M code.
• SNOMED: Accepted in the diagnosis list but not used to determine the E/M code.
• HCC: Not accepted as a diagnosis type in E/M Coding. Sending an HCC diagnosis causes validation to fail. HCC categories returned in Ambient structured data are separate from E/M Coding recommendations.

Send the diagnosis types your application already stores. You do not need to convert them to another supported format.

​

Review the E/M Coding recommendations

Suki returns a recommended E/M code with the reasoning behind it. A clinician or coding team can review the recommendation, verify the supporting details, and accept or change the code before billing.

Suki does not approve codes on your behalf, submit claims, or replace your existing billing workflow. Your application remains responsible for sending the approved code to your billing system.

• Field names and payload examples are in the how-to for your path.
• Use Add E/M codes to an ambient visit when coding runs with an ambient session, or Generate E/M codes from a note when you submit a note through the standalone APIs.
• After coding finishes, Get the generated E/M codes covers how to read the response.

​

Related guides

What E/M Coding Is

Understand E/M visit codes, how they are selected, and what Suki returns.

Choose Ambient or Standalone

Compare both integration approaches and choose the one that fits your application.

Add E/M Codes to an Ambient Visit

Enable E/M Coding for an ambient session, provide visit details, and retrieve the recommendations.

Generate E/M Codes from a Note

Submit a completed note through the standalone APIs and retrieve the recommended codes.

E/M Coding APIs Overview

Explore the standalone endpoints, authentication, and asynchronous generation workflow.

Get the Generated E/M Codes

Learn how to retrieve and interpret the generated codes and their supporting rationale.