feat: add OMOP CDM v5.4 table types and provider linkage fields

[fern-api]

16.4.0 → 16.5.0

Added

• CareSiteRow, DeathRow, LocationRow, ObservationPeriodRow, and ProviderRow — new Pydantic models under phenoml.fhir2omop representing the corresponding OMOP CDM v5.4 destination tables.
• OmopTables.location, .care_site, .provider, .death, and .observation_period — new optional list fields on OmopTables that surface rows for the newly supported OMOP tables returned by the FHIR-to-OMOP conversion endpoint.
• provider_id optional field added to ConditionOccurrenceRow, DrugExposureRow, MeasurementRow, ObservationRow, ProcedureOccurrenceRow, and VisitOccurrenceRow to link clinical events to their performing provider.
• care_site_id optional field added to VisitOccurrenceRow; location_id optional field added to PersonRow to capture physical location linkage.

---

See full changelog

---

Action required: 1 file with unresolved customization conflicts

The new generation changed code you previously customized. Non-conflicting customizations have been applied automatically. The following files need manual resolution:

File	Your customization	Why it conflicted
pyproject.toml	Release 15.0.2: restore bundled openapi.json packaging (#169)	The new generation changed the same lines you edited

How to resolve

1. Check out this branch:

   git fetch origin && git checkout -b fern-bot/2026-06-23_21-44-49_528 origin/fern-bot/2026-06-23_21-44-49_528

   Or if you don't have the repo cloned:

   git clone https://github.com/phenoml/phenoml-python-sdk.git && cd phenoml-python-sdk && git checkout -b fern-bot/2026-06-23_21-44-49_528 origin/fern-bot/2026-06-23_21-44-49_528

2. Run: fern replay resolve
3. Open the conflicting files in your editor — you'll see standard merge conflict markers
4. Resolve using your editor's merge tools (VS Code, IntelliJ, etc.)
5. Run: fern replay resolve again to finalize
6. Push your changes

Your resolved customizations will be remembered on future SDK generations.
If you merge this PR without resolving, your unresolved customizations will conflict again on the next generation.

---

Note

Low Risk
Additive, optional Pydantic fields and new types only; no client method or auth changes. Packaging conflict in replay is operational, not runtime.

Overview
Bumps the SDK to 16.5.0 (changelog, User-Agent / X-Fern-SDK-Version, Fern metadata) and expands phenoml.fhir2omop so FHIR-to-OMOP responses can deserialize additional OMOP CDM v5.4 tables and cross-table IDs.

New models — CareSiteRow, DeathRow, LocationRow, ObservationPeriodRow, and ProviderRow, exported from phenoml.fhir2omop and wired into lazy-import __init__ modules.

OmopTables — adds optional list fields location, care_site, provider, death, and observation_period alongside the existing clinical tables.

Linkage on existing rows — optional provider_id on condition, drug, measurement, observation, procedure, and visit occurrence rows; care_site_id on visits; location_id on person rows.

Wire tests’ mock /fhir2omop/create body is updated to include the new table keys. Fern replay records a new generation; the prior pyproject.toml customization (bundled openapi.json packaging) is marked unresolved because the regen also touched the version line—merge may need fern replay resolve before the next generation.

^{Reviewed by Cursor Bugbot for commit 0d97036. Bugbot is set up for automated code reviews on this repo. Configure here.}