Where are we with Blue Button API?Īt Health2.0 we launched the Develop Preview. This can help simplify the process involved in TPAs gaining access to data APIs.
Ivinci health human resources portable#
POET is a method for expressing the result of a policy assessment in a portable manner.
Ivinci health human resources software#
The idea of a verifiable software statement is fully in line with initiatives from The CARIN Alliance ( ) to promote interoperability. The objective is to encourage a network of endorsing bodies to spring up that can review and verify applications and use POET to express the results of their review/endorsement using a verifiable software statement that could be presented to data holders, like CMS and the BBAPI. To solve the application access issue the BBAPI team put forward a standard protocol we call POET (Pre-OAuth Entity Trust api – ). The process of enabling TPAs raised another challenge for the BBAPI team: how do we review applications that are requesting access to BBAPI? That authorization is handled by the OAuth 2.0 protocol. Insurance information will use the Coverage resource ( )Ĭlaims information will use the ExplanationOfBenefit resource( )Īccess to these FHIR resources will require registered third-party applications (TPAs) to be authorized by the beneficiary. demographics will use the Patient resource ( ).BBAPI is taking advantage of this emerging standard.īBAPI will be publishing Medicare claims information under the control of the individual beneficiary using the FHIR specification. At the same time a vibrant community has sprung up around HL7’s Fast Healthcare Interoperability Resources specification (FHIR).
The Office of the National Coordinator for Health IT (ONC) has done great work to promote this transformation. “build a developer-friendly, standards-based data API that enables Medicare Beneficiaries to share their data with the applications, services or research programs they trust.” Timing Is EverythingīBAPI has had the benefit of “building on the shoulders of giants.” In the past few years the health care industry has embraced APIs. A Consistent Vision For The Blue Button APIįrom the outset the vision for this project has been to… Accomplishing that feat while complying with all the necessary privacy, security and regulatory controls that apply to government solutions adds another level of complexity.Īs I have talked with some leading strategists and entrepreneurs while at the conference I have been encouraged to put something on digital paper that helps to tie together all of the threads involved in delivering the BlueButton API for CMS in a way that benefits Medicare beneficiaries, the health innovation community and consumer/patients everywhere. Building an API that supports a thriving ecosystem of applications and health solutions is the real challenge. Building an API server is really the easy part. For the last year Alan and I have been building the front-end system for the CMS Blue Button API morning (BBAPI) platform.Īt the conference we have met with numerous developers that are eager to build applications that will help Medicare beneficiaries by putting their claims information to use to help with their health, or to help support research.
I was here to present at the Dev Day pre-conference event with my colleague and co-conspirator, Alan Viars. The conference is in it’s 11th year and is one of the premier events to discover cutting edge health technology solutions. I am at the Health2.0 Conference in Santa Clara, CA.
0 kommentar(er)
