SNOMED-CT as a source?

Projects Open Concept Lab
8

Hello All,

A few points I would like to add:

  1. IPS Set: There is a free (Creative Commons License) terminology set released by SNOMED called: IPS (International Patient Summary). The IPS Terminology is the next evolution of the IPS free set, providing advanced terminology features for non-Affiliates to use in their IPS implementations. The full content of the IPS Terminology can be browsed here: SNOMED International IPS Browser. Read more about IPS here: https://www.snomed.org/international-patient-summary-terminology. I feel this set, should be in OCL (since this is the one that SNOMED encourages non-affiliated member countries to use).

  2. The IPS set is also a good choice for low-resource settings which want to run a mini version of the SNOMED Terminology Server (since terms are about 50K in IPL).

  3. Bahmni has done first cut integration of both OCL (using OCL Subscription module), and of SNOMED TS (over FHIR), which means any member country that wants to try Bahmni with SNOMED CT (snowstorm) can now browse diagnosis, reports, form-fields by configuring Bahmni to point to opensource Snowstorm server. Demos for this will be online soon here: https://bahmni.atlassian.net/wiki/spaces/BAH/pages/3132686337/SNOMED+FHIR+Terminology+Server+Integration+with+Bahmni

  4. It would be a good idea if OCL could ship with complete SNOMED-CT, but I agree with @akanter – from an interface perspective, many SNOMED terms will make the EMR complicated for data entry, and from past experience, it seems most facilities want to use a small set of terms in their facility. Also, it is better to use terms on the screen that people are familiar with, and instead use reference-term mappings to display SNOMED/LOINC/ICD-10 codes. It will also slow down the UI experience, because huge number of terms will match the entered sub-string. Also, legally, it is complicated for sure. In this case, the IPS mentioned above is better. It has been created keeping in mind the most commonly used terms across SNOMED CT deployments.

  5. By default, currently Bahmni has chosen to ship with CIEL out-of-the-box, because it offers the best balance between, ease-of-interface-use, mappings to multiple reference, opensource, and first class maintenance by OpenMRS community+OCL. We find that most implementations choose to use their own custom concepts, and we hope with CIEL, people will adopt it and make minor additions at max.

@kai – Maybe you can provide some perspective to this discussion from SNOMED International perspective. Thanks!