Click here to close now.


Microservices Expo Authors: Blue Box Blog, Janakiram MSV, Pat Romanski, Elizabeth White, AppDynamics Blog

Related Topics: @CloudExpo, Java IoT, Industrial IoT, Mobile IoT, Microservices Expo, Containers Expo Blog, SDN Journal

@CloudExpo: Article

Accelerate Mobile Application Development within Healthcare

Using API Management and Governance

Slide Deck from Gene Dragotta and Sachin Agarwal's Cloud Expo Presentation: A Peek into the Future of Mobile-Enabled Health Care

While unprecedented technological advances have been made in healthcare in areas such as genomics, digital imaging and Health Information Systems, access to this information has not been easy for both the healthcare provider and the patient themselves. Regulatory compliance and controls, information lock-in in proprietary Electronic Health Record systems and security concerns have made it difficult to share data across health care providers.

The opportunities inherent in mobile technology are dramatically changing the way healthcare business gets done. Healthcare provider professionals are adopting mobile devices and tablets as an alternative to desktops/laptops and using mobile applications to augment gaps in existing patient management system capabilities. Developing mobile applications for the healthcare industry has some unique challenges, particularly protecting your backend data services while making them available to mobile application frameworks and SDKs.

Mobile applications utilize messaging patterns similar to the client/server and AJAX patterns, however unlike desktop clients, mobile devices have to minimize client side processing to maximize battery life and also keep network chatter to a basic minimum. This is achieved by using RESTful APIs with machine-readable formats like JSON. The availability, reliability and performance of these API-based services are critical to the successful deployment and operating of your application.  Now add some healthcare domain requirements (encryption, security, etc.,) to this environment and there is a lot of work to do in addition to the actual coding of your mobile application.  An API management system will simplify exposing and consuming backend healthcare services through a variety of different channels. To successfully implement an API, you will need a tool that will enable simple enforcement of API controls, continuous monitoring capabilities, performance management, and assurance of high availability.

An API management system will typically provide capabilities for creating and registering service as follows:

  • Secure API Services
  • Manage API Lifecycles
  • Mediate and Virtualize Services
  • Govern Access to Services
  • Integrate Services and their Data
  • Support Authentication and Authorization for all APIs and Services, including OAuth, OpenID, SAML, Kerberos, WS-Security, LDAP and XACML
  • Support for all Major Security Standards, including WS*and WS-I

The focus of this article is to discuss how a unified API management and SOA governance platform can accelerate your organization's ability to deliver reliable, scalable and secure mobile applications for healthcare providers. First we will begin with the major technical challenges encountered when deploying healthcare-based mobile applications. Then we will discuss API management and governance platform expectations that can help you overcome these challenges such as the following:

  • Data Encryption
  • Access Control - Role and Application-based Access
  • Integration / Orchestration of data from Multiple Provider Systems
  • Mediation
  • Quality of Service Control
  • Usage Analytics / Event Management

Security - Encryption, Authentication and Authorization
A PKI facilitates users, applications and systems to exchange insecure data safely by encrypting it prior to transmission. Unlike traditional cryptography that uses private keys also known as symmetric cryptography, the public key infrastructure utilizes public key cryptography or asymmetric cryptography. This is used to authenticate a user or manage message encryption.

With asymmetrical cryptography, a public and private key are created simultaneously using the same algorithm (such as RSA) by the certificate authority. The private key is given to the requesting party and the public key is made publicly available (embedded within the certificate) in a location that all parties can access. The private key is used to decrypt text that has been encrypted with the public key. The certificate is used to authenticate the user.

Typically a PKI provides:

  • A certificate authority (CA) who issues and verifies the digital certificate. A certificate includes the public key or information about the public key
  • A registration authority (RA) acts as the verifier for the certificate authority before a digital certificate is issued to a requestor
  • Persistent storage of the certificates and keys
  • A certificate management system (creation, import, export, revocation, etc.)

In addition to authenticating with a validated digital certificate, using SAML, an SSO token, basic HTTP authentication, an X.509 certificate, an application token or a third-party IAM system are all popular approaches that can be used to securely connect your mobile application to back-end systems and data services residing with the HIE enterprise.

