I’m a clinical informatician, software developer and clinician based in the UK, and although I’ve had a lot of exposure to SNOMED-CT over the years, I’ve always found the tooling for local development, exploration, and learning of SNOMED to be quite sparse. I decided to see if I could build simple SNOMED tools that use files on disk - no Java, no Docker, no REST API, just simple deterministic tooling, modern file-based formats, normal developer workflows.
this is really interesting, thank you for submitting this. I’ve not had a chance to set it up and have a play, but will definitely be doing so after our conference. It’s good to see other open source tools to make access to SNOMED CT more accessible, especially ones that take a different approach from others we have seen.
Thanks @rdavidson - at this stage it’s been as much a learning and experimentation tool for me, but I’m trying to build it to be performant and robust, such that it could be included in my other software projects to give me fast, local-first SNOMED autocomplete, searches, etc.
Please do feed back here with anything you notice such as bugs etc. And feature requests!
Does anyone here know if it would be acceptable for sct to include the IPS SNOMED-CT subset, which has been openly released under Creative Commons license?
I would like sct to have some SNOMED terms in the repo, to make it easier for new people to get started with SNOMED, without having to separately obtain a SNOMED Edition from somewhere else (eg TRUD in UK or MLDS)
Is the IPS subset actually openly published anywhere? Having to register on the SNOMED website in order to be emailed a link to download it is not actually what the technology world considers ‘open’.
