Page History

• Tracy has not yet had an opportunity to run the latest test.
• Based on Scott's testing, it appears that this will improve performance.

Decision Points:

Decision Points:

• Jason - Not sure who's responsibility it is to QA/test the value sets after they are created.
• The Dev team suggested there be an automated test for value sets after the load is completed using Java.
• We could automate, via a shell script, to validate all value sets have been loaded and have data in them.
  • Definitions and Resolved value sets: 1:1 comparison that all are in the DB.
  • Test if a definition was loaded: Check a directory that contains all definitions that should be loaded and verify that it was added to LexEVS DB.
  • Test case we need to capture: The resolved value set only has one value - the head (top node) of the value set. (This is not a valid value set)
• Tracy/Rob will talk to the definition authors and understand what the best way to validate the definitions may be.

Decision Points:

• Dev team to create a JIRA item to create a value set validation tool as mentioned above.
• Jason will request that  this conversation be added to the Wednesday 1:00 meeting.