When health provider personnel authenticate themselves on systems that access patient health records; it's likely that different employees will require and qualify for various levels of data access based on their job description. For this reason, a role-based authentication / authorization framework is recommended. For example, the front office personnel may only have a need to see basic information such as patient demographics, insurance and medication information and a nurse might be required to have access to the entire patient's medical record. Having a framework for implementing role-based access will easily help filter and mask patient data attributes from un-authorized use.

Mediation and Service Orchestration
Where are your patient's medical records, how many sources of data needed to be aggregated, transformed and merged to assemble them, what formats of data do these sources of patient record fragments support etc.? Architects and developers typically face these questions when working with multiple systems both internally and externally to assemble a patient's holistic and contiguous health history or continuity of care document (HL7 CCD). Often developer are using integration engines such as Rhapsody, Mirth, etc., to transform HL7 messages, legacy EDI messages, database data, along with other source of patient information into in XML and usually exposed via a SOAP service.

Most mobile UX frameworks support some form of a model-view-controller runtime design pattern or at a minimum provide a way to perform an XMLHttpRequest to retrieve data. Whether using an MVC pattern or a lower-level URL request, REST is the preferred method (over SOAP) primarily for the simplicity of setting up the request. A SOAP service will return an XML document. When using a JavaScript-based framework such as Sencha Touch, using JSON for data objects is usually preferred. The mobile app framework's data store component prefers the use of a REST service and the data it returns to be in JSON format. With this approach, the integration engine is providing a SOAP/XML service, unless we re-write and convert the SOAP service to a REST service, the mobile application will need to mediate between the SOAP and REST protocols and XML and JSON object formats.

In addition to mediation, service orchestration and the creation of compound services are a common requirement for health care oriented mobile applications. As an example, in order to create a patient's HL7 CCD, patient data usually resides within multiple systems, data service requests (primitives) to these systems will need to be orchestrated to form the resulting CCD dataset. In some cases, data returned from some of the primitive service requests may require some transformation or may be used as input to a subsequent request. Encapsulating and abstracting multiple primitive requests and any associated logic into a single composite service operation will reduce overall mobile application implementation complexity and message traffic between the mobile device and the HIE data center.

Policy-based Governance Controls for API Services
In most cases, we probably want different licenses with different levels of service (and access) to the backend APIs that enable our mobile applications. The levels of service could be measured in throughput, the bandwidth consumed over time, concurrency and availability.

Within the realm of health care you might want to have some specific controls or governance policies regarding the use of the HIE's back-end system services or APIs. Below are some QoS and SLA examples.

  • Allow APIs to be called no more than 10 times per minute per device
  • Allow devices to consume no more than 100MB per hour
  • Prevent devices from outside the trusted country list (user-defined)
  • Allow devices with this IP address range x.x.x.x-x.x.x.x to access the service layer
  • Prevent Denial-of-Service attacks with quota management and white/blacklisting
  • Only allow certain APIs to be called by specific user roles

The back-end services within the HEI should be deployed within an infrastructure that can provide a similar level of API governance.

Usage Analytics
In order to understand how your HEI back-end service layer is performing and being utilized by its application consumers, the API management platform should provide access to real-time API usage statistics, API status and event and SLA violation monitoring. These analytics can be used for troubleshooting, performance tuning, threat detection and various usage reports.

Most enterprises utilize a dashboard and reporting system that ingests telemetry data from a variety of systems within the enterprise. Data from these systems are combined to create a complete picture of enterprise system activity. Therefore it may become important to have a capability that can export or publish API management system telemetry data to an enterprise activity monitoring system or reporting data warehouse.

Healthcare-focused mobile applications contain complex use cases and have strict operational requirements. Security models, message protocol mediation services, service usage statistic collection, data transformations and service orchestration functions are all features that can easily be added to your mobile application by leveraging and integrating an API management and governance system with your service oriented architecture.

More Stories By Gene Dragotta and Sachin Agarwal

