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: April 14, 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:
Marti Velezis (Donrisa / FDA), Ralf Herzog (Roche), JD Nolen (Mercy Children's Hospital), Riki Merrick (Vernetzt / APHL), Kathy Walsh (Labcorp), Alicia Francis, Rob Hausam (Hausam Consulting) Amy McCormick (Epic), Sara Armson (ONC), Sheryl Taylor (NIST)
Co-chair: JD Nolen
Scribe: Riki Merrick
- Quorum (Co-Chair + 2) Met
AGENDA
- Standing Topics
- Special Topics
- Workflow updates
- Other?
Meeting Minutes | Previous Meeting Notes | ||
|---|---|---|---|
Standing Topics | Discussed: |
|
eSignature Update
- Waiting for CMS - 1 June check-in
Race/Ethnicity Topics from OMB and CDC
- Waitning to see what comes back from the feedback - July 1 check in?
New Rule on Race/Ethnicity from OMB
Background:
- Federal Register :: Initial Proposals For Updating OMB's Race and Ethnicity Statistical Standards https://www.federalregister.gov/documents/2023/01/27/2023-01635/initial-proposals-for-updating-ombs-race-and-ethnicity-statistical-standards
CDC Race Category and Ethnicity Group
List of concepts present in CDC Race Category value set which is based upon OMB recommendations and list of concepts present in Ethnicity Group value set which is based upon OMB Race & Ethnicity.
FILE: 2022_RaceAndEthnicityFinal_TablesforPub_Final.xlsx - Race and Ethnicity Download File (Full Code System, relationships, and Hierarchy codes)
FILE: 2022 Race and Ethnicity Code System_Background_Final.pdf - Background and Purpose
ONC New Proposed Rule
- ONC New Proposed Rule HTI-1 on Information blocking and increase USCDI to version 3
- Laboratory RFI (LOI, LRI, FHIR COW/FOE, and could consider commenting on Catalog, LIVD efforts) - See pages 331 - 334
- ONC Intro call info: HTI-1 Proposed Rule Overview Information Session on April 27th, and you can find more information at this link https://www.healthit.gov/topic/laws-regulation-and-policy/health-data-technology-and-interoperability-certification-program
- Comment period ends: June 17, 2023
- Will take this up on a future call to give folks time to read
LIVD
- LIVD calls being now every other Thursday 2 - 3 PM EDT starting May 4, 2023
Update from FHIR Lab Workflow call - not discussed
JIRA Triage | Discussed: |
|
|---|
V2 Lab JIRAs (link)
- V2-25518 – Update the concept in RFR to account for Gender Harmony updates – should change Administrative Sex to Sex Parameter for Clinical Use as that is the concept we are really using to define reference ranges
- So change the name to Sex Parameter for Clinical Use and the value set that is linked to from HL70001 to HL70828 in RFR datatype in Chapter 2C
- And update the examples where needed
- Adopt the changes in all places where RFR is used
- Motion to find persuasive with mod – Ralf Herzog, Riki Merrick
- Further discussion:
- The new table was proposed by Gender Harmony
- The name was changed from Sex for Clinical Use to Sex Parameters for Clinical Use
- Against: 0, abstain: 1, in favor: 8
- Non-compatible – substantive
- Further discussion:
- He linked them to several ballot comments
- Send to GH main group and see what they say – add comment with this vote
- V2-25391 – SPM-1 Set ID
- V2 Management discussed this in more general terms – the best practice is to reset for the context it belongs to, but others do it for the entire message (for error tracking) – so in the base we don’t want to look it down, but be explicit that an implementation guide must state how to treat the set ID and with which number to start.
- Review the V2 Management Notes and bring back with updated text proposal, based on the quality criteria discussion and add as proposed disposition @Riki
- V2-25384 – V2-FHIR mapping of MSH-7
- Is asking to add a comment that this mapping can ONLY happen if timezone-offset is populated in MSH-7, because that is required in bundle.timestamp per the base definition of datetime
- is a comment enough, or do we need a different FHIR datatype?
- If you get a time, but no timezone-offset, then you have 2 options:
- Guess
- Strip off the time
- Neither of this is great for mapping and relative time is still important to retain
- Add to WGM agenda with FHIR-I joint and copy this text into a comment on the ticket
- Is asking to add a comment that this mapping can ONLY happen if timezone-offset is populated in MSH-7, because that is required in bundle.timestamp per the base definition of datetime
- V2-25361 – how to echo back the Placer Order number when having received an unsolicited POCTresult
- We don’t have an application level ACK message structure for ORU messages, so we don’t have a way to send the Placer Order number.
- You could use ORA messages, similar to how we do it for the ORU^R30
- Add to WGM agenda for joint with devices – Tuesday Q4
- V2-25341 – OBX-5 for specimen rejection in LRI
- Is OBX-5 required when OBX-11 = X or N since we added OBX-32?
- On first search of the latest version of LRI cannot find that sentence
- @Riki will do some research if this is still an issue
- Is OBX-5 required when OBX-11 = X or N since we added OBX-32?
FHIR Lab JIRA (link)
Add JIRAs for Next time – related to Lab
From Chat:
Call Adjourned at 1:59 PM ET
Next Meeting: April 21, 2023
Next Time:
<Add any overflow items here>