Hey @grace, we actually have already started to do some exploration and testing with SNOMED-CT in OCL. We have the ability to load that content into OCL, but because of the risk that may come with licensing restrictions, we ended up loading SNOMED-GPS into OCL instead. This seemed like a safe compromise until we could work more closely with SNOMED International to get their blessing, so to speak, for SNOMED-CT. In the future, I could see OCL doing something similar to what OHDSI does where we could display a disclaimer about licensing.
Given Ian’s input about whether OpenMRS can actually intake SNOMED-CT codes, it sounds like there may be other complications to work through too, but if the need is there to get SNOMED-CT into OCL, then we might want to discuss either pushing forward the SNOMED/OCL licensing talk OR talk about alternative options.
Also, though I am not entirely tuned in to this project and use case, I just wanted to note that mapping to SNOMED-CT can still occur, even if we don’t have the concepts in OCL. Even if the current state of OCL, you theoretically could create local concepts that could then be mapped to SNOMED-CT concepts.