Gene Dragotta is a senior software developer and architect with 20 years of experience building distributed systems for the finance, insurance, government, military and the health care sector domains. Mr. Dragotta recently completed and deployed a mobile solution that utilizes the HL7 messaging protocol to remotely manage emergency battlefield dialysis treatments from a mobile device. Additionally Gene spent 3 years as a Tibco / Data Synapse Cloud Computing solutions architect building private and hybrid cloud computing infrastructures and migrating applications to those environments.

Sachin Agarwal is Vice President of Product Marketing and Strategy at SOA Software. He possesses more than 17 years of enterprise and startup experience focussing on using disruptive technologies to drive business growth. His expertise spans from infrastructure technologies like security and middleware to business centric applications like social, digital marketing, and analytics. At SOA Software he drives product marketing, strategy and customer adoption for API Management solutions. Prior to SOA Software, he held senior management roles in Product Management and Development at Oracle, Oblix and Infosys.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.

@MicroservicesExpo Stories
In a report titled “Forecast Analysis: Enterprise Application Software, Worldwide, 2Q15 Update,” Gartner analysts highlighted the increasing trend of application modernization among enterprises. According to a recent survey, 45% of respondents stated that modernization of installed on-premises core enterprise applications is one of the top five priorities. Gartner also predicted that by 2020, 75% of
It is with great pleasure that I am able to announce that Jesse Proudman, Blue Box CTO, has been appointed to the position of IBM Distinguished Engineer. Jesse is the first employee at Blue Box to receive this honor, and I’m quite confident there will be more to follow given the amazing talent at Blue Box with whom I have had the pleasure to collaborate. I’d like to provide an overview of what it means to become an IBM Distinguished Engineer.
The cloud has reached mainstream IT. Those 18.7 million data centers out there (server closets to corporate data centers to colocation deployments) are moving to the cloud. In his session at 17th Cloud Expo, Achim Weiss, CEO & co-founder of ProfitBricks, will share how two companies – one in the U.S. and one in Germany – are achieving their goals with cloud infrastructure. More than a case study, he will share the details of how they prioritized their cloud computing infrastructure deployments ...
SYS-CON Events announced today that G2G3 will exhibit at SYS-CON's @DevOpsSummit Silicon Valley, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. Based on a collective appreciation for user experience, design, and technology, G2G3 is uniquely qualified and motivated to redefine how organizations and people engage in an increasingly digital world.
If you are new to Python, you might be confused about the different versions that are available. Although Python 3 is the latest generation of the language, many programmers still use Python 2.7, the final update to Python 2, which was released in 2010. There is currently no clear-cut answer to the question of which version of Python you should use; the decision depends on what you want to achieve. While Python 3 is clearly the future of the language, some programmers choose to remain with Py...
Opinions on how best to package and deliver applications are legion and, like many other aspects of the software world, are subject to recurring trend cycles. On the server-side, the current favorite is container delivery: a “full stack” approach in which your application and everything it needs to run are specified in a container definition. That definition is then “compiled” down to a container image and deployed by retrieving the image and passing it to a container runtime to create a running...
Somebody call the buzzword police: we have a serious case of microservices-washing in progress. The term “microservices-washing” is derived from “whitewashing,” meaning to hide some inconvenient truth with bluster and nonsense. We saw plenty of cloudwashing a few years ago, as vendors and enterprises alike pretended what they were doing was cloud, even though it wasn’t. Today, the hype around microservices has led to the same kind of obfuscation, as vendors and enterprise technologists alike ar...
“All our customers are looking at the cloud ecosystem as an important part of their overall product strategy. Some see it evolve as a multi-cloud / hybrid cloud strategy, while others are embracing all forms of cloud offerings like PaaS, IaaS and SaaS in their solutions,” noted Suhas Joshi, Vice President – Technology, at Harbinger Group, in this exclusive Q&A with Cloud Expo Conference Chair Roger Strukhoff.
Clearly the way forward is to move to cloud be it bare metal, VMs or containers. One aspect of the current public clouds that is slowing this cloud migration is cloud lock-in. Every cloud vendor is trying to make it very difficult to move out once a customer has chosen their cloud. In his session at 17th Cloud Expo, Naveen Nimmu, CEO of Clouber, Inc., will advocate that making the inter-cloud migration as simple as changing airlines would help the entire industry to quickly adopt the cloud wit...
As the world moves towards more DevOps and microservices, application deployment to the cloud ought to become a lot simpler. The microservices architecture, which is the basis of many new age distributed systems such as OpenStack, NetFlix and so on, is at the heart of Cloud Foundry - a complete developer-oriented Platform as a Service (PaaS) that is IaaS agnostic and supports vCloud, OpenStack and AWS. In his session at 17th Cloud Expo, Raghavan "Rags" Srinivas, an Architect/Developer Evangeli...
Culture is the most important ingredient of DevOps. The challenge for most organizations is defining and communicating a vision of beneficial DevOps culture for their organizations, and then facilitating the changes needed to achieve that. Often this comes down to an ability to provide true leadership. As a CIO, are your direct reports IT managers or are they IT leaders? The hard truth is that many IT managers have risen through the ranks based on their technical skills, not their leadership ab...
Apps and devices shouldn't stop working when there's limited or no network connectivity. Learn how to bring data stored in a cloud database to the edge of the network (and back again) whenever an Internet connection is available. In his session at 17th Cloud Expo, Bradley Holt, Developer Advocate at IBM Cloud Data Services, will demonstrate techniques for replicating cloud databases with devices in order to build offline-first mobile or Internet of Things (IoT) apps that can provide a better, ...
Despite all the talk about public cloud services and DevOps, you would think the move to cloud for enterprises is clear and simple. But in a survey of almost 1,600 IT decision makers across the USA and Europe, the state of the cloud in enterprise today is still fraught with considerable frustration. The business case for apps in the real world cloud is hybrid, bimodal, multi-platform, and difficult. Download this report commissioned by NTT Communications to see the insightful findings – registra...
Application availability is not just the measure of “being up”. Many apps can claim that status. Technically they are running and responding to requests, but at a rate which users would certainly interpret as being down. That’s because excessive load times can (and will be) interpreted as “not available.” That’s why it’s important to view ensuring application availability as requiring attention to all its composite parts: scalability, performance, and security.
SYS-CON Events announced today that HPM Networks will exhibit at the 17th International Cloud Expo®, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. For 20 years, HPM Networks has been integrating technology solutions that solve complex business challenges. HPM Networks has designed solutions for both SMB and enterprise customers throughout the San Francisco Bay Area.
There once was a time when testers operated on their own, in isolation. They’d huddle as a group around the harsh glow of dozens of CRT monitors, clicking through GUIs and recording results. Anxiously, they’d wait for the developers in the other room to fix the bugs they found, yet they’d frequently leave the office disappointed as issues were filed away as non-critical. These teams would rarely interact, save for those scarce moments when a coder would wander in needing to reproduce a particula...
All we need to do is have our teams self-organize, and behold! Emergent design and/or architecture springs up out of the nothingness! If only it were that easy, right? I follow in the footsteps of so many people who have long wondered at the meanings of such simple words, as though they were dogma from on high. Emerge? Self-organizing? Profound, to be sure. But what do we really make of this sentence?
As we increasingly rely on technology to improve the quality and efficiency of our personal and professional lives, software has become the key business differentiator. Organizations must release software faster, as well as ensure the safety, security, and reliability of their applications. The option to make trade-offs between time and quality no longer exists—software teams must deliver quality and speed. To meet these expectations, businesses have shifted from more traditional approaches of d...
Information overload has infiltrated our lives. From the amount of news available and at our fingertips 24/7, to the endless choices we have when making a simple purchase, to the quantity of emails we receive on a given day, it’s increasingly difficult to sift out the details that really matter. When you envision your cloud monitoring system, the same thinking applies. We receive a lot of useless data that gets fed into the system, and the reality is no one in IT or DevOps has the time to manu...
Last month, my partners in crime – Carmen DeArdo from Nationwide, Lee Reid, my colleague from IBM and I wrote a 3-part series of blog posts on We titled our posts the Simple Math, Calculus and Art of DevOps. I would venture to say these are must-reads for any organization adopting DevOps. We examined all three ascpects – the Cultural, Automation and Process improvement side of DevOps. One of the key underlying themes of the three posts was the need for Cultural change – things like t...