Medblocks Blog

Everything about health information standards like openEHR, FHIR, SNOMED CT, LOINC and more.


Poornachandra Vivekanenda
Poornachandra Vivekanenda
16 June 2024

Migrating Legacy Data to FHIR at scale using ETL's

ETL (Extract, Transform, Load) moves data from legacy systems to FHIR, using Apache Debezium and Nifi for syncing databases in FHIR format.

Migrating Legacy Data to FHIR at scale - ETL using Kafka, Debezium, and Nifi

Poornachandra Vivekanenda
Poornachandra Vivekanenda
16 June 2024

The missing step to complete healthcare digitization

Medblocks digitizes India's healthcare, integrating EHRs with Ayushman Bharat, targeting skill gaps and advancing structured data.

The missing step in a move to complete healthcare digitization - A market insight

Sidharth Ramesh
Sidharth Ramesh
16 June 2024

Case Study - Implementing ABDM for the Government of Andhra Pradesh

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.

Case Study - Implementing ABDM for the Government of Andhra Pradesh

Shilpi Dasgupta
Shaonli Dasgupta
16 June 2024

ABDM: Ushering in the UPI moment of healthcare

ABDM digitalizes India's healthcare with health IDs, interoperability, and data security, aiming for universal coverage via digital platforms.

Ayushman Bharat Digital Mission: Ushering in the UPI moment of healthcare

Im G20231205132743~2
Safa
9 April 2025

Designing openEHR templates using the Archetype Designer

openEHR standardizes health data with archetypes and templates for interoperability. Templates are built from Archetypes using the Archetype Designer Tool.

Designing openEHR templates using the Archetype Designer

Im G20231205132743~2
Safa
9 April 2025

How to Use the openEHR Clinical Knowledge Manager

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.

A Deep Dive Into The Clinical Knowledge Manager

S. B. Bhattacharyya
S. B. Bhattacharyya
16 June 2024

Extensions to SNOMED CT

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.

Extensions to SNOMED CT

Im G20231205132743~2
Safa
9 April 2025

Understanding the openEHR Clinical Knowledge Manager

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.

Understanding OpenEHR Clinical Knowledge Manager

Kritika Goyal
Kritika Goyal
16 June 2024

SMART on FHIR-Frontend Flows

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.

SMART on FHIR-Frontend Flows

S. B. Bhattacharyya
S. B. Bhattacharyya
23 May 2024

What is a Simple Refset in SNOMED CT?

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.

What is a Simple Refset in SNOMED CT?

Shilpi Dasgupta
Shaonli Dasgupta
16 June 2024

CMS Interoperability and Patient Access Final Rule

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.

CMS Interoperability and Patient Access Final Rule

Kritika Goyal
Kritika Goyal
16 June 2024

SMART on FHIR Authentication for Backend Services

SMART on FHIR defines two ways in which clients can authenticate - symmetric (shared secret) and asymmetric (public key) client authentication.

Authenticating Backend Services Using SMART on FHIR
Save lives with digital healthcare innovation
© 2024 Medblocks. All rights reserved.