- Team Agendas
Date | Agenda Items | Notes | Action Items |
---|---|---|---|
|
|
| Craig M. Zwickl will follow up with Ellie about status of this request – this variable needs to be requested for both LB and MI. Erin Muhlbradt to create folder on portal and create an attendance file. Done |
| |||
| |||
|
| 1. Completed Didn't get to 2 and 3. | |
|
| 1. Completed 2. Completed all except CT-95 Didn't get to 3, 4.
| Erin Muhlbradt to send CT-95 P29 public review comment to team via email to see if we can resolve offline. |
|
|
This is leading me to believe that the team needs to discuss potential solutions for these more complicated test names (both short-term and long-term) which involve numerous modifiers and subsets that have no name other than a portion of the marker string. So far, it seems we’ve only developed a partial modeling solution, so are not yet ready to provide a complete recommendation on implementation. As well, with a more complete solution in hand, our CT subteam will be able to continue its work of expanding the test name codelist beyond the simple terms we’ve already identified. There is a solution for the difficulties, but we need to discuss the various options to try to find the best one for the domain model. The central question is how much information do we want to cram into the test name? Audrey Walker also shared strong reservations towards publishing out this set of CT until more difficult issues are also resolved.
Sue Use case; First test – T Lymphocytes is the test code Antigen Marker string is CD3+CD8+CD4- Result is expressed as a percentage of total T lymphocytes I can’t use the test code/name of TLYCE - T-Lymphocytes because this is a relative count What code would you anticipate we would be using? TLYCTLYC – T-Lymphocytes (CD3+CD8+CD4-) as a percent of total T cells? Since the Antigen string which describes the T-cells being counted is in the SUPPQUAL field, how else will we describe the relative cell counts?
Team decision: (Craig, Sue, Ngaire, Erin, Manjula) Do not add these terms to P29 for now until the model can accommodate more complex use cases. Craig to email full Flow Cytometry team to let them know of this decision and refute this decision over email if necessary. CT-95, CT-95 public review comments were resolved. 2. New Term requests i. Team discusses relative tests and what to do with CD marker string in numerator and denominator – solution 1 would be to give guidance that the forward slash needs to be used in the new NSV to demarcate the CD marker string numerator and denominator; solution 2 would be to create 2 NSVs, one for the numerator marker string and one for the denominator marker string; solution 3 would be to give guidance to report CD marker string for numerator.; solution 4 would be to not use CD marker string at all for any of these relative measures. ii. Sue shared that her database does contain these relative type measures but the denominator CD marker string is very short (CD4+CD8+). 3.
i. Positive/negative: Please use + (positive) sign for Positive and – (negative) sign for Negative. ii. Bright/dim: Please use iii. Low/High/Moderate: Is this low/high synonymous with Bright/Dim? iv. Negative to Low: (this is from Sue) Do not use forward slash.
v. Forward slash for denominator: Only use forward slash for denominator
| Craig M. Zwickl to communicate decision to hold off on Flow Cytometry CT with P29. Erin Muhlbradt to prep requested flow cytometry terms for review next time. done |
|
| Review new term requests
Team re-discusses Batch 2: More complex normal cells and relative counts of normal cells. (Batch 3 will include abnormal cells and tumor cells). Flow Cytometry Team to come up with conventions for how to represent CD marker string (team members to send in their company conventions) – Do not do today. We’ll need a full session to flesh this out. | |
|
|
P29 Working Documents
Date | File | Author |
---|---|---|
2017-01-27 | em | |
2017-02-08 | em | |
2017-02-15 | em | |
| em |
Attendance