Page tree
Skip to end of metadata
Go to start of metadata

Chair:  @Paul Knapp   Scribe: @MaryKayMcDaniel

Call Logistics: 

This call is at 11 AM ET, 10 AM CT, 9 AM MT, 8 AM PT
Join using https://zoom.us/j/3965708082
Meeting ID: 396 570 8082
+12532158782,,3965708082# US
+13017158592,,3965708082# US
Dial by your location
        +1 253 215 8782 US
        +1 301 715 8592 US
        +1 312 626 6799 US (Chicago)
        +1 346 248 7799 US (Houston)
        +1 669 900 6833 US (San Jose)
        +1 929 436 2866 US (New York)
Meeting ID: 396 570 8082

Attendees - list maintained at the bottom of the meeting notes

PSS approval flow:  Sponsoring WG, Co-sponsors, US Realm, Management Groups, Steering Division, TSC

ID - Local to the resource creator, IDENTIFIER - an identifier everyone recognizes. Independent of where the information is created or by whom


  Agenda Outline

Agenda Item

Meeting Minutes from Discussion


"Agenda in Brief"

details follow

Review agenda - 

Review/Approve 6/23 Meeting minutes

Announcements

New Co-chair Announcement

Follow-ups

FHIR Tracker Items, update

IG Updates

RTPBC - Vote?

Vocabulary Updates



Change: 

No Co-chair announcement, waiting for listserv list from HQ

Persona Document will not be discussed to day, changes being made to document. Will bring back when changes are completed.

Added Gender Identity Survey from Gender Harmony Project




Weekly Call Minutes

Review & Approve 6/23 meeting notes

Accepted by unanimous concent

ANNOUNCEMENTS
  • Calls - listed to the right
  • Co-chair Announcement





Additional calls this week?

Set up all calls as they were:

  1. Accounts, Payments and Statements at 4pm ET today. Standing call
  2. CARIN - Consumer Directed (BB) Ballot Reconciliation 2:30ET Mondays
  3. Gender Harmony - Vocabulary WG EOW Monday 4pmET
  4. Sm Group Concepts/Nomenclature - Monday. Reach out to Linda Michaelsen

**See HL7 Conference Call Center for Da Vinci Calls


Gender Identity Survey, Gender Harmony Project:

The Gender Harmony Project


Follow-ups

1) Bob and Paul have a to-do:  R4 only notation to PSS, since REG specifies R4.

3/24/2020 - In Process

4/7/2020 - emails and documentation sent out to all balloters

5/5/2020 - Bob will update the PSS for TSC Review

5/12/2020 - Bob an d FM Co-chairs will update CRD PSS (it was the old process, need to update in Project Insight)

5/19/2020 - Bob. CRD, no pss changes/PDex ready to go, Paul will sent to TSC for eVote. CDS/CIC-DTR/HREx to Sponsors. Patient Care - CDex (not ready to ballot, so we have time). 

5/26/2019 - CRD/PDex to TSC. DTR is going to CIC. CDex in process.

FM approved date: 4/21/2020, CRD/PDex. Bob Dieterle/Laurie Burckhardt. 23-0-0

6/9/2020. Motion to accept removing support for STU2 and STU3 from HREX PSS and Implementation guide:

Bob Dieterle/Mark Schrimshire.  16-0-0

6/16/2020. Bob to PIE, CIC and Patient Care. 

6/30/2020. Bob working with Patient Care to get signoff

2) Schedule a joint with PA over the summer to touch base. Wednesday at 3pm.

3) Gender Harmony PSS 1387. FM CoSponsor. Who is monitoring? On Co-chair call agenda for 7/1/2020.

4) 4/27/2020 TSC Agenda Item. 3/3/2020:  In Process. ***follow-up:  setting up CARIN as a separate group (as DV) - webmaster@hl7.com. include Frank and Amol on email. Add this to the Accelerator start-up todos list. Ability to add calls. MK/Paul need to bring up at TSC. 

6/30/2020. In Process. Once Mark is a member his access rights will be updated giving him the ability to add/change/edit CARIN calls.

5) Extensions across profiles: Modeling and Methodology (MnM)

5/5/2020: FHIR-I took a stab at place to put extensions across profiles. Work in process.

5/12/2020: proposal fell apart at MnM - next call today, 5pmET

6/2/2020: Next MnM call 6/9/2020

6/30/2020: Next MnM call 7/8/2020

