Grahame Grieve, creator of a health data integration model based on RESTful Web services, discusses how a simplified approach could influence the future of health data with Georgia Tech health informatics expert Mark Braunstein.
If we are to free the data in healthcare that is too often locked inside isolated systems, simplicity matters.
A new term spreading (almost like fire) through the healthcare interoperability world is HL7 FHIR, pronounced as “fire.” Here are the Top 5 things I think you should know about this upcoming standard many hope will help solve many current issues in interoperability:
The developer portal is a template portal, designed as a base that you can easily customize to meet your specific requirementsYour customized developer portal should educate developers about your API—what it is and how it's used. It should also enable you to manage developer use of your API. This could include authorizing developers to use your API, giving developers an easy way to create apps that use your API products, assigning developers specific roles and permissions related to the API, or revoking developer access to the API as necessary. Beyond that, your developer portal can serve as the focal point for community activity, where developers can contribute API-related content to social media repositories such as blogs and forums. View more information about developer portals at apigee.com
You can customize the appearance of the developer portal to match your company theme, to add new content areas to the portal, or to change the layout of any page on the portal. Much of this configuration requires a working knowledge of Drupal. However, there is documentation that describes some of the basic tasks that you might want to perform to customize your portal. View more information about customizing your developer portals at www.apigee.com.