2026-07-30 LabMCoP Meeting Notes
Date
Jul 30, 2026
Attendees
Present | Name | Organization |
|---|---|---|
X | Nancy Cornish | CDC |
X | Manjula Dharmawardhana | CDC |
X | Riki Merrick | APHL |
X | Christina Gallegos | APHL |
- | Amy Liu | Inductive Health / APHL |
- | Raj Dash | Duke / CAP |
X | John Snyder | Pragmatic Terminologies, LLC |
X | Andrea Pitkus | UW |
X | Kathy Walsh | Labcorp |
| Rob Hausam | Hausam Consulting |
| Pam Banning | 3M |
| Elissa Passiment |
|
| Kristina Betz | CDC - NHSN |
| Jake Bunn | CDC |
| Marissa McMeen | CDC |
Upcoming OOO |
|
|
|
Announcements | Andrea |
1. What best practices has the laboratory implemented to reduce and monitor BCC?
We should make a comment to re-instate CLIAC, since data for this RFI came from their recomendations we got Specimen Collection Date/time and collection method added; Specimen Condition now has the correct name they still have the Healthcare Attributes class, that has the Reason Not Performed and Performance Date/time Looking in US COre: they have no lab specific ServiceRequest artifact, but the generic one prescribes the use of Lab LOINC for .code and use of Lab test SCT code from the procedure hierarchy (which might exacerbate the isseu of folks wanting to use Procedure to model a Labtest) |
|
SNOMED International proposal for Serologic terms | for when John is here | SNOMED International is purposing to revise content with “Serology” or “Serologic” in the FSN and remove this wording from FSN across clinical findings, procedures, and observable entities. I would like LabMCop team to review and provide any feedback on the topic during the meeting. Prior discussions: 2026-06-25 LabMCoP Meeting Notes Next Steps:
|
|
Salmonella Serotype SNOMED CT code requests | for when John is here | APHL has gotten this request for Salmonella serotype concepts (AIMSSD-14636) - John has mapped another enterics to existing concepts before - there are 219 unmapped, which we need to review:
There is actually another file with Salmonella serotypes (from OR PHL) Christina is working on (that’s the AIMS ticket linked above - need to find the other AIMS ticket wehre this file is coming from) Problem is that some of the testing for specific serotypes have qualitative results - those are not part of this file About a ddecade ago Patti Fields (CDC) had a great spreadsheet with mappings between the formula and serotypes - her preference would be to have folks just use the formula instead of names - potnetially we could reserve SCT coding at the species level (which is what most clinical labs can diagnose) and leave the serotypes just formula? Before creating any new concepts should check the veterinary extension: : https://vtsl.vetmed.vt.edu/TerminologyMgt/Browser/results.cfm Next Steps: Send file to Nancy for checking with Enteric Disease Lab Branch SMEs (DFWED) |
|
Working with DHQP for NHSN reporting | Nancy | Follow up list:
|
|
Follow up from AndesVirus codes question | Riki |
|
|
HPV screening/confirmatory testing workflow | John | Need to find a date with Hanna - John to do! We’d like to discuss with the group the current modeling and naming policy for procedures connected to detecting HPV and/or pre-cancerous/cancerous cells in the cervical region. From Andrea Pitkus' email: US protocols are usually to reflex to HPV testing with PAP Smears. Most use liquid based methods such as Thin Prep (brand). Technically, cytopathology is the term used for this area of laboratory testing. I'm sure Nancy will have more thoughts too. Robyn Temple-Smolkin (AMP) email: Our reference lab used to run HPV from ThinPrep or SurePath. Sample would go to the hospital cytopathology lab for preparation of the pap smear then the atypicals were reflexed as sendouts to us for high-risk HPV testing by PCR. The entire ThinPrep/SurePath vial was the specimen we received. We also did CT/NG off this sample when ordered. I believe this is still a very common workflow performed either within one institution or as a sendout, but defer to others' input on newer workflows as I have been away from day-to-day operations since joining AMP. prior discussion: https://www.hologic.com/hologic-products/collection-devices/thinprep-pap-test = example of the collection kit the collection is the swab/brush/spatula of cells, this is really the collection container though Here is the labcorp example: https://www.labcorp.com/tests/507385/high-risk-hpv-with-hpv-genotypes-16-and-18-cobas which shows the different colelction methods depending on container used at the bottom Hologic ThinPrep package insert page: https://www.hologic.com/package-inserts/diagnostic-products/thinprep-pap-test Try to see, if Jenna from Arup can be available then, too |
|
Call adjourned - below not discussed |
| 11:58 AM EDT |
|
Question on Karius Testing | Riki/Christina | Next Steps:
|
|
Specimen CMT - Hosting Options | Riki | Any Updates on FU with: Clinical Architecture: They could create conceptMap based on the content model they built, need to follow up about FHIR server usage ONC: Pull up email from Carmela |
|
Specimen CMT terms | Christina | Review collection method concepts (initiated by USCDI valueset creation: https://hackmd.io/38xa1BZ7TjaPMao6LJHuCA#Proposal ): retired concepts: 24139008 Endoscopy of urinary bladder (procedure) not in procedure hierachy: 258429002 Rectal scrape specimen Using preferred name, not FSN (these should not be an issue in the final version, since FSN or preferred name would be pulled based on the concept code, correct?): 122462000 Drainage procedure |
|
Reflex testing in FHIR follow up | Andrea | Andrea is working on a reflex workflow layout to check how the orders / grouping and specimen reject might work: - look at minutes from last week: 2026-07-02 LabMCoP Meeting Notes |
|
CMT Governance process |
|
|
|
CMT proposed maintenance process |
| Start writing this up on this confluence page: Specimen CMT Update Process Questions from Zulip thread that should be covered by the process we come up with here:
User Guide starter Specimen Cross-Mapping-Table (Specimen CMT) |
|
Follow up items |
|
|
|
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: https://browser.loincsnomed.org/?perspective=full&conceptId1=363787002&edition=MAIN/LOINC/2025-09-21&release=&languages=en 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
There is this question in the LOINC Community: https://forum.loinc.org/t/assistance-creating-a-value-set-for-all-loinc-procedure-concepts/2993 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: Confluence page: Ask if Rob can keep us updated |
|
Specimen CMT pilot implementers |
|
|
|
Specimen CMT - education |
|
|
|
Specimen CMT - tracking implementation impact
|
|
|
|
Future projects for this call after CMT |
|
|
|
Recording:
Please reach out to riki.merrick@aphl.org for access to the recording.
Chat:
11:20:00 From Andrea Pitkus : This is great to see for the serotypes. Do these include all the variations from qualitative testing (especially for serotypes) with all the organism identifications that could occur so the gaps in SCT organism hierarchy codes are reduced?
11:22:37 From Andrea Pitkus : For salmonella, 13, 23 non motile, it is mapped at salmonella Group O:13, but there also appear to be motile versions too
11:22:45 From Andrea Pitkus : so it may be a missmapping as I'm reading it
11:23:57 From Andrea Pitkus : Replying to "For salmonella, 13, 23 non motile, it is mapped at salmonella Group O:13, but there also appear to be motile versions too"
Is there a SCT org code for Salmonella Group O: 13, 23?
11:25:15 From John Snyder (NLM / US SNOMED NRC) : Replying to "For salmonella, 13, 23 non motile, it is mapped at salmonella Group O:13, but there also appear to be motile versions too"
Not that I see
11:26:02 From Andrea Pitkus : Replying to "For salmonella, 13, 23 non motile, it is mapped at salmonella Group O:13, but there also appear to be motile versions too"
It may be why they mapped to the higher level O:13, so it would be good to have that more detailed code like the row above it (row 4)
11:28:25 From John Snyder (NLM / US SNOMED NRC) : Salmonella 1,3,19:e,h:e,n,z15
11:33:05 From John Snyder (NLM / US SNOMED NRC) : https://vtsl.vetmed.vt.edu/TerminologyMgt/Browser/results.cfm
11:41:24 From Andrea Pitkus : Has this been emailed so we can provide the feedback?
11:46:02 From Andrea Pitkus : and updated specimen condition acceptability
11:47:23 From Andrea Pitkus : Given specimen collection is a procedure, procedure is a item that could be used
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.