Hospitals in the Netherlands hold extensive SNOMED-coded data for diagnoses, problems, and procedures, yet this resource is often underutilised. While Clinical BI experts are familiar with ICD-10 due to clinician demand, SNOMED remains largely unexplored. Despite SNOMED codes being accessible in Epic data platforms, a lack of suitable tools limits their use.
How can BI teams leverage the SNOMED ontology (ECL) within Epic, and who has experience doing so?
HELP: has no one knowledge of actual use of SNOMED data in Epic BI solutions?
@PimVolkert thank you for raising this, itâs a very interesting topic. The Implementation Support Team have not learnt anything about this from Members, we are very keen to hear more.
There is a mention of this capability in the SNOMED Data Analytics Guide as a Vendor Study, but it doesnât say how.
Reporting
Within Epicâs integrated analytics and reporting suite (i.e. Cogito) customers have achieved benefits by using SNOMED CTâs clinical finding hierarchy to aggregate local diagnosis concepts.The capability has for example been used by oncologists working with cancer-related ICD codes which are unsuited to grouping diagnoses by stage. Using the mapped SNOMED CT codes they are able to facilitate the reporting of staging data by utilizing the SNOMED CT hierarchy.
Thank you for your reply Kai,
It would be nice to have someone explain how to make use of SNOMED in Epic and add that content to the âPractical Guidesâ and Epic user Groups.
@PimVolkert
I havenât explored Epic data, but definitely, if there is Diagnosis, Problems and procedure data, irrespective of a vendor, this data can be aggregated to parent hierarchies within SNOMED CT ontology model using ECL.
I would be happy to help, should you have requirement.
I can be reached at âdrsudha9@gmail.comâ. Thanks