We are extremely excited to announce the PokitDok Platform is now part of the Microsoft Azure Marketplace. If you’re an engineer at a hospital system, digital health startup or at a systems integrator and you’re running on Azure already, you can use our development platform to improve workflows and leverage data science for economic intelligence. Our Application Programming Interfaces (APIs) are preconfigured for Microsoft Azure cloud computing environments. Beyond this technical deep dive, you can also read the press release as well as a post on the PokitBlog on this groundbreaking partnership in healthcare technology.
I’d like to cover some salient points concerning our involvement with the Azure development team, the security of the Pokitdok Platform on the Azure cloud and finally the accessibility of the PokitDok Platform in the Azure Marketplace.
Under the Hood
Azure now supports open source deployments which we - and third parties who have built more than 4000 applications on our development platform - truly appreciate. Currently we are running Ubuntu 14.04 on the Azure Cloud. Given most of the Internet is powered by open source software, this allows seamless development throughout our software stack. The PokitDok engineering team worked closely with Microsoft’s Azure engineers in defining and coding support for Red Hat’s Ansible as well as Docker and Apache Mesos. I’m a fan of Ansible because it allows for multi-cloud deployment with reusable and consistent patterns. Our engineering team finds that common container services like Docker and Apache Mesos streamlines component management in multi-cloud environments and eases migration of services. You can move to a more granular developer operations deployment and support a micro-services design, which PokitDok supports daily with multiple deployments.
Given the open source nature of the environment, there are also cross platform command line interface tools, so you can manage resources from Mac and Linux clients. In addition, the payloads are standardized to JSON formatting in both transmission and reception.
PokitDok is the standard when it comes to growth scale computing with respect to powering all of the APIs needed to create a one click health service purchase. The workflow of “Shop, Book and Pay” is supported throughout the continuum. Picture booking an MRI for the shoulder you tweaked while kite surfing. This seemingly simple task of scheduling a medical appointment actually involves search algorithms, protections for patient identity, multiple layers of financial transaction processing, geolocation and a variety of other technical elements that an open source system supports well.
Security is Paramount
More than 4000 third-party health applications have been built on our development platform. This includes an application DoctorOnDemand developed to automatically file an insurance claim when a patient sees a physician on their telemedicine service. We take security and personal health information seriously and so does Microsoft. We recognized that healthcare worldwide predominantly runs on Microsoft products and nearly 85 percent of clinical tools are Windows-based systems.
Connecting networks within Azure allows for highly secure net works where they matter most, between our customers’ infrastructure and ours. Virtual Network services makes managing a secure network easier than on premises provision. No more “spaghetti infrastructure.” The Service Trust Portal allows for easy access to Azure audit reports.
So let us dig a little deeper on some of these security features.
Microsoft employs the principles of Separation of Duties and Least Privilege (aka principle of minimal privilege) throughout Azure operations. Access to data is granted on a “just-in-time” basis that is logged and audited, then revoked after completion of the engagement.
In addition, Azure provides multiple capabilities for protecting data in-transit and at-rest, including encryption for data, files, applications, services, communications, and drives. You have the option to encrypt information before placing it in Azure, as well as storing keys in a secure fashion. This “built-in” hardware level cryptographic technology enables you to encrypt communications within and between deployments, between regions, and from point to point deployment centers. This will all happen in a seamless fashion behind the curtains when you sign up and adopt The PokitDok Platform through the Azure Marketplace. We take care of all the heavy lifting so you can focus on the development of your application set.
Take it for a Test Drive
So how do you go about getting access to our platform on the Azure Marketplace? It is literally as simple as this:
- You locate the PokitDok button in Azure Marketplace on the Developer Services Channel and click the icon
- Select the "plan" listed
- You get back your API key and secret
- Click "manage" in the Azure portal and you can Single sign-on (SSO) into our platform and analytics dashboard
- You are done. Go bring your idea to fruition.
The Microsoft Azure and PokitDok collaboration is a monumental step forward in reducing complexity and retrofitting #HealthIT systems littered with legacy technology. Health and non-health developers have an opportunity to efficiently adopt a scalable, secure approach that will bring deeper insights into their internal operations as well as external engagements with patients and business partners. This will usher in completely new behaviors and business models in the $3T healthcare industry.
We look forward to streamlining the business of health with you.
Ted Tanner Jr.
- Why PokitDok Joined Hyperledger - June 26, 2018
- Full Consensus and Distributed Ledger Hardware Acceleration - May 10, 2017
- Blockchain Virtual Machines with Consensus in Silicon - October 11, 2016
- Snake_Bytes #3: Statistics! - September 23, 2016
- DokChain Technical Deep Dive - Part One - September 13, 2016
- Welcome To Snake_Bytes - September 9, 2016
- The DokChain is Now - July 13, 2016
- PokitDok Now in the Microsoft Azure Marketplace - June 8, 2016
- ClearingHouses Are Oxymorons - May 4, 2016
- Social Capital Within Social Health Networks (part 2) - August 22, 2012