It’s been a while since I’ve seen it but I think Pablo Pazos has some quite good work for that topic on EHRServer, at least for subsumption [https://ppazos.github.io/cabolabs-ehrserver/ mentions “Support of SNOMED CT Expressions on openEHR queries (simplifies complex queries)”]. There is also a demonstration video on YouTube. With regards to binding to the model, though, things might be tricky.
Yes, I’ve integrated SNOMED Expressions into our path-based queries, that is basically another syntax for openEHR queries, alternative to AQL.
What I did was adding the operator in_snomed_exp associated to DV_CODED_TEXT, so you can say something like "retrieve all the compositions that contain a path to a DV_CODED_TEXT, such as the code value on that is in a expression e. This is at the syntax / query building level.
At the query evaluation level, if the evaluator finds a in_snomed_exp operator, it resolves the expression e against a SNOMED CT expression expansion service, provided by our partner VeraTech, and the expanded expression is integrated into an SQL query, generated from the path-based query evaluation. This mixed with complex conditions on other nodes, gives a lot of possibilities on what can be done with the query results. Our focus is CDS, so we mainly want those results to feed CDS rules.