Page History
...
The purpose of this document is to capture proposed agenda topics for the 2017 technical face to face meeting between NCI and Mayo.
Agenda Item | Purpose/Goals | Proposed Duration | Participants | Time/Date Restrictions |
---|
Technical Discussion/ |
---|
Presentation | Added to Schedule |
---|
Tuesday, December 5 9:00-11:00 EVS Status and Future Direction |
|
Larry Wright
Margaret Haber
Sherri De Coronado
| 2 hours | Broad cross-EVS participation | Tuesday 9:00 AM | Slide of technical components Full EVS view of all the technical components. | ||
11:00-12:00 EVS Project Architecture | Proposed topics for discussion:
| 1 hour | Broad cross-EVS participation
| Tuesday 11:00 AM | EVS Project Architecture | |
1:00-2:00 |
User Group Discussion |
- CTRP
- caDSR
| Proposed topics for discussion:
|
| 1 hour | caDSR contact - Denise, Philippa, developers | Tuesday 1:00 PM |
Discuss a new REST API to supplement CTS2 REST Services
- Examine current CTS2 REST API
- Discuss what doesn't work for the end users.
- Discuss user requirements for a new REST API
- Document the gaps from CTS2 REST API and user requirements.
Discuss surfacing terminology history in a REST service (NCIt and ULMS)
- Determine what history information is required by the user to be returned.
- Discuss if this fits in to LexEVS or is part of a new REST API
Discuss surfacing history of value sets in a REST service
Kim Ong
Tracy Safran
Rob Wynne
End users such as CTRP, others
Larry Wright
Margaret Haber
Sherri De Coronado
2:00-3:00 User Group Discussion
| Proposed topics for discussion:
| 1 hour | Editors Liz, Erin, Brenda | Tuesday 2:00 PM | ||
3:00-4:00 ? User Group Discussion
Reschedule - conflicts with Tiger Team (was at 11-12) | Proposed topics for discussion:
| 1 hour | CTRP / CTS-API - developers, managers, Tiger team (Brian, Peter, Tracy, Jason, others)
| Tuesday 3:00 PM | ||
Wednesday, December 6 9:00-10:00 EVS Architecture | Discuss Potential of using a variety of architectures Proposed topics for discussion:
|
|
|
|
|
|
| 1 hour | Gilberto Fragoso Kim Ong Tracy Safran Rob Wynne Larry Wright Margaret Haber Sherri De Coronado |
Tracy Safran
Bron Kisler Systems team John Cambell /Ruth Monterio users of the SQARL |
|
Wednesday 9:00 AM | Micro service proposals LexEVS and Triple Store - Would be useful to have slides for suggested integration
| |||||
10:00-12:00 EVS Architecture - Technical Discussion with Systems team | Discuss technical aspects of potentially using a variety of architectures Proposed topics for discussion:
| 2 hours | Systems team
| Wednesday 10:00 AM | ||
1:00-2:00 EVS Project Group Discussion (During regular call-in time) | Proposed topics for discussion:
|
Gilberto Fragoso
Systems Team
Tracy Safran
Kim Ong
Tracy Safran
Rob Wynne
Editor's Representative/Margaret Haber
MedRT: Medication Reference Terminology
|
| 1 hour | Kim Ong Tracy Safran Rob Wynne |
Editor's Representative/Margaret Haber Larry Wright Sherri De Coronado |
Wednesday 1:00 PM |
2:00-3:00 NCI Systems Discussions
| Proposed topics for discussion:
|
Discuss systems deployment issues to Stage/Prod.
Issues migrating from 6.4 to 6.5 database.
|
1 hour | Jacob and Systems team Gilberto Fragoso Rob Wynne Tracy Safran Kim Ong Larry Wright Margaret Haber Sherri De Coronado |
Q/A (Sana) | Wednesday 2:00 PM | ||
Thursday, December 7 9:00-12:00 API Services (10-12 Conflicts: Data Commons & GDC meetings) | Proposed topics for discussion:
| 3 hours |
Discuss Potential of using Micro Services
- Need to determine how to synchronize data on the back-end
- LexEVS DB and Triple Store need to be in sync when NCIt information (such as value sets) changes.
- Discuss the potential of a loader that relies on SPARQL queries
- After SPARQL query load, kick off LexEVS loader
Kim Ong Tracy Safran Rob Wynne End users such as CTRP, others Larry Wright Margaret Haber Sherri De Coronado |
Thursday 9:00 AM |
1:00-3:00 Prioritization and debrief | Determine strategic direction and priorities | 1-2 hours | Thursday 1:00 PM |
Discuss how to update LexEVS customers with jar files when updating LexEVS versions
- Releases need to be backwards compatible
Discuss evolving to all REST services and possibility of retiring the Java API
- What needs to be enhanced in the REST API need to support our Java API customers.
Larry Wright
Margaret Haber
Sherri De Coronado
Kim Ong
Tracy Safran
Rob Wynne
Gilberto Fragoso