Page History

...

• EVS REST API
  • CTRP and GDC are currently using the API.
  • https://evsrestapi.nci.nih.gov/evsrestapi/swagger-ui.html#/evs-controller
  • Working with other groups for API usage.
  • CTRP in the URL identifies the data being searched.  Kim noted that in future it would be coding system and version.
  • Modeled specific for the CTRP usecases.  Data in the response may have specific CTRP.
  • Larry would perfer to have a common API that could then be customized for specific users.  
  • Suggested to perform a gap analysis to look at what caDSR current uses and what is avaible available in the EVS CTRP API.
    • Will need to get parameter instances so we can know exactly what is used. (restrict to code/properties, etc)
    • This should be reviewed by NG, Tracy, Scott, etc and the caDSR team (Natalia, Vikram, etc.)
  • Agreement to have a joint working group to help build a combined REST service to get content from both LexEVS and TripleStore environments
  • Minimal testing has been completed (10 concurrent users).
• REST Service Future Direction
  • The REST service should not have application specific content.
  • There will be a need to consider input from users -  caDSR, GDC, CDISC, CTRP 
  • Sherri suggested that it may be worthwhile to generalize the existing CTRP REST service and then get user feedback.
  • Considerations for REST services:
    • Keep the CTRP API separate and build a more common API
    • Create a common API and provide specific convience APIs on top of the common API for specific customers.
    • Fill in the gaps (to be identified) with CTS2 based REST service. Create local extensions and look at opportunities to update the specification.
  • Customer needs will come first.
• LexEVS REST (CTS2) and LexEVS Remote Service gap analysis
  
  • Service Discovery - could be created
  • Paging and Iteration - no gap
  • Entity Search - gaps in search type (LexEVS 6.4 Search Algorithm Implementation Details)
  • Result Sorting - gaps exist
  • Custom Result Filtering - gap exists
  • CTS2 URI Read of Entiy - could be created
  • Code System Operations - gap exists
  • Entity Count - gap exists
  • Relational Operations - gap exists
  • Query Parameters - gap exists
  • Result Parameters - gap exists
  • Operation Functions - gap exists
  • Value Set Operations - gap exists
  • Value Set Search - gap exists

...

• Action Items:
  • Perform a gap analysis to look at what caDSR current uses and what is avaible available in the EVS CTRP API.
  • Assemble a joint working group to investigate a combined/coordinated REST service to get content from both LexEVS and TripleStore environments.
  • Identify additions to the existing EVS API to make it more useful to users.

...