Removed in @polaris/sdk 5.0.0. Polaris owns no FHIR construction. Every FHIR type, profile, canonical, terminology constant and client capability comes from @cognovis/fhir-sdk; @cognovis/fhir-release is internal to it. The /emission, /deidentification, /fhir-practitioner, /projections, /patient-context, /patient-summary, /agent-context, /punktwert and /eau subpaths no longer exist; the published surface is ., /adapters, /sync, /documents, /scanner and /llm. Examples below that import a removed subpath are historical.
FHIR integration boundaries
The previous Polaris client factory, custom HTTP transport and piiMode
integration instructions are retired with @polaris/sdk/fhir.
Ordinary FHIR access belongs to @cognovis/fhir-sdk/client.
Configure that client using its published setup contract, caller-specific
credentials and store-granted authority. No Polaris wrapper is required.
Generated profile descriptors and types come from
@cognovis/fhir-sdk, which owns the generated
@cognovis/fhir-release artifacts internally. The former
@polaris/sdk/emission, @polaris/sdk/projections and
@polaris/sdk/agent-context subpaths no longer exist and have no
Polaris replacement.
The advanced transport seam is reserved for tests, replay and deliberately implemented alternate stores. It is not the ordinary application setup path.
Use the canonical client's explicit deidentification policy scope for ordinary FHIR access. Polaris audited context helpers preserve their existing caller authority, audit and egress requirements.