SNOMED-CT as a source?

Thanks, Rory! Appreciate the feedback and was unaware that the IPS contains the appropriate hierarchies and relationships (not just to codes and descriptions). I need to update my understanding! As for the use of SNOMED as a point-of-care terminology service… as someone who has been working with SNOMED and pushing SNOMED use for 25 years, I have yet to be convinced that it makes sense for a reference terminology like SNOMED to be pushed directly to the point of care, particularly for unique environments like LMICs. I guess that is what we will learn from this experiment (but I want us to be fully transparent with lessons learned). Maps from single concepts within a reference terminology to another reference terminology (or admin terminologies like ICD-10) will always underperform conceptual mappings from pre-coordinated interface terms. I am concerned that tying users to a reference-based terminology server (rather than OCL or other server which allows for the sort of customizations which I have outlined before) will either lose clinical specificity or frustrate users.

I want to be clear that I am a strong supported of SNOMED CT and have been personally involved in getting the majority of the US using SNOMED through their EHRs. I need to be convinced that my implementation experience is wrong when it comes to my other passion… OpenMRS.

Lastly, on the CDSS front, my recent experience has been with the WHO SMART guideline efforts where there are substantial numbers of concepts that do not have SAME-AS SNOMED primitive representation (single codes).