Terminology Tooling Requirements

From CIMI
Revision as of 08:41, 18 December 2012 by Admin (Talk | contribs)

Jump to: navigation, search

The CIMI community has agreed to use SNOMED CT as the primary terminology in the CIMI modeling tool and to add whatever concepts are necessary within the CIMI namespace as necessary. The assignment and management of SNOMED CT concept identifiers for concepts, simple reference sets ("extensional" value sets), value set definition reference sets, etc. is a non-trivial process and will require supporting software and infrastructure. Following is a list of requirements for the supporting tools:

Requirements
Category Priority Requirement Description Notes
General 1 Global Access The CIMI Extension contents will be accessible to anyone via the internet with the appropriate credentials.
General 1 Provenance All changes will be tagged with the changing user id and change data
General 3 Change History The list CIMI originated changes for a given concept, value set, etc. should be queryable
General 2 Change Provenance A list of all changes by by a given user or all users should be queryable over a given date range
General 2 Browser UI Access The CIMI Extension contents will be accessible for query and browsing through a vanilla browser such as Firefox, Internet Explorer or Safari
Value Sets 1 Value Set Creation A CIMI author should be able create a new value set given a value set name
Value Sets 1 Value Set Modification A CIMI author should be able to add a list of concepts to a value set and/or remove one or more concepts from a value set
Value Sets 1 Value Set Query A CIMI author should be able to locate value sets by matching their description, authors or content.
Value Sets 1 Value Set Retrieval A value set should be retrievable by identifier
Concepts 1 Concept Creation A CIMI author should be able to create a new concept with a preferred name, parent concept (if known), and an optional description of its intent and purpose
Concepts 1 Concept Modification Change the preferred name, parent concept(s), and description of a concept
Concepts 1 Concept Query Retrieve concept(s) that match a text string and/or author
General 3 Spreadsheet Import Concept additions, value sets and other changes should be importable via a spreadsheet
General 2 Format Concept and Value Set Retrieval should support CTS2 Format
General 3 Format Concept and Value Set Creation and Modification should support CTS2 Format
Value Sets 2 Value Set Definition Value Sets should be constructable using a compositional grammar
General 1 Programmatic Access Tool should support a web-based API (ideally CTS2 compliant) that will allow external tooling to query and retrieve content
Import/Export 1 Import Import new releases of SNOMED CT in RF2 format
Import/Export 1 Export Export CIMI extension in RF2 format
Import/Export 3 Export Export CIMI extension in RF1 format RF2 --> RF1 conversion programs exist
Import/Export 3 Export Export extension in CTS2 format CTS2 provides ability to do spreadsheets and other formats via XSLT
Import/Export 3 Export Export extension as spreadsheet(s) Format would have to be defined
Import/Export 1 Import Ability to import CIMI spreadsheets Format will be forthcoming - close to RF2
Reasoning 1 Relationships Retrieve defining relationships for a concept
Reasoning 1 Subsumption Test subsumption between two concepts
Reasoning 1 Subsetting Test subsetting between two value sets Value set subsumption is a more difficult problem
Representation 1 Compositional Grammar Represent concept in SNOMED compositional grammar expression
Representation 2 OWL Represent concept or set of concepts in OWL
Maps 2 Simple Maps Represent simple maps between SNOMED CT and other terminology Q: "represent" or "create"?
Maps 3 Complex Maps Represent complex maps between SNOMED CT and other terminology Q: "represent" or "create"?
Reasoning 1 Classification Support classification of the ontology
Concept Model 3 Concrete Domains Support defining and non-defining concrete domains
Concept Model 3 MRCM Test the rules of the MRCM (including domain, range and cardinality)
Concept Model 3 MRCM Allow extension of MRCM to support CIMI modeling requirements
General 1 Meet acceptable performance measures

Priorities:

  • 1 Must be present
  • 2 Highly desirable
  • 3 Desirable
  • 4 Wish list / future