6)  5/12/2020:  Need to take 'CARIN BB' or 'CARIN Blue Button' to TSC. Can we use the 'Blue Button or BB' as key lookups, etc?

5/19. Paul/MK need to take to TSC  meeting on 6/1 for confirmation: Can Tag under which artefacts are cataloged, then there are the short names contain the "BB"

6/9/2020 TSC Feedback.

7) Common Profiles/Common Extensions

  • TO DO:  start building out a list of FM specific profiles registry until one is created for all HL7 Profiles (easy search and find)
  • For DV the common profiles are being put into HRex. Will that need to change in the future?
  • There are standard profiles and extensions that are currently in the FHIR specification. BUT, not all IG level profiles and extensions are there. Creating a common instance should make things easier. Create a common repository.

8)  FM to do:  Need to put together a list of .identifiers that are used in claims and EOBs to include how to match the 2

FYI: 

  • FM Steps to publication:
    • Ballot recon list,
    • Guide updated,
    • Request withdraw of negatives,
    • Highlevel review with WG,
    • Week for WG to review,
    • then WG for review of issues or final approval for publication


6/9/2020: Co-chair to do:  

Where are we at with vocabulary? Does everything have to go through UTG?



 5/12/2020:  Need to take 'CARIN BB' or 'CARIN Blue Button' to TSC. Can we use the 'Blue Button or BB' as key lookups, etc?

5/19. Paul/MK need to take to TSC  meeting on 6/1 for confirmation: Can Tag under which artefacts are cataloged, then there are the short names contain the "BB"

6/9/2020 TSC Feedback. Please forward written permission from CMS. HL7 HQ will follow-up with CMS for the same approval. 

6/16/2020-6/30/3030 Awaiting feedback from CARIN. Lorraine Doo will help facilitatel.





FHIR Tracker Items. 
  • How do we get Coverage records for someone? how do we get member's data when you are not the member?
    • It is a payer's process that will drive the ability. (plan based authorization)
    • Is there something that will need to be done with coverage? Token gives the requestor the right to see the information. 
    • Must be able to issue tokens so that an individual/warm body can be revoked. The token is revoked by the insurance company.
    • The 3rd party app may go and pull your information for you. It is the 3rd party app that holds the token to get the information, but the update token is the 3rd party app.
    • An app by itself that is registered with the payer. The app gets data on behalf of the person. That app gets registered. When the app comes into get data it is coming in on behalf of an individual. It must say I'm APP #1 and getting information for Member A. If member a authorized the app to get it's data, the app can get the data. The app holds the tokens and presents to the payer and asks if the app can still get the information - the refresh token is used after a period of time. The token is granted a set of scope. The token by itself doesn't give unlimited access to the data. The payer can refuse to answer the question. The control is really at the data giver (payer) side. The token sets the scope to the data. Beyond that, the payer can add additional limits to the scope. 
    • SMART authorization sequence - http://hl7.org/fhir/smart-app-launch/#smart-authorization-sequence


Issues:

Issue

Specification

Summary

Created

Last changed

FHIR-24398

[FHIR-us-davinci-pas]

In order to clarify, the IG should include verbiage that requires the payer to specify what information was missing that led to the rejection - PAS #189 ***more information is needed, how would this be done?

2020 03 09:  FM Chairs. Schedule meeting with Bob to discuss offline. This AND the ppt from WGM need to be reviewed.

2020 03 17:  If the PA has been rejected and Payer needs more information (after add'l information has been sent) - how does Payer send the information?

Bob:  There is nothing in the guide to do this. There is no attachment rule. The real question, if payer needs more additional information how do they convey this to the provider? 

2 flows to review: 1) using CRD/DTR     2) Not using CRD/DTR - 

Response:  "We will provide additional guidance on how the provider MAY submit additional information. This is an exception process and not the focus of the IG."

Bob will update the diagrams in the IG.

3/24/2020. Bob has updated the resolution will update the diagram.

Check 4/14. May need to vote

4/21/20. Bob. Will be a bit of text and a picture displaying the different ways to submit additional documentation (upload, transaction, fax) Payer will need to indicate which methods they will allow. There will be a sentence added to indicate the 'preferred' way if their technology allows. 

Motion to approve. Bob D./Laurie B. Discussion, would prefer to see the changes before voting.

2019-20-15

2020-51-06

FHIR-24174

[FHIR-us-davinci-pas]

Sadly, this seems to imply that Claim items should be resources. - PAS #23

Keith Boone submitted:  Based on the fact that there is a line item number.

2020 03 17  Discussion:  FHIR doesn't generally contain a line item concept. 

Response:  This conversation was addressed at a WGM. The community consensus was that breaking the item into a separate resource, but there was a recognition that there may need to be a separate identifier for that line. 

4.0 has item.sequence. in the US we actually use a real identifier that has been added as an extension. Need to consider item.detail, item.subdetail also. Will compose an email and send out to listserv(s) - FM/PIE/Pharmacy.

Resolution:  Paul will check with other affiliates to see if this would be helpful. If not, it will be an extension. If so, there will be a standard extension for R4. Will reach out to other realms to determine if used, if not it will remain an extension. 

2019-15-15

2020-16-07


6/30/2020 No updates.







6/9/2020

FHIR-24398:  

Bob reviewed the following flow. Thisis a complete functional picture.

Feedback: 

The red lines are a bit confusing

Can we remove the Portal/fax boxes? Portal/fax comes out of step 4 or 7

will make the followng changes (see bottom right)

V2 Tracker Items.

tracker #25203 to add use cases. see:  V2 Identifiers

https://gforge.hl7.org/gf/project/v2-ballot-pkg/tracker/?action=TrackerItemEdit&tracker_item_id=25203&start=50

tracker #25193 to update the IN2-25, IN2-26, and IN2-27 field definitions.

https://gforge.hl7.org/gf/project/v2-ballot-pkg/tracker/?action=TrackerItemEdit&tracker_item_id=25193&start=50

Email thread is located at: V2 Questions - tracker #25203/#25193

Tracker:  15632: V2 GForge Ticket 15632 - PRT1:14 is broken

2020 06 04 Updates:

We have identified the changes needed and sent an email to V2-MGT to get next steps. New publication process for both V2 and Vocabulary. Yay! 2 new processes to navigate to make this change.

Positive, only new V2 update process to navigate once complete

Move to new version

Opportunity for FM to update descriptions on resources and the descriptions of the code sets. Update the actual code sets, can't change the binding strength. 

Need to prioritize:

1) the resources that need to be reviewed

2) the code systems that need to be reviewed and updated (EXAMPLE). are they really an example or can they be 'updated' to the correct /updated value set

3) map resources to RIM (reference implementation model)

4) vocabulary needs (see separate row below)




***CMS Regulation below refers to:

The Interoperability and Patient Access final rule (CMS-9115-F):  https://www.cms.gov/Regulations-and-Guidance/Guidance/Interoperability/index


Education:

Confusion among the implementers between CARIN BB and PDex (immediate 2 that seem to be causing confusion) & JIRA Tickets. 

There is a graphic https://confluence.hl7.org/download/attachments/30638450/PDex%20vs%20CARIN%20BB%20v5.4.pptx?api=v2 

 and word document: https://confluence.hl7.org/download/attachments/30638450/CARIN%20BB%20and%20PDEX%20V2.4.docx?api=v2

(words to explain the graphic) which have been created as a response to 2 JIRA tickets:

FHIR-26699 :  There is clear overlap between this implementation guide and the DaVinci payer data exchange and clinical data exchange implementation guides

FHIR-26733 :  Clinical FHIR artifacts should be mentioned in this guide

As FM we need to review (and update if needed) and figure out where all to POST, INCLUDE, PROMOTE these for industry understanding.

CARIN BB Payer to 3rd party app for person

DV PDex Payer to CMS person API (3rd party app) or Payer-to-Payer for representing 'clinical' concepts, DX/ICD-PCS, HCPCS, represented in resources that represent concepts represented in Procedures, Observations, Medications, Condition

at the time PDex was created the providers are interested in dates, who did it, etc. 

Questions to FM: how to include the same information in both the IGs.


CARIN Update:

Consumer Directed Payer Data Exchange (AKA BB)

7 minutes 

3/24/2020: This guide supports CMS Regulation***. Reg date is 1/1/2021

http://hl7.org/fhir/us/carin-bb/2020Feb/index.html

  • CARIN BB PSS got ARB and TSC approval OCT 2019
  • FMG suggested new name 11/X/2019.
    • Consumer Directed Payer Data Exchange
  • CARIN NIB review, IG review  CARIN Blue Button IG Proposal. Been through a Connectathon based on draft content., FM reviewed and approved NIB 11/5/2019

 PSS for CARIN Blue Button

CARIN BB confluence ballot reconciliation page:  Ballot Reconciliation Calls for the CARIN IG for Blue Button®


6/30/2020:  Personas Review:  new document to follow

https://confluence.hl7.org/download/attachments/30638450/Personas%20and%20Patient%20Access%20Stories%202020%200623%20PIE%20-%20FHIR-26798.docx?api=v2



6/30/2020:  Informational:  

search parameter document represents the agreement of the CARIN Workgroup and FM co-chairs regarding the search parameters, payer requirements to provide data for reference resources (i.e., is it to be provided as of the date or service or as of the current date), and how payers will return data bundles in response to requests. This document can also be found on the CARIN Confluence page.

https://confluence.hl7.org/download/attachments/30638450/CARIN%20BB%20RESTful%20API%20Combined%20-%20FHIR-26702%20-%20FHIR-26693%200617%202020.docx?api=v2


*****Zulip Chat:  defining a custom operation that does the job ($assemble-eob or whatever)

Steps for STU-1 publication:

1) load ballot comments into JIRA
2) identify technical block votes
3) substantive, propose dispositions, bring to the Monday CARIN call, block vote on FM call
4) update the guide
5) send ballot worksheet and updated guide to all ballot voters (and give some period of time to review) and withdraw negative comments

ALL comments must be resolved. Do not need to vote again. Becomes an STU-1.


2020 06 30:

1) review block vote #2

2) see item to the left - zulip chat suggestion for search

JIRA Ticket 26693.

Learning conversation, agreement in approach. Document will be updated. Lisa asked that the implementers be allowed to review. Bring back next week 7/7.

3) Personas

CARIN Update:

RTPBC IG

7 minutes 

Real-Time Pharmacy Benefit Check

3/24/2020: This guide does not support the CMS Regulation***.

Pooja Babbrah  (Pooja.Babbrah@pocp.com)

Frank McKinney will develop the IG.  

http://hl7.org/fhir/us/carin-rtpbc/2020FEB/index.html

Zulip stream (https://chat.fhir.org/#narrow/stream/208660-CARIN-Benefit.20Check.20IG)

6/8/2020:  

An updated version of the CARIN Real-time Pharmacy Benefit Check IG with all ballot resolutions applied is available for review at:

http://build.fhir.org/ig/HL7/carin-rtpbc/index.html

6/23/2020. Pharmacy approved RTPBC to move to publish. 

NDC-11 can handle via words in the IGs in the interim. 10 digit and 11 digit are the same concept, represented differently. Can't create a value set that only includes 

WG needs to review and will approve next week (6/30/2020)


6/30/2020:  Motion to approve publication of this guide. Frank McKinney/Mark Scrimshire. Unaminous. 

Frank will share the NCD-11 verbiage.

 DV Update

20 minutes 






The Da Vinci IG Dashboard:  Da Vinci Implementation Guide Dashboard


Da Vinci Update

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Da Vinci IGs: 

Coverage Requirements Discovery (CRD)http://hl7.org/fhir/us/davinci-crd/2019May/index.html

3/24/2020: Implementation of this guide is not required by the CMS Regulation***.

Documents, Templates and Rules - DTRhttp://hl7.org/fhir/us/davinci-dtr/2019May/index.html

DTR - STU-1. Re-ballot (Ballot for Comment previously - comments resolved). SEP Ballot

3/24/2020: Implementation of this guide is not required by the CMS Regulation***.

HRex (Common across IGs – i.e., post/put without all use case details ) - http://build.fhir.org/ig/HL7/davinci-ehrx/index.html Approved Monday 6/17/2019

3/24/2020:  Used by guides that support the final CMS rule. By itself it does not support the final rule***. 

Notifications:  http://build.fhir.org/ig/HL7/davinci-alerts/branches/master/index.html - Feb 2020 Ballot

3/24/2020: This guide supports CMS Regulation***. Reg date is 6 months from publication

Payer Coverage Decision Exchange: Portability of current treatment, STU-1, SEP 2019 Ballot

Payer Coverage Decision Exchange: http://build.fhir.org/ig/HL7/davinci-pcde/ 

3/24/2020: This guide supports CMS Regulation***. Plan to Plan 1/1/2022

Provider/Payer Clinical Data Exchange (CDex) (infrastructure)- http://build.fhir.org/ig/HL7/davinci-ecdx/index.html Approved Monday 6/17/2019

3/24/2020: Implementation of this guide is not required by the CMS Regulation***.

Payer/Provider Data Exchange (PDex) - http://build.fhir.org/ig/HL7/davinci-epdx/ :  Approved by FM WG 6/11/2019

PDex IG: http://build.fhir.org/ig/HL7/davinci-epdx/

3/24/2020: This guide supports CMS Regulation***. Plan to Plan 1/1/2022

3/24/2020: This guide supports CMS Regulation***. Plan to Member 1/1/2021

PDex Plan Directory IG: http://hl7.org/fhir/us/davinci-pdex-plan-net/2020FEB/index.html  : Early FEB 2020

3/24/2020: This guide supports CMS Regulation***. Plan to Member 1/1/2021

PDex Plan Formulary - http://build.fhir.org/ig/HL7/davinci-pdex-formulary/ - approved by pharmacy 6/11/2019

3/24/2020: This guide supports CMS Regulation***. Plan to Member 1/1/2021

PAS, STU-1, JAN Ballot

Prior Authorization Support: http://build.fhir.org/ig/HL7/davinci-pas/index.html

3/24/2020: Implementation of this guide is not required by the CMS Regulation***.

Risk-Based Contracts Member Attribution List project, FHIR IG Review

3/24/2020: Implementation of this guide is not required by the CMS Regulation***.

http://hl7.org/fhir/us/davinci-atr/2020FEB/index.html

-->updated PSS for Value Based Care Member Identification (Updated) that includes the secondary use of Bulk Data Exchange along with the member list and the data definitions in other Da Vinci IGs (e.g. PDex) to define the scope of data that should be exchanged.

https://confluence.hl7.org/pages/viewpage.action?pageId=58657072

preparing a FHIR IG and we are working towards balloting for the upcoming Feb 2020 cycle. link to the IG proposal is here:

https://wiki.hl7.org/Da_Vinci_Risk_Based_Contract_Member_Identification_FHIR_IG_Proposal#Risk_Based_Contract_Member_Identification 

NIB review and approval:  11/19/2019.



5/5/2020.Bob D. Update: Single biggest issue is to land on exchange methods (path vs. communication request - content and exchange method very intertwined). What exactly do we use for consistency and what will the vendors be willing to support. Viet and Bob are working on this and it will be implemented across the guides. Payer coverage decision exchange and PDex. how to you ask someone to do something that requires manual intervention. still in process.


Paul: One more overall issue. When you have complex information that you are returning, something that requires more than one resource. Two ways to deliver that information. you can either deliver all of it in a package (bundle). OR you can deliver it granularity - one resource at a time. you can ask for a provider, then next resource. If you choose the latter approach, you won't get the same answers out of the 2 approaches. Option 1 you can get all the information contextually. If you choose the 2nd you will get the current version, may not be the version at the time.

Bob:  IGs are attempting to give the receiver enough information to make a decision. there may be a 2nd query to get the rest of the information.

Paul: must give people enough information so they can come back and get the right resource instance. 

Bob: Yes. Depends on the IG. 

Paul: the instance version in context is not generally understood. 

Lisa: and there is no clear indication or committment on the part of the vendors. 

Bob:  how do we take into account the different way this will be implemented. Endpoint only vs. instances.

>>>Need to continue this discussion next week (5/12)

>>>didn't discuss 5/12 - take to 5/19. 



Vocabulary

All about vocab

AHA, AMA, CMS, NCPDP, X12

  • Register Code systems and value sets for use across implementation guides.
    • How do we do this across all IGs using the same code systems and value sets?
    • Register them in the UTG

1) RTPBC & CARIN BB

Value Sets for Coverage Levels and Payment Types

2) What IGs are impacted by:

5 Code Systems (NUCC, CARC, NUBC)

3) Large amount of work to do.

1) validating existing OIDs/code systems/ value sets in play across HL7 versions (research that is painful and time consuming)

2) updated new code system/value sets and then going back to depricate those that are questionable

4) R4.1:  Vocab in conjunction with RTPBC: Adjudication value set.  see:  https://confluence.hl7.org/download/attachments/30638450/CARIN-rtpbc-carinbb-HL7-CARC%20patient%20pay%20type%20comparison%20v3.4.xlsx?api=v2

  • FM will add this to the "Adjudication" vocabulary 
  • Amol question: are we tracking identifer type. CN for payer claim number. DV has a UMB. Are we keeping track of these additional value set codes? 

UTG:  create naming system and value sets and send to UTG (Ted). 


6/8/2020 Update:

AHA-NUBC, Pattern created. Given to Developers to use. Waiting to see what it looks like in an IG/UTG and will reach out to AHA-NUBC contact for approval.

AMA - CPT:  should be ok to go. see: http://hl7.org/fhir/cpt.html. Make sure you read all the way to the bottom!!! need the implicit value set URL http://hl7.org/fhir/ValueSet/cpt-all is a value set that includes all CPT codes. 

CMS - DRG, POS, RARC. in-flight. POS pretty close. 

NCPDP: DAW, Prescription Orgin Code, Plan reported brand - generic code.  DO we have V2/V3 Code System/Value Codes for these already? IF NOT: IF the pattern holds up, will reach out to NCPDP via HL7 Liaisons (Scott Roberts and Jean Duteau) to NCPDP Liaison (Margaret Weiker) to confirm. Research needed. 

X12.org - Pattern created. Developers using. Waiting to see what it looks like in IG/UTG and will reach out to X12.org for approval.


6/16/2020. brief overview to the WG on progress to day.

Conversation around multiple Code Systems with different IP licenseure in one element. Pat will bring an actual example to the group and we will walk through it. 

Account, Payment and Statement 

Work Effort Update

5 minute 

Invoice/Statement/Payment Work WG introduction to effort

Look for emails/doodle polls for meeting times and dates.

PIE WG will be included. 

Calls on Tuesday's. See FM Conference Call for details.

PSS awaiting ASD approval.

6/30:  Co-chair to do:  Has this been approved by TSC? Need to check PSS Process.

Insurance Concepts. 

Create definitions

Health Care Insurance Concepts/Nomenclature

Linda Michaelson is willing to drive:  please send her an email if you are interested:  linda.michaelsen@optum.com

Old version:  https://confluence.hl7.org/download/attachments/30638450/PlanType_InsType_LOB%202018%2009%2004.xlsx?api=v2

FHIR 4.0 FM page link:  http://hl7.org/fhir/financial-module.html#fingloss

Gathering Concepts:  Example of concept:  "The individual who owns the policy", "The individual who is being treated"

Documentation can be found at:

Concept/Nomenclature Definitions


Work continues.

Anesthesia Billing Support Update

5 minutes


Update: 

Meeting once a month. Next meeting:  

***Documentation here:  Anaesthesia Billing Support (under documentation)

***PSS:  PSS for Anaesthesia Billing Support

Preparing to create the V2 IG using the NIST tooling.

4/17/2020 - Pause in effort

Payer Identifiers

Identifiers that are used to identify a Payer


2020 03 03: Kathleen, research has been done. Needs V2 CR.  V2 - Kathleen/Donna work, any updates or discussion needed? KC - RE: Clarify IN1-36 & 49, IN2-61 Member ID.  Analysis done, guidance drafted. Just need to create V2 CR to add guidance and have WG approve to submit.


See:  V2 Identifiers

Needs to be a CR for V2



There are identifiers that are issued by Payers. Things like member id, group id, etc. Those are already covered within the Coverage Resource. (Member id - Coverage.identifier, Subscriber ID in the subscriber ID). Other identifiers go in class. 

Two conversations going on:  how do we identify a payer. There is not a consistent way to identify a payer in the US. There is no 'authority' that creates an "NPI" for a payer.



BACKLOG

Backlog rows have been moved to:

Parking Lot - Things we need to address


Backlog:

DRG

Need to add DRG at the root, currently at line in procedures. Analysis work to be done, then JIRA Ticket needed.


Backlog:

FM DAM

US DAM for FM

Co-chairs agree

Base it on v3 FICR DMIM

see:  http://www.hl7.org/documentcenter/private/standards/v3/edition_web/domains/uvcr/editable/images/FICR_DM000000UV.png


Open Discussion

CARIN Block Vote #2.

Schedule separate call to review these tickets.

There will be a new zoom number.

Thursday 1-3.

Paul will chair, Jeff will take notes.


Key

Summary

Reporter

Grouping

FHIR-24846

Cant see purpose of CarinBBPatient profile

Document pic needs to be updated in Ticket. It is 'old'. Whose Patient Account number? Provider's. This is a substantive change.


Amol question: are we tracking identifer type. CN for payer claim number. DV has a UMB. Are we keeping track of these additional value set codes? FM, we are not. Amol/Pat will get us those updates.

Virginia Lorenzi

Block-Vote-2 Pre-Ballot Profiles USCore

FHIR-25596

Binding on Diagnosis example should be to ICD10-CM instead of ICD-10

Linda Michaels

Block-Vote-2 Profiles Terminology

FHIR-25601

Clarify requirements for Consumer App Actors

Craig Newman

Block-Vote-2 MustSupport

Narrative

FHIR-25602

Clarify action when required data is not available

Craig Newman

Block-Vote-2 MustSupport

Narrative

FHIR-25604

Cardinality of RelatedPerson.subscriberID

Craig Newman

Block-Vote-2

Profiles

FHIR-25605

EOB.insurance.primaryinsurance -- Fixed values of .focal need clarification

Craig Newman

Block-Vote-2

Narrative

Profiles

FHIR-25609

Notes to Balloters - I find this IG title confusing. When I first saw it, I thought it related to consumers directing payers to exchange data among themselves.

Thomson Kuhn

Block-Vote-2

Narrative


What does it mean when min=0 and no 'must support'

Eric Haas

Block-Vote-2

MustSupport

Profiles

FHIR-25685

Patient: Why do you need to require all three identifiers?

Eric Haas

Block-Vote-2

mapping

FHIR-25688

EOB: why is id required?

Eric Haas

Block-Vote-2

Profiles

mapping

FHIR-25689

EOB.diagnosis and EOB.procedure rendering of CodeableConcept

Eric Haas

Block-Vote-2

Narrative

mapping

FHIR-25690

All the supporting information fields need descriptions

Eric Haas

Block-Vote-2

Narrative

Profiles

EOB.provider change

Mark Roberts

Block-Vote-2

mapping

FHIR-26629

relax EOB.careteam.provider

Mark Roberts

Block-Vote-2

Profiles

FHIR-26693

Compiled comments on Search from Zulip

Mark Roberts

Block-Vote-2

Narrative

searchParameters

FHIR-26702

The IG requires a major overhaul on the search parameter specification

Patricia Taylor

Block-Vote-2

Narrative

searchParameters

FHIR-26704

The CARINBBRelatedPerson resource should be deleted  (Comment 47 Summary)

Patricia Taylor

Block-Vote-2

Profiles

FHIR-26705

This IG will not use the US Core Location Profile as a this use case does not support the US Core required element of name (Comment 48 Summary)

Patricia Taylor

Block-Vote-2

Profiles

FHIR-26737

This IG will not use the US Core Practioner Profile as a this use case does not support the US Core required element of name (Comment 80 Summary)

Patricia Taylor

Block-Vote-2

Profiles

FHIR-26745

               

Is "Must Support" different between US Core/FHIR and CarinBB?

Isaac Vetter

Block-Vote-2

MustSupport

Narrative

FHIR-26779

Using StructureDefinition-CARIN-BB-Coverage as an example: MustSupport elements have not been indicated

Paul Knapp

Block-Vote-2

MustSupport

Profiles

FHIR-26790

EOB.provider: Reference to PractitionerRole resource allows an organization or provider to be expressed

Lisa Nelson

Block-Vote-2

mapping

FHIR-26816

Slicing on carin-bb-explanationofbenefit- - insurance

David DeRoode

Block-Vote-2

Narrative

Mapping

slicing

FHIR-26819

Why are there three supportingInfo slice names referring to 'Inpatient' information in the Outpatient Facility profile?

David DeRoode

Block-Vote-2

Profiles

FHIR-26929

Abstract vs Concrete Profile: CarinBBExplanationOfBenefit

Saul Kravitz

Block-Vote-2

Narrative

Profiles

FHIR-26996

MustSupport elements shouldn't be bound with example strength

Saul Kravitz

Block-Vote-2

MustSupport

Profiles

Terminology

FHIR-27014

Increase the binding strength of NUCC Taxonomy to required

Patricia Taylor

Block-Vote-2

Profiles

Terminology

FHIR-27021

Increase binding strength of Coverage.relationship

Patricia Taylor

Block-Vote-2

Profiles

Terminology

FHIR-27025

Add EOB types for Vision and Dental/Oral

Saul Kravitz

Block-Vote-2

Profiles



Next MeetingNext Tuesday.

ATTENDEES -

Meeting ID : 396 570 8082  Topic : Financial Management Work Group's Personal Meeting Room  User Email : fm-cc@lists.hl7.org  

Duration (Minutes) : 132  Start Time : 2020-06-30 10:58:22 AM  End Time : 2020-06-30 01:09:52 PM  

Participants : 39

Name (Original Name)User EmailJoin TimeLeave TimeDuration
(Minutes)

MaryKay McDaniel (Financial Management Work Group)

fm-cc@lists.hl7.org

2020-06-30 10:58:21 AM2020-06-30 01:00:01 PM122

Kathleen Connor


2020-06-30 10:58:24 AM2020-06-30 01:08:11 PM130

Laura


2020-06-30 10:58:33 AM2020-06-30 11:12:15 AM14

Matt Reid


2020-06-30 10:58:42 AM2020-06-30 11:11:54 AM14

Jeff Brown (Cigna)

jeff.brown@cigna.com

2020-06-30 10:59:16 AM2020-06-30 01:01:11 PM122

celine a lefebvre


2020-06-30 11:00:00 AM2020-06-30 01:09:52 PM130

Paul Knapp


2020-06-30 11:00:25 AM2020-06-30 01:09:52 PM130

Laurie Burckhardt


2020-06-30 11:00:52 AM2020-06-30 11:08:03 AM8

Frank McKinney


2020-06-30 11:00:59 AM2020-06-30 12:51:00 PM111

Pat Taylor


2020-06-30 11:01:12 AM2020-06-30 01:09:34 PM129

Patricia Taylor

taylorpatriciab@bellsouth.net

2020-06-30 11:01:48 AM2020-06-30 01:09:32 PM128

smay5


2020-06-30 11:01:49 AM2020-06-30 01:00:05 PM119

Saul Kravitz

saul.kravitz@gmail.com

2020-06-30 11:01:53 AM2020-06-30 01:09:52 PM128

12564578118


2020-06-30 11:02:03 AM2020-06-30 11:11:54 AM10

Amol Vyas (Cambia Health)


2020-06-30 11:02:39 AM2020-06-30 01:09:52 PM128

18168537164


2020-06-30 11:03:17 AM2020-06-30 12:28:34 PM86

Call-In User_1


2020-06-30 11:03:26 AM2020-06-30 11:32:26 AM29

Robert Dieterle


2020-06-30 11:03:33 AM2020-06-30 11:42:31 AM39

Rachel Foerster


2020-06-30 11:03:52 AM2020-06-30 01:02:21 PM119

Bhanu Vemuri ( Blue Cross NC)


2020-06-30 11:05:48 AM2020-06-30 11:20:24 AM15

David Hill


2020-06-30 11:05:56 AM2020-06-30 12:01:09 PM56

Serafina Versaggi


2020-06-30 11:06:27 AM2020-06-30 01:09:52 PM124

Laurie Burckhardt


2020-06-30 11:08:26 AM2020-06-30 12:40:59 PM93

Susan Langford


2020-06-30 11:12:15 AM2020-06-30 01:09:52 PM118

lorraine.doo@cms.hhs.gov


2020-06-30 11:13:02 AM2020-06-30 12:09:04 PM57

Mark Roberts

mark.roberts@leavittpartners.com

2020-06-30 11:14:24 AM2020-06-30 01:09:49 PM116

Mark Scrimshire


2020-06-30 11:26:13 AM2020-06-30 11:45:39 AM20

Molly Malavey


2020-06-30 11:32:55 AM2020-06-30 12:29:39 PM57

Call-In User_2


2020-06-30 11:34:18 AM2020-06-30 01:09:52 PM96

Lisa Nelson


2020-06-30 11:36:36 AM2020-06-30 01:09:17 PM93

14013482176


2020-06-30 11:37:45 AM2020-06-30 01:08:42 PM91

Robert Dieterle


2020-06-30 11:44:54 AM2020-06-30 11:55:56 AM12

16082358341


2020-06-30 11:50:45 AM2020-06-30 12:58:08 PM68

Robert Dieterle


2020-06-30 12:01:24 PM2020-06-30 12:28:31 PM28

Gail Kocher


2020-06-30 12:02:11 PM2020-06-30 01:09:53 PM68

Mark Scrimshire


2020-06-30 12:06:07 PM2020-06-30 01:00:32 PM55

Igor Sirkovich

sirkovich@gmail.com

2020-06-30 12:16:14 PM2020-06-30 12:34:19 PM19

Laurie Burckhardt


2020-06-30 12:42:55 PM2020-06-30 12:58:03 PM16

Pat Taylor


2020-06-30 01:09:40 PM2020-06-30 01:09:53 PM1

Patricia Taylor

taylorpatriciab@bellsouth.net

2020-06-30 01:09:32 PM2020-06-30 01:09:52 PM1





  • No labels