Aleksandr Kislitsyn

Run CMS/HEDIS eCQMs as SQL on FHIR — no CQL engine. ViewDefinitions and SQLQuery Libraries pack into one FHIR package you can move to any SQL-on-FHIR server, making measure calculation portable and standard.

Aidbox & Formbox February update: compliant $purge, vault-based secrets, and modular Formbox deployment.

Use agentic coding on FHIR to build a Patient Weight dashboard from a single prompt — data model, terminology, and live demo with Aidbox.

In 2025, Aidbox focused on performance, FHIR conformance, and developer experience—removing bottlenecks and aligning deeply with the FHIR ecosystem. This post highlights the key architectural changes that make Aidbox faster, more transparent, and production-ready.

Aidbox just became the first FHIR server to pass all SQL-on-FHIR tests — thanks to full support for the repeat element. This update lets engineers query deeply nested FHIR structures like QuestionnaireResponse.item with a single, elegant definition.

Role-Based Access Control for FHIR resources using Keycloak and SMART on FHIR v2: scopes, role mapping, token configuration, and Aidbox enforcement.

Discover how AI and Aidbox make building FHIR Implementation Guides faster, easier, and accessible to both developers and healthcare experts.

We recently added experimental support for the MCP Server in Aidbox. Let's explore how to set it up and use it to interact with FHIR resources through an LLM interface.

Discover how a FHIR-native microservices approach streamlines healthcare system development. Learn how to build scalable, interoperable services using FHIR’s ready-to-use APIs, domain models, and terminology tools—ideal for greenfield and legacy system modernization.

FHIR API gateway design: routing, security, rate limiting, and API management for healthcare — with architecture patterns and Aidbox examples.

What is SearchParameter’s code? Which SearchParameters are available in the FHIR Server? Is it possible to have a clash of two different SearchParameters having the same code? How should this clash be resolved according to the FHIR specification? What to do in such situations in Aidbox?