Transforming healthcare in the cloud through data, analytics, and machine learning

From electronic health records to medical imaging, healthcare is an industry with an unprecedented amount of data. At Google Cloud, we want to help more healthcare organizations turn this data into health breakthroughs, through better care and more streamlined operations. Over the past year, we’ve enhanced Google Cloud offerings with healthcare in mind, expanded our compliance coverage, and welcomed new customers and partners. Here’s a look at a few milestones along the way.Welcoming new healthcare customers to Google CloudThe challenges of healthcare are increasingly data challenges—creating it, storing it, and analyzing it to find meaningful insights. This year we welcomed many new healthcare customers to Google Cloud, and we’re continually inspired by how these customers use data to benefit both patients and providers. Here are a few examples:National Institutes of Health (NIH) is bringing the power of Google Cloud to biomedical research as a part of their STRIDES (Science and Technology Research Infrastructure for Discovery, Experimentation, and Sustainability) Initiative. As NIH’s first industry partner on this initiative, Google Cloud made some of the most important NIH-funded datasets available to users with appropriate privacy controls and have helped to simplify access to these datasets.The BARDA DRIVe Solving Sepsis initiative is partnering with a research consortium consisting of Emory University School of Medicine, Massachusetts General Hospital (MGH), University of California San Diego (UCSD) School of Medicine, and Atlanta’s Grady Health System to leverage Google Cloud to develop interoperable learning software for early prediction of sepsis in hospital intensive care units. Now DRIVe can help develop and implement that platform to reduce the approximately 270,000 deaths from sepsis in the United States each year.Hurley Medical Center is increasing operational efficiencies, reducing costs and improving patient outcomes by moving to G Suite from on-premises productivity software and email. Moving to G Suite has saved the organization $150,000 in annual software costs.Hunterdon Healthcare uses G Suite to improve collaboration and efficiency, reclaiming 30% of caregivers’ time for patient interactions while reducing costs by $1.3 million over three years.Imagia is leveraging GCP in its mission to help predict patient outcomes and detect disease specific markers from imaging data. With GCP, the company has reduced test processing time from 16 hours to one hour, and has improved time to discovery for researchers.Wellframe uses GCP to power their platform that connects people and care teams, helping them build trusted relationships that drive early interventions. Automating care intelligence empowers Wellframe providers to scale care delivery and optimize care strategy, which has already resulted in an 80 percent increase in weekly patient care plan engagement. We’re excited to see how these and other organizations in the healthcare space utilize data to solve their most pressing challenges.Working with partners for better patient outcomesOur Google Cloud partners play a critical role in helping healthcare providers and organizations embrace and evolve their cloud strategies. Today, we are pleased to announce several new partnerships established to accelerate our commitment to data interoperability.Our relationship with Health Level 7 (HL7), an international standards body for clinical data, builds upon our existing work with the FHIR Foundation to include the broader set of standards managed by the organization. Representatives from Google are joining the standards community.By partnering with the SMART Advisory Council, a group designed to facilitate applications integrated directly into electronic health records, Google Cloud developers will be able to share feedback to improve the SMART specification and help maintain a robust set of tools for application designers, engineers, and users.As a partner of Rock Health, an industry leader in digital health research and new venture support, we will incorporate integration requirements from novel and fast-growing companies, share best practices for scalable and compliant product development around the world, and consult with investors, industry executives, regulators, legislators, and academics shaping the future of digital health.MITRE, a not-for-profit organization that operates federally funded research and development centers, is collaborating with Google Cloud to give developers access to SyntheticMass through Cloud Healthcare API and Apigee Edge. SyntheticMass is a population-level, FHIR-formatted dataset that contains realistic but fictional residents of the state of Massachusetts. It statistically mirrors the real population in terms of demographics, disease burden, vaccinations, medical visits, and social determinants, which makes it a risk-free environment for experimenting and exploring new healthcare solutions.  SyntheticMass is generated by Synthea, an open-source, synthetic patient generator that models the medical history of patients. The FHIR dataset will be made publicly available to developers soon.We’ve also made great strides with other technology partners within the healthcare ecosystem. Novo Nordisk selected the medical-grade BrightInsight platform, which is hosted on GCP, to build and operate digital health solutions for diabetes patients and securely manage millions of its smart medical devices and the corresponding data within a regulatory-compliant environment.Flywheel is integrating Google’s Healthcare API, as well as BigQuery and AutoML Vision, with their platform to capture multi-modality images and data, boost the productivity of data classification, and securely collaborate with peers to manage analysis and metadata.Life Image and the Athena Breast Health Network at the University of California selected Mammosphere on GCP for its breakthrough WISDOM Study to determine the optimal frequency and methods of breast cancer screening. Life Image is also using our Healthcare API to bridge the gap between care systems and applications built on Google Cloud.Our partnership with Imprivata, the healthcare IT security company, makes it possible for Chrome devices to work seamlessly with Imprivata’s single sign-on and virtual desktop access platform for healthcare. This will enable secure mobile workstations and patient devices.Elastifile launched Elastifile Cloud File Service, a fully-managed file storage service. With scalable, high-performance, pay-as-you-go file storage at their fingertips, healthcare organizations are empowered to burst data-intensive NFS workloads to Google Cloud for accelerated processing.Unlocking the power of data with our productsAt Google Cloud, we’re always looking to expand our healthcare product offerings—and help our customers do the same. Many organizations host datathon events as a way to collaboratively tackle data challenges and quickly iterate on new solutions or predictive models. To help, we’re announcing the Healthcare Datathon Launcher, which provides a secure computing environment for datathons. And if you want to learn how to do clinical analysis, University of Colorado Anschutz Medical Campus has just launched a Clinical Data Science specialization on Coursera, with 6 online courses, giving you hands-on experience with Google Cloud.Additionally, we’ve enhanced our healthcare offerings in numerous ways over the past year, including making radiology datasets publicly availableto researchers with the Google Healthcare API, and hosting over 70 public datasets from the Cancer Imaging Archive (TCIA) and NIH. With these datasets, researchers can quickly begin to test hypotheses and conduct experiments by running analytic workloads on GCP—without the need to worry about IT infrastructure and management. Helping healthcare providers meet their security and compliance needsSecurity and compliance are fundamental concerns for healthcare providers, and are among Google Cloud’s topmost priorities. To date, more than three dozen Google Cloud Platform products and services enable HIPAA compliance, including Compute Engine, Cloud Storage, BigQuery, and most recently, Apigee Edge and AutoML Natural Language. In addition, Google Cloud Platform and G Suite are HITRUST CSF certified. Google Cloud is also committed to supporting compliance with requirements such as the GDPR, PIPEDA, and more. We recently published a whitepaper on Handling Healthcare Data in the UK that provides an overview of NHS information governance requirements.This week at HIMSS, throughout speaking sessions and within our booth (#2221), we’re highlighting the inspiring ways our customers and partners are using Google Cloud to positively transform healthcare . We’ll also be sharing more on products and services we’ve designed specifically for our healthcare customers’ needs and with security and compliance top of mind. Finally, we are thrilled that Aashima Gupta, Google Cloud’s Director of Healthcare Solutions, has been recognized by HIMSS as one of 2019’s most influential women in health IT for her contributions in this space. Come see her and our many other speakers throughout the event.
Quelle: Google Cloud Platform

Jib 1.0.0 is GA—building Java Docker images has never been easier

Last year, we set out to make it easier for developers to containerize their Java applications. We had noticed that developers were having a hard time with the existing tools. Build times were slow. Dockerfiles were messy. The containers were too large.We built Jib to change that. Jib is an open-source tool that containerizes your Java applications with minimal effort—no need to install Docker, run a Docker daemon, or even write a Dockerfile. Simply apply the plugin to your Maven or Gradle build, and run the build. Jib uses the build information to automatically containerize your applications quickly and efficiently. With Jib, building Java containers is now as easy as packaging a JAR.We announced Jib beta last year, and since then, we’ve received feedback and contributions from our community that have helped us make the containerization experience even better. Today, we’re announcing the general availability of Jib 1.0.0, making it fully ready and stable for production use.We’ll cover the major changes below, including support for WAR projects, integration with Skaffold, and Jib Core, a new container building library for Java.What’s in Jib 1.0?Dockerize WAR projectsWeb applications in Java are often packaged as WAR files. Jib can now containerize WAR projects as well, with no extra configuration. Simply run:Maven:$ mvn package jib:buildGradle:$ gradle jibThe default application server in the container is Jetty, but you can also use a different server like Tomcat by configuring the base image and appRoot:Maven (pom.xml):Gradle (build.gradle):See details for dockerizing Maven WAR projects and dockerizing Gradle WAR projects.Integration with Skaffold for Java on Kubernetes developmentSkaffold is a command-line tool for continuous development on Kubernetes. We integrated Skaffold with Jib to make developing on Kubernetes seamless. Jib is now available as a builder in Skaffold.To start using Skaffold with your Java project, install Skaffold and add a skaffold.yaml to your project:Make sure you have your Kubernetes manifests in a k8s/ directory and that the image reference in a Container spec matches gcr.io/my-project/my-java-image. See the Skaffold repository for an example.Then, start Skaffold’s continuous development with:$ skaffold dev –trigger notifySkaffold eliminates the tedious steps involved in rebuilding and redeploying your application for every change you make. Skaffold does this by containerizing your application with Jib and deploying it to your Kubernetes cluster whenever it detects a change. You can now focus on what you really care about—writing code.Jib Core: build Docker images in JavaJib runs on our own general-purpose library for building container images, which we’ve released as Jib Core along with some API refinements. Now you can use Jib as more than just Maven and Gradle plugins—you can now build containers in Java without a Docker daemon, for any application.Start using Jib Core by adding it to your project:Maven (pom.xml):Gradle (build.gradle):The following is an example that builds a simple Docker image. It starts with a base image, adds a single layer, sets the entrypoint, and pushes to a remote registry with just a few lines of code:We welcome you to use Jib Core to build your own custom containerization solutions. Feel free to share with us any projects you’re using Jib Core with on our Gitter channel. Check out some other examples of how to use Jib Core, like from a Gradle build script.All that, and the same simple containerization experienceContainerizing a Java application with Jib is still just as easy as before. If you are using Maven, add the plugin to your pom.xml:To build and push the image to a container registry, use:Or, to build to a Docker daemon, use:You can now even containerize your application without touching your pom.xml just by calling:For more details, see the Jib Maven Quickstart.When using Jib for Gradle, add the plugin to your build.gradle:You can then containerize your application to a container registry with:Or, containerize to a Docker daemon with:For more details, see the Jib Gradle Quickstart.Get started todayWe want everyone to use Jib to simplify and accelerate their Java development. To get started with Jib, check out our samples and Codelabs for deploying a Spring Boot application to Kubernetes or deploying a Micronaut application to Kubernetes. Jib works with most Docker registry providers and hosted registries; try it out and let us know what you think at github.com/GoogleContainerTools/jib.
Quelle: Google Cloud Platform

python-tempestconf’s journey

For those who are not familiar with the python-tempestconf, it’s a tool for generating a tempest configuration file, which is required for running Tempest tests against a live OpenStack cluster. It queries a cloud and automatically discovers cloud settings, which weren’t provided by a user.
Internal project
In August 2016 config_tempest tool was decoupled from Red Hat Tempest fork and the python-tempestconf repository under the github redhat-openstack organization was created. The tool became an internal tool used for generating tempest.conf in downstream jobs which were running Tempest.
Why we like `python-tempestconf`
The reason why is quite easy. We at Red Hat were (and still are) running many different OpenStack jobs with different configurations which execute Tempest. And there python-tempestconf stepped in. We didn’t have to implement the logic for creating or modifying tempest.conf within the job configuration, we just used python-tempestconf which did that for us. It’s not only about the generating tempest.conf itself, because the tool also creates basic users, uploads an image and creates basic flavors which all of them are required for running Tempest tests.
Usage of python-tempestconf was also beneficial for engineers who liked the idea of not struggling with creating a tempest.conf file from scratch but rather using the tool which was able to generate it for them. The generated tempest.conf was sufficient for running simple Tempest tests.
Imagine you have a fresh OpenStack deployment and you want to run some Tempest tests, because you want to make sure that the deployment was successful. In order to do that, you can run the python-tempestconf which will do the basic configuration for you and will generate a tempest.conf, and execute Tempest. That’s it, isn’t it easy?
I have to admit, when I joined Red Hat and more specifically OpenStack team, I kind of struggled with all the information about OpenStack and Tempest, it was too much new information. Therefore I really liked when I could generate a tempest.conf which I could use for running just basic tests. If I had to generate the tempest.conf myself, my learning process would be a little bit slower. Therefore, I’m really grateful that we had the tool at that time.
Shipping in a package
At the beginning of 2017 we started to ship python-tempestconf rpm package. It’s available in RDO repositories from Ocata and higher. python-tempestconf package is also installed as a dependency of openstack-tempest package. So if a user installs openstack-tempest, also python-tempestconf will be installed. At this time, we also changed the entrypoint and the tool is executed via discover-tempest-config command. However, you could have already read all about it in this article.
Upstream project
By the end of 2017 python-tempestconf became an upstream project and got under OpenStack organization.
We have significantly improved the tool since then, not only its code but also its documentation, which contains all the required information for a user, see here. In my opinion every project which is designed for wider audience of users (python-tempestconf is an upstream project, so this condition is fulfilled), should have a proper documentation. Following python-tempestconf’s documentation should be any user able to execute it, set wanted arguments and set some special tempest options without any bigger problems.
I would say that there are 3 greatest improvements. One of them is the user documentation, which I’ve already mentioned. The second and third are improvements of the code itself and they are os-client-config integration and refactoring of the code in order to simplify adding new OpenStack services the tool can generate config for.
os-client-config is a library for collecting client configuration for using an OpenStack cloud in a consistent way. By importing the library a user can specify OpenStack credentials by 2 different ways:

Using OS_* environment variables, which is maybe the most common way. It requires sourcing credentials before running python-tempestconf. In case of packstack environment, it’s keystonerc_admin/demo file and in case of devstack there is openrc script.
Using –os-cloud parameter which takes one argument – name of the cloud which holds the required credentials. Those are stored in a cloud.yaml file.

The second code improvement was the simplification of adding new OpenStack services the tool can generate tempest.conf for. If you want to add a service, just create a bug in our storyboard, see python-tempestconf’s contributor guide. If you feel like it, you can also implement it. Adding a new service requires creating a new file, representing the service and implementing a few required methods.
To conclude
The tool has gone through major refactoring and got significantly improved since it was moved to its own repository in August 2016. If you’re a Tempest user, I’d recommend you try python-tempestconf if you haven’t already.
Quelle: RDO

Merlin uses IBM Cloud Garage to fast-track new cybersecurity technology

The cybersecurity marketplace is crowded. There are hundreds of vendors with an amazing array of solutions flooding the space, yet many organizations still struggle to stay ahead.
In many companies, everyone is working as hard as they can to plug holes, but there is still a lack of knowledge about how to manage and understand all the tools and how they interact. IT executives are finding that the tools are confusing, too diverse and susceptible to attack. They are left evaluating dozens of tools without the ability to look toward a future roadmap of how they might integrate them.
Building a comprehensive cybersecurity offering
Merlin International, which provides software and solutions for the US federal government, saw the frustration of its clients in spending tremendous capital and time without getting any better at protecting themselves. Clients witnessed the number of tools quadruple without a commensurate ability to see what was coming, prioritize activity or tie back to overall security remediation processes.
That is why Merlin is building a comprehensive cybersecurity offering to improve how security operation centers (SOCs) respond to threats. The solution is based on security operations and analytics platform architecture (SOAPA) and will translate relationships with security software vendors into an ecosystem that will incrementally go after the gaps that exist in most large scale SOCs.
The platform architecture helps with flexibility and speed across multiple applications to address and solve legacy problems.
Building with the IBM Cloud Garage
Merlin partnered with the IBM Cloud Garage to define and build the first minimum viable product (MVP) on IBM Cloud Private (ICP). We chose ICP because it had ready-built functionality the company could use. Future components of the cybersecurity solution will incorporate the resident automation and AI functionality of ICP.
The cybersecurity solution focuses on user-centric designs to provide improved access to actionable data. For instance, the solution started with the concept of augmented asset visibility to enable a security supervisor to quickly gain understanding of the protection status (current and historical) of key threats and vulnerabilities such as anti-virus, malware, DNS, firewall and privileged access. 
The IBM Cloud Garage provided a venue for Merlin to ideate and hypothesize with a talented team of experts that included architects and designers along with stakeholders from across our company. The IBM Design Thinking approach used agile methodology and lean startup techniques to help us visualize our ideas, and our own product development team was able to adopt the tools we learned.
Six weeks to MVP
The MVP build engagement lasted just six weeks and focused on laying a solid foundation for both the user experience and the technical underlying framework. Merlin developed a browser-based dashboard to display data of near-real-time and historical cybersecurity events through various metrics and data visualizations. Users can also drill down into specific data points using dynamic graphs and charts.
In building the cybersecurity solution, we aimed to create scaffolding for an ecosystem that will use clients’ existing toolsets against each other to solve specific use cases. Instead of boiling the ocean, we started with endpoint security, thereby making a junior analyst confident in what is a threat, what action they need to take and how best to take it while leaving a detailed history for compliance.
The IBM Cloud Garage engagement helped us bring a very new, difficult and previously unvalidated technology to market. The cybersecurity solution is expected to be announced and available in the first quarter of 2019.
Explore how the IBM Cloud Garage can help your company.
The post Merlin uses IBM Cloud Garage to fast-track new cybersecurity technology appeared first on Cloud computing news.
Quelle: Thoughts on Cloud