HIMSS 19: Microsoft for Healthcare Innovation Award Winners – Microsoft Industry Blogs

Health innovation award trophies

The winners of the 2019 Microsoft for Healthcare Innovation Awards were announced at HIMSS19 yesterday during the Microsoft Health Forum.  Each year, the awards acknowledge health and life sciences organizations and their technology solution partners that are achieving innovation excellence with a Microsoft-based solution.

We’re always excited to highlight the achievements of our forward-thinking customers and partners as they advance digital transformation in health. Here are the winners in each of the submission categories:

Award Category:  Artificial Intelligence and Machine Learning

NHS Greater Glasgow and Clyde and KenSci

To better understand which patients are at the highest risk of COPD, NHS Greater Glasgow and Clyde worked with KenSci to leverage AI and Machine Learning to predict long-term hospital stays based on clinical history, socio-economic factors and risk to stratify the top 20% high risk patients likely to admit for the first time due to COPD, in order to drive preventive intervention.

Award Category:  Empower Your Care Teams and Employees

Vision Source, LP and Kno2

To meet the needs of populations with diabetes, Vision Source needed to establish a nationwide interoperability network for their 3,350 independent locations. As a result, Vision Source selected Kno2’s Interoperability as a Service, enabling immediate access to over 2 million referring providers through the nation’s major health information networks: Direct, referral networks, care quality, and those connected through Commonwell Health Alliance.

Award Category:  Engage Your Patients & Enable Personalized Care

Premera Blue Cross

Premera Scout™ is an intelligent virtual assistant that helps customers find the information they need to make the most of their health plan. Premera powers this solution using advanced AI from Microsoft Healthcare. Guided by a customer-centered strategy, Premera transforms complicated and confusing experiences to simple and easy ones.

Award Category:  Optimize Clinical Operational Effectiveness & Improve Outcomes

Prediction of Patient Placement (POPP) Team at Boston Children’s Hospital

Boston Children’s Hospital uses Prediction of Patient Placement (POPP), a real time forecasting tool to predict incoming admissions from the Emergency Department. This tool enables proactive coordination of downstream operations in order to reduce transfer wait time. The model uses hospital-specific, historical data and is EHR- and hospital-agnostic.

Award Category:  Outstanding Innovation

St. Jude Children’s Research Hospital and DNAnexus

A partnership between St. Jude, DNAnexus, and Microsoft developed the St. Jude Cloud, a secure cloud-based data-sharing and collaboration environment, to provide researchers access to an extensive public repository of pediatric cancer genomics data, accelerated data mining, analysis and visualization capabilities.

Award Category:  Transform the Care Continuum & Reimagine Healthcare

Johns Hopkins Medicine

Johns Hopkins Medicine developed the Precision Medicine Analytics Platform (PMAP) to empower faculty to make discoveries; improve diagnosis, treatment, and outcomes; and lower the cost of care. PMAP is comprised of two parts: Discovery – for faculty researchers to fuel the discovery of new insights and algorithms; and Care Delivery – after discovery medical validation, promoted for use by other physicians.

Thank you to our judges

In addition to acknowledging the innovative solutions of the award recipients, we would like to thank each of the distinguished judges who reviewed this year’s entries:

  • Ahmad Hashem, MD, PhD, CEO, Boston Biopharma, Inc.
  • Benjamin Rooks, Managing Director, ST Advisors, Inc.
  • Gienna Shaw, Senior Writer, Amendola Communications
  • Jane Sarasohn-Kahn, MA (Econ), MHSA, Health Economist and Advisor, THINK-Health and Health Populi blog
  • Jay Srini, FHIMSS, Chief Strategist, SCS Ventures; Adjunct Associate Professor, SHRS, University of Pittsburgh
  • Keith Fraidenburg, MBA, EVP & COO, CHIME
  • Melinda Richter, Global Head, Johnson & Johnson Innovation, JLABS
  • Michael Docktor, MD, Gastroenterologist, Clinical Director of Innovation @ Boston Children’s Hospital / Harvard Medical School
  • Taren Grom, Founding Partner/Editor, PharmaVOICE
  • Victoria (Vicky) L. Tiase, MSN, RN-BC, Director – Informatics Strategy, New York Presbyterian Hospital

