Attendees
Name | Role | Present |
---|---|---|
Wright, Larry | NIH/NCI | x |
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] | |
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 | |
Gavin Brennan | x | |
Preston Wood | 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 | |||
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 | on hold | ||
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 | ||
200 | Larry/Sherry | Query current LexEVS users about use of SOAP, REST or QBE services in the legacy caCORE api's | 2014.6.18 | on hold | ||
207 | Cory | Write issue against CTS2 OMG regarding the ability to return INACTIVE concepts only. | 2014.07.30 | on hold | ||
209 | Craig/Larry | Plan Techical F2F/AMIA meetings. | 2014.07.30 | on hold | ||
210 | Larry/Gilberto | Determine if there is a need to meet with the CTRP | 2014.07.30 | on hold | ||
212 | Larry | Include LexGrid XML Export as part of the 5.1 retirement notice. | 2014.07.30 | on hold | ||
224 | Scott | URI Resolver - Provide overview of how to access the URI Resolver | 2014.09.03 | on hold | ||
225 | Scott | URI Resolver - Look at TLAMP and VSAC service to determine usage of URI Resolver | 2014.09.03 | on hold | ||
233 | Cory | Let Tracy know when to re-Index after CTS2 fix is rolled up the tiers. | 2014.10.02 | done | ||
234 | Joanne and Brian | Provide ICD10-CM issue details to Scott for evaluation. | 2014.10.02 | done | ||
235 | Mayo Team | Identify additional value set JIRA items to be included in 6.3 release. | 2014.10.02 | open | ||
236 | Craig | Create MOD4 project plan. | 2014.10.02 | open | ||
237 | Scott | Final code deliverables posted to SFTP site and wiki pages updated. | 2014.10.02 | open | ||
238 | Scott | Create JIRA items for ICD10-CM issues (from Joanne) | 2014.10.08 | done |
Progress
Immediate Priorities and Problems (Mayo Team) | Scott: CTS2 deployment, SNOMED/ ICD10CM issues, Issues support
Cory: CTS2 issue and AMIA Poster
Craig: Project Plan, Project Startup, Poster
|
SNOMED/ICD10CM Load | Loads at NCI are acting differently than our loads here at Mayo. Plan on reload transitive table (after DB restart). Then look at SQL settings/variables in configuration to determine if there are differences. ICD10 CM - comments from Joanne and Stephanie. It was decided that LexEVS is now doing what is needed, but Stephanie needs to work out some content issues. |
CTS2 Issue | Cory and Scott investigated and determined that index is missing in the DB - need to have indexes built on QA to reflect the database on QA. Rob working on getting the indexes on Dev - going to bounce the DB and then reload. If successful, then move the indexes to QA. |
Production Tier Server Configuration (Gavin @ 2:30-3PM) | Stage currently not avaible to outside users for testing. Want to move Stage to the same segment as Production. Separate STAGE server in the production network segment. (1 production blade and 1 stage blade) Would prefer to have a fail-over blade. This is a security policy in that the servers that are on an external segment need to be APP scanned. There cannot be a non-app scan server on the network with external accessible servers (PROD). There are 2 blades provisioned in the production environment (Blade A is primary and Blade B is fail over) There is a need to isolate tiers from other tiers. Suggested to use the second Blade (with option to use the blade if primary blade goes down). Need to consider I/O contention, lucene indexes, paths, etc, if 2 instances. There is sufficient DB storage. 100GB was planned in the arch document. (2 instances (STAGE and PROD) on the same blade server) There are currently 4/socket and 4 sockets per blade server. LexEVS was first to be deployed in this new environment. Blade A is running production (like Stage on lower tier). Blade B is running differently than production. It was suggested to start with the 2 Blades in production as A - Production and B - Stage. As procurement processes get better, then consider additional servers. Lucene on SAN-based (8 GB fiber, not internal drive) - would this work? Would normally try this in QA. Collaborators are testing software outside the firewall. Diagrams to be created to visual the environment.
|
POST AMIA Discussion | Possible discussion on Wednesday PM or Thursday AM/PM. Thursday could work. Need to come up with agenda/topics. |
JIRA Issues
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 |
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 |
---|---|---|