NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

Versions Compared

Old Version 2

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

Saved on

compared with

New Version 3

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

Saved on

Key

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

...

NameRolePresent
Wright, Larry NIH/NCI  x
Fragoso, Gilberto NIH/NCI    x

De Coronado, Sherri    

NIH/NCI   x

Safran, Tracy

NIH/NCI [C]x
Ong, Kim L
ISx
Lucas, Jason R
ISx
Bauer, Scott  Mayox
Stancl, Craig
Mayox
Endle,  CoryMayox
Solbrig, HaroldMayox
Jiang, GuoqianMayox
Wynne, Robert    NIH/NCI [C] 
Tran, Tin    NIH/NCI [C]  
Carlsen, Brian NIH/NCI [C] 
Wong, Joanne NIH/NCI [C] 

Kuntipuram, Kumar

NIH/NCI [C]

 

Haber, MargaretNIH/NCI  x
Campbell, JohnNIH/NCI  x


Goals

 

  1. LexEVS and CTS2 are planned to continue as key components of NCI terminology services, but NCI also plans to extend beyond them, notably with RDF triple store SPARQL and REST components.  This raises important design and coordination issues.
  2. REST services need substantial extensions, within and beyond CTS2.  NCI plans to offer REST APIs that can support the requirements of its own and others’ applications, and expects a significant component to be REST services from the RDF triple store.  An obvious test case is ability to support EVS browser functionality (even while these browsers will likely use the Java API for some time to come).
  3. We face some immediate needs from other users, notably CTRP and GDC, so need to clarify design approaches and produce new services based on them in the relatively near term.


Agenda

 

Review and discuss (Kim's/Jason's) concerns

  • Each of these are to support the browser (via java API)
  1. Handling of metadata
    1. Metadata to be stored as RDF
  2. Supported search algorithms (currently, only exactMatch, startsWith, and contains are available)

    1. CTS2 service - would like to have CTS2 support the full LexEVS Search Extension

    2. Need to confirm that the Lucene algorithm is available.

  3. CTS2 Handling of namespace in read service. Could namespace be included as a parameter in a REST call?

    1. entity read service is able to include namespace.

    2. Need to confirm the responses to determine both namespaces are supported for single concept code
    3. Need to provide ability to return concept with different namespaces.

Review and discuss (Kim's/Jason's) concerns

  • Each of these are to support the browser (via java API)
 
Next Steps

  • Review notes from previous F2F.
  • Determine priority for browser support
  • determine requirements that fit into CTS2
  • Determine an architecture to support requirements that do not fit into CTS2
  • Determine integration of LexEVS, CTS2, Triple Store
    • separate rest services? 
    • discussion necessary

Continue discussion around what is missing from current REST CTS2 service. (All)

 

  • OWL2 considerations
    • Statement 
    • BNode (not supported purely in CTS2)
    • No canonical RDF Spec for CTS2
  • Modeling considerations (for example Neoplasm)
    • Flattening of content necessary to represent in LexEVS
    • There are things that were not able to be represented in LexEVS nor CTS2.
      • Issues
        • Restrictions bundled together in role groups
        • Ability to represent conjunctions and disjunctions.
        • within a given cancer, there are multiple prognosis - but will be flattened and nonsensical.
  • Relationship between LexEVS and graph or RDF/SPARQL
    • Support for partonomy
  • GDC groups
  • Value Set complexity
  • Mapping considerations
    • current LexEVS CTS2 support - search and complex construction
  • Available CTS2 services
    • LexEVS widely known service today.
    • Research is looking for a mature standard.  However there are gaps in functionality currently implemented.
    • Suggested that someone represent LexEVS at the FHIR table at HL7.

 

Next Steps
  • Schedule our next meeting to prioritize the above list
    • Schedule focused discussions on each topic (follow on meetings).