Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current Restore this Version View Page History

« Previous Version 2 Next »

Date

Attendees

Present

Name

Organization

Nancy Cornish

CDC

Manjula Gama-Ralalage

CDC

regrets

Riki Merrick

APHL

Christina Gallegos

APHL

Amy Liu

Inductive Health / APHL

Raj Dash

Duke / CAP

John Snyder

National Library of Medicine (SNOMED CT)

Andrea Pitkus

UW

Kathy Walsh

Labcorp

Rob Hausam

Hausam Consulting

 

Doug York

APHL

 

Pam Banning

 3M

 

Sandy Jones

CDC

Discussion topics

Upcoming OOO

 

Speicmen CMT presentation for SHIELD

Presentation on September 10, 2024 went welll - here is the link to the recording: 2024-09-10 SHIELD Topic#2 Call Meeting Notes

HL7 FHIR Profile: Skin and Wound Assessment, Release 1 (For Comment)

Background in the Proposal:  Skin and Wound Assessment - FHIR - Confluence (hl7.org)  There was a vendor that created a FHIR App that apparently is used.

While not specific about pathology there was much discussion on how to document "landmarks" on the body like moles, tattoos, etc in relation to wound location.  Conceivably, if a wound culture was performed, the specimen source site info would overlap with wound details.  Pathology specimens would have similar needs.   There are various refsets, value sets and SCT extensions listed.  It was mentioned it should align with laboratory and pathology specimen information, but I haven't reviewed the codes/terms.  Not sure if anything they developed would fill any CMT gaps or already contained therein?   Mitre did a lot of the work on this too.  

Discussion:

specimen condition and reject reason work

Here is the confluence page where OO is tracking this project: https://confluence.hl7.org/display/OO/Specimen+Condition+and+Specimen+Reject+Reason+Vocabulary

Next step is to review against the concepts in

#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) maybe consider using this (if so, HL7 would need joint copyright or something) and also

#2 international standard for biobanking: the ISO 20387:2018 - is anyone member and has access?

  • Annex A lists some requirements regarding documented information during sample acquisition (see A.2 Acquisition)

  • Annex B gives a list of examples for the respective requirements mentioned in Annex A (see B.2 Acquisition). Based on the acceptance criteria 'reject reasons' can be deduced.

#3 ISBER BP5 for information regarding 'Specimen Reject Reason'

Previous Action Items

 

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.

      • 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.)

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.