Overview

Sprint to extend some of the "read only" APIs, to finalize unit/integration testing for existing functionality, to extend the interface, to develop additional loaders, and to begin developing editing capabilities.

Priority things

• Model: GCI
• User Interface
  • Enable glass pane while switching tabs - need to say increment in tab controller and decrement at the end of the controller.
• Integration Tests - Jpa/REST - get them tested again
• Add "createdb" and "reindex" features to loaders
  • support a "mode" parameter that if set to "create" recreates the schema and reindexes before performing the load
  • RRF loader, Claml loader, RF2-snapshot loader, (DONE) RF2 full loader
• Improve search
  • for short strings containing special characters, consider doing a literal search (e.g. "!" or "+" or "Ca+")
    • alternative is to save untokenized forms of all strings for exact searching
  • Acronym expansion (based on a configured list)
    • config/src/main/resources/data/acronym.txt
  • Spelling correction (based on a dictionary)
    • config/src/main/resources/data/acronym.txt
    • Use Lucene SpellChecker class for this.
  • Search algorithm
    • First search on exact string (e.g. "literal" search)
    • Then search on matches
    • if no results, Then do acronym expansion and spelling correction and search again
    • if no results, then try putting * after each term and search again
  • should autocomplete algorithm include acronym expansion?

Marketing/SEO

• Create a video demo of the site (camtasia) and post as a link on the header (video glyphicon if there is one)
• Promote "ICD10" browser on various lists
• Ensure all entry pages for applications contain SEO text for browsers and are indexed by google
• Verify all entry pages for applications are officially mobile friendly
• Consider advertising SNOMED/UMLS/ICD browsers on google adwords.
• FB?

User Interface Enhancements

• Add features for "deep" relationships when browsing UMLS.    
  
  • Need a generalized way to know when to use this
  • it is definitely only for "concept"
  • It may be that if any "atoms" of the concept don't match the terminology, then we show it.
• Reimplement the component report as a directive (with service callbacks for  history and other features)
• Implement routing for terminologyId/terminology/version/type so we can preserve URLs.  can even include ?query=... for the query
• Support opening a concept in a new window (e.g. there's a pointing off arrow icon that opens a new window with a routing URL that  shows exactly that concept - then drag/drop between windows can be editing mechanism).
• DONE: Websocket (for a WebsocketWorkflowListener)
  • What to do with it??
• Expression-based searching?
• Consider adding "LABELFOR" all subsets and making the star pop up a picklist of the things to highlight (ordered by type with extensions first, subsets later)
• RECURRING: Mobile-friendly and other style issues

Additional/Enhanced  Loaders ****PRIORITY

• RF2 delta/full loaders
  • Implement mojo testing too
• Owl loader (e.g. for NCIt) - will require use of "DL" features
  • Step 1: create the infrastrucure (mojo, rest call, client, algorithm, get parameters right).
  • Step 2: get OwlAPI into the project,
    • http://owlapi.sourceforge.net/owled2011_tutorial.pdf
    • http://owlapi.sourceforge.net/
    • http://www.w3.org/TR/owl2-profiles/#OWL_2_EL
    • http://protege.stanford.edu/ontologies/pizza/pizza.owl
    • Handle "Class" and "class"
  • Step 3: add complexity
  • May need a "SNOMED" style and a general style to capture "distribution normal form" for SNOMED (e.g. rel groups, etc)
  • Also have a corresponding Owl export feature (e.g. "release")
  • Implement mojo testing too

Services

• Action Service
  • Implement classification.
  • Need to go to/from Owl so do Owl loader FIRST.

Testing 

• Mojo integration tests
  • RRF-umls load/unlolad
  • RRF-single load/unload
  • RF2-Snapshot load/unload
  • Claml load/unload
  • RF2-full load/unload
• Implement additional unit tests for model objects (PrecedenceListJpa, LabelSet, etc)
• RRF loader -> create label set for SNOMED (both "single" and "umls")
• Handler002Test for normal use
• Implement Handler003/008Test - for ID assignment algorithms.  Borrow code from other project (though there may be differences).  The uuidHash algorithm is implemented properly for UMLS and may be different than for SNOMED.
  
  

Editing Features

• Basic metathesaurus editing
• Project
  • Figure out how to capture "project scope" for SNOMED and for UMLS in a generalized way.  Update project objects to be able to properly capture (and compute) project scope.  NOTE: the scope definition may involve concepts/terminologies/semantic types.  IN that event, the scope computer gets a little bit more complicated.
• Test loading a DB with envers auditing disabled and then making changes in a DB while it is enabled. Does it properly create audit entries?
  • for the old edition of the component?
  • for the new edition?
• Metathesaurus editing actions
  • MetathesaurusContentEditingRest
    • methods for each "edit action"
    • Create a RestImpl
    • Create a client
    • Create integration tests to run against a "stock" dev  database
  • Add a semantic type component, Remove a semantic type component
    • Have a pencil icon by  the STYs section
    • clicking gives you a list of available STYs assigned, in tree order with a filter box for typing characters of the STY you want.
      • See the metadata "semantic type" option
    • User may want to choose multiple ones (so have a "finished" button)
    • Dont allow user to choose STYs already assigned to the concept.
    • Final action is to call "contentService.addSemanticTypeComponent"
    • Consider what happens to workflow status
    • Consider how to show "NEEDS_REVIEW" content in the browser
    • Consider how to support "Undo". - perhaps an action log (atomic/molecular) is a good idea still for that
  • Implement this completely including testing before moving on to other actions (each which requires a UI enhancement)
    • Approve a concept (e.g. set workflow status values).
    • Add an atom (e.g. MTH/PN - that needs to be generalized somehow)
    • Merge two concepts (consider the "workflow status "when this happens).
    • Move an atom (or atoms) from one concept to another
    • Split an atom (or atoms) out of a concept and specify a relationship type between the two concept
• Terminology Editing (first use case)
  • Add a concept (as a child of an existing concept) with one or more atoms and a PAR/CHD relationship.
  • Run the classifier
  • Show classifier results (e.g. new inferred relationships, etc)
  • NOTE: this only works with a description logic based source that tracks inferred relationships.
  • PREREQ: SNOMEDCT RF2 loader.

Admin Tools

• Test QA queries and flesh them out for 100% coverage.

Optimizations

• TBD

Future Stuff

• Test conditional envers auditing: http://stackoverflow.com/questions/14250612/conditional-envers-auditing
• escg (expression grammar - research)
• Use Lucene SynonymFilter with synonym table
• Component-Component relationships (between any two components).
• Value set definitions (and marking of subset.isValueSet()) and linking to definition? via attribute?
• Owl loader, Owl export of DL terminologies (e.g. RF2-loaded SNOMED)

  • http://owlapi.sourceforge.net/owled2011_tutorial.pdf

• Rdf export (flat)
• Classifier (owl interface)
• Expression language (based on SNOMED expression constraint grammar)
• Sub-branching
  • branchResolutionHandler - figures out how to copy and mark branched objects  and update indexes  - for different branching strategies.
• Handle mappings - may be not worth it
• Implement an RF2 loader (use DL features)
• Implement a ClaML loader
• Support semantic network (e.g. sty rels, etc).  - probably want to wait for a real ontology - and maybe even load it as such.