feat: add AsyncFhir2OmopClient and fhir2omop service support#172
Closed
fern-api[bot] wants to merge 3 commits into
Closed
feat: add AsyncFhir2OmopClient and fhir2omop service support#172fern-api[bot] wants to merge 3 commits into
fern-api[bot] wants to merge 3 commits into
Conversation
Generated by Fern CLI Version: unknown Generators: - fernapi/fern-java-sdk: 4.9.2
…ce support Expose the FHIR-to-OMOP CDM v5.4 mapping service through the async client surface. Consumers can now call `client.fhir2Omop().create(...)` to post a FHIR R4 resource or Bundle and receive typed OMOP rows grouped by table, per-coding mapping entries, dropped-resource details, and a resolution summary. Key changes: - Add `AsyncFhir2OmopClient` with a `create(CreateOmopRequest)` method posting to `POST /fhir2omop/create` - Expose `AsyncPhenomlClient.fhir2Omop()` accessor returning the new client - Register `fhir2omop` as a new service in the OpenAPI spec with full request/response schemas (`fhir2omop_CreateOmopRequest`, `fhir2omop_CreateOmopResponse`, OMOP row types, `MappingEntry`, `Summary`, `DroppedResource`) - Add `"aidbox"` as a supported `Provider` enum value in code examples and OpenAPI spec - Update spec commit hash and code-example SDK version metadata 🌿 Generated with Fern
…de6df7e477ecd13e [skip ci]
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
17.5.0 → 17.6.0
Added
Fhir2OmopClient/AsyncFhir2OmopClient— new synchronous and asynchronous clients (plus raw-response variants) accessible viaPhenomlClient.fhir2Omop()andAsyncPhenomlClient.fhir2Omop(), exposingcreate(CreateOmopRequest)to convert a FHIR R4 resource or Bundle to OMOP CDM v5.4 rows viaPOST /fhir2omop/create.CreateOmopRequest/CreateOmopResponse— new request/response types for the FHIR-to-OMOP conversion endpoint, carryingfhirResourcesand returningtables,mappings,dropped,vocabVersion,summary,success, andmessagefields.PersonRow,VisitOccurrenceRow,ConditionOccurrenceRow,DrugExposureRow,ProcedureOccurrenceRow,MeasurementRow, andObservationRowclasses aggregated underOmopTables.MappingEntry/Summary/DroppedResource— new supporting types describing per-coding resolution status (ALREADY_STANDARD,MAPPED,UNCHECKED,UNMAPPED), aggregate mapping statistics, and resources that could not be shaped into OMOP rows.BadRequestError,UnauthorizedError,InternalServerError,ServiceUnavailableError— new typed exception classes extendingPhenomlClientApiException, thrown for HTTP 400, 401, 500, and 503 responses from the FHIR-to-OMOP endpoint.Provider.AIDBOX—"aidbox"is now a supported value in theProviderenum, with a correspondingVisitor.visitAidbox()method.See full changelog
Note
Low Risk
No runtime or API signature changes in the diff—only version strings and generated/docs text updates.
Overview
Bumps the Java SDK to 17.6.0 (Gradle/Maven, Fern metadata,
User-Agent/X-Fern-SDK-Version, and embedded OpenAPI spec commit).The substantive change is documentation for
POST /fhir2omop/create: Javadoc on thefhir2omopclients,CreateOmopRequest,CreateOmopResponse,reference.md, andopenapi.jsonnow spell out which FHIR R4 types produce OMOP rows (e.g.Patient→person, medication resources andImmunization→drug_exposure, numeric vs non-numericObservation→measurementvsobservation), which bundle entries are accepted but not mapped, and thatdroppedis only for supported types missing required subject/code/medication data—not for ignored unsupported types.changelog.mdadds a 17.6.0 entry that also lists broader FHIR2OMOP client/types additions; those are not part of this diff’s file changes.Reviewed by Cursor Bugbot for commit e3dc42b. Bugbot is set up for automated code reviews on this repo. Configure here.