/
2026-02-19 LabMCoP Meeting Notes
Edit

2026-02-19 LabMCoP Meeting Notes

Date

Feb 19, 2026

Attendees

Present

Name

Organization

Present

Name

Organization

X

Nancy Cornish

CDC

 

Manjula Dharmawardhana

CDC

X

Riki Merrick

APHL

X

Christina Gallegos

APHL

X

Amy Liu

Inductive Health / APHL

 

Raj Dash

Duke / CAP

-

John Snyder

Pragmatic Terminologies, LLC

X

Andrea Pitkus

UW

 

Kathy Walsh

Labcorp

 

Rob Hausam

Hausam Consulting

 

Pam Banning

 3M

Upcoming OOO

 

Follow up items

 

Nancy Update

 

CDC is working on https://isp.healthit.gov/united-states-core-data-interoperability-uscdi#draft-uscdi-v7

Specimen Collection Date/Time: is covered by Performance Time under the Healthcare Information Attributes

looking for use cases to support these othere elements - this was discussed 2026-01-20 LIDR Meeting Notes

Specimen CMT terms review

Christina

no new terms to review

 

Lab tests as procedures or orderables

not discussed

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: SNOMED International Browser

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

Specimen CMT - Hosting Options

not discusse

  • How can we publish the content in the dB?

    • Allow access somehow to query the dB

    • as access or excel or csv

    • Using FHIR conceptMap similar to Conceptmap-example-specimen-type - FHIR v6.0.0-cibuild - based on this profile: ConceptMap - FHIR v6.0.0-cibuild using a script to create this from dB content - - zulip thread review: Public view of FHIR Community | Zulip team chat

      • Check if ConceptMap resource in FHIR R6 incorporated the coding datatype for valueset attributes

    • Clinical Architecture has modeled the Specimen CMT in Symedical, though still need to check how to deal with the prototype additional field instructions (for nice to have elements) so can then be shared at least via their subscription, but maybe also arrange sharing via API

  • SNOMED CT Extension and use of RefSets (start with VSAC value sets as proof of concept and then migrate over) to indicate:

    • preferred specimen types by domain

    • maybe also terms that need additional attributes (by kind of attribute) if we also write an implementation guide for it

  • How do we decide what format to share this in - get input from EHR-s and LIS vendors:

    • Write letter of mulitple stakeholders to request EHR-s and LIS vendors to implement

      • indicating that this is a patient safety issue, as incorrect Abx treatment will contribute to multi-drug resistance (use CTSI findings to provide background)

      • focus on blood, urine, wound cultures (get data from NHSN, too)

    • Nancy is talking to DHQP about the linkage with specimen collection

    • Professional organizations - like CAP and ACOS and AJCC get them to write the synoptic reports (better structuring of data) - for surgical aspects - similar to what CAP has done for Cancer

    • try to get AMA support to get providers to adopt this

    • Reach out to IDSA, too

  • Need to consider long-term curation

European Semantic work

not discusse

Link to the German FHIR IG around suceptibility testing:

ARS Implementation Guide (EN)

Semantic Example section: ARS Implementation Guide (EN)

Confluence page:

Ask if Rob can keep us updated

Specimen CMT pilot implementers

not discusse

Specimen CMT - education

not discusse

  • 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 SHIELD FDA BAA Year 2

Specimen CMT - tracking implementation impact

  • Setting baseline

  • Define metrics

not discusse

 

Future projects for this call after CMT

not discusse

  • 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:

Please contact riki.merrick@aphl.org for a copy

Chat:

Screenshot 2026-02-19 113225.png
Screenshot 2026-02-19 120220.png

 

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.