Date

Aug 1, 2024

Attendees

Present

Name

Organization

X

Nancy Cornish

CDC

X

Manjula Gama-Ralalage

CDC

X

Riki Merrick

APHL

X

Christina Gallegos

APHL

regrets

Amy Liu

Inductive Health / APHL

regrets

Raj Dash

Duke / CAP

X

John Snyder

National Library of Medicine (SNOMED CT)

X

Andrea Pitkus

UW

X

Kathy Walsh

Labcorp


Rob Hausam

Hausam Consulting

X

Doug York

APHL

 

Pam Banning

 3M

 

Sandy Jones

CDC

Discussion topics

Upcoming OOO

 Yes

TINKAR IG


  • TINKAR is developed by Deloitte under FDA (BAA)

  • John and Andrea have been attending the meetings (thank goodness!)

    • needed to provide clarity about the difference between

      • LIVD

      • Lab test compendium

  • they are working on setting up a connectathon track

  • treating PLT codes as LOINC extension, which is what APHL has been doing

    • reasons of making PLT codes:

      • very limited use across programs- not likely to make it intou other data streams (EPI specific questions)

      • order codes for panels - will submit all of these back to Regenstrief, now that the policy around this may change

      • for every submission until we have LOINC

    • we have been talking with Regenstrief about this

    • need to make sure the TINKAR folks do not sell PLT as LOINC extension (as it does not completely follow all the editorial guidelines)

    • viewer: https://aphl.clinicalarchitecture.com/SymedicalAPHLViewpoint/#/search

    • also Clinical Architecture can distribute PLT codes

    • PLT is in HL70396 table and also should have an OID (I will doubleckeck on that - but would need to figure out the URL for use in FHIR)

    • Consider talking with Regenstrief about including PLT mappings (the deprecated ones - or maybe all - in the LOINC SNOMED extension?

      • alternate concept identifiers may be more explicit than the main code? - it is disributed differently than a maping RefSet

    • On HL7 calls AMA has requested use of PLA codes instead of LOINC to identify orders

    • Related to LIDR work - most likely - need to compare to the LIDR Whitepaper requirements

    • CDC is working with FDA and manufacturers via their CLIAC biosafety group

      • to include industrial hygenist in development of new instruments to ensure is that these are safe to operate by the lab personnel

Previous Action Items


  • Nancy Follow up:

  • Riki’s Follow up - none of these got done yet Emoji :disappointed:

    • liquid-based cytology specimen vial = https://us-request.ihtsdotools.org/#/requests/preview/354843?fromList=truehttps://request.ihtsdotools.org/#/requests/edit/786429

    • submit a code for formalin10

    • work with John

      • new term for pacemaker insertion site sample

        • in SCT there are only swabs for insertion sites (line, drain, chest tube, vascular catheter) - this should be fixed

        • we should model it after 435971000124108 | Body fluid specimen from peritoneal dialysis insertion site (specimen) and require method, which should be aspirate

      • 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

      • IDSA has a guidelines for wound cultures (deep and superficial - related to surgical wounds) - link sent to Amy

Specimen CMT - review of terms with questions

 

  • Amy can’t be on

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

    • 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 August 16th 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:

Andrea Pitkus 12:23 PM
https://confluence.hl7.org/display/VOC/TINKAR+Milestones+and+Deadlines

Andrea Pitkus to Everyone 12:34 PM
https://confluence.hl7.org/display/VOC/May+2024+Connectathon+Storyboard
Here are the call notes: https://confluence.hl7.org/display/VOC/Standardized+Terminology+Knowledgebase+Project+Calls+and+Meetings
If folks want to join future calls.
https://confluence.hl7.org/display/FHIR/2024+-+09+Terminology+Change+Set+Exchange
The Sept Connectathon testing scenario

Andrea Pitkus 12:39 PM
Scenario 2: Change Set of new terminology concepts to support LIVD/LIDR

Recording:


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.

Create from Template