Health Affairs February 15, 2019
Lucia C. Savage

In 2015, when the Office of the National Coordinator for Health IT (ONC) – where I served as chief privacy officer at the time — started planning what would become the “open specification API” rule of ONC’s 2015 Edition Certification Rule, we purposefully grounded that rule, and the corollary CMS rule (now called “promoting interoperability”), on an individual’s right to get, use and send their protected health information. We did so because this right cannot lawfully be denied. Unlike information sharing between health care businesses (B2B), which is permitted but not required, disclosure to an individual is required. Driven by the vision that this strategy would help APIs take root and flourish in healthcare, we hoped that over time, apps...

Today's Sponsors

LEK
ZeOmega

Today's Sponsor

LEK

 
Topics: Apps, ASTP/ONC, CMS, EMR / EHR, Govt Agencies, Health IT, Health System / Hospital, HHS, HIE (Interoperability), Insurance, Medicaid, Medicare Advantage, Physician, Provider, Public Exchange, Technology
Improving Public Health Data Exchange With the Cloud
State of privacy consent management requires more collaboration, says Sequoia Project
Final agreement on the European Health Data Space: Cross-border access to EU health data
Advancing Cancer Care through FHIR-Based Reporting: Updates from USCDI+ Cancer
Aneesh Chopra talks Cancer Navigation Challenge & more

Share This Article