While staying far away from USA political discussions, I thought the next paper we should publish should address API use cases in the
Healthcare and Life Sciences industries.
One of the most common discussions I have with any business is about API use cases related to industry specific scenarios – their scenarios. We are making the information shared in these discussions more accessible to everyone by publishing a series of industry specific white papers covering these and related topics. Each white paper has a consistent format that includes:
- Identifying the common business drivers for API initiatives
- Describing an API identification methodology
- Supplying industry-specific examples using the methodology
- Discussing the current state of regulatory requirements and industry standards for APIs
- Providing recommendations for starting an API initiative
The healthcare and life sciences industries are becoming very active in the API economy. These industries are data-intensive and accessing data quickly across the enterprise, using data in new ways and interfacing with partners rapidly can provide competitive differentiation. In this paper we cover use cases across a wide variety of scenarios – internal, partnering, social, analytics, and more.
I am excited to have worked with industry subject matter experts to author each paper in this series. In each case my co-authors bring years of real world industry experience working with companies in the industry. My co-author for this paper is Roger Tobias who is the Public Sector leader for IBM Worldwide Mobile API Economy Solutions.
You can
click here to access the white paper.
To understand more about IBM’s thoughts on the API Economy visit the IBM
API Economy website. IBM API Connect is IBM’s complete foundation to Create, Run, Manage, and Secure APIs. You can find more information about IBM API Connect at the
API Connect website. And you can also experience a
trial version of API Connect.
If you have questions, please let me know. Connect with me through comments here or via twitter
@Arglick to continue the discussion.