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.
Getting started with Polaris helpers
Install @polaris/sdk through the Cognovis npm registry at
https://npm.cognovis.de, using the version approved for your application.
Map the @polaris scope in your package-manager configuration, for example
@polaris:registry=https://npm.cognovis.de in .npmrc or an
equivalent scope entry in bunfig.toml. Registry credentials belong in that
configuration, never source code.
The former FHIR client and mock walkthrough using @polaris/sdk/fhir is retired.
The SDK has no general FHIR client subpath.
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.
LLM integration uses @polaris/sdk/llm. A transformed FHIR response
does not by itself authorize external egress; use the applicable audited context and
gateway contracts.