Page History

...

• House keeping Items
  • Reviewed agenda and approved - unless there are changes along the way.
  • WebEx will be live all day.
  • Goal is to record key tasks and wikis
• Goal is to set context for the rest of the meetings this week and to start identifying the issues to be addressed.  
• Larry would like to start to complete the complete EVS Project Architecture (including LexEVS)
• General workflow for architecture:
  • Gather terminology content → protege and meme → loaded into LexEVS terminology service → accessed via java api, rest service api, browsers
  • Architecture now needs to include the triple store database and usage (REST API and native REST API).  This service is to support clinical trials (CTRP).  Ability to make changes into the production service was a driving factor in going to TripleStore architecture.  Loading into triplestore can be done nightly if needed.  Currently the loads have been nightly.
  • OBO is currently being looked as as a third delivery channel.  
  • Expected to have expanded use of services and downloads
    • Adverse events were the most downloads  - and then used and built in other systems (CDISC and FDA, etc).
  • Report Writer extracts value sets from LexEVS
    • Current work happening to create a SPARQL based report writer. Planned for early February.
      • This would be only on QA team.
      • External use would require a security layer (doesn't exist today)
      • Gilberto noted that report writer cannot currently take a search and return result set (with preferred names).  Noted this is "simple search" and could also be part of the term browser.
      • Existing templates should be able to be run without authentication.
  • The TripleStore still cannot provide all the terminology data needed for EVS and is stored in LexEVS. 
  • Mappings - need to determine how to capture and allow access to mappings.  The LexEVS model and triplestore model do not provide the needed flexibility today.

Decision Points:

...