2024-05-16 LabMCoP Meeting Notes

Date

May 16, 2024

Attendees

Pesent

Name

Organization

Pesent

Name

Organization

X

Nancy Cornish

CDC

X

Manjula Gama-Ralalage

CDC

X

Riki Merrick

APHL

X

Christina Gallegos

APHL

X

Amy Liu

Inductive Health / APHL

 regrets

Raj Dash

Duke / CAP

X

John Snyder

National Library of Medicine (SNOMED CT)

 

Andrea Pitkus

UW

X

Kathy Walsh

Labcorp

 

Rob Hausam

Hausam Consulting

 

Doug York

APHL

 

Pam Banning

 3M

X

Sandy Jones

CDC

 

Discussion topics

Upcoming OOO

 

Previous Action Items

 

Reporting Biomarkers to Cancer registries

Yes

National Program of Cancer Registries (NPCR) | CDC

One pager

NAACCR IG in V2.5.1 and FHIR IGs support synoptic Cancer protocols, but FHIR IG has not been implemented, V2.5.1 is in production; Neometrics is configured and once they migrate to V5.1 they will start reporting that

Working with Epic and CAP to inform their clients that use Beaker - they can turn on modules that produces the NAACR V5 format

Currently working on hospital onboarding with DataPult

  • How can we help?

    • Any input on use of FHIR

    • NAACCR V5.1 has not been balloted, but is widely implemented - have done crosswalks with LRI IG (and ELR IG) before, but we should redo the crosswalk against LRI base E5 - APHL can create the comparison once we have the LRI base in IGAMT

    • Association of Pathology informatics - get them involved with implementations, maybe create a checklist for the steps needed for implementation

    • Reach out to LIS vendors for Anatomic Pathology Labs

      • Epic (already working with)

      • Oracle

      • Sunquest

      • Vital Access (smaller specialty labs) - already reporting via AIMS

  • Update from CAP Cancer Summit with ONC and NCBI and CMS

    • CAP has synoptic report - SCT codes for all templates for questions and answers (Scott Campbell has modeled all of that )

  • Dataflow:

    • Cancer Checklist is completed in the template by the pathologist

    • Challenges:

      • available to licensed users only

      • currently labs are storing the synoptic data in a textblob, which means we are loosing the discrete coded data

      • could maybe add in checklists for the gross exam of the specimen?

Specimen CMT - review of terms with questions

 

Specimen CMT pilot implementers

 

Specimen CMT - Hosting Options

 

  • 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

    • @riki.merrick to ask Eric if he still has that or how he built it:

    • ANSWER FROM ERIC:

      • if you look in the xml source Conceptmap-example-specimen-type.xml - FHIR v6.0.0-cibuild . you can see how it is mapped. 

      • I am not sure if you mean the table rendering or creating the concept map from a spreadsheet or CSV file.  The FHIR build tool did the table rendering for that mapping, I think I entered the data by hand, or Grahame did it. It would not be hard to create a script to create a concept map from an excel or csv file if needed.  The table needs to be large enough to make it worthwhile though. you could even create formula cells in the spreadsheet to generate the XML or json for each item. and then copy to a text editor and append to the Metadata fields.

      • There will be a call Clinical Architecture on May 3rd to discuss moving specimen CMT to Symedical

      • Manjula will take a look at the concept map

Specimen CMT - education

 

 

Specimen CMT - tracking implementation impact

  • Setting baseline

  • Define metrics

 

 

Specimen CMT - Compare to NHS Medical Terminology testing

 

 

LOINC to SNOMED CT mapping

 

 

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 (i.e., Specimen Condition table, etc.)

Chat:

Recording:

 

https://youtu.be/Co0ardOcKuc

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.