openEHR vs FHIR and other health IT standards
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.
SNOMED Articles
We believe healthcare deserves better software. Follow our journey building open infrastructure for the future of health.
Why We're Reinventing the EHR
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.
What is a FHIR Terminology Service?
The FHIR terminology service offers functions derived from a collection of CodeSystem, ValueSet, and ConceptMap resources.
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.
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.
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.
Setting up a SNOMED CT Terminology Server using Hermes
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.