Medblocks Blog | Health IT Standards

Health Informatics for everyone. We want to make sure everyone has access to information about health informatics and standards like openEHR, FHIR, SNOMED CT and LOINC.

FHIRSNOMED

Terminologies on FHIR

FHIR terminologies ensure interoperability in healthcare, enabling efficient data sharing with CodeSystem, ValueSet, and ConceptMap for standardized communication across systems.

Kritika Goyal

Business Development

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.

S. B. Bhattacharyya

Clinical Modeller

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.

Kritika Goyal

Business Development

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.

S. B. Bhattacharyya

Clinical Modeller

Authenticating Backend Services Using SMART on FHIR

SMART on FHIR secures third-party app integration with EHRs, offering authentication and authorization via OAuth2 and Discovery API, supporting both symmetric (shared secret) and asymmetric (public key) client authentication methods for backend services.

Kritika Goyal

Business Development

FHIR poised to gain center stage in the US

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.

Shaonli Dasgupta

Business Analyst

The Story of Medblocks

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

Sidharth Ramesh

Founder and CEO

The SNOMED CT Browser Explained

Use SNOMED CT Browser for exploring clinical concepts, synonyms, relationships, and semantic tags. Supports ECL for advanced search and MRCM for rules validation.

Kritika Goyal

Business Development

Introducing Medblocks UI

Medblocks UI, open-source alternative to Better EHR Studio for auto-generating forms from openEHR templates, now available under Apache 2 license.

Sidharth Ramesh

Founder and CEO

Setting up VSCode for Creating FHIR Resource

FHIR, developed by HL7, modernizes health data exchange by structuring it as resources for interoperability, contrasting with older HL7 versions. It uses a RESTful API, breaking down clinical data into resources like Patient and Medication Request.

Sidharth Ramesh

Founder and CEO