AWS provided documentation detailing the creation and state management of FHIR Subscriptions within AWS HealthLake. This documentation explains the various states, such as 'requested' and 'activated', that a Subscription can transition through.
AWS has introduced the capability to manage FHIR Subscriptions in AWS HealthLake. This feature utilizes the FHIR R5 Backport topic-based subscription model, enhancing data publication capabilities.
AWS provided documentation detailing the creation and management of the FHIR Subscription lifecycle using AWS HealthLake. This guide outlines the technical steps for establishing and maintaining data subscriptions.
AWS HealthLake enables searching of stored data using FHIR standards. This functionality supports using search parameters either in the URL or the request body via a POST request.
AWS has provided functionality to initiate FHIR import jobs directly into its HealthLake storage. This feature allows users to streamline the process of ingesting FHIR data into the AWS ecosystem.
AWS documentation describes the process of creating a HealthLake data store. This process utilizes the CreateFHIRDatastore function to ensure compliance with FHIR standards.
AWS provided documentation outlining the process for importing FHIR data into AWS HealthLake. The process involves specifying the input location in an Amazon S3 bucket and the output location.
AWS HealthLake provides support for SMART on FHIR OAuth 2.0 scopes. This feature allows the SMART on FHIR AuthorizationStrategy to be set during data store creation.
AWS provided documentation for reading FHIR resources within AWS HealthLake. This documentation directs users to the FHIR RESTful R4 read API documentation for further details.
AWS provides functionality to create FHIR resources directly within the HealthLake data store. This feature utilizes the FHIR R4 RESTful API for resource creation.
Medicare Payers are required to support the portability of patient data. This requirement mandates the use of FHIR APIs for transferring patient data to and from various systems.
AWS is enhancing healthcare data interoperability through the use of its API Gateway service. This effort utilizes the Fast Healthcare Interoperability Resources (FHIR) standard to improve data exchange.
AWS released a decision-maker's guide covering the benefits and architecture fundamentals of FHIR. The guide helps organizations decide whether to buy off-the-shelf solutions, partner with others, or build their own FHIR implementation.
AWS is demonstrating the capability to build advanced healthcare agents using Amazon Bedrock AgentCore. This integration leverages FHIR standards to ensure interoperability in healthcare applications.
AWS introduced an AI-powered solution designed to capture and structure patient symptoms. This tool is available on the AWS Marketplace and leverages the Smart on FHIR standard for interoperability.
AWS Marketplace has launched AI-driven telephonic questionnaires. This tool allows for conversational patient engagement and data capture using the SMART on FHIR technology.
Medicare Payers are required to support the portability of patient data. This requirement mandates that patient data must be transferable to and from other payers using FHIR APIs.
AWS released a decision-maker's guide covering the fundamentals of FHIR architecture. The guide helps organizations decide whether to buy off-the-shelf solutions, partner, or build custom FHIR implementations.