Chair: Paul Scribe:
This call is at 11 AM ET, 10 AM CT, 9 AM MT, 8 AM PT
Find your local number: https://us02web.zoom.us/u/kfWlHSVu3
Attendees - list maintained at the bottom of the meeting notes
Antitrust Statement (HL7 GOM §05.02):
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 Minutes from Discussion|
Remember the Antitrust Statement, see above
3/7/2023 - reviewed May WGM agenda and did room request
Weekly Call Minutes
Review & Approve Interim Meeting 2/28/2023
Accepted by unanimous consent
2023 May Ballot Cycle
2023MAY , Mar 31, 2023 - May 01, 2023
V2 to FHIR:
V2 to FHIR Mapping Review/Updates.
OO: 2-To-FHIR Project - Orders & Observations - Confluence (hl7.org)
3/7/2023. Reviewed the IG.
challenge: what is the correct payer/plan and how do we determine (define). No national source for a plan identifier
On the national level, national standard and there is only 1 instance. can always look it up.
Today there is no unique identifier for the payer/provider. There is no standard.
The system becomes the national directory. Becomes the national assigner of identities.
NAIC, is it unique? NAIC calls it a producer id. Producer Database (PDB) | NIPR
No national payer database
Digital Certificate ID - what happens when a new cert is issued?
Bob putting out block votes tonight, please put on agenda for next week vote.
Da Vinci - Risk-Based Lists
4th Meeting of the month Agenda (regularly), 10-15 minutes for Risk-Based Lists:
Risk Adjustment - Da Vinci - Confluence (hl7.org)
PSS: PSS for Risk Based Contract Member Identification (Updated) - Financial Management - Confluence (hl7.org)
Tickets to review for R5 - QA Updates
Paul will followup on the following:
3/7/2023. No Updates will be made, even through the QA period. Will need to take to R6.
Reviewed outstanding tickets. Will separate otu the Terminology tickets and begin to work. Some tickets just need a response, others will need to be reviewed and moved to the next version.
VOCABULARY: New Code System needed for Surface Codes:
Existing: HL7.TERMINOLOGY\Surface Codes - FHIR v4.0.1
CREATE a new Code System
2. Create a US value set that inclues all except the "V"
3. Create a FDI value set that inclues all except the "F"
4. The existing code system will then be deprecated
5. will there need to be a naming system entry created? Question for Vocab
Create new Value Sets:
existing EXAMPLE VS: HL7.TERMINOLOGY\Surface Codes - FHIR v4.0.1 URL: http://terminology.hl7.org/ValueSet/surface urn:oid:2.16.840.1.113883.4.642.3.546
From ADA Standard No 1084_May2019.pdf: Surface Code (2.16.840.1.113883.4.642.1.316)
From the OID registry:
From the new V2+ web version:
HL7.TERMINOLOGY\bodySiteModifier - FHIR v4.0.1 Official URL: http://terminology.hl7.org/CodeSystem/v2-0495
See FHIR-33202. Another ADA code system (tooth identifying system). Add to THO
Jeff reaching out to Rick for an update.
Paul - we can do a better job for example codesets, especially in places where each country may have their own codeset. (IE Billing codes) where the codesets can vary widely.
We are working on value sets in improving definitions for interoperability. Targetting R6 for that cleanup.
VOCABULARY UPDATES: Coverage.type
Replacing the v3 ActCoverageTypeCode Value Set
***We have SEVERAL R5 tickets around this value set: 13024, 14127, 24916, 20361 (these are linked and in FMWG-Discussion Grouping)
C/N Working List of Definitions - Financial Management - Confluence (hl7.org)
See also JAN WGM work: 2022 01 20 Thurs Q3 - FM WGM Minutes - Financial Management - Confluence (hl7.org)
R5 Work - Clarification ADJ Category vs. ADJ Reason... what is the difference between Category and Reason use
PaymentReconciliation - add a ticket to request documentation addition to describe how to do a refund.
Category = Large Bucket
Reason = further description of why something ended up in the bucket
Category: Patient Responsibility / Reason: Deductible / Amount: 256.00
Category: Patient Responsibility / Reason: Co-Pay Amount / Amount: xx.xx
Category: Patient Responsibility / Reason: Co-Insurance Amount / Amount: xx.xx / Value: .20
Category: Patient Responsibility / Reason: Non-Par Provider
Category: Contractual / Reason: exceeds fee schedule / Amount: 27.00
Category: Contractual / Reason: exceeds plan contractual / Amount / 98.00
Category: Contractual / Reason: POS step down amount / Amount: 11.00
Category: Other / Reason: Tax Not Covered / Amount: 33.45
Category: Other / Reason:
Category: Constractual / Reason: exact dup claim/service
Category: Payer Initiated Reductions / Reason: Performance program proficiency requirements not met / Amount
01-Nov-22: The US has unique requirements. There's a desire to see how we can synchronize international code usage, as much as possible.
There are also situations where different jurisdictions have elements with the same name, but different meaninging.
supportingInfo Slices in existing IGs:
Do we need to add any of these to the base?
01-Nov-22: We might add to base is to guide IG authors in the best practice for adding this data.
CARIN made the design desicion to NOT use any extensions, and so they are using supportingInfo slices. Other IGs are using extensions for the same data elements. We'd like to simplify this for implementers with a standard.
|Patient/Related Person||Patient vs Related Person.pptx|
HL7 Antitrust Policy - Updated 10/2021
HL7 Code of Conduct
HL7 is a community where we can always ask searching questions about technical matters and how our decisions might impact our various communities and stakeholders, but HL7 and its participants are committed to a harassment-free environment for everyone, regardless of level of experience, professional background, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, or nationality. Generally this should mean there is no reason for those subjects to come up with regard to any specific individual.
Co-chairs are asking our WG participants periodically review the HL7 Code of Conduct .
Human Services WG:
3/29/2022: Motion that FM be a co-sponsor. Approved. 16-0-0
Withdrawn (FM was sponsoring):
Meeting ID : 820 3100 5986 Topic : FM Full WG Weekly Conference Call User Email : firstname.lastname@example.org Duration (Minutes) : 113
Start Time : 2023-03-07 10:59:52 AM End Time : 2023-03-07 12:52:08 PM Participants : 16
|Name (Original Name)||User Email||Join Time||Leave Time||Duration|
|Guest||In Waiting Room|
Tom Kakanowski (Smile)
|2023-03-07 10:59:52 AM||2023-03-07 11:27:51 AM||28||Yes||No|
|2023-03-07 11:13:15 AM||2023-03-07 12:52:07 PM||99||No||No|
|2023-03-07 11:52:42 AM||2023-03-07 12:52:08 PM||60||Yes||No|
Jeff Brown (Lantana)
|2023-03-07 11:00:35 AM||2023-03-07 11:56:33 AM||56||Yes||No|
Susan L Langford (BCBST)
|2023-03-07 11:00:44 AM||2023-03-07 12:52:11 PM||112||Yes||No|
|2023-03-07 11:01:54 AM||2023-03-07 11:37:19 AM||36||Yes||No|
Rachel Foerster (RFA Ltd)
|2023-03-07 11:02:03 AM||2023-03-07 11:44:11 AM||43||Yes||No|
Chris Johnson - BCBSAL
|2023-03-07 11:02:24 AM||2023-03-07 12:02:22 PM||60||Yes||No|
MaryKay McDaniel (Financial Management Work Group)
|2023-03-07 11:04:03 AM||2023-03-07 12:52:10 PM||109||No||No|
|2023-03-07 11:04:18 AM||2023-03-07 11:40:23 AM||37||Yes||No|
|2023-03-07 11:08:32 AM||2023-03-07 11:44:32 AM||36||Yes||No|
|2023-03-07 11:16:34 AM||2023-03-07 11:28:13 AM||12||Yes||No|
RachelFoerster (RFA Ltd)
|2023-03-07 11:47:07 AM||2023-03-07 12:52:11 PM||66||Yes||No|
Chris Cioffi (Elevance Health)
|2023-03-07 11:52:11 AM||2023-03-07 12:52:11 PM||60||Yes||No|
|2023-03-07 11:56:15 AM||2023-03-07 12:52:11 PM||56||Yes||No|
|2023-03-07 12:31:17 PM||2023-03-07 12:52:11 PM||21||Yes||No|