Participants for today’s call:
Membership:
Name | Organization | Role |
---|---|---|
Raj Dash | College of American Pathologists (CAP) | Chair Steering Committee member |
Scott Campbell | UNMC | Steering Committee member |
Dan Rutz | Epic | Steering Committee member |
Muktha Natrajan | CDC |
|
Sandy Jones (Secondary) | CDC Cancer Surveillance |
|
Anne Peruski (Secondary) | CDC |
|
Andrea Pitkus | University of Wisconsin-Madison | Steering Committee member |
Xavier Gansel | bioMérieux | Steering Committee member |
Stan Huff | Graphite Health | Steering Committee member |
John Snyder | NLM | Steering Committee member |
Rob Hausam | Hausam Consulting |
|
Marjorie Rollins | Regenstrief | Steering Committee member |
Amy McCormick (secondary) | Epic |
|
Nanguneri Nirmala | Tufts Medical Center | Steering Committee member |
Mehdi Nassiri | Indiana University/Indiana University Health/Association for Molecular Pathology | Steering Committee member |
Eza Hafeza | Regenstrief | Steering Committee member |
Jim Case | Snomed International | Steering Committee member |
Kevin Schap | CAP |
|
++++
Discussion topics
Item | Notes |
|
---|
Item | Notes |
---|
Item | Notes |
---|---|
Review: Identify tangible activities for this working group |
|
Use case review | D-Dimer (qualitative) AST (quantitative) |
LRI review | Observation Result Status Codes Interpretation - Final, prelim, etc OBX-11, significant overlap with Result Status, OBR-25. These are transactional and more focused on implemented configuration and not required for semantic interoperability. No data standard recommended beyond the HL7 valueset. Result Status - Final, prelim, etc., significant overlap with Observation Result Status Codes. These are transactional and more focused on implemented configuration and not required for semantic interoperability. No data standard recommended beyond the HL7 valueset. Value Type - Data type of the result. Recommend continue to use the HL7 valueset (table 0125) Examples: Encapsulated Data Formatted Text (Display) Multiplexed array Numeric array Numeric Numeric range Reference Pointer Structured Numeric String Data Time Text Data (Display) Value range Extended Address Specimen Type Specimen Reject Reason Specimen Condition Relevant Clinical Information Device Type LOINC SNOMED CT UCUM |
Next steps |
|
Cloud recording: https://duke.zoom.us/rec/share/9ZJc-QAGiwPgo_R_in1WcmRM8oah8xWqg6D8KKIlGQ9BR56z-azlKygBOTTzV5I.nA8hcNRDiegpr2Un?startTime=1710782966000
From Chat:
I agree with both Jim and Xavier – we should recommend what we feel is correct and then make adjustments:
Personally I like interpretations always in OBX-8 to have a consistent place where to find them – OBX-8 can repeat, in case you need more than one aspect of interpretation – for example detected and abnormal.
HL70078 values are drawn from the observationInterpretation code system – it is harmonized across all HL7 product families (one of the only ones!), so any changes to use SCT instead (rather than in addition) should be done across all HL7 products.
FYI – there is a vocabulary group in Europe working on these issues, too – we should take a look at what they are doing: https://confluence.hl7.org/display/HEU/2024-03-08+Lab+-+Semantic+WG and provide input there, so we don’t have a US way and a European way!
Riki