What’s your story?

Congratulations again to our winners. We would love to hear how your health organization is creating better experiences and delivering better care, please share with us through emailFacebook, or Twitter.

Go to Original Article
Author: Steve Clarke

Announcing Windows Admin Center Preview 1902 | Windows Experience Blog

Hello Windows Insiders,
Thank you for your continued interest in Windows Admin Center! This preview release builds on the previous 1812 version and adds new functionality including all-new software defined networking tools in the HCI solution, and one of the top-requested customer features: shared connection lists. For folks that use RDCman, we have published a small script that you may use to export your saved RDCman connections to a .CSV file which you can then import with PowerShell to maintain all your RDCman grouping hierarchy using tags.

We’re excited to release a highly-requested feature: a single connection list that can be shared across all users of a WAC gateway.
To add servers, clusters, and PCs as shared connections, you must be a WAC gateway administrator. Go to WAC Gateway Settings > Shared Connections, and then add servers, clusters, and PC as you normally would. You can tag servers in this pane as well, and these tags will appear for all users. The tags are immutable from the home “All Connections” page, meaning WAC users cannot change tags on shared server connections.

New Tool – Access Control List management (SDN)
With SDN, you can use access control lists (ACLs) to manage data traffic flow using Datacenter Firewall and ACLs on virtual subnets. You can enable and configure Datacenter Firewall rules by creating ACLs that get applied to a virtual subnet.

New Tool – Gateway Connection (SDN)
SDN Gateway is a software-based, multitenant, Border Gateway Protocol (BGP) capable router designed for Cloud Service Providers (CSPs) and Enterprises that host multiple tenant virtual networks using Hyper-V Network Virtualization.
In the Gateway Connection tool, you can manage and monitor your gateway connections in an SDN environment. It supports all three types of gateway connections – IPSEC, GRE and L3.
For more information about Gateways, see https://docs.microsoft.com/en-us/windows-server/networking/sdn/technologies/network-function-virtualization/ras-gateway-for-sdn

New Tool – Logical Network Management (SDN)
VM networks are abstract objects that act as an interface to logical networks. In a virtualized network environment, by using the VM networks, you can abstract virtual machines from the underlying logical network.
In the Logical Network tool, you can manage and monitor your logical network.
For more information about Logical Networks, see https://docs.microsoft.com/en-us/windows-server/networking/sdn/plan/plan-a-software-defined-network-infrastructure

SDN Feature enhancement – Connect VM to VLAN or Virtual Network
Based on customer feedback, now you can choose to connect a VM to a VLAN or a Virtual Network in your SDN environment.

Virtual machines – When adding a new VHD to a VM, and selecting the option to add a new, empty disk, you can’t save your changes. [20420660]
Network – If you have configured an Azure Network Adapter, the value under Microsoft Azure Virtual Network Gateway Address will be formatted as a hyperlink but leads to an invalid address. [20420185]

Registered Insiders may download Windows Admin Center Preview 1902 directly from the Windows Server Insider Preview download page, under the Additional Downloads dropdown. If you have not yet registered as an Insider, see Getting Started with Windows Server on the Windows Insiders for Business portal.

The most important part of a frequent release cycle is to hear what’s working and what needs to be improved, so your feedback is extremely valued. Send us feedback via UserVoice. We also encourage you to visit the Windows Admin Center space on the Microsoft Tech Communities forum to collaborate, share and learn from experts.

All pre-release software made available to you via the Windows Server Insider program are governed by the Insider Terms of Use
No downtime for Hustle-As-A-Service,Dona

Container security tools pitch service mesh integrations

Container security tools have pinned their hopes on service mesh, as the microservices networking stack gains altitude among cloud-native app developers.

Service meshes such as Linkerd, Istio and others offer granular security management and monitoring features, but only for areas of the infrastructure where service mesh sidecar container proxies are deployed. Meanwhile, defense in depth for container security environments is a hot topic, as vulnerabilities such as this week’s disclosure of a runC flaw illustrate.

Enter container security tools, which offer a comprehensive view into container environments inside and outside of the purview of service mesh, as well as security management for service mesh deployments themselves.

