Nikolai Ryzhikov

FHIR's nested structure works for APIs but frustrates SQL analytics. SQL on FHIR uses a simple DSL to define flat views – portable across ETL/ELT runners, tested via shared suites. Nikolai Ryzhikov's DevDays session demos the workflow from Synthea data to Grafana dashboards.

Master unified FHIR async patterns for bulk exports and other long-running operations using Bulk Data Access and R5/R6: Prefer headers (bundle/redirect/manifest), polling, callbacks, long polling, plus HTTP examples and visual flows for Manifest, Bundle, Redirect, Cancel, and Callback workflows.

SQL on FHIR in PostgreSQL. Two types of SQL on FHIR View Runners - ETL (in-memory) & ELT (in-database) and demo the ELT implementation for PostgreSQL.

Discover how to flatten complex healthcare data using ViewDefinition resource. Dive into our article for tips and examples.

How to keep patient records consistent and complete

Terminology in Health IT is a very important and complicated aspect. A lot of interoperability depends on how accurately do you encode your data.

If you are interested in FHIR databases and analytics on FHIR and going to be not far from Baltimore September 29–30 — please join us at the FHIR Connectathon 19 and brand new Storage and Analytics track!

Last week Ryan Brush (author of Bunsen project) from Cerner published on Github the first version of the SQL-on-FHIR draft. This will be a hot topic to discuss in the upcoming FHIR Connectathon #19.

Using FHIR for data persistence is becoming a popular topic of discussion in the community. Our CTO shares his thoughts on when and why you would use FHIR as the storage format for your healthcare data.

Our CTO provides a brief technical overview of the HL7 FHIR Standard, from analysis of HL7 FHIR healthcare informational data model to potential use cases using FHIR APIs and potential limitations you should be aware of when planning to develop using FHIR standard.

Many people are talking about microservies as the preferred approach to structure complex health information systems. But there are overlooked consequences to using microservices over monolithic architectures.

Making sure your healthcare data is secure is a top priority for any health information system. Here’s what you should think about when managing access control for your FHIR server.

The FHIR standard is becoming the de facto way to manage healthcare data. Our CTO explains why FHIR implementations with dynamic languages could provide valuable feedback to the FHIR standard and FHIR community.

Deciding between which healthcare data standard to use can be hard. We evaluated whether HL7 v2, v3 & CDA, or FHIR is the best choice for a laboratory integration project. We found FHIR is the best choice because the FHIR API perfectly compliments the custom API of the laboratory system.