Page History

De Coronado, Sherri    

Safran, Tracy

Kuntipuram, Kumar

 x

ASU Team (Preston Lee, Austin Michne, Mohit Mulchandani)

• Overview and Discussion

Discussion Points:

LexEVS team approached by the ASU group based on docker activity in github and meeting notes.  Preston Lee from the VA through ASU spoke on his efforts including ocal project leveraging LexEVS including a commercial application.  Resolves terminology through the UI.  Screen shots shown of commercial UI.  Uses FIHR. Need to be able to distribute this. 

Service marketplace meant to provide backend applications that could be autowired into health services.  Would like to add to this by distributing LexEVS in the same manner.  OCI known as Docker is the target package and this team is offering to help get this done.  Garrick Hammel is working on the container image. 

HSPC or health services platform consortium provides guidelines.  Need to be able to move and scale services as necessary and the policies are designed to facilitate that.  Environment variables are used to get things like database configuration at run-time.  Used by health and research organizations. 

Can't be just for VA or Cerner for instance.  Licensing is working around open source licenses.  Content loaded via script at run-time.  Can't be preload-ed due to licensing issues. 

Decision Points:  LexEVS to possibly allow a pull request for configuration.

Sprint Status

Current Sprint -  Sprint 58 (June 8, 2017 – June 21, 2017)

Future focus on value sets, unless CTRP becomes a priority.

Sprint Status

Discussion Points:

Goals of REST API from CTRP and others

• Much simpler format with just thesaurus content
  • Harmonized with the REST (JSON) output with the CTS2 service.   This will make it compatible with users of both CTS2 output (JSON) and this REST service.
  • Is there an easier REST API to put on the top of CTS2?
• There are current users of CTS2 REST service, so we need to make sure any API changes will have a similar format.
• EntityDescription vs RDF label - how do we harmonize the data.
• CTS2 is generic.  The NCI team is suggesting going to a more specific (RDF OWL) model for a thesaurus API.
  • Current SPRARQL REST calls to StarDog returns JSON (OWL2 model).

Decision Points:

• Tracy requested from the LexEVS team: mapping to/from lexgrid↔OWL.
• Kim will share with the Mayo team the output/format he has from SPRARQL REST calls to StarDog. 
• Mayo team will see if anyone in our group has triple store expertise that may be able to answer questions from NCI.
  

• Tier Deployment
  • Data deployment
• 6.5.0.1.FINAL LexEVS Admin testing

Discussion Points:

Stage server is still in progress.  6.5.0 is the what the browser is running against. 6.5.0.1.Final is what is needed for loader. 

• LexEVS Deployment Status

Decision Points:

CTRP Support

• Updates

Discussion Points: URL's are evaluated for LexEVS to owl2 semantic mapping sense

Docker - Next Steps Discussion

Discussion Points:

.

Decision Points:

Mayo willing to help with any schema, modeling tasks as needed.  Readiness is the watch word. 

Value Set Architecture

• Update

Discussion Points:

• Working on miscellaneous issues on the value set workflow.
Moving toward replacing the hierarchy implementation.We will need to understand the current hierarchy structure and how it is handled in the browser.
• • We are stepping away from the external documents and creating a fully automated approach
• • 
    

Decision Points:

LexEVS External Users

Discussion Points:  Brazilian academic user.  Not much feedback. 

Decision Points:

Mayo Team

• Cory - 6/19 - 6/23
• Scott - 7/27 - 7/28, 7/31- 8/1
• Craig -

NCI

• Tracy
• Rob June 16,19
• Kim
• Larry - 6/23 - 6/29