Let's Talk APIs at Health Camp!

HealthCa.mp/dev 
Location: AcademyHealth (1666 K Street NW, Ste. 1100, Washington, D.C.) 
Dare and Time:  March 26  9:00 a.m. – 5:00 p.m. ET
Cost: $50
As Application Programming Interfaces proliferate across the industry, we still face challenges for consumers, data holders and application developers. How can API endpoints be discovered? How can consumers have confidence in applications that are receiving their health data? How can data holders know which applications to trust? How can we address all of these challenges without limiting choice for consumers? 
HealthCa.mp/dev is hosting a pre-Palooza un-conference that will examine and brainstorm these issues and discuss standard approaches to addressing the challenges in a way that can unleash innovation that will enable an accelerated adoption and use of APIs for health data. If you are an application developer producing consumer-facing health apps, or if you are a data holder needing to provide an API for consumers to use to share their health data, you want to be at this event.

Comments

Post a Comment

Popular posts from this blog

Conveying Identity and Authenticator Assurance Levels in OpenID Connect and Beyond in Healthcare

Conveying Identity and Authenticator Assurance Levels in OpenID Connect and Beyond in Healthcare 1. Standards and the Proposed Rule NIST's Special Publication 800-63-3 Digital Identity Guidelines outlines 3 identity assurance levels, "1", "2", and "3" to codify how well a person is or isn't, with 1 being a low confidence a person is who they say they are.  Similarly, Authentication Assurance Levels (AALs) of "1", "2", and 3" are also defined in NIST guidelines.  IAL details the  "login" or Authentication event. In ONC's proposed rule, " 21st Century Cures Act: Interoperability, Information Blocking, and the ONC Health IT Certification Program ", OpenID Connect is proposed in the following passage:   To enable and support persistent user authentication and app authorization processes, we propose to adopt a standards and additional implementation specification for the FHIR standard. First, w
Read more

A National Patient Identifier Would Be Totally Awesome!

Fun Fact:  Did you know that congress actually has a gag order preventing Health and Human Services(HHS) from even discussing the idea of a national health identifier?  Well fear no more... word on the street is that this might finally change . America's multi-payer system is already complex enough. We also have to contend with a lack of a national health identifier?  Certainly national health identifiers have issues, but it is still a monumental step in the right direction.  While a national patient identifier will not fully solve the patient linking and matching problem, it will go quite a long way in improving the status quo.  I've spent way too much time thinking about how such an identifier should be constructed and issued.  Here are some main points: It should be numeric so it is easy to enter via a number pad/telephone. It should, in-part, be defined by the end user.  For example the first 10 digits could be someone's phone number It should contain a check d
Read more