“Third-party container security tools can provide coverage for things the mesh doesn’t do,” said Fernando Montenegro, analyst at 451 Research. The Istio service mesh, for example, is focused primarily on application security monitoring at Layer 7, while container security tools can offer in-depth Layer 2 and 3 monitoring.

It’s also a matter of convenience, he said. Third-party tools, such as NeuVector, Twistlock and Aqua Security, offer a complete view of the environment that’s easy to configure, as opposed to Kubernetes network policies, which still require command-line interface and JSON expertise.

Container security tool reinforces service mesh security

Some early service mesh adopters take wide-reaching security considerations into account as they head to production with Kubernetes and tools such as Linkerd 2.

“NeuVector lets us dig down to the port level, where containers talk to each other,” said Christian Hüning, systems architect at Figo.io, a fintech startup in Hamburg, Germany, that plans to put Linkerd 2, Kubernetes and NeuVector into production this month.

Third-party container security tools can provide coverage for things [service] mesh doesn’t do.
Fernando Montenegroanalyst, 451 Research

The company plans to use service mesh integration NeuVector added this week that allows the container security tool to see and manage traffic encrypted within the service mesh with mutual TLS. This will give Figo container security policy enforcement for its entire Kubernetes environment.

“NeuVector sees packets as network traffic hits the container host and forwards them or drops them before they reach the container,” Hüning said. As an added defense, Figo forwards NeuVector’s syslog data to broader security information and event management tools for centralized IT security monitoring.

“Even if someone manages to bring in a compromised container image and start a pod for it, our container security policies would block it from executing network calls,” Hüning said.

NeuVector service mesh UI
NeuVector’s container security tool visualizes network security policy data in service mesh environments.

NeuVector entered the market in 2017 focused on container runtime monitoring, but added container image scanning with version 2.0 in April 2018. That release also added integration that combines image scanning data with information about application artifact dependencies supplied by the JFrog Artifactory repository Figo uses. This combination broadens Figo’s container security posture to include parts of the CI/CD pipeline that are well beyond the scope of service mesh security.

However, Hüning said he hopes NeuVector will expand its list of integration partners to include GitLab.

“In our dev cluster, we’ve had to tell NeuVector to ignore the GitLab namespace, because it was going wild with every change,” he said.

Better GitLab integration is on the roadmap for this year, a NeuVector spokesperson said.

Go to Original Article
Author:

For Sale – Mac Mini (Late 2014) – 1.4GHZ – 4GB – 500GB

Good Afternoon!

After having a little clear out, I’ve got two Mac Minis which are no longer needed… They were in a small office, but have been sat on a shelf since we upgraded a couple of months ago! £220 each including delivery.

They are both 1.4GHZ – 4GB – 500GB, and in mint condition (fully boxed).

Will be sent via courier.

Price and currency: 220
Delivery: Delivery cost is included within my country
Payment method: BACS
Location: Hampshire
Advertised elsewhere?: Not advertised elsewhere
Prefer goods collected?: I have no preference

______________________________________________________
This message is automatically inserted in all classifieds forum threads.
By replying to this thread you agree to abide by the trading rules detailed here.
Please be advised, all buyers and sellers should satisfy themselves that the other party is genuine by providing the following via private conversation to each other after negotiations are complete and prior to dispatching goods and making payment:

  • Landline telephone number. Make a call to check out the area code and number are correct, too
  • Name and address including postcode
  • Valid e-mail address

DO NOT proceed with a deal until you are completely satisfied with all details being correct. It’s in your best interest to check out these details yourself.

Go to Original Article
Author:

What are some common Windows Server 2019 SDN errors?

Even though Microsoft added software-defined networking features to ease the maintenance of complex data centers, administrators can still encounter problems in their deployments.

Software-defined networking (SDN) increases versatility and network performance in the enterprise, but administrators who use Windows Server 2019 SDN risk introducing networking errors. Until Microsoft advances Windows Server 2019 SDN further to ease its deployment burden, administrators must learn how to troubleshoot different errors, and knowing the most common ones can help resolve problems more quickly.

Common errors that can affect SDN deployments

Most problems that crop up in an SDN deployment usually fall into four categories.

  1. API errors. SDN combines multiple software layers for virtualization and communication. Southbound APIs typically support lower-level interfaces, such as OpenFlow or protocols that foster communication between the SDN controller and the network nodes. Northbound APIs usually handle communication between the controller and higher-level layers, such as management tools and applications. If the controller invokes the APIs improperly or calls faulty policies, such as with task automation, the API call will fail and produce errors. Administrators will need a detailed log, including the source and destination of the faulty call, to uncover the cause of the API errors.
  2. Policy errors. Automation is a central element of SDN, enabling complex tasks to be invoked quickly and consistently. Automation requires clearly delineated policies that guide — or prevent — certain actions. Administrators often create these policies centrally, and they then get distributed or shared between devices across the network. The SDN controller usually delivers policies to Hyper-V hosts. Issues with delivery or delay or update failures can produce policy errors.

Administrators must ensure the configuration of each network device is optimal to avoid data flow problems.

  1. Configuration errors. Complex LAN arrangements can involve numerous physical and virtual network devices. Administrators must ensure the configuration of each network device is optimal to avoid data flow problems. Any misconfiguration can cause delays or dropped packets that generate errors. Administrators who troubleshoot SDN network issues can check logs for any recent device settings changes to uncover configuration drift or incorrect settings on a device replacement. Repeated configuration issues may also indicate the need for improved configuration change management or workflow management to avoid disruptions.
  2. Hardware errors. Administrators can trace SDN errors to faults in low-level network hardware, such as a faulty network interface controller, or to problems with network cabling. In some cases, issues with functionality, such as with virtual machine queues, might require a settings adjustment, while problems with faulty hardware might require a replacement.

Dig Deeper on Enterprise infrastructure management

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever’s puzzling you.

Go to Original Article
Author:

Microsoft, Moovit, and TomTom team up for multi-modal transport platform

A triumvirate of tech companies today announced what they’re touting as the “world’s first truly comprehensive multi-modal trip planner.”

Taking the stage at the Move mobility conference in London, executives from Microsoft, TomTom, and Moovit outlined how they’re pooling their various transport, data, and cloud processing smarts so developers can integrate more extensive transport options into their own applications.

“Over the last few years, cities have experienced rising urban sprawl, where residents of metropolitan areas have been pushed out toward suburban areas, often beyond the limits of public transit lines,” noted Azure Maps head Chris Pendleton. “With most jobs still residing in densely populated cities, the typical commute is becoming multi-modal.”

Moovit, for the uninitiated, constitutes two core elements: a consumer-facing app that gives travelers the easiest way to get around a city and a mobility-as-a-service (MaaS) platform that provides municipalities with data and analytics to improve city transport infrastructure.

A few months back, Moovit and Microsoft announced a partnership that would allow developers who use Azure Maps to hook into Moovit’s transit data. Last week, GPS navigation stalwart TomTom announced an expanded tie-up with Microsoft, one that will bring TomTom’s extensive maps and traffic data into the Azure fold — in effect, TomTom will serve as the primary location data provider for Microsoft’s cloud platform, Bing Maps, and Cortana.

Fast-forward to today, and the three companies are now pooling their respective capabilities for an urban transport offering that any third-party developer can leverage.

“This will lead to commuters having the best option to plan a trip [by] combining legs on public transit, ride-sharing, bike, or scooter and other legs by car, including finding available parking lot spaces in real time,” added Moovit cofounder and CEO Nir Erez.

Through Azure Maps, Microsoft’s developer-focused mapping platform, users will be able to access not only Moovit’s public transit data, but also TomTom’s real-time driving and parking data. So developers will be able to include the full gamut of transport options inside their own apps — including buses, trains, metros, ferries, carpooling, bike-sharing, and now driving and parking.

“Blending TomTom’s specific auto and parking lot data with Moovit’s multi-modal trip planning gives Azure Maps an unprecedented view of every facet of urban mobility,” Pendleton continued. “No one else has provided this comprehensive level of service in one solution.”

Multi-modal

We’ve seen a growing number of integrations between transport service providers, and the term “multi-modal” is springing up more frequently in urban mobility conversations.

Back in 2016, Moovit combined its public transport data with Uber to find the best route in dozens of cities. A year later, Uber revealed that it would make it easier for its ride-hailing customers to keep tabs on other transit options by displaying real-time public transport data alongside private vehicles. Earlier this month, Uber revealed it was doubling down on efforts to show full transit options directly inside the Uber app.

