`.
* **Laterality**: Left/right/bilateral information when applicable
* **Post coordination flag**: Indicates if the diagnosis requires additional modifiers
The IMO code returned in the output may be different from any IMO code that was sent in the input payload. This is normal: Suki uses the most accurate code based on the conversation content.
If enrichment fails, Suki still returns the diagnosis with available information to ensure you don't lose generated content.
### Retrieving generated diagnoses
Refer to the [How to use PBC for APIs and SDKs](/api-reference/capabilities/problem-based-charting#how-to-use-pbc-for-apis-and-sdks) section for more details.
## Handling reambient scenarios
In reambient scenarios, where a single patient encounter involves multiple recording sessions, understanding how context is managed is critical.
Sessions do not **automatically inherit diagnoses** from previous sessions. Each session starts fresh. You must provide all relevant diagnoses for each new session.
**What this means:**
* When you use APIs in your implementation, only diagnoses passed via the Context APIs for the current session are considered
* Diagnoses from previous sessions are **not automatically carried forward**
* You must provide the complete and current list of all relevant diagnoses for each new session
**Your responsibilities:**
Because sessions don't inherit context, you must provide the complete list of all relevant diagnoses for each new session. This includes:
* **Modified diagnoses**: Any diagnoses that were changed by the provider in previous sessions
* **New diagnoses**: Any newly added diagnoses from previous sessions
* **Existing diagnoses**: Diagnoses from previous sessions that should be retained
**Recommended workflow:**
```mermaid actions={false} theme={"theme":{"light":"github-dark","dark":"material-theme-darker"}}
%%{init: {'theme':'base', 'themeVariables': { 'primaryColor':'#FFE148','primaryTextColor':'#1a1a1a','primaryBorderColor':'#FFE148','lineColor':'#FFE148','secondaryColor':'#FFF394','tertiaryColor':'#FFFADE','mainBkg':'#FFF394','secondBkg':'#FFFADE','border1':'#FFE148','border2':'#FFE148','arrowheadColor':'#FFE148','fontFamily':'Inter, system-ui, sans-serif','fontSize':'14px','nodeBorder':'#FFE148','clusterBkg':'#FFFADE','clusterBorder':'#FFE148','defaultLinkColor':'#FFE148','titleColor':'#1a1a1a','edgeLabelBackground':'#FFE148','nodeTextColor':'#1a1a1a'}}}%%
graph TD
A[Start session] --> B[Context with
existing diagnoses]
B --> C[Conduct encounter]
C --> D[End session]
D --> E[Get generated
diagnoses]
E --> F{Reambient session?}
F -->|Yes| G[Include all
relevant diagnoses]
F -->|No| H[Complete]
G --> B
style A fill:#FFF394,stroke:#FFE148,stroke-width:2px,color:#1a1a1a
style B fill:#FFF394,stroke:#FFE148,stroke-width:2px,color:#1a1a1a
style C fill:#FFF394,stroke:#FFE148,stroke-width:2px,color:#1a1a1a
style D fill:#FFF394,stroke:#FFE148,stroke-width:2px,color:#1a1a1a
style E fill:#FFF394,stroke:#FFE148,stroke-width:2px,color:#1a1a1a
style F fill:#FFE148,stroke:#FFE148,stroke-width:2px,color:#1a1a1a
style G fill:#FFF394,stroke:#FFE148,stroke-width:2px,color:#1a1a1a
style H fill:#FFF394,stroke:#FFE148,stroke-width:2px,color:#1a1a1a
```
After each session, retrieve the generated diagnoses using the Structured Data API, then include all relevant diagnoses (including any modifications) when starting the next session.
## Best practices
* **Provide complete context**: Always include all relevant existing diagnoses when starting a session
* **Use ICD10 when possible**: ICD10 codes are preferred and processed most reliably
* **Handle reambient carefully**: Retrieve diagnoses after each session and include them in the next session
* **Validate codes**: Ensure diagnosis codes are valid before sending them
* **Monitor output**: Check which diagnoses were updated or generated to understand what was discussed
* **Update after user edits**: If providers modify diagnoses, include those modifications in subsequent sessions
## FAQs
In reambient scenarios, the system does not automatically carry forward diagnoses from previous sessions. You must provide the complete and current list of all relevant diagnoses for each new session.
The system uses [IMO APIs](https://www.imohealth.com/) to find the best possible ICD10 code equivalent for non-ICD10 codes. If a code cannot be mapped, that diagnosis is skipped.
The system normalizes all codes to ICD10 before processing. ICD10 is used as the source of truth for all diagnosis operations.
The system deduplicates diagnoses based on the ICD10 code. Diagnoses with the same ICD10 code are merged, and their notes are combined.
Only diagnoses that were updated or newly generated are returned. Diagnoses that weren't discussed during the session are not included in the output.