Attendees
Name | Role | Present |
---|---|---|
Wright, Larry | NIH/NCI | x |
Fragoso, Gilberto | NIH/NCI | |
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 |
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 | |||
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 | ||
235 | Mayo/NCI 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 | done | ||
237 | Scott | Final code deliverables posted to SFTP site and wiki pages updated. | 2014.10.02 | on hold | ||
238 | Scott | Post GEM loader onto GIT. | 2014.10.22 | open | ||
239 | Scott | Discuss Transitivity issues with Kevin. | 2014.10.22 | open |
Progress
Immediate Priorities and Problems (Mayo Team) | Scott: SNOMED Transitivity table, Tree update, external users
Cory: AMIA poster
Craig: Project Plan, Poster
|
Lock file issue on Dev for Metabrowser | MetaBrowser had lock - couldn't use the indexes. Jacob changed permissions and it resolved the issue. (Happening on Stage) Group permissions on specific groups needed to by applied. Storage team notified and they will change users when the indexes are being written (different Tomcat users). PTE updated to include change of permissions command. No notices that this has been applied up the tiers. (It is running on QA). |
SNOMED/ICD10CM Load | SNOMED - time spent performing loads locally at Mayo - transitivity load happening every time. Cannot duplicate error seen at NCI. Reviewed the SQL output - there is nothing that stands out that would identify a problem. There is a QUIT command - not sure why it is there, so investigating why it is needed. Local install is set to all defaults, so nothing specific has changed (or is changed for the load). Learning about how MySQL works to determine of there are any problems associated to DB config. May need to consider having Kevin take a look |
External Users/Interest in GEM loader/ lbGUI/ Authoring | Several ongoing external support discussions. Recent user: Wants to use the GEM loader as we describe in the documentation.
Also was interested in using the GUI for authoring. Possible interest generated from Git? Other reasons?
|
Tree Update/ NPO file | There is a risk that the hierarchy will change to support this tree update. Running this against the NPO file to look at issues that may exist. Possibly look at zebrafish (small enough). Namespace issue is holding up the update. There should be a supported coding scheme for each supported namespace in LexEVS. Scott will revisit and confirm the underlying issue. |
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 |
---|---|---|