Sanjay Patil is a healthcare IT consultant with extensive experience successfully delivering large-scale custom development projects, application integration, content management, portal solutions, and implementing healthcare business solutions. He has been actively involved in meaningful use initiatives and is passionate about creating IT solutions for providers regarding different regulatory programs. Patil has worked on delivering solutions across product lines such as EMR, EHR, care coordination, and patient engagement.

1. Sanjay Patil is a Healthcare IT consultant with top-tier consulting experience in
successfully delivering large scale custom development projects, application
integration, content management ,portal solutions and implementation of
health care business solutions. He has been actively involved in Meaningful
Use and is passionate about creating IT solutions for providers w.r.t different
regulatory programs. He has worked in delivering solutions across all product
lines such as EMR, EHR ,Care Co-ordination, Patient Engagement.
Sanjay Patil
TEFCATrusted Exchange Frame work and
Common Agreement

2. 1 Copyright © 2019 Nalashaa
What’s TEFCA?..............................................................................................
Need for TEFCA............................................................................................
Steps taken by Government to mitigate..................................................
interoperability challenges
TEFCA Frame work......................................................................................
Recognized Coordinating Entity
Health Information Network
Qualified Health Information Network
Use cases covered under the Trusted......................................................
Exchange Framework
Trusted Exchange Framework - Privacy and............................................
security protections
Data Classes in U.S. Core Data for Interoperability................................
(USCDI) and Proposed Expansion Process
Users of the Trusted Exchange Framework............................................
Benefits and Impacts of TEFCA on PPP....................................................
(Patient, Payer, Provider) and HINS
Conclusion...................................................................................................
Go Through
Page 2
Page 2
Page 3
Page 4
Page 6
Page 6
Page 7
Page 8
Page 9
Page 10

3. Some common issues submitted on TEFCA:
Information Blocking: Several industry stake
holders would like more guidance on this issue
before ONC goes down the path of implementing
TEFCA, which may, or may not be a mechanism to
enforce information blocking.
Time line challenges for implementing
TEFCA: This frame work and agreement comes
several years after HIE networks and other industries
have collaboratively stood up legal agreements,
use cases, and business operations.
Data Privacy and Security: Stakeholders
require specific information on how will the TEFCA
requirements interact with HIPAA requirements as
they govern both QHINs and HIN and specifically
how this will affect the future of data exchange
Cost burdens: In order for the Trusted Health
Information Exchange and Frame work to work,
ONC must allow differentiation between state
health information exchange models. Otherwise,
there will be significant financial implications to
state economies, infrastructure, and communities.
Conclusion
TEFCA is designed to bridge the gap between provid-
ers’ and patients’ information systems and enable
interoperability across disparate Health Information
Networks by providing a “single on-ramp” to patient
information.
It is recommending that providers, payers and state
advocates to include requiring TEFCA connectivity in
future legislations.
Despite the fact that the procedures and draft agree-
ments described, if adopted by ONC, would remain
completely voluntary, the Act mentions that Federal
agencies may require its use in certain circumstances.
This may profoundly affect both health agencies and
their trading partners.
Regardless, if they don’t consider TEFCA in their plan-
ning, it may become a requirement. In the short run,
existing HIEs (or HINs) and collaborative activities may
not find it convincing to alter their course. Only time
will tell if TEFCA will have the impact on interoperability
that on interoperability that Congress desires.
10 Copyright © 2019 Nalashaa
If you would like to bounce off your thoughts on this,
let’s have a conversation.
Connect with
the experts!
About Us
At Nalashaa, we partner with healthcare organizations, from startups
to established firms, and work with them to build solutions with
engaging user experiences that reduce organizational cost and risk.
Our healthcare and technology expertise, along with our flexible
engagement models, make us a great fit for developing the quality
technology solutions while reducing time to market and costs.
555 US Highway 1 South, Suite 170, Iselin, NJ 08830, USA
732-602-2560 X 200
Reach Us:
www.nalashaahealth.com