LexEVS Meeting Minutes - 02 July 2014

Attendees

#	Assigned	Description	Date Identified	Status
64	Scott	To follow up on URI's on OWL2 with Harold.		on hold
154	Larry	Provide an email update to NCBO, NLM, and Mayo with current activities and what has been built.		done
156	Scott	Scott to work with Gilberto to determine what is needed for OWL 2 requirements	2014.04.30	on hold
164	Cory	Cory to add implementation to CTS2 implementations page.	2014.04.30	on hold
170	Scott	Update the ARC dates to include range of dates for each tier.	2014.05.14	on hold
185	Gilberto	Create Jira for OWL 2 Annotation issue in the API.	2014.05.28	open
197	Scott	Do a gap analysis on what the URI_Resolver logs and what NCI would like to know from these logs	2014.6.18	on hold
199	Scott	Ask Ann Wiley to create a sticky for the VKC forum directing users to post to appropriate gitHub	2014.6.18	done
200	Larry/Sherry	Query current LexEVS users about use of SOAP, REST or QBE services in the legacy caCORE api's	2014.6.18	open
201	Scott	caCORE Inquiry - Outline the services that exist and what is proposed to be dropped.	2014.06.25	open

Immediate Priorities and Problems (Mayo Team)	Scott: Loader testing against 5.5, Lucene Review. Loader Testing on Mayo system. System drive failure on our system. Currently working to get that resolved. UMLS Load on ICD-10 CM issues. Lucene review - preparing LOE for implementation. Cory: Start JIRA Items, review NLM Services Started on JIRA 590 VS Client - Craig: Project Plan Updates
Agile adoption Schedule	July 16 same time as our weekly meeting. 1-2PM EDT
caDSR and Value Set and other URIs (Weekly Status)	URI Resolver logging prioritization
Dev DRT request
GitHub, build workflow	http://stackoverflow.com/questions/6675994/is-it-possible-to-fork-a-fork-in-github
Forum Links on GitHub (Scott)
Plans for the future of caCORE webservices.
Update on Value Set Client services (Corg)
UMLS Load of ICD10 issue

Description
LEXEVS-570 - Getting issue details... STATUS
LEXEVS-573 - Getting issue details... STATUS
LEXEVS-579 - Getting issue details... STATUS
LEXEVS-586 - Getting issue details... STATUS
LEXEVS-594 - Getting issue details... STATUS
LEXEVS-597 - Getting issue details... STATUS
LEXEVS-598 - Getting issue details... STATUS
LEXEVS-599 - Getting issue details... STATUS
LEXEVS-605 - Getting issue details... STATUS
LEXEVS-606 - Getting issue details... STATUS
LEXEVS-607 - Getting issue details... STATUS
LEXEVS-608 - Getting issue details... STATUS
LEXEVS-609 - Getting issue details... STATUS
LEXEVS-612 - Getting issue details... STATUS
LEXEVS-613 - Getting issue details... STATUS
LEXEVS-615 - Getting issue details... STATUS
LEXEVS-616 - Getting issue details... STATUS
LEXEVS-617 - Getting issue details... STATUS
LEXEVS-618 - Getting issue details... STATUS
LEXEVS-619 - Getting issue details... STATUS
LEXEVS-620 - Getting issue details... STATUS
LEXEVS-621 - Getting issue details... STATUS
LEXEVS-622 - Getting issue details... STATUS
LEXEVS-623 - Getting issue details... STATUS
LEXEVSCTS2-2 - Getting issue details... STATUS
LEXEVSCTS2-3 - Getting issue details... STATUS

#	Opened Date	Due Date	Description	Likelihood (H, M, L)	Impact	Assigned	Status	Mitigation Strategy

Opened Date	Description	Assigned