| Feature | Compliance | Notes |
|---|---|---|
The creation and maintenance of both extensional and intensional reference sets including version management of these reference sets | Meets | Initial extensional refsets can be loaded and then members added/removed. Intensional refset definitions based on expression constraint grammar supported by the terminology server (with explicit code “include” and “exclude” features). |
Version management of reference sets including draft and published reference sets | Meets | Handled through reference sets version and workflow status metadata. |
Import of existing reference sets as content | Meets | Import from RF2 (Simple pattern) |
Distribution of any reference set products (including documentation, rf2 and human-readable versions) | Meets | Attachments can be associated with a published reference set. The “human readable” form of the refset will be a link into the tool itself. |
Role based access control to the maintenance of reference sets (Admin / Author / Reviewer / Public) | Meets | Role based access (VIEWER, AUTHOR, REVIEWER, ADMIN). API calls and application access is validated by role. |
The computation of the effect of a related SNOMED CT version on a reference set | Meets | Tool will use the terminology server to obtain identifier lists from adjacent versions and compute changes in active concepts and enable author to visualize the changes (additions, deletions) and accept/reject them is supported. |
Workflow for approval before publishing but also to provide a facility for external feedback | Meets | Simple workflow for authoring then handing off to a reviewer, then declaring a preview version, and then formal versioning and publishing. During preview phase, broader (or even public) feedback can be solicited. |
A searchable, and publicly available, directory containing existing reference sets, as well as entries about reference sets that may be available elsewhere | Meets | VIEWER based access to available reference sets (including all prior versions). Features for discovery, searching, etc. |
The ability to host SNOMED CT extensions in the same instance as International editions | Meets | Hosting of terminology is done via terminology server not directly by this tool. Whatever terminologies hosted by that server are available for use. Reference sets within the system can reference any edition of SNOMED CT available to the underlying terminology server. |
Separation between a tool for ‘sub-setting’ SNOMED CT components and a tool for managing releasable SNOMED CT reference sets | Meets | The tool supports refset development processes in which subsetting and analyzing changes in what would be the computed refset are supported. It also supports a publication process for releasing a refset (and its membership) at a particular point in time. Features for search and discover among published refsets will be available. |