Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

...

Upcoming OOO

 

specimen condition and reject reason work

 Yes

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

Reviewed ore terms and made notes there.

Next step is to review Also pulled up this image of a label to reivew attributes: SampleLabelImage.jpgImage Added

Reviewed 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- RM Review: these are a lot of differnt attributes that need to get captured, like source site, collection method, contrifugation times, storage container types etc, not really reject reasons or specimen conditions

#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 ‘Specimen Reject Reason' - RM review: Didn’t find actual concepts - mainly noted that one should record rejection reasons

CALL ADJOURNED

12:01 PM ET

Previous Action Items

 No

Specimen CMT - review of terms with questions

 No

 

Specimen CMT pilot implementers

 No

Specimen CMT - Hosting Options

 No

  • 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

 No

 

Specimen CMT - tracking implementation impact

  • Setting baseline

  • Define metrics

 No

 

Specimen CMT - Compare to NHS Medical Terminology testing

 No

 

LOINC to SNOMED CT mapping

 No

 

Future projects for this call after CMT

 No

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

...