Author: Craig Stancl, Scott Bauer, Cory Endle
Email: craig.stancl2@nih.gov, scott.bauer@nih.gov, cory.endle@nih.gov
Team: LexEVS
Contract: 16X237
Client: NCI CBIIT
National Institutes of Heath
US Department of Health and Human Services
The purpose of this document is to document the 2017.12 technical face to face meeting details between the NCI and the LexEVS Team.
2017 December Face-to-Face Meeting Notes
Tuesday, December 5th, 2017
Time | Location | Topics | Participants | Resources |
---|---|---|---|---|
9:00 AM - 11:00 AM | 4-W-034 | EVS Status and Future DirectionDiscuss EVS current state, trends, and future directions
| Broad cross-EVS participation | EVS Project Architecture |
Attendees:
Jason, Scott Bauer, Larry Wright, Cory Endle, Kim Ong, Tracy Safran, Rob Wynn, Gilberto Fragoso, Margaret Haber, Kumar, Sherri De Coronado, John Campbell, Ron, Luba
Discussion Points:
- 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.
- Current work happening to create a SPARQL based report writer. Planned for early February.
- 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 triple store model do not provide the needed flexibility today.
- Synchronization of data sources and coordination of distribution of data is an open issue. Consideration is needed to provide an umbrella API (Federated) that serves both LexEVS and TripleStore content.
- Gilberto noted that CTS2 services should be revisited and he'd like to review missing functionality and complexity (noted by CTRP).
- LexEVS historically has been based on standards since the early inception of the tooling.
- As a terminology service, all the content has been loaded into Lexgrid data model.
- Focus from standards has shifted to providing usable services to end users.
- There are possibilities for enhancing the service today that still provides interoperability.
- Thesaurus based use cases should be considered when determining goals.
- CTRP usage of TripleStore was speed in loading content. LexEVS loading of transitive table is long process. Tracy noted that LexEVS could start to use TripleStore technology to remove that bottleneck when loading content.
Decision Points:
Time | Location | Topics | Participants | Resources |
---|---|---|---|---|
11:00 AM - 12:00 PM | 4-W-034 | EVS Project ArchitectureEVS Project Architecture Review and Update
| Broad cross-EVS participation | EVS Project Architecture |
Attendees:
Discussion Points:
Decision Points:
Time | Location | Topics | Participants | Resources |
---|---|---|---|---|
1:00 PM - 2:00 PM | 5-W-032 | User Group Discussion - caDSRUser Teams to share how they are using EVS and discuss requirements/priorities for the future.
| caDSR contact - Denise, Philippa, developers |
Attendees:
Discussion Points:
Decision Points:
Time | Location | Topics | Participants | Resources |
---|---|---|---|---|
2:00 PM - 3:00 PM | 5-W-032 | User Group Discussion - FDA and CDISCUser Teams to share how they are using EVS and discuss requirements/priorities for the future.
| Editors Liz, Erin, Brenda |
Attendees:
Discussion Points:
Decision Points:
Time | Location | Topics | Participants | Resources |
---|---|---|---|---|
3:00 PM - 4:00 PM | 5-W-032 | User Group Discussion - CTRP / CTS-APIUser Teams to share how they are using EVS and discuss requirements/priorities for the future.
| CTRP / CTS-API - managers, developers, Tiger team (Gisele, Samantha, David, Brian, Peter, Tracy, Jason, others) |
Attendees:
Discussion Points:
Decision Points:
Wednesday, December 6th, 2017
Time | Location | Topics | Participants |
---|---|---|---|
Attendees:
Discussion Points:
Decision Points:
Time | Location | Topics | Participants |
---|---|---|---|
Attendees:
Discussion Points:
Decision Points:
Thursday, December 7th, 2017
Time | Location | Topics | Participants |
---|---|---|---|
Attendees:
Discussion Points:
Decision Points:
Time | Location | Topics | Participants |
---|---|---|---|
Attendees:
Discussion Points:
Decision Points: