2025-04-10 LabMCoP Meeting Notes
Date
Apr 10, 2025
Attendees
Present | Name | Organization |
---|---|---|
- | Nancy Cornish | CDC |
- | Manjula Gama-Ralalage | CDC |
X | Riki Merrick | APHL |
X | Christina Gallegos | APHL |
X | Amy Liu | Inductive Health / APHL |
- | Raj Dash | Duke / CAP |
- | John Snyder | National Library of Medicine (SNOMED CT) |
X | Andrea Pitkus | UW |
X | Kathy Walsh | Labcorp |
| Rob Hausam | Hausam Consulting |
| Pam Banning | 3M |
Discussion topics
Upcoming OOO |
|
|
CSTE Presentation | Riki - no update |
|
European Lab related Vocab | Riki | European Lab Terminology group final list of containers - they will submit anything they need to SNOMED CT - |
LOINC SNOMED Extension Follow up |
|
|
Specimen CMT - review of terms with questions | Christina/Amy |
|
SCT hierarchy for methods | ask John | Observation method the thought was to map to techinque hierarchy - background from email here: A decade ago we didn’t have the LOINC/SNOMED collaboration with a SNOMED Extension, so mapping to the procedure hierarchy made perfect sense. Fast forward to where we are today.The most useful way to handle this would be to map to the “Technique” attribute value range. Right now that attribute is restricted to referencing concepts in << 272394005 |Technique (qualifier value)|, however as we get into the clinical and radiology domain, I can see that range constraint being expanded to include << 129265001 |Evaluation - action (qualifier value)| in order to pick up the imaging method (i.e. MRI, CT, US, etc.) and possibly but unlikely other subhierarchies in the qualifier value hierarchy Specimen collection (SPM-7) should be from procedure hierarchy, correct? |
Creating Value Sets for specimen related attributes | John - no update |
|
Previous Action Items | Not discussed |
|
Specimen CMT - Hosting Options |
|
|
Specimen CMT pilot implementers |
|
|
Specimen CMT - education |
|
|
Specimen CMT - tracking implementation impact
|
|
|
Specimen CMT - Compare to NHS Medical Terminology testing |
| Will get updated vocab at a later date |
Future projects for this call after CMT |
|
|
Recording:
Per APHL policy we are not currently allowed to record any meetings
From Chat
Action items
Quick decisions not requiring context or tracking
For quick, smaller decisions that do not require extra context or formal tracking, use the “Add a decision…” function here.
Decisions requiring context or tracking
For decisions that require more context (e.g., documentation of discussion, options considered) and/or tracking, use the decision template to capture more information.