22 Followers · 542 Posts

Fast Healthcare Interoperability Resources (FHIR, pronounced "fire") is a draft standard describing data formats and elements (known as "resources") and an application programming interface (API) for exchanging electronic health records

Official site

Discussion Luis Angel Pérez Ramos · Nov 8, 2023

Hi everyone!

The other day I was reflecting on the possibilities that FHIR brings us in the world of interoperability and electronic medical records and it gave me mixed feelings, let me explain, first a small introduction.

Introduction

As you well know, FHIR is based on parameterizing a series of concepts that it calls resources in JSON or XML format with the intention of covering the most common cases within the healthcare environment, relying on HTTP communications to cover CRUD and query functionalities.

15
1 856
Discussion Jose-Tomas Salvador · Oct 21, 2022

Good morning, evening, night,... wink

A small reflection/question for today... it's true that new IRIS for Health (I4H) releases are more and more powerful each time regarding FHIR capabilities. Nowadays it allows us to consume FHIR resources with extrem easiness, we can connect with end-points in external FHIR servers very easily and make I4H act as passthrough or consume their resources... or, even more, we can define, configure and run a FHIR repository in, literally, less than 5 minutes.

3
0 441
Discussion André Sheydin · Feb 28

Hello everyone,

I am André from MedVertical. We are exploring InterSystems-native ways to operationalize continuous FHIR conformance: repeatable regression runs, baseline/delta comparisons, and evidence-style reporting to detect drift after releases and IG changes.

In many FHIR implementations, validation is done “point-in-time” in pre-prod, but conformance degrades in production due to IG/profile updates, terminology changes, mapping evolution, upstream releases, and configuration drift.

1
2 202