Page History

Versions Compared

Old Version 51

changes.mady.by.user Unknown User (endlecm)

Saved on Dec 07, 2017

compared with

New Version 52

changes.mady.by.user Unknown User (stanclcr2)

Saved on Dec 07, 2017

Key

This line was added.
This line was removed.
Formatting was changed.

...

Time	Location	Topics	Participants	Resources
9:00 AM - 12:00 PM	1-E-030 (9:00-1112:00)(gap 11-12)	API Services Proposed topics for discussion: Overview of EVS REST API and future direction Discuss what exists today. Discuss future plans. Overview of LexEVS provided API services and future direction LexEVS API LexEVS Remote API LexEVS REST API (CTS2-based) Discuss a new REST service Discuss user requirements for a new REST API Document the gaps from CTS2 REST API and user requirements. Explore how simple searches and searches with an identifier and how this could replace most of the remote API. Consider a new REST API to supplement CTS2 REST Services Propose examination of current CTS2 REST API Capture what doesn't work for the end users. Review gap between Remote API and REST services. Discuss surfacing terminology history in a REST service (NCIt and ULMS) Determine what history information is required by the user to be returned. Discuss surfacing history of value sets in a REST service Discuss if this fits into LexEVS or is part of a new REST API	Kim Ong Tracy Safran Rob Wynne End users such as CTRP, others Larry Wright Margaret Haber Sherri De Coronado Gilberto Fragoso	DiffCTS2_LexEVS.pptx

Time

Location

Topics

Participants

Resources

9:00 AM - 12:00 PM

1-E-030

(9:00-1112:00)(gap 11-12)

API Services

Proposed topics for discussion:

Overview of EVS REST API and future direction
- Discuss what exists today.
- Discuss future plans.

Overview of LexEVS provided API services and future direction
- LexEVS API
- LexEVS Remote API
- LexEVS REST API (CTS2-based)

Discuss a new REST service
- Discuss user requirements for a new REST API
  - Document the gaps from CTS2 REST API and user requirements.
  - Explore how simple searches and searches with an identifier and how this could replace most of the remote API.
- Consider a new REST API to supplement CTS2 REST Services
  - Propose examination of current CTS2 REST API
  - Capture what doesn't work for the end users.
  - Review gap between Remote API and REST services.
- Discuss surfacing terminology history in a REST service (NCIt and ULMS)
  - Determine what history information is required by the user to be returned.
    - Discuss surfacing history of value sets in a REST service
  - Discuss if this fits into LexEVS or is part of a new REST API

Kim Ong

Tracy Safran

Rob Wynne

End users such as CTRP, others

Larry Wright

Margaret Haber

Sherri De Coronado

Gilberto Fragoso

DiffCTS2_LexEVS.pptx

Attendees:

Scott Bauer, Craig Stancl, Cory Endle, Gilberto Fragoso, Larry Wright, Lyubov, Tracy Safran, Rob Wynne, Kim Ong, Jason Lucas, Liz, Margaret

Discussion Points:Decision Points

EVE REST API
- CTRP and GDC are currently using.
- 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 like to have a common API that could then be customized for specific users.

Decision Points:

Action Items:

Time	Location	Topics	Participants	Resources
1:00 PM - 3:00 PM	5-E-030	Prioritization and debrief Determine strategic direction and priorities	Kim Ong Tracy Safran Rob Wynne Larry Wright Margaret Haber Sherri De Coronado Gilberto Fragoso