Elsewhere, navigation giant Here recently launched a new social transport app for planning and sharing rides, merging all modes of transport, including public, private, and personal, into a single platform.

Tying these myriad transport options together is maps and data, which is the currency for urban mobility companies. TomTom was pretty much blindsided by the arrival of iOS and Android a decade ago, with smartphones enabling portable navigation in everyone’s pockets. In recently times, TomTom has been striving to refocus its core business to better compete with Google in maps and navigation, and it recently offloaded its telematics unit for $1 billion to help with this push.

Today’s announcement, alongside TomTom’s broader Azure partnership announced last week, should go some way toward helping the company gain more traction.

“Location data has become more relevant and important than ever before, and no one knows this better than TomTom,” added managing director Anders Truelsen.

Go to Original Article
Author: Steve Clarke

Linkerd vs. Istio fray dominates service mesh battle

Linkerd vs. Istio is the main event in the battle of service mesh heavyweights. And, pound for pound, underdog Linkerd has held its own against the Google goliath so far.

It’s still early for service mesh adoption among mainstream enterprises, many of which still struggle with Kubernetes and containers in production. A microservices infrastructure built on containers is a key precursor to service mesh, a set of network orchestration tools that provide fine-grained control over telemetry, security and network provisioning.

Linkerd, an open source project, was the first service mesh available in 2016, and the revamped Linkerd 2 — initially dubbed Conduit — arrived in 2018, with a focus on Kubernetes integration. Another open source project, Istio, was also released in 2018 by powerful backers, such as Google, IBM and Lyft, and soon captured much of the market’s attention.

Initially, service mesh was the domain of web-scale companies, such as Netflix and Twitter, but it’s headed for mainstream enterprise use.

“The complexities of east-west traffic management are growing for anyone with a reasonably large microservices footprint,” said Fintan Ryan, analyst at Gartner. “Service mesh will become essential to microservices, and more people are getting serious about evaluating it.”

There are numerous service mesh competitors in the market, with products from HashiCorp, Kong and NGINX, among others. But Linkerd 2 and Istio both focus on integration with Kubernetes. And by virtue of the container orchestration tool’s momentum, they are at the center of the service mesh conversation in its early days.

Linkerd vs. Istio: Simplicity vs. versatility

Linkerd 2 doesn’t yet match Istio’s features. Linkerd 2.2, released this week, introduces automatic network request retries and timeouts and moves sidecar proxy auto-injection from an experimental phase to a fully supported feature. Both features were in Istio since its 1.0 release in July 2018. Mutual TLS (mTLS) encryption, a popular application security feature for service mesh early adopters, remains experimental in Linkerd 2.2.

Linkerd 2 is also more limited in its ability to perform dynamic tracing, and Linkerd 2’s tight integration of the control plane, service discovery and sidecar layers limits configuration choices, compared with what’s offered by Istio.

But, as IT pros experiment with service mesh deployments, the more significant difference is they’ve only been able to get one of these utilities to work, even just to kick the tires in test environments.

“[Istio] was complex to install, and you need to define external calls,” said Jerome Mirc, senior software developer for Expedia Inc., an online travel service provider based in Bellevue, Wash. “It was not very friendly for the developer to know which server they need to be connected to and which port to open.”

By contrast, Linkerd 2 was simple to install and use for Mirc, who primarily wants to use service mesh for advanced monitoring and telemetry on microservices apps. This also happens to be Linkerd 2’s primary focus of development.

“Service mesh gives us a real-time view into microservices performance, and we can react quickly instead of waiting for Grafana or Graphite to update, or to check Splunk logs,” Mirc said.

Linkerd 2 doesn’t yet include tracing gRPC traffic on a TCP transport layer, but Mirc said he will try to bridge that gap with another tool. Otherwise, Linkerd 2 meets Mirc’s needs for granular microservices monitoring.

Another early advantage for Linkerd 2 is its low performance overhead. One published benchmark test showed significantly higher queries-per-second performance on Linkerd vs. Istio, and this has been the anecdotal experience for early service mesh adopters, as well.

