Page History

...

Attendees:  Jason, Gilberto, Rob, Tracy, Scott, Cory, Craig, Tin, Larry, Kim, Sana, Liz

...

• Properties in Thesaurus that support the browsers
  • Subsets in Thesaurus (Protege)
    • Publish_Value_Set
    • Term_Browser_Value_Set_Description
    • Value_Set_Location - where browser fetches the report from (ftp location and path within evs, and filename, BNF)
    • TVS_Location - Terminology Value Set OWL file - hierarchy and components
  • Properties are scrubbed before loading into LexEVS - these are private/internal properties.
• Baseline - A diff is done on the value sets from month to month.  Triggers update load procedures monthly.  
  • Load, Remove and Resolve scripts are generated for changes
• OWL file provides information about where the value set lives in the hierarchy.
• NCI Thesaurus and TVS  (provides structure to value sets)  - used by the browser
• Process was created to provide structure/hierarchy to value sets
• Value Set loads - 700 coding schemes - loaded in 24 hours
• If value set resolution is performed against a new version of the code system, does LexEVS handle the versions?
• Process currently isn't limited to NCIT.
• Script created to create a txt file that views hierarchy of concepts on value set.
• value set downloads are ~10k a month and used across agencies by diverse set of consumers.
• curation and delivery processes are driven by the users and consumers.
• EVS authors editors work directly with CDISC and other groups.
• CDISC and FDA have different formats and standards 
• Resolved value sets as coding schemes - done that way for performance.
• Process can be error prone for the EVS Editors.  The editors need to do specific things to drive Browser.

Decision Points:

...