Author: Doug Dennington
US Department of Defense Expands Partnership with MaestroDev and Apelon to Improve Clinical Data Interoperability
Our ongoing work with the Veterans Health Administration has expanded to include the Department of Defense to help exchange clinical data from existing electronic medical record systems. The focus of the first deliverable is the exchange of patient allergy information.
The partnership between Apelon and MaestroDev is enabling use of the International Health Terminology Standards Development Organization (IHTSDO) Workbench — an important open source tool for the development of standardized medical terminology — by the two Federal Agencies.
By streamlining the exchange of clinical data between electronic medical record systems, MaestroDev and Apelon are making it easier for DoD and VA teams to share critical healthcare information. This will help eliminate confusion and ensure that patients receive the right diagnosis and care, based on consistent medical definitions, across DoD bases worldwide. Early stage implementations of the new data sharing and modeling capabilities are focusing on the exchange of patient allergy information.
Through the partnership, MaestroDev is providing the DoD with development and operations automation, including a platform on which to build, test, and release software. Apelon is contributing products and expertise in terminology and data standardization.
A Deeper Dive on the Solution
Apelon and MaestroDev are configuring the Workbench to manage each Agency’s local terminology along with industry standards including SNOMED CT, ICD-9-CM, CPT, LOINC, RxNorm, and others. The synergistic integration of Apelon’s terminology experience and MaestroDev’s DevOps Orchestration platform allows multiple users to complete the necessary workflows enabling frictionless contribution of new content to the U.S. extension of SNOMED CT and the rest of the IHTSDO community.
This project leverages each company’s experience with open source technologies to achieve efficiency and quality. Together, MaestroDev and Apelon deploy a particularly effective system for modeling and distributing medical terminologies.
Apelon and MaestroDev Partner to Improve Healthcare Terminologies at VHA.
Apelon and MaestroDev are teaming up to help the Veterans Health Administration develop a new open source terminology management environment. The collaboration will allow the VHA to extend its use of the International Health Terminology Standards Development Organization (IHTSDO) Workbench, an important emergent open source terminology development tool.
Through the partnership MaestroDev is providing development and operations automation, including an open source tools-based platform on which to build, test and release software. Apelon is providing products and consulting expertise in terminology and data standardization.
The joint solution will allow the VHA to configure Workbench to manage local, national, and international terminology standards across VA hospitals nationwide. The integration of Apelon’s terminology experience and MaestroDev’s DevOps Orchestration engine offers an ideal approach to streamlining workflows and enhancing productivity in a terminology project of this scale.
The MaestroDev team has extensive experience with Workbench projects. This includes successful engagements with Kaiser Permanente, the Australian National eHealth Transition Authority, and IHTSDO.
By automating best practices from DevOps and agile methodologies the MaestroDev team can provide Continuous Delivery of the Workbench software. This helps drive the internal terminology standardization program at VHA, improves the exchange and analysis of veterans’ health information, and improves the VHA’s interactions with community partners.
DevOps Orchestration automates customers’ software lifecycle toolchain across physical, virtual, and hybrid cloud environments
Manhattan Beach, CA, May 22, 2012 — BusinessWire — MaestroDev, an innovation leader in DevOps Orchestration, has been included in the list of “Cool Vendors in DevOps, 2012” report by Gartner, Inc.
“We’ve had some great customer accolades this year, and we believe this recognition from Gartner confirms our innovation of DevOps Orchestration, and it’s impact in the marketplace,” said Doug Dennington, CEO of MaestroDev. “Customers are using our Maestro™ product to automate cloud-era development processes with their own choice of build/test/deploy tools and hybrid environments, and they are achieving Continuous Delivery, real-time control of development resources, and faster time to market.”
Keith Campbell, CTO, Informatics, said “The Maestro product has automated our build process all the way through packaging. We are using our same toolset, but the Maestro Composition engine gives us consistency and speed that we did not have before. With Maestro, we are planning our development-cloud environment as well — reducing our build cost even further because we can dynamically integrate hybrid resources and external services into our workflows.”
DevOps Orchestration is the practice of executing a broad scope of tasks across both the software development lifecycle and IT Operations functions, with any choice of tools and environments, and with the process logic abstracted away from the individual tools themselves. Maestro is a central console that automates heterogeneous tools through a company’s custom processes for build, test, artifact, release, and deploy, and is optimized for Continuous Delivery, Agile development, DevOps, and Cloud Federation.
MaestroDev is able to deliver its technology-agnostic capability with the introduction of Compositions™, which persist the customer’s processes over time and inevitable changes to tools, people, and environments. Compositions enable a common language to express bi-directional changes and configurations between business, development, testing, and IT operations, in order to achieve Continuous Delivery. Maestro manages process rules, and even handles human (asynchronous) interaction in the workflow. Internal and external environments as well as cloud services can be provisioned in an elastic manner, and with controls to limit exposure to additional costs or unintended system utilization.
Examples of customers’ DevOps Orchestration projects include:
- Fortune 100 Financial Services company is processing thousands of builds per day
- National Healthcare provider is leading a world-wide terminology development and release project
- Fortune 50 Banking company streamlining artifact management across globally distributed teams
As software development evolves with Agile and Lean methods, MaestroDev continues to innovate open automation solutions so that customers can more easily utilize the latest open source and proprietary tools, cloud services, and hybrid infrastructures with their development cloud environments.
MaestroDev provides DevOps Orchestration and best practices for enterprise-scale development organizations across a range of industries. A single interface automates task management for Continuous Delivery, Agile development, DevOps, and Cloud Federation. F500 companies rely on MaestroDev to deliver their business-critical applications with more frequency, consistency, and faster time to market.
Headquartered in Manhattan Beach, California, MaestroDev provides product subscriptions and DevOps consulting from five countries around the globe. MaestroDev is a portfolio company of Mission Ventures, a leading early-stage technology venture capital firm, and G2VC, an Asia-based technology investment fund.
About the Cool Vendors
Gartner does not endorse any vendor, product or service depicted in our research publications, and does not advise technology users to select only those vendors with the highest ratings. Gartner research publications consist of the opinions of Gartner’s research organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose.
Who is John Galt?
As DevOps continues to be defined and debated, what is undeniable is that change is hard — as John Galt tried to show her, and as Dagny Taggart eventually conceded in Ayn Rand’s Atlas Shrugged — and especially so for large and distributed enterprise teams. DevOps evangelists are passionate about benefits and critics challenge origins, but the end of the DevOps discussion is the same; if we agree that more communication between developers and IT operations produces better software, then the discussion should focus on “How?”
As MaestroDev works with our customers and prospects, one consistent request of both our consulting work and our Maestro product is how to facilitate the best practices that are discussed in blogs, lunches, and sprints. So there is the question; How do we implement the DevOps ideas we have?
The answer is what we call DevOps Orchestration. Automating tasks and tools that span the DevOps lifecycle are a first step. An extension of Continuous Integration and Delivery, it describes the automation of tasks insofar as they are set up the first time. But DevOps Orchestration also prescribes the “How” of daily interaction between groups. What is needed is a common location and mechanism to communicate and share the very best practices that DevOps promotes, and their unique details for each task, team, and project.
Maestro excels at DevOps Orchestration by providing a central location for this bi-directional communication and abstracting the logic away from the tools themselves with a tool-agnostic task-based mechanism which captures the “language” of DevOps interactions between developer, testing, and operations groups, and even allows manager approvals to interact with the automated processes. DevOps Orchestration accelerates the pace of change, fosters best practices, and removes friction from the best intentions of teams who, ultimately, agree on the same end-goals.
Maestro DevOps Orchestration automates your existing installed toolset from source code management through build, test, deploy, and environment management — all from a single screen. Ease-of-use gains alone promote DevOps adoption by making it easier to capture task details of all types in a single location for the author, but also because all other users know there is a single place to find / review / change task definitions and configurations. Great things can start from a single place.