feat: expand OMOP CDM coverage and add provider_id/location_id fields

[fern-api]

16.4.0 → 16.5.0

Added

• CareSiteRow, DeathRow, LocationRow, ObservationPeriodRow, ProviderRow — five new OMOP CDM v5.4 row types exported from phenoml.fhir2omop, covering care sites, deaths, locations, observation periods, and providers.
• OmopTables.location, .care_site, .provider, .death, .observation_period — new optional list fields on OmopTables populated when the corresponding OMOP tables are produced by the FHIR-to-OMOP conversion.
• provider_id field — added as an optional field to ConditionOccurrenceRow, DrugExposureRow, MeasurementRow, ObservationRow, ProcedureOccurrenceRow, and VisitOccurrenceRow to link clinical events to their ordering provider.
• PersonRow.location_id and VisitOccurrenceRow.care_site_id — new optional linkage fields connecting persons to their location and visits to their care site.
• CreateMultiResponseResourcesItem.source_pages — new optional List[int] field containing 1-indexed page numbers indicating which source document pages a FHIR resource was extracted from (populated by /lang2fhir/document/multi only).

---

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-30_15-41-54_988 origin/fern-bot/2026-06-30_15-41-54_988

   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-30_15-41-54_988 origin/fern-bot/2026-06-30_15-41-54_988

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 API types and version bump; main operational risk is merging without resolving the Fern replay pyproject.toml conflict, which could drop custom OpenAPI packaging on the next regen.

Overview
Release 16.5.0 (Fern regen from API spec 5275e24…) bumps package/SDK metadata, bundled OpenAPI, wire tests, and examples to match the updated API.

FHIR → OMOP (phenoml.fhir2omop) adds five OMOP CDM v5.4 row models (CareSiteRow, DeathRow, LocationRow, ObservationPeriodRow, ProviderRow) and wires them into OmopTables as optional location, care_site, provider, death, and observation_period lists. Existing clinical row types gain optional provider_id; PersonRow gets location_id; VisitOccurrenceRow gets provider_id and care_site_id.

Lang2FHIR adds optional source_pages (sourcePages in JSON) on CreateMultiResponseResourcesItem for 1-indexed document page provenance (document multi endpoint).

Merge note: Fern replay marks an unresolved conflict on pyproject.toml between the new generation (version 16.5.0) and the prior customization that pins version and openapi.json wheel/sdist packaging—resolve with fern replay resolve before merge if you rely on that patch.

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