We believe healthcare deserves better software. Follow our journey building open infrastructure for the future of health.
Tired of EHR vendors holding your data hostage? openEHR separates clinical meaning from software, ensuring your health records outlive any application. No vendor lock-in, just future-proof healthcare data that works everywhere.
A simple XDS tutorial: understand Registry vs Repository and run the core XDS flow end-to-end with the NIST XDS Toolkit, Docker, and Postman.
In conversation with Dr. Videha Sharma, CEO of Fava Health, Sidharth discusses the future of precision medicine, and the technology infrastructure needed to support it.
Catalonia wanted to build an openEHR-based Clinical Data Repository for 8 million people. Medblocks worked with IBM and vitagroup to design the sync layer that keeps hundreds of hospital CDRs aligned with one central source of truth.
In this article, we walk you through how we built a FHIR server on top of Couchbase's NoSQL database. We'll cover the challenges, technical decisions, system architecture, and provide a step-by-step local setup guide.
Develop applications that better suit your clinical needs with a deeper understanding of openEHR Archetype Classes (Compositions, Sections and Entries) and the Clinical Knowledge Manager publishing lifecycle.
Explore how FHIR compares to XDS in healthcare data sharing and what it means for interoperability between hospitals and clinics.
Learn how FHIR uses semantic versioning to manage updates, ensure compatibility, and support smooth transitions between healthcare data standards like R4 and R5.
Curious how FHIR is used and who’s adopting it? Here are real-world examples of how FHIR is reshaping healthcare across the globe.
A journey through 30 years of healthcare interoperability, from costly 1980s interfaces to modern FHIR APIs, following how HL7 evolved from messages to models to web-friendly resources.
Learn when FHIR was created, why HL7 developed it, and how it transformed healthcare data interoperability across the industry.
From structured data to policy alignment, explore the 4 levels of interoperability and why they matter for compliance, care, and innovation.
Understand how FHIR resources like Patient, Observation, and Medication enable smooth, standardized healthcare data exchange.
Here we explore a real-world project we did with GE HealthCare, where we tackled the challenges of data normalization in oncology care.
EHR sidecars have a long history of filling gaps that core EHRs couldn’t. This blog looks at how sidecars started, how they evolved, and why they’re still relevant in healthcare today.
While open standards set the rules, open source gets the work done. We discuss choosing tools, handling semantics and making health systems actually interoperable.
In this article, we break down the Top 10 FHIR tools every developer should know in 2025, from building and hosting servers to validating, profiling, exploring, and testing your FHIR data.
In this article we’re breaking down the 12 most essential FHIR resources you need to know when starting out.
In episode 17 of the Digital Health Hackers Podcast, Sidharth speaks to Christopher Jones, CEO and founder of MatchRite Care. Born from personal loss, MatchRite Care is a unified health record portal that places the patient at the center.
Here we assess three main approaches to implementing RESTful FHIR servers - Facade, Synchronization and Hybrid. Additionally, we look at FHIR Documents and Messaging information exchange paradigms.
Deploy your patient-facing FHIR app across Epic hospitals in just 48 hours with this simple guide. We demystify Epic's Automatic Client Record Distribution, letting your apps reach patients without manual installs, legalese and red tape.
What does it take to build a truly modern EHR? In this in-depth conversation with Health Samurai CTO Nikolai Ryzhikov, we explore the path from monolithic systems to modular, FHIR-first platforms.
A 'facade' could be the answer you're looking for to solve your legacy data's FHIR-compatibility woes. In this simple tutorial, we take you through how to create a FHIR Facade on a Postgres database using Python.
This hands-on guide shows you how to code using the HAPI FHIR library in Java. and create real FHIR apps. Learn to work with FHIR Resources and interact with FHIR REST APIs.
This guide explores how to perform real-world operations like creating, reading, updating and deleting patient data on a FHIR Server using FHIR REST APIs and Python.
Introducing openFHIR, an open-source bidirectional mapping engine that converts between openEHR and FHIR health data standards. Built on the FHIRConnect specification and Apache 2.0 licensed.
FHIR's Questionnaire resource is a great way to build scalable and interoperable forms. Using the right question types can make or break your form data quality.
In episode 15 of the Digital Health Hackers Podcast, Sidharth speaks to Prof. David Ingram, one of the creators of openEHR. In this article we explore his story, from physicist to engineer to healthcare information technology innovator.
Health IT has various standards, and choosing the right one is often confusing. Let's understand the differences clearly so you can select the standard for the required task.
This article simplifies AQL (Archetype Query Language) by breaking it down into its basic concepts and providing examples that are suitable for readers at even beginner levels of openEHR proficiency.
This article provides a step-by-step guide to hosting an authenticated EHRbase server in the cloud and exposing its REST APIs over HTTPS using Traefik.
Have you been confused by all the openEHR terminology? What even are archetypes and templates? Read on to find out.
Let's go ahead and apply the fundamentals we learnt in 'Patient App Integration with SMART on Epic - How To Guide - The Fundamentals' and code a fully functional application. In the end, you'll be able to make more applications of your own using SMART.
Healthcare apps rely on a powerful framework called SMART on FHIR, a technology that’s quietly transforming healthcare. In this series, we’ll uncover how it works, and by the end, you’ll know how to build your SMART-powered health app from the ground up.
With the revolutionary technology of Large Language Models and AI assisted coding tools, building healthcare applications are no longer reserved for the seasoned programmers. This article is an introduction to building a FHIR web app for an absolute beginner using AI coding tools and techniques.
One organizes existing health data and the other gathers new inputs. Which is which? Do you need both? Read on to find out.
E-Patient Dave’s journey highlights the power of patient data access, collaboration, and open standards like FHIR and openEHR in transforming healthcare and redefining the doctor-patient relationship.
Leveraging PostgreSQL’s native full-text search, we cut query times from seconds to milliseconds, giving clinicians instant access to critical patient data.
Catalonia is set to make history by building the world’s first open-source, interoperable unified health record under the guidance of the Director of Digital Health Strategy—Jordi Piera.
Explore how Medblocks' user-friendly patient management solution, powered by FHIR APIs, optimizes hospital workflows. The design prioritizes clinician efficiency and flexibility, facilitating easy registration and real-time patient tracking. Discover how a user-centered design and vendor-neutral APIs enhance healthcare delivery.
Is it even possible to have healthcare forms that comply with a unified standard? In this tutorial, we explore FHIR's Questionnaire resource, which is a step in the right direction.
Grahame Grieve, known as the “father of FHIR,” stops by the Digital Health Hackers podcast with an update on global adoption and we look at some of the ongoing stumbling blocks to universal data sharing.
A thought leader in healthcare technology, Christian Chevalley joins us on the Digital Health Hackers podcast and shares his insights on connecting healthcare's disparate data landscape.
Explore the process of redesigning a user-friendly EHR interface for ophthalmology, emphasizing collaboration with domain experts and iterative design improvements.
Traditional approaches to healthcare software development have significant drawbacks. We believe a platform that has some standardized features and some extensible features might be the right answer.
Walkthrough on how to configure HAPI FHIR to do profile validation for you, and few fundamental concepts of FHIR Profiles.
Discover why FHIR is changing healthcare IT. Learn about FHIR's advantages over traditional HL7 standards like v2, C-CDA and v3, its rapid adoption, and how it simplifies health data exchange.
ERPNext is capable of handling almost all requirements of your healthcare enterprise. And with the low-code, open-source nature of the platform you can easily suggest improvements or customise it for your needs.
Learn 5 Key HL7 FHIR Concepts - Resources, Data Elements, Profiles, Exchange Paradigms, and Implementation Guides.
Extend your openEHR Server! Learn how to create an EHRbase plugin that can make additional calls to the database and create a transactional outbox.
Follow along and create your first HL7 FHIR CDS Hooks Service using NodeJS and the CDS Hooks Sandbox in less than 10 minutes.
HL7 CDS Hooks is a specification by HL7 that enables EHRs to integrate Clinical Decision Support using RESTful HTTP APIs.
Each domain has its own best-suited standard: FHIR, openEHR, and OMOP respectively. There's an art to picking the standard for the data use case.
The FHIR terminology service offers functions derived from a collection of CodeSystem, ValueSet, and ConceptMap resources.
Explore Clayton M. Christensen's vision for healthcare in "The Innovator's Prescription" – a groundbreaking approach to improving patient care.
Discover the critical role of Enterprise Master Patient Indexes (EMPI) in managing patient data across healthcare systems, ensuring accuracy and safety in treatment.
Learn to create FHIR patient resources: Navigate HL7, use JSON schemas and code with VS Code for seamless development. Learn healthcare interoperability step-by-step.
FHIR boosts healthcare data exchange, linking clinical, admin, and research via EHR, REST, Documents, Messages, and Services.
India's PM-JAY aims for value-based care with bundled pricing, tech access, and quality incentives for better health outcomes.
ETL (Extract, Transform, Load) moves data from legacy systems to FHIR, using Apache Debezium and Nifi for syncing databases in FHIR format.
Medblocks digitizes India's healthcare, integrating EHRs with Ayushman Bharat, targeting skill gaps and advancing structured data.
Medblocks implemented all 3 ABDM milestones for Andhra Pradesh's Health Ministry, overcoming challenges with ABHA API, webhook handling, encryption, and FHIR data transformation, contributing to India's digital healthcare evolution.
ABDM digitalizes India's healthcare with health IDs, interoperability, and data security, aiming for universal coverage via digital platforms.
openEHR standardizes health data with archetypes and templates for interoperability. Templates are built from Archetypes using the Archetype Designer Tool.
A beginner friendly guide to to navigating the openEHR CKM or Clinical Knowledge Manager, including searching, viewing and downloading clinical artefacts like archetypes and templates.
SNOMED allows creating extensions for terms not in its release, adhering to specific rules for standards. Extensions can map to pre-coordinated concepts or require post-coordination, published with a namespace for semantic interoperability.
In this comprehensive guide to the Clinical Knowledge Manager, understand how the CKM drives the core principles of openEHR - ensuring and facilitating standardization, interoperability, governance and community development.
SMART on FHIR enables health apps to connect with EHRs securely, including OAuth2 and OpenID for authorization and authentication. It supports standalone and EHR app launches, emphasizing security, PKCE support, and specifying access through scopes.
Refsets in SNOMED CT allow subsets for specific use cases, enabling standard compliance and external sharing. They cater to language, mappings, and situational needs with a mandatory regeneration post-SNOMED release.
CMS's Patient Access Rule mandates HL7 FHIR API for data access, provider directory via API, payer-to-payer data exchange, and daily federal-state data exchanges, enhancing interoperability and patient data access.
SMART on FHIR defines two ways in which clients can authenticate - symmetric (shared secret) and asymmetric (public key) client authentication.
FHIR leads healthcare interoperability, enabling secure data exchange across systems. CMS/ONC's initiatives like Blue Button 2.0, BCDA, and DPC pilot utilize FHIR for Medicare data sharing, enhancing patient access and care coordination.
Medblocks, initially focused on blockchain for medical record interoperability, evolved to address healthcare data challenges utilizing openEHR, FHIR, SNOMED, and LOINC for standardized data format and terminology, and using OAuth2 for secure data access
PHC system by Kyushu University & Grameen Communications uses eHealth and telemedicine, integrates openEHR and FHIR, serving 45,000+ since 2010, now includes Tele-Pathology and Tele-Eye Care.
Use SNOMED CT Browser for exploring clinical concepts, synonyms, relationships, and semantic tags. Supports ECL for advanced search and MRCM for rules validation.
Medblocks UI, open-source alternative to Better EHR Studio for auto-generating forms from openEHR templates, now available under Apache 2 license.
Set up a SNOMED CT terminology server using Docker and Hermes: Clone Hermes, index SNOMED CT files, execute index.sh, start server with docker-compose up.
Dr. Sidharth and team developed a Covid care application for Dr. Sunil Gokavi's facility during the second wave, enhancing patient data analysis and care readiness.
Exploring web components for front-end development, moving from Vue to Svelte for Medblocks UI due to performance, with a focus on lit-html and web components for framework-independent, efficient UI construction.
