Attendees
| Name | Role | Present |
|---|---|---|
| Wright, Larry | NIH/NCI | x |
| Fragoso, Gilberto | NIH/NCI | x |
De Coronado, Sherri | NIH/NCI | |
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 |
| Brem, Larry | NIH/NCI [C] | |
| 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 | |||
| 72 | Scott | Add release date to Release notes when appropriate | open | |||
| 129 | Scott | Further testing on Production around the breaking value set | open | |||
| 130 | Scott | Update 227 for flag for exceeding max clause count | open | |||
| 131 | Scott | Check the database to make sure the MOA value set entries are there | open | |||
| 132 | Scott | Fix the value set name truncation by the end of the week | open | |||
| 133 | Scott | Talk to Harold about value set versioning | open | |||
| 134 | Scott | Fix the value set truncation problem | done | |||
| 135 | Scott | Check compatibility of 6.0 and 6.1 clients against 6.1 | done | |||
| 136 | Cory/Craig | UI design | done | |||
| 139 | Scott/Cory/Craig | Face to face notes review | done |
Progress
| Immediate Priorities and Problems (Scott) | RRF Loader - problem resolved. There were LF chars in some of the files, so the script files were causing problems with the load. Scott and Tracy were able to resolve - Scott updated the files and checked in the changes. ICD9CM successful so far. Tracy will then try the rest of the loads to confirm the fixes. CTS2 Client UI - Project Plan - Updating JIRA items and will hope to have an initial of plan ready by end of the week. | ||
| Face To Face Followup | Distribution of Notes Please send comments or concerns to Craig or Larry. | ||
| 6.1 Deployment | Status - Passed the Nessus scan. Still waiting on request for waiver (JBoss5.1 issue) - may be complete today. Security team doesn't see any additional concerns. | ||
| Resolved Value Sets from different Coding Scheme versions (Kim) | Scott to talk to Harold about the Resolved Value Set versioning issue. Notably they are allowed to use previous value set versions. Will need to keep previous versions of value sets for CDISC. Scott did get to talk with Harold. This is supported, but will be a complex and difficult functionality to implement. If a work around exists, it may be better to use such a work around. There is a call to get the coding scheme name and coding scheme version and this should work fine for the LexEVS resolved value sets (represented as a coding scheme). When loading the resolved value set, there is a coding scheme version specified. Is there a way to expose that version - exposed as version of coding scheme (can be resolved against several different versions of coding schemes)? This will need additional discussion and design - we can discuss again next week. | ||
| JIRA or GitHub for forum (Jason) | What is meant by a Sandbox? There was an email thread (Gilberto and Julie) regarding the immediate solution as a "sandbox" - but there is concern about how to proceed if this isn't a permanent solution. Gilberto confirmed this isn't meant to be a sandbox. LexEVS/LexEVS is to be considered a production development location. Development to be done in LexEVS/LexEVS and then periodically, the code would be updated on the NCIP channel. JJ to send us information. | ||
| Value Set Truncation problem | Status - This code delivered on Tuesday by Scott. It is now available to Tracy (although there is a current workaround). Tracy should need to resolve the value sets. | ||
| Confirming distributed backward compatibilities | Need to confirm that 6.0 can talk to 6.1 in distributed mode. Scott confirmed this - 6.0 and 6.1 behave the same in distributed mode. Minimal review was done and junits were run - and when failures, confirmed the failures were expected (source issues). | ||
| ARC Meeting (Craig) | Craig to coordinate with Jason. ARC document needs to be created first - to be provided for the request. There is a 6.1 ARC document - use this as a starting point. (Resources - ask what we want - 16GB, SSD, etc). | ||
| Tech stack upgrade (Protege) - Gilberto | Java 7, CentOS update related. Protege worked fine - except with search behavior (Lucene and Java 7). There is a server freeze situation. | ||
| Searching - Contains search issue | There is a forward slash in the search. Note was sent to Kevin and others. Kevin hasn't had a chance to respond. | ||
| MedDRA loader | Kim sent an email regarding how getting loaded. Kim can resend to Scott (possibly in NCI). |
JIRA Issues
| Description |
|---|
| LEXEVS-570 - Getting issue details... STATUS |
| LEXEVS-572 - Getting issue details... STATUS |
| LEXEVS-573 - Getting issue details... STATUS |
| LEXEVS-574 - Getting issue details... STATUS |
| LEXEVS-576 - Getting issue details... STATUS |
| LEXEVS-579 - Getting issue details... STATUS |
| LEXEVS-583 - Getting issue details... STATUS |
| LEXEVS-584 - Getting issue details... STATUS |
| LEXEVS-585 - Getting issue details... STATUS |
| LEXEVS-586 - Getting issue details... STATUS |
| LEXEVS-587 - Getting issue details... STATUS |
| LEXEVS-588 - Getting issue details... STATUS |
| LEXEVS-589 - Getting issue details... STATUS |
| LEXEVS-592 - Getting issue details... STATUS |
| LEXEVS-593 - Getting issue details... STATUS |
| LEXEVS-594 - Getting issue details... STATUS |
| LEXEVS-595 - Getting issue details... STATUS |
| LEXEVS-596 - Getting issue details... STATUS |
| LEXEVS-597 - Getting issue details... STATUS |
| LEXEVS-598 - Getting issue details... STATUS |
| LEXEVS-599 - Getting issue details... STATUS |
| LEXEVS-600 - Getting issue details... STATUS |
| LEXEVS-601 - Getting issue details... STATUS |
| LEXEVS-602 - Getting issue details... STATUS |
| LEXEVS-603 - Getting issue details... STATUS |
| LEXEVS-604 - 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 |
Project Plan Changes
| # | Description | Due Date | Resources | Notes | Risks | Mitigation |
|---|---|---|---|---|---|---|
| None | ||||||
Planned Activities
| Area of Interest | Details |
|---|---|
| VSMC definition | Need a dialog defining module use around ResolvedValueSets |
| Update LexEVS CTS2 Service to CTS2 1.1 | Need deployment tests |
| Work on a variety of EVS JIRA Priorities | Scripting, convenience methods, tree extension namespace issues |
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 |
|---|---|---|
