Medtools — a potent tonic for charting medications in the public cloud
App and software centric businesses are increasingly leveraging cloud platforms and unbridled connectivity to reach customers everywhere. However, today’s technology leaders must be experts in two domains: software and cloud infrastructure.
There is no software without infrastructure. And while cloud platforms have virtualised physical IT, software developers must understand how everything works to deliver the quality of service their customers expect.
The Challenge
Review and fine-tune Microsoft Azure environment to streamline cloud services and establish DevOps best practice to support business growth.
The Solution
Spark Health Cloud Architecture Review and consulting.
The Background
Prescribing medication for patients is becoming simpler and safer with Medi-Map, a cloud based medicines and e-prescription management platform.
Pharmacist couple Greg and Julie Garratt founded the company after spotting an opportunity to evolve prescription systems from heavy reliance on paper to a fully integrated e Health solution.
Making quick inroads into New Zealand’s aged care sector, the Christchurch headquartered company continues to grow, adding major clients across the Tasman, and broadening its focus to addiction methadone prescribing.
Public Cloud provides global launchpad
Public cloud is a key enabler for Medi-Map’s global business aspirations. Like most high growth cloud businesses, Medi-Map requires push button scalability and as a service infrastructure to keep pace with customer demand and service upgrade cycles.
Microsoft Azure ticked the boxes, providing a secure cloud ready launchpad for Medi-Map’s Australian operation and beyond. However, working in the cloud highlighted a skills and experience gap that knocked the health services provider’s confidence to progress optimally at the required pace.
While Medi-Map’s development team continued to write applications for Microsoft Windows and other operating systems, as self described “cloud immigrants” they were less familiar with much of Azure‘s cloud native functionality.
“Our skillset was geared more to deploying software to servers rather than serverless infrastructure, we’re software people not infrastructure people, so we needed help to ensure what we were delivering wasn’t going to be a fizzer requiring unexpected additional work.”
Ongoing management key to confidence
Now with a better understanding of the rules of the game in Azure, Medi-Map operates with new confidence in the cloud. However, a less heralded part of the health services provider’s progress comes from cloud monitoring and security under the guise of a Managed Cloud Service (MCS).
Covering Medi-Map’s Azure environments with ongoing management and support, including monitoring, alerting, and threshold management, MCS delivers control and transparency to align the company’s internal team with external providers, Hilton said.
“The ability to get the attention of an individual rather than just an 0800 helpdesk is extremely comforting.” Public cloud services such as Microsoft Azure increasingly form the foundations of global facing companies.
But getting the best from these services is harder than it looks. It pays to know your way around. “You don’t know what you don’t know ignorance is not bliss,” Hilton said
A little guidance goes a long way.
Work kicked off with a Cloud Architecture Review; an audit of Medi-Map’s existing Azure environment to ensure the company’s applications scaled to support projected growth. The work also identified potential cost savings the company could realise.
Spark Health investigated five key areas to gauge the state of Medi-Map’s Azure environment, including scalability, availability, resiliency, security, and DevOps.
Feedback prioritised over 100 recommended improvements for future release cycles. “The surface area on Azure from a functionality perspective is huge, and growing every month” Hilton said.
“Rather than wrestle with three to four options, Spark Health understood each use case, narrowed the options and outlined the pros and cons of each so we could make an informed decision with confidence.”
While the review pinpointed wide ranging improvements, Hilton specifically mentioned an early win involving the retirement of a load balancer technology that distributes web traffic across multiple servers to improve application performance and resiliency. Switching to Azure’s Web Application Gateway, described by Hilton as a “load balancer on steroids”, the technology enables hardware scaling profiles to support variable traffic while maintaining systems availability and application uptime.
The move provided Medi-Map with greater functionality at a lower cost than the original load balancer supported.
Switching on DevOps
A fan of agile development but unfamiliar with its application to Azure DevOps, Hilton used Spark Health as a sounding board to critique his early foray into the domain. Using both Kanban and Taskboard for each sprint, Hilton wanted to fine tune his team’s agile processes with a view to shortening release cycles, improving the accuracy of task estimates, increasing the quality of development, and improving the visibility of resource availability for future projects. “We went from virtually no implementation to using agile processes daily without drowning everything in IT speak.”