How to Configure the Pipeline in Firely Server
Configure the pipeline — Firely Server documentation - Firely Docs
Documentation was published detailing the configuration of the Firely Server pipeline to support FHIR R3 and FHIR R4 standards.
Summary
This article technically explains how to configure the data processing pipeline within Firely Server. It utilizes `PipelineOptions` and `SupportedInteractions` to precisely control the API's operational scope and supported FHIR operations (CRUD, etc.).
Details
Firely Server allows users to define their data processing pipeline using `PipelineOptions`. This configuration enables granular control over which plugins are integrated into the service (`Include`) and which are excluded (`Exclude`). Furthermore, the system supports controlling the supported operation levels via `SupportedInteractions`. Operations can be enabled or disabled across three scopes: Instance Level, Type Level, and Whole System. For example, standard FHIR operations like `read`, `create`, `search`, and specialized functions like `$expand` or `$compose` can be explicitly managed. The default setup defines two main branches: the root path (`/`) for the primary FHIR RESTful API, and `/administration` for the administration API. This detailed control mechanism is crucial for enhancing security and stability by strictly limiting the required FHIR operations and business logic within a system.
Technology Note
FHIR（Fast Healthcare Interoperability Resources）は医療データ交換の国際標準。このエントリの関連技術: FHIR
Original content copyright by respective publishers