Inventory of existing services
- Complete spreadsheet to include all services in EVS REST API and LexEVS (EVS Services Inventory)
Inventory of customers
- Capture API usage by caDSR
- Capture API usage by Browser (new)
- Capture API usage by Browser (current)
- Future customers (Cancer Data Aggregator and other TBD projects) will create multiple requests for terminology information for NCIt, Meta as well as others.
Inventory of requirements
- Continued availability of Metathesaurus
- Continued availability of Single Source Ontologies
- Continued availability of Value Sets
- Ability to capture usage statistics
- Mapping (Auto) in support of Cancer Data Aggregator
- Browser (new) support
Inventory of use cases
- SEER: Map to RxNorm
- CTRP use cases
- API use cases
- example: Given a SNOMED concept code - find the ICD10 concept code
Evaluation of services/data
- Evaluate and identify the high-usage APIs
- Evaluate Triple Store support for existing Metathesaurus
- Metathesaurus to OWL
- Metadata OWL
- Evaluate Triple Store support for existing Value Sets
- Evaluate Triple Store support for existing Maps
- Evaluate expanding Mapping support in LexEVS and Triple Store
- Evaluate Stand Alone maps in LexEVS and Triple Store
- Evaluate a consolidation of combined lucene-based search engines
- Performance of Triple Store and LexEVS
- Inventory of Triple Store strengths
- Inventory of LexEVS strengths
- List of services that could be enhanced or created
- Explain how these strengths will be utilized
- Evaluate maintenance of Triple Store and LexEVS
- Evaluate and document architecture (EVS Architecture)
Prepare proposal
- Document best case solutions
- Architecture
- EVS REST API
- LexEVS REST API
- produce a roadmap for each
Present proposal(s)
Prototype/Implement
