Skip to content

Release 17.6.0: add agent conflict errors#173

Merged
gavinsharp merged 4 commits into
mainfrom
fern-bot/2026-06-18_18-09-52_727
Jun 18, 2026
Merged

Release 17.6.0: add agent conflict errors#173
gavinsharp merged 4 commits into
mainfrom
fern-bot/2026-06-18_18-09-52_727

Conversation

@fern-api

@fern-api fern-api Bot commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

17.5.0 -> 17.6.0

Adds a typed 409 conflict error for concurrent agent chat turns and clarifies session concurrency docs. Also expands fhir2omop docs around supported resource mappings and dropped-resource semantics. Minor bump because the SDK adds a public typed exception.

Added

  • ConflictError — new typed exception thrown by RawChatClient.send(...), RawChatClient.stream(...), AsyncRawChatClient.send(...), and AsyncRawChatClient.stream(...) for HTTP 409 responses when a session already has an active turn.

Changed

  • AgentChatRequest.getSessionId() and AgentStreamChatRequest.getSessionId() — Javadoc now states that only one request may be active per session at a time and overlapping turns return 409 Conflict.
  • Fhir2OmopClient.create(...) and AsyncFhir2OmopClient.create(...) — Javadoc now lists the supported FHIR resource-to-OMOP table mappings and clarifies that unsupported resource types are accepted but ignored.
  • CreateOmopResponse.getDropped() — Javadoc now clarifies that only supported resources missing required subject/patient, code, or medication reference data appear in dropped; unsupported resource types are ignored.

Note

Low Risk
Adds a new public exception type and documentation-only fhir2omop clarifications; no runtime mapping or auth changes beyond reflecting the API spec.

Overview
17.6.0 is a Fern-regenerated SDK bump (17.5.0 → 17.6.0) aligned with an updated OpenAPI spec.

Agent chat: Adds public ConflictError (HTTP 409) and maps it in sync/async RawChatClient for send and stream when a session already has an in-flight turn. session_id Javadoc on AgentChatRequest / AgentStreamChatRequest (and reference docs) now documents one active request per session and 409 on overlap.

FHIR2OMOP: No mapping logic changes—only expanded Javadoc/OpenAPI text on create, CreateOmopRequest, and CreateOmopResponse.getDropped() listing supported FHIR→OMOP row types, which bundle types are ignored vs. listed under dropped, and that unsupported types are silently ignored.

Reviewed by Cursor Bugbot for commit 640eb50. Bugbot is set up for automated code reviews on this repo. Configure here.

fern-api Bot and others added 3 commits June 18, 2026 18:09
Generated by Fern
CLI Version: unknown
Generators:
  - fernapi/fern-java-sdk: 4.9.2
…gent chat

Introduce the FHIR-to-OMOP mapping service as a first-class SDK client,
and add HTTP 409 Conflict error handling to the agent chat endpoints.

Key changes:
- Add `Fhir2OmopClient` and `AsyncFhir2OmopClient` (plus raw variants) accessible via `PhenomlClient.fhir2Omop()` and `AsyncPhenomlClient.fhir2Omop()`, exposing `POST /fhir2omop/create`
- Add new request/response types: `CreateOmopRequest`, `CreateOmopResponse`, `OmopTables`, `PersonRow`, `VisitOccurrenceRow`, `ConditionOccurrenceRow`, `DrugExposureRow`, `ProcedureOccurrenceRow`, `MeasurementRow`, `ObservationRow`, `MappingEntry`, `Summary`, and `DroppedResource`
- Add `ConflictError` (HTTP 409) to agent chat sync and async clients (`RawChatClient`, `AsyncRawChatClient`)

🌿 Generated with Fern
@gavinsharp gavinsharp changed the title feat: add Fhir2Omop client and ConflictError for agent chat Release 17.6.0: add agent conflict errors Jun 18, 2026
@gavinsharp gavinsharp merged commit 2f42bfb into main Jun 18, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant