Publicado el Deja un comentario

Amazon EC2 R6a instances now available in Canada (Central)

Starting today, the memory-optimized Amazon EC2 R6a instances are now available in Canada (Central) region. R6a instances are powered by third-generation AMD EPYC processors, and deliver up to 35% better price performance than comparable R5a instances. These instances offer 10% lower cost than comparable x86-based EC2 instances.

With this additional region, R6a instances are available in the following AWS Regions: US East (Northern Virginia, Ohio), US West (Oregon, N. California), Asia Pacific (Mumbai, Hyderabad, Singapore, Sydney, Tokyo), Canada (Central), and Europe (Frankfurt, Ireland). These instances can be purchased as Savings Plans, Reserved, On-Demand, and Spot instances. To get started, visit the AWS Management Console, AWS Command Line Interface (CLI), and AWS SDKs. To learn more, visit the R6a instances pages.

 

​Starting today, the memory-optimized Amazon EC2 R6a instances are now available in Canada (Central) region. R6a instances are powered by third-generation AMD EPYC processors, and deliver up to 35% better price performance than comparable R5a instances. These instances offer 10% lower cost than comparable x86-based EC2 instances. With this additional region, R6a instances are available in the following AWS Regions: US East (Northern Virginia, Ohio), US West (Oregon, N. California), Asia Pacific (Mumbai, Hyderabad, Singapore, Sydney, Tokyo), Canada (Central), and Europe (Frankfurt, Ireland). These instances can be purchased as Savings Plans, Reserved, On-Demand, and Spot instances. To get started, visit the AWS Management Console, AWS Command Line Interface (CLI), and AWS SDKs. To learn more, visit the R6a instances pages.  

Publicado el Deja un comentario

Amazon Timestream for InfluxDB Adds Read Replica support

Amazon Timestream for InfluxDB now supports Read Replicas, enabling customers to scale their read operations across multiple instances and Availability Zones. Customers can activate a Read Replica via the AWS Marketplace from the Timestream AWS Management Console while creating a Timestream for InfluxDB instance.

Adding Read Replicas allow customers to support higher read throughput by distributing read requests across multiple database instances while maintaining a single write endpoint. This helps customers meet the demands of read-intensive workloads, such as real-time analytics and monitoring applications, and improve application performance and availability. Customers can create a Multi-AZ Read Replica cluster with just a few clicks in the AWS Management Console.

Support for Timestream for InfluxDB Read Replicas is available the following Timestream for InfluxDB Regions: US East (Ohio), US East (N. Virginia), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Milan), Europe (Paris), and Europe (Stockholm). To learn more about Amazon Timestream for InfluxDB, please refer to our user guide.

You can create a Amazon Timestream for InfluxDB Read Replicas cluster from the Amazon Timestream console, AWS Command line Interface (CLI), or SDK, and AWS CloudFormation. To learn more about the Read Replica Cluster for Amazon Timestream for InfluxDB, visit the product page, documentation, and pricing page.

 

​Amazon Timestream for InfluxDB now supports Read Replicas, enabling customers to scale their read operations across multiple instances and Availability Zones. Customers can activate a Read Replica via the AWS Marketplace from the Timestream AWS Management Console while creating a Timestream for InfluxDB instance. Adding Read Replicas allow customers to support higher read throughput by distributing read requests across multiple database instances while maintaining a single write endpoint. This helps customers meet the demands of read-intensive workloads, such as real-time analytics and monitoring applications, and improve application performance and availability. Customers can create a Multi-AZ Read Replica cluster with just a few clicks in the AWS Management Console. Support for Timestream for InfluxDB Read Replicas is available the following Timestream for InfluxDB Regions: US East (Ohio), US East (N. Virginia), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Milan), Europe (Paris), and Europe (Stockholm). To learn more about Amazon Timestream for InfluxDB, please refer to our user guide. You can create a Amazon Timestream for InfluxDB Read Replicas cluster from the Amazon Timestream console, AWS Command line Interface (CLI), or SDK, and AWS CloudFormation. To learn more about the Read Replica Cluster for Amazon Timestream for InfluxDB, visit the product page, documentation, and pricing page.  

Publicado el Deja un comentario

Dynamically update your running EMR cluster with reconfiguration for instance fleets

Amazon EMR on EC2 now supports real-time update of application configurations for EMR instance fleets without requiring cluster termination or restart. With this feature, customers can now dynamically adjust application configurations, such as Spark’s executor memory, YARN’s resource allocation, and HDFS settings seamlessly, on a running cluster, minimizing interruptions to your workloads. This is particularly useful for adjusting resource allocation and fine-tune applications to match data processing and job performance requirements, while ensuring optimal resource utilization.

Amazon EMR is a cloud big data platform for data processing, interactive analysis, and machine learning using open-source frameworks such as Apache Spark, Apache Flink, and Trino. Previously, you had to terminate and relaunch instance fleet clusters with new configurations. This process resulted in downtime, increased operational effort, and delayed workflow adjustments. With support for reconfiguration, EMR dynamically applies the updated configurations on cluster nodes on a rolling basis while ensuring cluster stability and resource availability. It provides notifications to customers via Amazon CloudWatch and EMR events. In the event of a failure or an incompatible update, EMR rolls back the changes to ensure your cluster remains operational. You can continue to run workloads on the cluster during the update process.

You can leverage this feature on all EMR 5.21 and later releases using AWS CLI, or API. This capability is available in all AWS Regions, including the AWS GovCloud (US) Regions, where Amazon EMR on EC2 is available. To learn more, please refer to the documentation here.

 

​Amazon EMR on EC2 now supports real-time update of application configurations for EMR instance fleets without requiring cluster termination or restart. With this feature, customers can now dynamically adjust application configurations, such as Spark’s executor memory, YARN’s resource allocation, and HDFS settings seamlessly, on a running cluster, minimizing interruptions to your workloads. This is particularly useful for adjusting resource allocation and fine-tune applications to match data processing and job performance requirements, while ensuring optimal resource utilization. Amazon EMR is a cloud big data platform for data processing, interactive analysis, and machine learning using open-source frameworks such as Apache Spark, Apache Flink, and Trino. Previously, you had to terminate and relaunch instance fleet clusters with new configurations. This process resulted in downtime, increased operational effort, and delayed workflow adjustments. With support for reconfiguration, EMR dynamically applies the updated configurations on cluster nodes on a rolling basis while ensuring cluster stability and resource availability. It provides notifications to customers via Amazon CloudWatch and EMR events. In the event of a failure or an incompatible update, EMR rolls back the changes to ensure your cluster remains operational. You can continue to run workloads on the cluster during the update process. You can leverage this feature on all EMR 5.21 and later releases using AWS CLI, or API. This capability is available in all AWS Regions, including the AWS GovCloud (US) Regions, where Amazon EMR on EC2 is available. To learn more, please refer to the documentation here.  

Publicado el Deja un comentario

Amazon Aurora PostgreSQL zero-ETL integration with Amazon Redshift now available in 18 additional regions

Amazon Aurora PostgreSQL-Compatible Edition zero-ETL integration with Amazon Redshift is now supported in 18 additional regions, enabling near real-time analytics and machine learning (ML) using Amazon Redshift. With this launch, Aurora PostgreSQL zero-ETL integration with Amazon Redshift is supported in all AWS commercial regions where Amazon Redshift is supported.

Zero-ETL integration with Amazon Redshift enables near real-time analytics and machine learning (ML) using Amazon Redshift to analyze petabytes of transactional data from Aurora. Within seconds of transactional data being written into Amazon Aurora PostgreSQL-Compatible Edition, zero-ETL seamlessly makes the data available in Amazon Redshift, removing the need to build and manage complex data pipelines that perform extract, transform, and load (ETL) operations.

Amazon Aurora PostgreSQL zero-ETL integration with Amazon Redshift is available for Aurora PostgreSQL version 16.4 and higher in US West (N. California), Africa (Cape Town), Asia Pacific (Hyderabad), Asia Pacific (Jakarta), Asia Pacific (Melbourne), Asia Pacific (Osaka), Asia Pacific (Seoul), Canada (Central), Canada West (Calgary), Europe (London), Europe (Milan), Europe (Paris), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), Middle East (Bahrain), Middle East (UAE), South America (São Paulo). For all regions supported by the Aurora PostgreSQL zero-ETL integration, see the supported AWS regions.

To learn more and get started with zero-ETL integration, visit Amazon Aurora zero-ETL integration with Amazon Redshift and the getting started guides for Aurora and Amazon Redshift.
 

 

​Amazon Aurora PostgreSQL-Compatible Edition zero-ETL integration with Amazon Redshift is now supported in 18 additional regions, enabling near real-time analytics and machine learning (ML) using Amazon Redshift. With this launch, Aurora PostgreSQL zero-ETL integration with Amazon Redshift is supported in all AWS commercial regions where Amazon Redshift is supported. Zero-ETL integration with Amazon Redshift enables near real-time analytics and machine learning (ML) using Amazon Redshift to analyze petabytes of transactional data from Aurora. Within seconds of transactional data being written into Amazon Aurora PostgreSQL-Compatible Edition, zero-ETL seamlessly makes the data available in Amazon Redshift, removing the need to build and manage complex data pipelines that perform extract, transform, and load (ETL) operations. Amazon Aurora PostgreSQL zero-ETL integration with Amazon Redshift is available for Aurora PostgreSQL version 16.4 and higher in US West (N. California), Africa (Cape Town), Asia Pacific (Hyderabad), Asia Pacific (Jakarta), Asia Pacific (Melbourne), Asia Pacific (Osaka), Asia Pacific (Seoul), Canada (Central), Canada West (Calgary), Europe (London), Europe (Milan), Europe (Paris), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), Middle East (Bahrain), Middle East (UAE), South America (São Paulo). For all regions supported by the Aurora PostgreSQL zero-ETL integration, see the supported AWS regions. To learn more and get started with zero-ETL integration, visit Amazon Aurora zero-ETL integration with Amazon Redshift and the getting started guides for Aurora and Amazon Redshift.    

Publicado el Deja un comentario

AWS CDK releases L2 construct support for Amazon Data Firehose delivery streams

AWS Cloud Development Kit (AWS CDK) now includes L2 construct support for Amazon Data Firehose delivery streams, enabling developers to define and deploy streaming data infrastructure as code. This new capability allows you to programmatically configure delivery streams that automatically deliver real-time data to destinations like Amazon S3.

With this addition to AWS CDK, you can define sophisticated streaming architectures using familiar programming languages like TypeScript, Python, Java, and .NET. The module simplifies the process of setting up fully-managed delivery streams that push data to your desired destinations on a regular cadence, making it easier to build data lakes, enable real-time analytics, and create data archival solutions.

To learn more about using Amazon Data Firehose with AWS CDK, see the AWS CDK documentation and the Amazon Data Firehose Developer Guide. You can also explore sample applications and use cases on the AWS CDK Workshop website.

 

​AWS Cloud Development Kit (AWS CDK) now includes L2 construct support for Amazon Data Firehose delivery streams, enabling developers to define and deploy streaming data infrastructure as code. This new capability allows you to programmatically configure delivery streams that automatically deliver real-time data to destinations like Amazon S3. With this addition to AWS CDK, you can define sophisticated streaming architectures using familiar programming languages like TypeScript, Python, Java, and .NET. The module simplifies the process of setting up fully-managed delivery streams that push data to your desired destinations on a regular cadence, making it easier to build data lakes, enable real-time analytics, and create data archival solutions. To learn more about using Amazon Data Firehose with AWS CDK, see the AWS CDK documentation and the Amazon Data Firehose Developer Guide. You can also explore sample applications and use cases on the AWS CDK Workshop website.  

Publicado el Deja un comentario

AWS Price List API supports AWS PrivateLink

AWS Price List API now supports AWS PrivateLink. With AWS PrivateLink, you can simplify private network connectivity between virtual private clouds (VPCs), the AWS Price List API, and your on-premises data centers by using interface VPC endpoints and private IP addresses.

The AWS Price List API provides a catalog of the products and prices for AWS services that you can purchase on AWS.
AWS PrivateLink is compatible with AWS Direct Connect and AWS Virtual Private Network (VPN) to facilitate private network connectivity, and helps you eliminate the need to use public IP addresses, configure firewall rules, or configure an internet gateway to access the AWS Price List API from your on-premises data centers. Using the AWS Price List API with AWS Private Link enables you to access AWS product and pricing data without the need to access the public internet.