“Linkerd is very fast for a user space service mesh,” said Christian Hüning, systems architect at Figo.io, a fintech startup in Hamburg, Germany, which plans to put Linkerd 2 into production this month alongside its first deployment of Kubernetes. “Its data plane is written in Rust, a very low-level and efficient language, and is decentralized, which avoids bottlenecks with control components.”

While mTLS officially remains an experimental feature, it already works well for Figo, Hüning added.

Istio maintainers acknowledge manageability problems and formed the User Experience Working Group to address those issues. A Google spokesperson said users have reduced performance overhead by as much as 50% when they turned off Istio’s Mixer policy feature, under which each sidecar proxy calls out to a centralized Mixer to validate every network call.

Linkerd 2.2 UI
Linkerd 2.2 UI offers visibility into Kubernetes namespaces.

Istio sews up market buzz, momentum

Linkerd 2 has been a boon for users frustrated with Istio, and increased competition in this market has validated the idea that service mesh is a mainstream enterprise technology, which also helps Linkerd.

The complexities of east-west traffic management are growing for anyone with a reasonably large microservices footprint. … More people are getting serious about evaluating [service mesh].
Fintan Ryananalyst, Gartner

Still, the odds are long that Linkerd will ultimately rule the service mesh market. Istio has a close relationship with Kubernetes powerhouses and cloud service providers, which may sway user decisions more effectively than any technical consideration.

Even early service mesh adopters who turned to Linkerd 2 for its simplicity view Istio as a strong contender when packaged and hosted by cloud service providers such as Google Kubernetes Engine (GKE).

“We started going down the path of Istio on AWS, but after three months, we never got anywhere. It would send traffic only to some pods, or would get no traffic but a heartbeat,” said a CTO for an analytics startup on the East Coast. Linkerd 2, meanwhile, installed with one command and connected all pods to the mesh with no manual configuration, he said.

However, the CTO, who requested anonymity because he hasn’t yet made a final decision, said he’s still torn between Linkerd 2 in a self-hosted AWS Kubernetes environment and a move to GKE with Istio as a service.

This type of consideration will ultimately win the market for Istio, some analysts predict.

“Debates like this often come down to who the champions of a particular technology are,” said Tom Petrocelli, analyst at Amalgam Insights in Arlington, Mass. “Linkerd’s main champion is Buoyant, while Istio seems to have captured the major vendor mindshare, with IBM, Red Hat and Google all looking at Istio as the way to go.”

Expedia’s Mirc said it’s still uncertain which service mesh will end up in production for the company at large, particularly if AWS launches a hosted Istio service to compete with Google’s.

“We need to do performance testing to see if we’re happy with the overhead for Linkerd, and every team makes its own decisions about what to use,” Mirc said. “I don’t know what the wider company will use. It’s difficult for a small team to push a specific tool.”

Go to Original Article
Author:

For Sale – M-ITX Desktop Computer – Intel Atom – 2GB DDR3 Ram – 500GB Hard Drive – Windows 7 Pro

I have a Mini-ITX build for sale.

The motherboard and case are new, never used before and the ram was taken from another machine, the hard drive has been used before but is in full working order.

Running Windows 7 Professional already activated with a key.

It does have a slot for a slimline DVD drive.

Specs

Mini-ITX case
Jetway Mini-ITX NC9KDL-2550 Motherboard
2GB DDR3 Ram
Seagate 500GB Hard Drive
Intel Atom 1.86Ghz CPU
PS/2 Mouse
PS/2 Keyboard
HDMI
VGA
USB 2.0
2 X Ethernet
SPDIF

Power cable included.

Price and currency: 40
Delivery: Delivery cost is included
Payment method: BT
Location: Leeds
Advertised elsewhere?: Advertised elsewhere
Prefer goods collected?: I have no preference

______________________________________________________
This message is automatically inserted in all classifieds forum threads.
By replying to this thread you agree to abide by the trading rules detailed here.
Please be advised, all buyers and sellers should satisfy themselves that the other party is genuine by providing the following via private conversation to each other after negotiations are complete and prior to dispatching goods and making payment:

  • Landline telephone number. Make a call to check out the area code and number are correct, too
  • Name and address including postcode
  • Valid e-mail address

DO NOT proceed with a deal until you are completely satisfied with all details being correct. It’s in your best interest to check out these details yourself.

Go to Original Article
Author: