TEFCA! Live in 2022- What You Need to Know. A FREE EVENT - Shared screen with speaker view
Who can see your viewing activity?
flexibility typically means lack of consistency which is needed for a standard - how are you addressing that as you're stressing additional flexibility?
Questions for Dr. Tripathi-enter them here!
Are you familiar with a new Law in California called AB 133 which mandates HIE participation using API and other HL7 data types by Hospitals, Clinics and SNFs. Is your position that the HIE's like CMT and LANES are not ready currently to support this LAW?
TEFCA seems almost entirely focused on provider interoperability - how do you see it fitting in with the larger landscape, particularly with the increasing CMS focus on patient access and a patient-centric healthdata system?
Payers are trying to support this TEFCA but we need money incentives to move Hospitals SNFs and LTACs to get them to particpate
What would be your two sentence value statement to convince people TEFCA is a better option for them than direct exchange or other models, especially given the various direct FHIR exchanges already in the process of being built (some of which are mandated)
BTW, We will be collecting ALL comments and forwarding them to ONC and Sequoia after the event
How would I as a patient manage the sharing of sensitive data via these TEs?
How is the consent model different under TEFCA in relation to release and access to PHI for authorized providers and patients?
no, I meant point-to-point exchange
but many of the payer-provider exchanges (in both directions) are high volume and those are supposed to happen via FHIR APIs
+ David Delano question: [How is the consent model different under TEFCA in relation to release and access to PHI for authorized providers and patients?] And payers?
what's meant by "all exchange modalities"?
How do you envision the revenue sharing to work with all of the QHINs connected as sustainability is still an outstanding issue for all HIEs
you mentioned that USCDI was the minimum data exchange requirements, but many of those exchange purposes require other types of data outside of clinical - are there requirements around the data requirements in those areas?
do individuals who want to receive their own data have to have a participation agreement?
also, can individuals send data as well as receive it?
and, to cycle back to previous quesitons, what consent controls can they specify for their data?
Are QHIN's repositories or federated exchange services?
What should state health departments be doing now to prepare for TEFCA?
Who gets priority for getting QHIN qualification? Federal, followed by state, regional and private entities?
Isn’t every exchange essentially point to point. Someone sends, someone receives. The distinction seems to be about whether you have to have large clearnghouse agents in the middle of every exchange. Kind of like the “you can’t get there from here, you have to go somewhere else first”. In 2021 is it a valid assumption that technology can’t support complex, broadly distributed networks of nodes suported by automated directories and packet standards?
What is the incentive to become a QHIN?
Has TEFCA solved the patient identification dilemma? ☺️
are entities restricted to access records they can show some type of connection to? do providers need to show someone is a patient, payers that they have coverage, individuals that they are that person or have that person's permission? (and we're back to consent)
Are there conflicts of interest that will limit what types of organizations can be QHINs or would require strict firewalls and independence from QHIN operations.
Do you believe we need formal principles (such as the Generally Acceptable Accounting Principles) to promote common and uniform end-to-end health information governance and management practices (source to use – point of origination to each ultimate point of access/use, including exchange)?
Are there any learnings in building the FHIR directory mentioned?
how does a QHIN protect someone from information blocking? they still need to address all specific requests that come in, don't they?
The CMS interoperability Final Rule entrusts the consumer’s health plan with being their “point of connection” for all health data. How does TEFCA align (or not) with this explicit principle?
do you see there being a geographic assignment element of QHIN selection? Are you looking to having one QHIN and one QHIN only covering area X or region Y? If there are more than one are there expectations around how entities interact with them? for that matter, is there any expectation that an organization would chose a network near them to send their data for further dissemination?
you previous said that QHINs protected providers from information blocking - I was just following up
the stakeholder panels are also FREE to the industry. sign up at wedi.org
Thank you, Charles, for inviting me to talk with the group this afternoon. And thanks to everyone who joined all for your wonderful questions.