 |
Page History
Attendees
| Name | Role | Present |
|---|---|---|
| Wright, Larry | NIH/NCI | |
| Fragoso, Gilberto | NIH/NCI | x |
De Coronado, Sherri | NIH/NCI | x |
Safran, Tracy | NIH/NCI | x |
| Ong, Kim L | IS | x |
| Lucas, Jason R | IS | x |
| Bauer, Scott | Mayo | x |
| Stancl, Craig | Mayo | x |
| Endle, Cory | Mayo | x |
| Wynne, Robert | NIH/NCI | x |
| Pan, JJ | NIH/NCI [E] | x |
| Tran, Tin | NIH/NCI [C] | x |
| Ahmed, Shamim | NIH/NC [C] | |
| Haber, Margaret | (NIH/NCI) | |
| Roth, Laura | (NIH/NLM) | |
| Ramani, Vivek | (NIH/NCI) [C] | |
| Carlsen, Brian | (NIH/NCI) [C] | |
| Wong, Joanne | ||
Kuntipuram, Kumar | x |
Action Items
| # | Assigned | Description | Date Identified | Due Date | Date Completed | 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 | done | |||||||||||
| 202 | Craig | Confirm Agile meeting on July 16 from 1-2 EDT | 2014.07.02 | open | ||||||||||||||||
| 203 | Craig | Discuss and include URI Resolver Logging into the current plan - to be included in this release. | 2014.07.02 | opendone | ||||||||||||||||
| 204Gilberto | Gilberto to contact Larry Brem to set up a meeting to discuss next week. | 2014.07.02 | open | 205 | Scott | Plan for August NLM Demo/Meeting.Scott to follow up with Helpdesk about ability to create a sticky post | 2014.07.0209 | done | 206 | Cory | Send lessons learned and limitations to current prototype. | 2014.07.02 | open |
Progress
| Immediate Priorities and Problems (Mayo Team) | Scott: Loader testing against 5.5, Lucene Review., Working on JIRA #598
Cory: Start JIRA Items, review NLM Services
Working JIRA #'s 590, 605. 531, 371
Craig: Project Plan Updates - set out plan for review.Lucene planning
| Agile adoption ScheduleJuly 16 same time as our weekly meeting. 1-2PM EDT Mayo to confirm on calendars.
| |||
| caDSR and Value Set and other URIs (Weekly Status) | URI Resolver estimation and included in project plan. caDSR code (provided by Kim) successfully worked for Tracy. URI Resolver logging prioritization. This will need to be included in this current release. Tech team to identify when to work on this in the current plan. | ||||
| Dev DRT request | Jacob still waiting on Linux team. Possibly this week - will try to get an update. Once Dev is available, Scott will deploy on NCI dev and will look at performance. Dev blade server and DB server are expected to be up next week. This includes the tech stack updates. DB server will need additional configuration (Tracy to create loader folder and LB Runtime). Scott may be able to do some of our load testing on this server. | ||||
| GitHub, build workflow http://stackoverflow.com/questions/6675994/is-it-possible-to-fork-a-fork-in-github | |||||
| Forum Links on GitHub (Scott) | No response form the helpdesk Scott was able to get access to update the wiki with a sticky post . Scott to contacting the helpdesk again. on the forum (with help of Sarah). This does not exist on the NCIP channel, but on the LexEVS Channel. | ||||
| Plans for the future of caCORE webservices. | caCORE REST service may still be used by caDSR. Sherri sent note to Denise to confirm. Still waiting on additional feedback. It was agreed to send to the change control board. | ||||
| NLM Service Discussion (Craig) | Issue identified in the prototype where "latest" was no longer used to identify the current version of the value sets. The prototype was updated | Update on Value Set Client services (Cory) | NLM server is no longer supplying a current "latest" version of a value set. Code changes made to point to a specific version "MU2 EP Update 2014-05-30". This will not sustainable as new versions will be created. Cory Confirmed the NLM fix and the VS Client works correctly. Craig email the NLM team and is awaiting to hear back from them. . We asked NLM development team about the removal of "latest" and they indicated that currency was not relevant for MU value sets. The Mayo technical team will continue to discuss with NLM to understand and hopefully influence changes to the NLM service. There is a possible demo with NLM in August. This will need to be planned with both teams. To be discussed next weekCory will complete the lessons learned and limitations of the VS client prototype. These will be shared when Larry sends a note to announce the prototype. | ||
| UMLS Load of ICD10 CM issue | This was identified as a source issue - structure of the RRF. ICD10-CM - there was a source issue - merged top level concepts (available in next export to NCI) Scott has not been able to successfully load SNOMED. Once we new version to be loaded, Scott can try again to see if successful or not. Raw RRF files to be updated to allow ICD10 CM Hierarchy to work. SNOMED load at Mayo has problems, but NCI load does not. Scott is looking into this - compared to previous loads. |
JIRA Issues
| Description | ||||||
|---|---|---|---|---|---|---|
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
|
Project Plan Changes
| # | Description | Due Date | Resources | Notes | Risks | Mitigation |
|---|---|---|---|---|---|---|
| None | ||||||
Planned Activities
| Area of Interest | Details |
|---|---|
Risks, Issues, Dependencies
Risks
| # | Opened Date | Due Date | Description | Likelihood (H, M, L) | Impact | Assigned | Status | Mitigation Strategy |
|---|---|---|---|---|---|---|---|---|
Issues
| # | Opened Date | Description | Impact | Assigned | Status |
|---|---|---|---|---|---|
Dependencies
| Opened Date | Description | Assigned |
|---|---|---|
...