AWS PrivateLink for AWS Price List API is available in all commercial regions where the AWS Price List API is available (US East (N. Virginia), Asia Pacific (Mumbai), Europe (Frankfurt), China (Ningxia). There is an additional cost to use this feature. Please see AWS PrivateLink pricing for more details.

You can get started with the feature by using the AWS Management Console, AWS API, AWS CLI, AWS SDK, or AWS CloudFormation. Learn more at Access AWS Billing and Cost Management using an interface endpoint (AWS PrivateLink).
 

 

​AWS Price List API now supports AWS PrivateLink. With AWS PrivateLink, you can simplify private network connectivity between virtual private clouds (VPCs), the AWS Price List API, and your on-premises data centers by using interface VPC endpoints and private IP addresses. The AWS Price List API provides a catalog of the products and prices for AWS services that you can purchase on AWS. AWS PrivateLink is compatible with AWS Direct Connect and AWS Virtual Private Network (VPN) to facilitate private network connectivity, and helps you eliminate the need to use public IP addresses, configure firewall rules, or configure an internet gateway to access the AWS Price List API from your on-premises data centers. Using the AWS Price List API with AWS Private Link enables you to access AWS product and pricing data without the need to access the public internet. AWS PrivateLink for AWS Price List API is available in all commercial regions where the AWS Price List API is available (US East (N. Virginia), Asia Pacific (Mumbai), Europe (Frankfurt), China (Ningxia). There is an additional cost to use this feature. Please see AWS PrivateLink pricing for more details. You can get started with the feature by using the AWS Management Console, AWS API, AWS CLI, AWS SDK, or AWS CloudFormation. Learn more at Access AWS Billing and Cost Management using an interface endpoint (AWS PrivateLink).    

Publicado el Deja un comentario

AWS WAF enhances Data Protection and logging experience

AWS WAF expands its Data Protection capabilities with new controls for sensitive data in logs. In addition, we have updated the Logging configuration console experience, making it easier for customer to select the optimal logging option.

Data Protection works together with existing Logging Redaction and Filtering features. You can select which protection method to use based on your use case and where you need to apply the controls. When configured, selected request log fields can be replaced with cryptographic hashes (e.g. ‘ade099751d2ea9f3393f0f’) or a predefined static string (‘REDACTED’) before logs are sent to WAF Sample Logs, Amazon Security Lake, CloudWatch, or other logging destinations. This centralized approach is designed to simplify the management of data and reduces the risk of accidental exposure. In addition, we simplified the WAF console experience for managing logging configurations. Customers can now view all available logging options and select their preferred settings in a simple unified experience.

This feature is available in all AWS Regions and endpoints where AWS WAF is available. To learn more, see the AWS WAF developer guide. There is no additional cost for using this feature, however standard AWS WAF charges still apply. For details, visit the AWS WAF Pricing page.

To use the new Data Protection feature, simply navigate to your Web ACL ‘Logging and metrics’ section in the AWS WAF console and choose the desired data protection option. Existing logging configurations will remain unchanged. For more information about the Data Protection, visit AWS documentation.

 

​AWS WAF expands its Data Protection capabilities with new controls for sensitive data in logs. In addition, we have updated the Logging configuration console experience, making it easier for customer to select the optimal logging option. Data Protection works together with existing Logging Redaction and Filtering features. You can select which protection method to use based on your use case and where you need to apply the controls. When configured, selected request log fields can be replaced with cryptographic hashes (e.g. ‘ade099751d2ea9f3393f0f’) or a predefined static string (‘REDACTED’) before logs are sent to WAF Sample Logs, Amazon Security Lake, CloudWatch, or other logging destinations. This centralized approach is designed to simplify the management of data and reduces the risk of accidental exposure. In addition, we simplified the WAF console experience for managing logging configurations. Customers can now view all available logging options and select their preferred settings in a simple unified experience. This feature is available in all AWS Regions and endpoints where AWS WAF is available. To learn more, see the AWS WAF developer guide. There is no additional cost for using this feature, however standard AWS WAF charges still apply. For details, visit the AWS WAF Pricing page. To use the new Data Protection feature, simply navigate to your Web ACL ‘Logging and metrics’ section in the AWS WAF console and choose the desired data protection option. Existing logging configurations will remain unchanged. For more information about the Data Protection, visit AWS documentation.  

Publicado el Deja un comentario

Amplify Hosting announces support for IAM roles for server-side rendered (SSR) applications

We’re excited to announce the launch of IAM compute roles for AWS Amplify Hosting, enabling secure connections to other AWS resources from server-side rendered applications. This allows developers to integrate their SSR applications with AWS services while maintaining robust security practices.

Use Cases Unlocked:

  • Secure credential management for SSR applications
  • Direct integration with AWS services like Secrets Manager and Parameter Store
  • Support for database connections (RDS, DynamoDB)
  • Granular permission controls
  • Branch-specific role configurations

This feature is available in all 20 AWS Amplify Hosting regions: US East (Ohio), US East (N. Virginia), US West (N. California), US West (Oregon), Asia Pacific (Hong Kong), Asia Pacific (Tokyo), Asia Pacific (Osaka) Asia Pacific (Seoul), Asia Pacific (Mumbai), Asia Pacific (Singapore), Asia Pacific (Sydney), Canada (Central), Europe (Frankfurt), Europe (Stockholm), Europe (Milan), Europe (Ireland), Europe (London), Europe (Paris), Middle East (Bahrain) and South America (São Paulo).

To learn more, read the documentation. To get started with a tutorial, check out our blog post.

 

​We’re excited to announce the launch of IAM compute roles for AWS Amplify Hosting, enabling secure connections to other AWS resources from server-side rendered applications. This allows developers to integrate their SSR applications with AWS services while maintaining robust security practices.
Use Cases Unlocked:

Secure credential management for SSR applications
Direct integration with AWS services like Secrets Manager and Parameter Store
Support for database connections (RDS, DynamoDB)
Granular permission controls
Branch-specific role configurations

This feature is available in all 20 AWS Amplify Hosting regions: US East (Ohio), US East (N. Virginia), US West (N. California), US West (Oregon), Asia Pacific (Hong Kong), Asia Pacific (Tokyo), Asia Pacific (Osaka) Asia Pacific (Seoul), Asia Pacific (Mumbai), Asia Pacific (Singapore), Asia Pacific (Sydney), Canada (Central), Europe (Frankfurt), Europe (Stockholm), Europe (Milan), Europe (Ireland), Europe (London), Europe (Paris), Middle East (Bahrain) and South America (São Paulo).
To learn more, read the documentation. To get started with a tutorial, check out our blog post.  

Publicado el Deja un comentario

AWS Storage Gateway is now available in AWS Mexico (Central) Region

AWS Storage Gateway expands availability to the AWS Mexico (Central) Region enabling customers to deploy and manage hybrid cloud storage for their on-premises workloads.

AWS Storage Gateway is a hybrid cloud storage service that provides on-premises applications access to virtually unlimited storage in the cloud. You can use AWS Storage Gateway for backing up and archiving data to AWS, providing on-premises file shares backed by cloud storage, and providing on-premises applications low latency access to data in the cloud.

Visit the AWS Storage Gateway product page to learn more. Access the AWS Storage Gateway console to get started. To see all the Regions where AWS Storage Gateway is available, please visit the AWS Region table.
 

 

​AWS Storage Gateway expands availability to the AWS Mexico (Central) Region enabling customers to deploy and manage hybrid cloud storage for their on-premises workloads. AWS Storage Gateway is a hybrid cloud storage service that provides on-premises applications access to virtually unlimited storage in the cloud. You can use AWS Storage Gateway for backing up and archiving data to AWS, providing on-premises file shares backed by cloud storage, and providing on-premises applications low latency access to data in the cloud. Visit the AWS Storage Gateway product page to learn more. Access the AWS Storage Gateway console to get started. To see all the Regions where AWS Storage Gateway is available, please visit the AWS Region table.    

Publicado el Deja un comentario

Azure para cargas de trabajo críticas en el sector sanitario: EHR y más allá

febrero 18, 2025

Azure para cargas de trabajo críticas en el sector sanitario: EHR y más allá

Por: Kees Hertogh, vicepresidente de marketing de salud y ciencias de la vida.

En el panorama sanitario actual, que evoluciona con rapidez, la transformación digital ya no es un lujo, sino una necesidad. Uno de los componentes más críticos de esta transformación es el sistema de historia clínica electrónica (HCE), que desempeña un papel fundamental en las operaciones de atención médica y la prestación de atención. Las organizaciones exploran de manera activa alternativas para sus infraestructuras locales tradicionales para superar desafíos significativos, incluidos los altos gastos de capital, los frecuentes y costosos ciclos de actualización de hardware, los protocolos de seguridad obsoletos y, lo que es más importante, la administración de la red de datos de los sistemas en silos. Al aprovechar los sistemas EHR conectados en la nube, los proveedores también pueden desbloquear todo el potencial de sus datos y ofrecer aún más innovaciones de IA basadas en datos.

Azure para cargas de trabajo críticas

La migración de sistemas EHR a Microsoft Azure proporciona a las organizaciones sanitarias una plataforma sólida para cargas de trabajo de misión crítica, lo que garantiza un rendimiento optimizado, un acceso rápido a los datos, una recuperación ante desastres integrada y funciones de seguridad mejoradas, como la detección de amenazas impulsada por IA y la supervisión automatizada del cumplimiento. Además, Azure maximiza las inversiones en la nube, al ofrecer nuevas posibilidades para aprovechar los datos y aprovechar las innovaciones de IA.

Los datos están en el corazón de la atención médica. Los hospitales producen más de 50 petabytes de datos en más de 10 sistemas aislados cada año. A medida que el sector sanitario se enfrenta al doble reto de gestionar grandes cantidades de datos no estructurados y a la escasez de mano de obra, hasta el 97% de los datos sanitarios no se utilizan, lo que pone de manifiesto una importante oportunidad perdida para la excelencia operativa y un mejor conocimiento de los pacientes.1 Una de las mayores ventajas para los clientes sanitarios de Azure es la capacidad de unificar sus datos sanitarios multimodales para el análisis y la inteligencia artificial con soluciones de  datos sanitarios de Microsoft Fabric que les permite ingerir, almacenar y analizar datos de diversos orígenes y modalidades. Mientras que Fabric unifica los datos, Microsoft Purview ofrece el servicio de gobernanza de datos que les ayuda a clasificar los datos en todo el patrimonio de datos, incluida la identificación de datos confidenciales. La integración de Microsoft Purview con las soluciones de datos sanitarios en Fabric no solo refuerza la seguridad, sino que también les ayuda a garantizar el cumplimiento, lo que permite a las organizaciones sanitarias gobernar sus datos con confianza. Somos muy conscientes de las expectativas del sector en el que se utiliza nuestra tecnología, y esta es una de las muchas razones por las que nuestros clientes sanitarios confían en Azure para las cargas de trabajo críticas.

A medida que ofrecemos innovaciones de datos, vemos que nuestros clientes utilizan sus datos conectados en un amplio espectro de capacidades de IA. Con Azure AI, las organizaciones sanitarias pueden acelerar la innovación a través de análisis predictivos, automatizar las tareas clínicas y mejorar las interacciones con los pacientes con la ayuda de soluciones de IA ambiental como DAX Copilot (integrado de manera directa en los sistemas EHR), así como aprovechar  los modelos de IA para el sector sanitario de Microsoft en Azure AI Foundry y GitHub, una colección de modelos de IA generativa multimodal de última generación que benefician a los flujos de trabajo de imágenes y radiología.

Soporte mejorado para misiones críticas

Las cargas de trabajo de misión crítica exigen un soporte integral. En 2024, Microsoft Unified mejoró su soporte para cargas de trabajo de misión crítica en la atención médica a través de sus ofertas de misión crítica. Esta iniciativa proporciona apoyo proactivo para mejorar la salud, la resiliencia y el rendimiento de los sistemas de atención médica a través de evaluaciones periódicas, orientación y recomendaciones de optimización, lo que garantiza la continuidad del negocio y aborda los desafíos únicos de la atención médica.

Colaboración para la excelencia tecnológica: una asociación estratégica que se destaca

Nuestro compromiso con la misión crítica se refleja en nuestras colaboraciones con los principales proveedores de EHR, como Epic®. Esta larga relación de más de 20 años ha dado lugar a una solución optimizada para Epic® en Azure, que ofrece una plataforma sólida y diseñada de manera especial, respaldada por una arquitectura de referencia conjunta. De manera reciente, Microsoft anunció la ampliación de la escalabilidad en Azure para las organizaciones sanitarias, en concreto para ejecutar la base de datos operativa (ODB, por sus siglas en inglés) Chronicles* de Epic®, para aumentar su capacidad a 65 millones de referencias globales por segundo (GRefs/s), lo que supone una mejora del 171% con respecto a 2023 en la nueva serie de máquinas virtuales Mbv3.

La colaboración con Epic® se extiende mucho más allá de la infraestructura de la nube, a varios productos y capacidades que forman parte de Microsoft Cloud for Healthcare. Epic® y Microsoft han ampliado su colaboración para integrar tecnologías avanzadas de IA como Microsoft Azure OpenAI Service y DAX Copilot en el sistema EHR de Epic®. La integración ayuda a proporcionar información clínica impulsada por IA, agilizar los procesos administrativos y mejorar la productividad de los médicos a través de funciones como el resumen de notas y las sugerencias de codificación automatizadas.

Ofrecer valor más allá de la infraestructura: la promesa de Microsoft Cloud for Healthcare

La asociación integral de Microsoft con Epic® es una de las muchas razones por las que Azure es la nube elegida por muchos de nuestros clientes de atención médica.

La decisión de trasladar las cargas de trabajo de misión crítica a la nube a menudo no se trata solo de la infraestructura. Clientes como Mercy eligieron Azure no solo para modernizar su infraestructura, sino también para extraer valor de archivos de datos de gran tamaño. La transformación digital de Mercy en Azure le permitió conectar datos antes aislados y usar varios servicios de Microsoft, como Azure Data Lake, para obtener resultados comerciales positivos. Por ejemplo, al dotar a los equipos de atención de los equipos de atención de paneles inteligentes y de información sobre los factores que determinan el alta de los pacientes, Mercy ha podido reducir de manera significativa la duración de las estancias de los pacientes. Mercy emplea Azure AI Document Intelligence para escanear y reconocer la información de las tarjetas de seguro de los pacientes, que luego se actualiza automáticamente en sus registros de EHR.

Reconocemos el deseo de nuestros clientes de tener una transformación digital completa en la nube que trascienda todas las capas de la pila, y Microsoft Cloud for Healthcare nos permite cumplir esa promesa. Encapsula un amplio espectro de innovaciones de datos e inteligencia artificial de Microsoft, diseñadas en específico para la industria de la salud, lo que permite a nuestros clientes alcanzar sus objetivos en la nube de manera más rápida y sencilla. De manera reciente, Microsoft anunció varias innovaciones como parte de la cartera, incluidos nuevos modelos de IA  para el cuidado de la salud en Azure AI Foundry, capacidades para soluciones de datos de atención médica en Microsoft Fabric, el servicio de agente de atención médica en Copilot Studio y una solución de flujo de trabajo de enfermería impulsada por IA.

A medida que los clientes se dan cuenta del valor de consolidar sus inversiones en TI en torno a un único proveedor, Azure se adopta cada vez más para las cargas de trabajo críticas. Al conectar y ofrecer valor sin problemas en todas las capas de la pila, Azure para misión crítica amplía el retorno de las inversiones en la nube de un cliente. Clientes como St. Luke’s University Health System cosechan los beneficios de su migración de Epic® a Azure al aprovechar varias sinergias en la cartera de Microsoft, como la interoperabilidad de Microsoft Teams con Epic®. La seguridad es de suma importancia cuando se trata de registros de pacientes, y clientes como Jefferson Health migran sus entornos de Epic® a Azure con gran confianza con Microsoft Defender para la detección y respuesta de puntos de conexión.

Pasos siguientes

A medida que continuamos con la transformación de las cargas de trabajo de misión crítica en la nube, facilitamos a nuestros socios y clientes la creación de experiencias conectadas en cada punto de atención, empoderar a su personal de atención médica y desbloquear el valor de sus datos, todo con privacidad y seguridad sin concesiones. Microsoft Cloud for Healthcare apoya a las organizaciones sanitarias en cada paso de su recorrido hacia la configuración de un futuro más saludable.

*Epic® y Chronicles son marcas comerciales de Epic Systems Corporation.

1 Foro Económico Mundial, 4 maneras en que los datos mejoran la atención médica, diciembre de 2019.

The post Azure para cargas de trabajo críticas en el sector sanitario: EHR y más allá appeared first on Source LATAM.

 

​The post Azure para cargas de trabajo críticas en el sector sanitario: EHR y más allá appeared first on Source LATAM.