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 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:
- 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.
Decision Points:
- Action Items:
- Perform a gap analysis to look at what caDSR current uses and what is avaible in the EVS CTRP API.
- Assemble a joint working group to help build a combined REST service to get content from both LexEVS and TripleStore environments
...