2026-05-07 LabMCoP Meeting Notes

Date

May 7, 2026

Attendees

Present	Name	Organization
X	Nancy Cornish	CDC
X	Manjula Dharmawardhana	CDC
X	Riki Merrick	APHL
X	Christina Gallegos	APHL
X	Amy Liu	Inductive Health / APHL
-	Raj Dash	Duke / CAP
X	John Snyder	Pragmatic Terminologies, LLC
-	Andrea Pitkus	UW
X	Kathy Walsh	Labcorp
	Rob Hausam	Hausam Consulting
	Pam Banning	3M
	Elissa Passiment
	Kristina Betz	CDC - NHSN
	Diego Arambula	CDC

Upcoming OOO		Reminder: We are now using https://aphlinformatics.atlassian.net/wiki/spaces/LMCOPL/calendars and everyone can just keep it updated NOTE: you will need to use type “Event” if you do not have a confluence account Riki not available 5/21 and 5/28 - what do folks want to do with these dates - we will decide next week
Working with DHQP for NHSN reporting	Nancy	Follow up list: Urine culture results for HAI - ask Kristi when we ask her to help us formulate the questions for SHIELD goal is to set up the LOINC codes needed for collecting blood culture contamination data - future best practice - reached out to Xavier and working on an email that can be shared with Raj (for Duke and CAP for
Specimen CMT terms	Christina	only NHSN terms left for questions: NHSN blood has different info from our blood term will combine comment and collection method links - keep both: one for venipuncture (need to update to new link) one for blood culture - Nancy sent: Prevent Adult Blood Culture Contamination \| Laboratory Quality \| CDC cardiovascular sample - too broad - do not use cartilage - our term already has everything NHSN term has, so no need to add CervixCytologicalMateriallMaterial - should add, links are working; remove the SPM-7 entry by Andrea, this is not part of the current SPM-4 term definition in SCT browser ChylousFluid - need that as PHLP PreferredName; should further define from where in the body this has been collected, so SPM-8 required, SPM-9 nice to have; micro-related - also chemical, partially defined; preferred; example for chemistry:
Call adjourned		11:59 AM EDT - below not discussed
Specimen CMT - Hosting Options		Any Updates on FU with: Clinical Architecture: ONC:
CMT Governance process
CMT proposed maintenance process		Start writing this up on this confluence page: Questions from Zulip thread that should be covered by the process we come up with here: Requests for terms used in practice that are not yet in the Cross Map Table? Requests for any corrections or needed updates to terms? What type of version control will be leveraged for releases and major/minor updates? How do you plan to incorporate SNOMED CT Release Updates into Cross Map updates/releases? At what frequency will updates occur? For example, will you process SCT updates once yearly and have a subsequent Cross Map release yearly with changes or more or less often? How do you communicate differential changes between releases? Is a differential file produced or is it expected that users will be able to find changes on their own? What type of customer support for downloads is expected? Will the release entity provide or is it expected of the site hosting the content for download? Both need to work colLABoratively to ensure no blockers arise for users/consumers. User Guide starter
Follow up items		Riki’s Follow up - none of these got done yet Contact United Network for Organ Sharing for input on donor terms (pre-coordinated or not?) = ISBT 128 \| ICCBBA \| Technical Documents https://www.isbt128.org/_files/ugd/1a7593_edfd176861c94dca94c34eff8fa3ad0d.pdf - for organs Riki has some contact now with European bloodbank and biobanks = Home - BBMRI-ERIC working with the folks that define their minimum data set: MIABIS - BBMRI-ERIC - these folks shared the follwoing for the reject reason topic, but it seems they differentiate between source site and the organ: #1 Standard PREanalytical Code Version 4.0 - (version 3.0 is here: https://cdn.ymaws.com/www.isber.org/resource/resmgr/isber_2019/pdf/standard_preanalytical_code_.pdf) and also Robin for US Clinical Archtecture unmapped LOINCs: Riki should check up with Charlie to see, if he knows where the LOINCs using the shorname in the description come from - as that is discouraged Riki to set up her VSAC authoring log in For wound modeling (see 2023-11-30 LabMCoP Meeting Notes ) create a few pre-coordinated specimen terms to cover the wound causes as children under: 119365002 \| Specimen from wound (specimen) another child term for aspirate under 445611000124106 \| Specimen from bite wound (specimen), since that is preferred over the existing swab
Lab tests as procedures or orderables	Do we still need this?	Recommendation by SNOMED is that the Observable entity hierarchy be used for both ordering and resulting. As for the technique hierarchy, that in no way is intended to be used for either ordering or resulting laboratory tests. Those concepts are used to model both observables and procedures. SNOMED LOINC extension: The problem is that major EHR-s vendors have set up CPOE using Procedures for orders to initiate a workflow (that creates the triggering event in the system) - that’s where the push-back comes from. There is a CPT to SNOMED CT mapping (as a paid mapping available from AMA), but no LOINC mapping. Can we reach out to CAP Informatics, ADLM Informatics and ASCLS Informatics to get their take on where Lab tests should live We had said we would work through the Colonoscopy example: Reference links: clinical guidelines: Official journal of the American College of Gastroenterology \| ACG Quality Indicators: Official journal of the American College of Gastroenterology \| ACG For CAP cancer reporting is using SNOMED CT - would be good to look which they chose to represent the performed lab test There is this question in the LOINC Community: it is related to this US Core FHIR Change request: https://jira.hl7.org/browse/FHIR-54415 Answer to this one is that in USCDI Procedure (https://isp.healthit.gov/taxonomy/term/781/uscdi-v6) does not list LOINC as applicable Vocab standard in any verion, so remove it. Often folks think of lab tests as procedures, because they can be ordered in CPOE (and outsidde the US, in the UK for example that’s how folks have modeled those, which is why LOINC was adding more of the high level order codes in 2.81 release, so we still should tackle the LOINC community question. John was working on creatign an intesnional valueset definition based on class + type and maybe a few other attributes
European Semantic work		Link to the German FHIR IG around suceptibility testing: Semantic Example section: Confluence page: Ask if Rob can keep us updated
Specimen CMT pilot implementers		Review where we are: Vendor Connections
Specimen CMT - education		Need education for providers and IT folks that helps with set up of the EHR-S / LIS configuration -this can be supported / accomplished? with the Implementaiton Guide we could write if we have a use case of how a patient is impacted on their journey through the healthcare system - CAP created a nice video that showed how patient care was affected by incorrect data
Specimen CMT - tracking implementation impact Setting baseline Define metrics
Future projects for this call after CMT		In general the call is intended as a forum for ANY messaging related issues to work out. In the past we have reviewed containers re-vive that - and how does that interact with devices (UDI identification?) review code systems around additives (HL70371 and SCT substance and product hierarchies) started work on cross-mapping between HL7 method codes and SNOMED CT procedure / technique concepts American College of Surgeons is working on procedure protocol and synoptic data elements / surgical synoptic reports - we could work with them together on that Look at other HL7 tables that we would want to migrate SCT

Recording:

If you are interested in the recording, please email riki.merrick@aphl.org

Chat:

11:18:32 From John Snyder (NLM / US SNOMED NRC) : Sorry am running late today
11:27:29 From vgh5@cdc.gov :
11:28:16 From vgh5@cdc.gov : Prevent Adult Blood Culture Contamination | Laboratory Quality | CDC
11:50:30 From sage.zoom@aphl.org :

Action items

Type your action, use '@' to assign to someone.

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.

Add a decision…

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.

Create from Template