Versions Compared

Key

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

ANSI Anti-Trust Policy:  Professional Associations, such as HL7, which bring together competing entities are subject to strict scrutiny under applicable antitrust laws. HL7 recognizes that the antitrust laws were enacted to promote fairness in competition and, as such, supports laws against monopoly and restraints of trade and their enforcement. Each individual participating in HL7 meetings and conferences, regardless of venue, is responsible for knowing the contents of and adhering to the HL7 Antitrust Policy as stated in §05.01 of the Governance and Operations Manual (GOM).

Meeting Details

Date:September 29, 2023

Time: 1PM ET

Coordinates:  Join Zoom meeting: https://zoom.us/j/5100467805 | Meeting ID: 510 046 7805 | +1 929-436-2866-US (New York)

Attendees:

Riki Merrick, Rob Hausam, Hans Buitendijk, JD Nolen, Alec Johnson (IMO), Andrea Pitkus, Dan Rutz, Daniel Golson, Jeff Crichlake, Kathy Walsh (Labcorp), Nancy Spector (AMA), Pat Banning (3M Health Info Systems), Peter Kendall, Scott Fradkin, Shawn Cleary, Sheryl Taylor (NIST), Marti Velezis

Chair: Rob Hausam

Scribe:  

  •  Quorum (Co-Chair + 2) Met 

AGENDA

  • Standing Topics 
    • eSignature Update
    • Race/Ethnicity Code changes
    • COW/FOE updates
    • LOI/LRI ACK Choreography questions
  • Copy from prior notes:
    • ObservationDefinition.qualifiedInterval.condition (October 20)
    • DiagnosticReport.status
    • Other JIRAs form Triage Inventory below
    • Other agenda items?

Meeting Resources

JIRA Dashboards:

JIRA Grouping Tags:

Handy Tip
id656082889240371

A grouping tag is a way for the working group to track tickets related to a product or project.  This tag can be added in the JIRA "Grouping" field to add it to the OO Lab project team's filter of open issues.

  • OO-Lab - to indicate when the JIRA Ticket should be reviewed by the OO Lab SMEs, especially when the issue is not assigned to the Resource owner.


Meeting Minutes

Previous Meeting Notes



Standing Topics


eSignature Update

  •  Follow-up date

No updates today

eSignature Update

2023-02-24 OO - LAB/LIVD

From Chat (2023-06-23 LAB)  Andrea Pitkus:  Regarding e-sig, I came across this CLIA doc (see #5):  https://www.cms.gov/files/document/qso-21-10-clia-revised.pdf

New Rule on Race/Ethnicity from OMB/CDC

  •  Follow-up date  

No updates today

New Rule on Race/Ethnicity from OMB/CDC

COW/FOE Update

Link to Minutes:

2023-09-29 OO FHIR COW


Special Topics


LOI/LRI ACK Choreography Question

It seems like the structure of when to send back an AA response with I and or W's?, and AE with E's (or maybe W's) isn't as clearly defined as it is with immunizations.  So I'm trying to find a general rule of thumb that applies to these,

If an error warning severity, is I or W, do we send back an AA response? or do Ws belong with AE's in a nut shell!

MSH|^~\&|MT^1.3.6.1.4.1.24310^ISO|IA.DOH.IDSS^2.16.840.1.114222.4.3.3.19^ISO|BMC^16D0383666^CLIA||20220902092354.0000-0500||ACK^R01^ACK|1c1b750a-c8ca-4602-8c2d-e56199872fef|P|2.5.1|||||USA

MSA|AA|1c1b750a-c8ca-4602-8c2d-e56199872fef

ERR|||101^required field missing|W|||Field lastName is required.

As far as I recall, the original ELR standard didn’t have much to say on when the MSA-1 values should be used. The MSA-1 value set for the harmonized LOI/ELR updated IG which does provide some guidance on when to use each code.

But I think there is a larger (and much messier) question here about original versus enhanced mode acknowledgments. Looking at both the original and harmonized IGs, I think support for at least MSH-15 is required. This means that the exchange is locked into enhanced mode acknowledgments. Technically (anyone correct me if I get this wrong), this essentially means that MSH-15 is AL (perhaps not technically a requirement in the original ELR) and MSH-16 is NE (I don’t know of any system that responds to an ORU message with an application level ACK). Assuming that the ORU you are getting has MSH-15 and/or -16 populated, what you are probably responding with is the accept ACK and not the application ACK which means the relevant codes are CA, CR and CE (not AA, AR and AE). Note that this is little bit different than the immunization space where (despite using MSH-15 and -16) the expectation is that the IIS will return the equivalent of an application level ACK.

Now if you look at Chapter 2 of the v2.5.1 base standard it says:

This tells you what validation should be performed upon accepting a message and how to populate MSA-1. It’s fairly limited in it’s scope although I think that condition (c) might be interpreted pretty broadly to allow syntactic correctness checks (such as a missing required field).

All of this to say, that CE is probably the right code to use when there is an error that isn’t related to the contents of specific MSH fields.

Now, having said all that, in the real world, I don’t know what your trading partners are going to expect. Or if the ACK you construct will ever actually get back to the sending application unless it’s a direct connections with no intermediaries (including interface engines) in between. The diagram below is from the harmonized LRI IG which clearly shows the distinction between accept and application level ACKs. If I had to guess, there will only be accept ACKs used and the ACK you construction will only ever go back one “hop” to indicate acceptance of the message.


  • Will follow up with InM and report back in 2 weeks.


DiagnosticReport.status

Observation.status

  • Substantive changes to Normative – requires community consensus
  • Lab status may not work with current value set hierarchy
  • Options:
    • Add a condition - If Observation.value and .interpretation is changed – b/c it is important - the value of .status should be set
    • Add a new code 

Action item: 

  • Need to write up for Lab specific use – 

Chat History:

Marti Velezis to Everyone (Sep 29, 2023, 1:38 PM)
https://confluence.hl7.org/pages/viewpage.action?pageId=171450118#id-2023091115WGM-StatuscodesinobservationanddiagnosticReport
 
Riki Merrick to Everyone (Sep 29, 2023, 1:39 PM)
FHIR-33042
 
Marti Velezis to Everyone (Sep 29, 2023, 1:39 PM)
https://jira.hl7.org/browse/FHIR-33042
 
Andrea Pitkus to Everyone (Sep 29, 2023, 1:55 PM)
Amended/amendment - Any change in a previously issued anatomic pathology or cytopathology report
intended to correct an inaccuracy, including changes in the diagnosis, narrative text, clinical history, pre- and
post-operative diagnoses, patient identification, or other content.
from CAP general checklist
and Corrected/correction - A change in a previously issued clinical pathology test report intended to correct an
inaccuracy, including changes in test results, patient identification, reference intervals, interpretation, or other
content.
CAP is the largest accreditor of labs.
Note CAP indicates amendment is used in AP/cytopathy, but not clinical lab/clinical pathology

These definitions should be in notes from a few weeks ago when discussed too


JIRA Triage Inventory


V2 Lab JIRAs (link)

The following JIRA Tickets need to be reviewed by the Lab members as carry over from May 2023 WGM:

FHIR Lab JIRA (link)

The following JIRA Tickets need to be reviewed by the Lab members as carry over from May 2023 WGM:


--------Backlog of Topics---------

  • Other JIRAs from Triage Inventory - Not discussed