chore: expand fhir2omop docstrings and clarify dropped field semantics

[fern-api]

16.2.0 → 16.2.1

Improve developer-facing documentation across the fhir2omop client and
types. The changes clarify exactly which FHIR resource types produce
OMOP rows, how unsupported resources are handled, and what the dropped
field represents. No public API signatures were changed.

Key changes:

• Add detailed FHIR-to-OMOP resource mapping table to create() docstrings in Fhir2OmopClient, AsyncFhir2OmopClient, RawFhir2OmopClient, and AsyncRawFhir2OmopClient
• Clarify CreateOmopResponse.dropped field description: only supported resource instances with missing required data appear here; unsupported types are silently ignored
• Update fhir_resources parameter docstring to enumerate all supported row-producing resource types explicitly

🌿 Generated with Fern

---

✅ Customizations automatically preserved in this update.

---

Note

Low Risk
Documentation and version/metadata updates only; no runtime or API contract changes beyond clearer field descriptions.

Overview
Releases phenoml 16.2.1 from an updated API spec (Fern regen): version metadata, User-Agent / SDK headers, bundled openapi.json, and minor lockfile bumps (anyio, certifi).

The substantive change is developer documentation for fhir2omop.create and related types—no public method signatures change. Docstrings and OpenAPI/reference.md now spell out the FHIR → OMOP table mapping (e.g. Patient → person, medication resources → drug_exposure, numeric vs non-numeric Observation), which resource types are accepted but not mapped, and that Medication is reference-only.

CreateOmopResponse.dropped and the fhir_resources parameter docs are clarified: dropped lists only supported resources that lacked required subject/code/medication data; unsupported types are ignored and do not appear in dropped.

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