News from NATE! – November 11, 2015

 November 2015
NATE logo
HAPPY VETERANS DAY!
  • NATE Celebrates Veterans Day with the VA
  • Hey Health App Developers: What Are Your Questions About HIPAA?
  • NATE CEO Appointed to Joint HITPC/HITSC API Task Force
VA logoOne Way NATE Celebrates
Veterans Day:


Welcoming a Membership Application from the Department of Veterans Affairs

NATE is thrilled to celebrate Veterans Day by accepting a new membership application from the US Department of Veterans Affairs (VA). The VA has always led the way in giving veterans access to their health information – first by being the earliest champions of the Blue Button initiative and now by being the first federal agency to join NATE. Becoming a member of NATE will open additional opportunities for the VA to empower veterans to better use their health information to improve outcomes. For more information on NATE membership, visit nate-trust.org/membership.
HHS OCR logoHey Health App Developers!
What are Your Questions About HIPAA?

New OCR website available to answer
your privacy and security questions

 
engage with OCRAttention All Consumer-Facing App Developers! 
Check out this new website developed by the HHS Office for Civil Rights to take your questions and concerns about applicable law, consumers’ right to access and your apps. Ask and receive answers to your questions at hipaaqsportal.hhs.gov.
ONC logoNATE CEO Aaron Seib Invited to Participate in Joint HITPC/HITSC API Task Force

NATE CEO Aaron Seib has been invited to participate in the joint Health IT Policy (HITPC) and Health IT Standards Committee (HITSC) API Task Force.  The task force will be co-chaired by Josh Mandel and Meg Marshall and will be working to bring final recommendations to the committees in April.  

The task force will be charged with:

•       Identify perceived security concerns and real security risks that are barriers to the widespread adoption of open APIs in healthcare

–      For risks identified as real, identify those that are not already planned to be addressed in the Interoperability Roadmap (for example, identity proofing and authentication are not unique to APIs)

•       Identify perceived privacy concerns and real privacy risks that are barriers to widespread adoption of open APIs in healthcare

–      For risks identified as real, identify those that are not already planned to be addressed in the Interoperability Roadmap (for example, harmonizing state law and misunderstanding of HIPAA)

•       Identify opportunities for policy guidance to build provider trust and accelerate the use of APIs to enable individual data access

 

NATE’s NBB4C Trust Bundle makes it easier for providers to share health information with their patients so that their patients can do what they want with it.
NATE url2
Copyright © 2015 National Association for Trusted Exchange. All rights reserved.
Contact email: meryt.mcgindley@nate-trust.org
You are receiving this message because you have an interest in health information exchange.