Attendees
Name | Role | Present |
---|---|---|
Wright, Larry | NIH/NCI | |
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 |
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 | open |
Progress
Immediate Priorities and Problems (Mayo Team) | Scott: URI Changes, SNOMED load, Kim's Issue, CTS2 Issues
Cory: CTS2 issue and AMIA Poster
Craig: Project Plan, Project Startup, Poster
|
| |
SNOMED Load | Continued review of SNOMED issue. Determined there is no transitivity table built. This would possibly be why hierarchy isn't displayed in the term browser. Scott to continue to investigate and identify if hierarchy was ever present - or merely using the qualifiers to determine hierarchy (CHD Relation). Need to know how this is being done in the term browser (Kim to provide??).
| ||
AMIA Poster | Plan on having a draft to show next week to get feedback. | ||
ICD10-CM Loading Issue with 6.1 | Scott did get the information from Joanne. Hasn't had time to review. There may be todos for the loader based on feedback - will create JIRA item to capture these requests. Should be less priority than SNOMED as Joanne has a work around. Determined that we are not showing hierarchy - no "@" or "@@" rows being created. | ||
CTS2 Issue | Re-indexing is expected to solve problems. There are DRT tickets that need to be resolved for DEV (too many files). |
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 |
---|---|---|