Click here to close now.


Microservices Expo Authors: Elizabeth White, Ian Khan, Jason Bloomberg, AppDynamics Blog, Liz McMillan

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
The Internet of Things (IoT) is growing rapidly by extending current technologies, products and networks. By 2020, Cisco estimates there will be 50 billion connected devices. Gartner has forecast revenues of over $300 billion, just to IoT suppliers. Now is the time to figure out how you’ll make money – not just create innovative products. With hundreds of new products and companies jumping into the IoT fray every month, there’s no shortage of innovation. Despite this, McKinsey/VisionMobile data...
One of the most important tenets of digital transformation is that it’s customer-driven. In fact, the only reason technology is involved at all is because today’s customers demand technology-based interactions with the companies they do business with. It’s no surprise, therefore, that we at Intellyx agree with Patrick Maes, CTO, ANZ Bank, when he said, “the fundamental element in digital transformation is extreme customer centricity.” So true – but note the insightful twist that Maes adde...
Just over a week ago I received a long and loud sustained applause for a presentation I delivered at this year’s Cloud Expo in Santa Clara. I was extremely pleased with the turnout and had some very good conversations with many of the attendees. Over the next few days I had many more meaningful conversations and was not only happy with the results but also learned a few new things. Here is everything I learned in those three days distilled into three short points.
Using any programming framework to the fullest extent possible first requires an understanding of advanced software architecture concepts. While writing a little client-side JavaScript does not necessarily require as much consideration when designing a scalable software architecture, the evolution of tools like Node.js means that you could be facing large code bases that must be easy to maintain.
As organizations realize the scope of the Internet of Things, gaining key insights from Big Data, through the use of advanced analytics, becomes crucial. However, IoT also creates the need for petabyte scale storage of data from millions of devices. A new type of Storage is required which seamlessly integrates robust data analytics with massive scale. These storage systems will act as “smart systems” provide in-place analytics that speed discovery and enable businesses to quickly derive meaningf...
DevOps is about increasing efficiency, but nothing is more inefficient than building the same application twice. However, this is a routine occurrence with enterprise applications that need both a rich desktop web interface and strong mobile support. With recent technological advances from Isomorphic Software and others, rich desktop and tuned mobile experiences can now be created with a single codebase – without compromising functionality, performance or usability. In his session at DevOps Su...
You may have heard about the pets vs. cattle discussion – a reference to the way application servers are deployed in the cloud native world. If an application server goes down it can simply be dropped from the mix and a new server added in its place. The practice so far has mostly been applied to application deployments. Management software on the other hand is treated in a very special manner. Dedicated resources are set aside to run the management software components and several alerting syst...
In his General Session at DevOps Summit, Asaf Yigal, Co-Founder & VP of Product at, explored the value of Kibana 4 for log analysis and provided a hands-on tutorial on how to set up Kibana 4 and get the most out of Apache log files. He examined three use cases: IT operations, business intelligence, and security and compliance. Asaf Yigal is co-founder and VP of Product at log analytics software company In the past, he was co-founder of social-trading platform Currensee, which...
It's been a busy time for tech's ongoing infatuation with containers. Amazon just announced EC2 Container Registry to simply container management. The new Azure container service taps into Microsoft's partnership with Docker and Mesosphere. You know when there's a standard for containers on the table there's money on the table, too. Everyone is talking containers because they reduce a ton of development-related challenges and make it much easier to move across production and testing environm...
People want to get going with DevOps or Continuous Delivery, but need a place to start. Others are already on their way, but need some validation of their choices. A few months ago, I published the first volume of DevOps and Continuous Delivery reference architectures which has now been viewed over 50,000 times on SlideShare (it's free to registration required). Three things helped people in the deck: (1) the reference architectures, (2) links to the sources for each architectur...
Continuous processes around the development and deployment of applications are both impacted by -- and a benefit to -- the Internet of Things trend. To help better understand the relationship between DevOps and a plethora of new end-devices and data please welcome Gary Gruver, consultant, author and a former IT executive who has led many large-scale IT transformation projects, and John Jeremiah, Technology Evangelist at Hewlett Packard Enterprise (HPE), on Twitter at @j_jeremiah. The discussion...
Hiring the wrong candidate can cost a company hundreds of thousands of dollars, and result in lost profit and productivity during the search for a replacement. In fact, the Harvard Business Review has found that as much as 80 percent of turnover is caused by bad hiring decisions. But when your organization has implemented DevOps, the job is about more than just technical chops. It’s also about core behaviors: how they work with others, how they make decisions, and how those decisions translate t...
In today's enterprise, digital transformation represents organizational change even more so than technology change, as customer preferences and behavior drive end-to-end transformation across lines of business as well as IT. To capitalize on the ubiquitous disruption driving this transformation, companies must be able to innovate at an increasingly rapid pace. Traditional approaches for driving innovation are now woefully inadequate for keeping up with the breadth of disruption and change facin...
The Internet of Things is clearly many things: data collection and analytics, wearables, Smart Grids and Smart Cities, the Industrial Internet, and more. Cool platforms like Arduino, Raspberry Pi, Intel's Galileo and Edison, and a diverse world of sensors are making the IoT a great toy box for developers in all these areas. In this Power Panel at @ThingsExpo, moderated by Conference Chair Roger Strukhoff, panelists discussed what things are the most important, which will have the most profound...
PubNub has announced the release of BLOCKS, a set of customizable microservices that give developers a simple way to add code and deploy features for realtime apps.PubNub BLOCKS executes business logic directly on the data streaming through PubNub’s network without splitting it off to an intermediary server controlled by the customer. This revolutionary approach streamlines app development, reduces endpoint-to-endpoint latency, and allows apps to better leverage the enormous scalability of PubNu...
I recently attended and was a speaker at the 4th International Internet of @ThingsExpo at the Santa Clara Convention Center. I also had the opportunity to attend this event last year and I wrote a blog from that show talking about how the “Enterprise Impact of IoT” was a key theme of last year’s show. I was curious to see if the same theme would still resonate 365 days later and what, if any, changes I would see in the content presented.
Microservices are a very exciting architectural approach that many organizations are looking to as a way to accelerate innovation. Microservices promise to allow teams to move away from monolithic "ball of mud" systems, but the reality is that, in the vast majority of organizations, different projects and technologies will continue to be developed at different speeds. How to handle the dependencies between these disparate systems with different iteration cycles? Consider the "canoncial problem"...
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...
Discussions of cloud computing have evolved in recent years from a focus on specific types of cloud, to a world of hybrid cloud, and to a world dominated by the APIs that make today's multi-cloud environments and hybrid clouds possible. In this Power Panel at 17th Cloud Expo, moderated by Conference Chair Roger Strukhoff, panelists addressed the importance of customers being able to use the specific technologies they need, through environments and ecosystems that expose their APIs to make true ...
There are over 120 breakout sessions in all, with Keynotes, General Sessions, and Power Panels adding to three days of incredibly rich presentations and content. Join @ThingsExpo conference chair Roger Strukhoff (@IoT2040), June 7-9, 2016 in New York City, for three days of intense 'Internet of Things' discussion and focus, including Big Data's indespensable role in IoT, Smart Grids and Industrial Internet of Things, Wearables and Consumer IoT, as well as (new) IoT's use in Vertical Markets.