...
Ideally there'd be a place where all known extensions of SNOMED CT can be pulled together, a "Universal Edition" of SNOMED CT. Additionally it would be very useful for this content to be loaded into a terminology server with a standard, rich API (for example a fairly complete FHIR terminology service implementation) and a browser which allows anyone to find out about a SNOMED CT identifier from anywhere in the SNOMED CT universe.
Use Case
Dealing with content spread across a range of editions.
Priority : Highly desirable. ML "Universal content is highly desirable and cheap. A universal 'Edition' would be much more expensive." Notes that will be taken forward anyway with the work done by Rory's evolution working group.
Issues
- Merge conflicts.
- Quality issues in editions eg module dependency problems, rows failing to adhere to RF2 specification.
Suggested actions
- make SNOMED CT URIs more useful by making them resolvable in collaboration with the extension owners
- create a SNOMED CT "Universal Edition" by collecting the known extensions and making that available as a complete unit. By providing a standard technical mechanism to push extension releases to, extension builders could facilitate this universal edition by pushing their releases rather than a central effort to continuous pull/collect releases
- make the Universal Edition available as an RF2 package for download
- load the Universal Edition regularly into a suitable terminology server and make that available, ideally publicallypublicly
- load the Universal Edition regularly into a terminology browser available, ideally publicallypublicly
Thoughts, comments, suggestions, objections?
Discussion
ML Suggested first step of creating a union of all concepts that have ever been defined.