人工智能
在符合HIPAA条件的环境中部署AI，使用Amazon快速
医疗组织想从AI那里得到其他企业想要的相同的东西：更快的答案，更少的手工工作，以及及时到达决策者面前以采取行动的洞察力。 然而，医疗行业之所以不同，是因为数据是独特的复杂、内在和严格管理。 因此，这篇文章从几个定义开始，为接下来的一切打下基础。
保护性健康信息是指识别某人并与其健康、护理或护理付款有关的任何信息，如医疗说明、索赔或成员身份证。 当软件触及PHI时，它属于《健康保险可携带性和问责制法》(HIPAA)，该法是联邦法律，规范如何获取、保护和审计PHI数据。
Agentic AI将软件的含义改变为“摸摸PHI”。 一个传统的分析工具读取数据并返回一个响应。 像AmazonQuick这样的代理工作空间可能会更进一步。 例如，它的聊天agents的工作既跨越非结构化的内容，如临床的指出和上诉信，也跨越结构化的数据，如声称和成员记录。 Agents可能从无结构化和结构化来源获取数据，通过连接器调用其他系统，并代表用户完成多步任务。 连接器是预建的集成器，可以让Amazon快速安全地从您的外部系统中读取并采取行动，如Slack,Microsoft Outlook,Salesforce,Atlassian Jira，以及Microsoft SharePoint. 也可以通过模式上下文协议(MCP)添加自己的自定义工具。 只有您组织内授权的连接器可见。 当聊天 agent 既能读取又能在 PHI 上行动时，你需要足够的治理：决定性的守护者，agent 所作所为的行为审计线索，以及明确的责任所采取行动没有个人的循环。 为了支持这种治理，Amazon Quick 揭露了ACL的认知检索、聊天和反馈记录以及控制 agent每次聊天都允许做什么
Amazon快车是HIPAA的合格服务。 这一资格适用于Amazon快速网络，桌面，移动客户端，但需遵守分担责任模式和您的配置。 然而，这个帖子专注于Amazon快速网络版本的能力，您通过您的浏览器访问这些版本。
在此文中，我们从基金会开始：HIPAA向谁申请以及HIPAA合格和HIPAA合格之间的区别。 然后，我们引入AmazonQuick作为平台和PHI的两个数据流(非结构化和结构化). Amazon Quick提供规范的环境，以及它没有提供的环境，我们最后提出逐步实施指南、结论和深化阅读的资源。
HIPAA申请给谁？
卫生局的工作范围比医院和诊所更远。 根据法律，两类组织承担义务，大多数AI项目都触及两者。
覆盖的实体
- 健康计划 - 健康保险公司、保健组织、雇主赞助的计划、医疗保险和医疗援助。
- 保健信息中心 - 将非标准保健信息处理成标准电子格式的组织。
- 保健提供者 -- -- 医生、诊所、医院、药房、疗养院以及任何通过电子方式传送保健信息的提供者。
商业伙伴(BA)
- 企业合伙人是指代表被保险实体创建、接受、维持或传送受保护的卫生信息(PHI)的任何个人或实体，不在被保险实体的劳动力范围内。
常见的例子包括云服务提供者、信息技术供应商、计费公司、数据分析公司、声称处理商、律师事务所和咨询公司。
- 代表另一商业伙伴处理个人健康倡议的分包商本身就是商业伙伴。
在PHI换手之前，被覆盖的实体和企业合伙人必须同时签署商务协理增编(BAA). 在通过AWS Artifact接受AWS BAA后，AWS担任该特定AWS账户的商务合伙人，只有当您使用像Amazon快速处理其中的PHI这样的HIPAA合格服务。 本增编不延伸至您的其他账户，也不扩展至不合格于HIPAA的服务的PHI，也不扩展至您如何配置服务。 这些仍然是你的责任。 总是审查和确认现有的AWS BAA条款，以及你对自己的法律和遵守团队的义务。
HIPAA符合条件与HIPAA符合条件不同
虽然HIPAA符合AWS指定条件，HIPAA符合是您整个环境的财产。 符合HIPAA条件的表示AWS已经对服务进行了评估，并允许您使用它来处理，存储，以及传输一个签有AWS BAA的PHI. Amazon 电话 Quick是一个符合HIPAA条件的服务，第三方审计员根据AWS合规方案对其进行评估，包括HIPAA,FedRAMP,PCIDS,SOC，和ISO. AWS没有正式的HIPAA认证作为云服务，AWS本身没有"HIPAA合格".
兹Amazon 快速参赛资格仅作为基石。 仅此而已，您仍需要签署BAA，对您的数据进行分类，正确配置控制，并拥有 HIPAA 所需的行政和实体保障，包括员工培训、风险分析、以及 AWS 不为您执行的违反程序。 AmazonQuick等符合条件的服务，签有BAA，正确的配置，治理，以及你自己的保障措施，就是产生HIPAA符合的部署。 兹Amazon 快速获得资格意味着您可以在上面构建一个符合要求的工作流程。 这并不意味着打开它会让你自动遵守。
Amazon快是什么来着？
AmazonQuick通过它的聊天agents经常是推出，但HIPAA的资格适用于整个工作空间，而不是一个单一的功能，所以一个平台级的查看事项是遵守的。 Amazon快车的所有能力均由以下构件组装：1.
- 聊天是主要接口一个用户可以用自然语言提出问题或提供指示，Amazon快速决定如何回答。
- 聊天agents 处理每一个请求。 这是你在控制台上看到的，在Chat agents菜单下。 每个聊天agent可以配置指令，以知识源为基础，并赋予采取行动的工具。 Amazon快船默认聊天 agent(我的助手)，您可以为特定域创建自定义聊天 agents.
- 空间组织聊天agent需要的资源，例如文件、仪表板、数据集、知识库和行动连接器。 一个空间可以与团队共享。
- 集成连接 Amazon Quick to your Environment：用于Amazon简单存储服务(Amazon S3),Microsoft SharePoint，和Atlassian聚合等非结构化内容的知识库；将Amazon快速视与你结构化的数据库，数据仓库和数据湖连接的结构化数据连接；动作连接器(由OpenAPI规格或模式上下文协议服务器建造)；以及扩展(Chrome,Slack,Microsoft Teams，和Microsoft 365).
在这些建筑的顶部坐着它从栏中提取的遵守问题，因为它是显示的构件，因此，每个特性都借鉴了哪些数据路径。
注：SPICE是Amazon快视的内置查询引擎。 一个 SPICE 数据集在创建时使用账户默认客户端管理的密钥，要将已有的数据集导入到新的默认密钥中，您必须进行全新更新。 如果您的数据包含 PHI，请将 SPICE 包含在您的加密策略中( 如果您使用 AWS 密钥管理服务( KMS) 密钥，请与客户一起保护)，并包含在您关于导入什么的数据最小化决定中，例如查询 live 或者装入一个解识别的提取。
同样的资格，BAA，加密，访问控制和审计姿态，遍及每个功能。 但如开头所指出，PHI通过两条路径快速到达Amazon，每条通道的安全性不同。 无结构的路径贯穿知识库，其中文件由文档级别的ACL控制，并在查询时进行评估。 结构化路径贯穿Amazon快速视读您的数据库和数据湖，其中行和列访问由行级和列级安全控制。 这两个数据流携带PHI的方式不同，作为下面的显示节，在每个路径中执行控制的方式也不同。
Amazon快速提供规范的环境
AmazonQuick是HIPAA的资格，我们概述了这在实践中的含义。
管理下的基础设施
兹Amazon 快讯是一个完全管理好的服务。 AWS运行基础基础设施，负责云层安全，由第三方审计师按照AWS分担责任模式进行核查。
加密
Amazon快速在默认情况下对数据进行休息加密，并支持对在途数据进行加密。
- 默认使用 AWS 拥有或 AWS 管理的密钥进行休息加密。 对客户管理的密钥进行登记是可选的，不是《投资促进法》的要求。 如果您需要直接控制加密密钥，您可以注册客户管理的AWS KMS密钥(需要企业订阅)，用于参与的资源类型，包括SPICE数据集，数据源证书，OAuth令牌，以及报告文物。 在不应用客户管理密钥的情况下，AWS会用AWS拥有或AWS管理密钥加密数据。
用户对聊天回应的反馈，包括可选的自由文本评论，并没有用客户管理的密钥或保护 Amazon Quick AI 索引数据的密钥加密。 用户的反馈应作为潜在的PHI表面处理，并相应加以管理。
- 对于在途数据，Amazon快件通过运输层安全(TLS)加密传输。 对于一些数据库连接，您可以选择传输是否是加密的，所以您应该明确启用这些数据源连接上的TLS/SSL，而不是假设它总是在运行。
您的数据不训练模型
AmazonQuick不使用客户数据来训练或改进基础大语言模型(LLMs).
出入控制和身份联合会
Amazon快速通过AWS IAM身份中心，Microsoft Active Directory，以及SAML 2.0身份提供者，支持基于角色的访问控制(RBAC)和单一签名(SSO). 对于商业智能(BI)工作量，您可以用行级和列级的安全以及运行中的角色来补充，以限制查询时间的数据访问。 凭借这些能力，可以强制实施独特的用户识别和最小的特权。
审计和监测信号
Amazon快速发射几个截然不同的信号。 他们无法互换
- AWS CloudTrail记录支持API操作和一套有记录的非API事件，如仪表板查看和用户管理行动。 它可以捕捉谁做什么和何时做什么，但不聊天消息机构或响应内容。
- Amazon Cloud Watch vended logs将AI特定记录传送到您控制的目的地(Cloud Watch Logs, Amazon S3，或 Firehose). 有五个日志类型：聊天对话(CHAT LOGS)，用户反馈(FEEDBACK LOGS),agent和研究时数(AGENT HOURS LOGS)，索引存储使用(INDEX USAGE LOGS)，以及知识库文件同步(KB FILE SYNC LOGS). 这是“用户问到的是什么，Amazon快速回答的是什么”，而不是CloudTrail。
- 云量表和警报也提供近实时的业务监测。
- 分析仪表板显示管理人员使用和采用。 请注意，它可以在负面反馈审查的范畴中披露详细的查询文本和完整的对话背景，因此只允许访问 autho
本文由 AI图鉴自动抓取并翻译，版权归原作者所有；如需查看原文请点下方链接。
Artificial Intelligence
Deploy AI in a HIPAA-eligible environment with Amazon Quick
Healthcare organizations want the same thing from AI that every other business wants: faster answers, less manual work, and insights that reach decision-makers in time to act on them. However, what makes the healthcare industry different is that the data is uniquely complex, deeply contextual, and strictly regulated. So this post starts with a few definitions to set the foundation for everything that follows.
Protected Health Information (PHI) is any information that identifies a person and relates to their health, care, or payment for care, such as a medical note, a claim, or a member ID. When software touches PHI, it falls under the Health Insurance Portability and Accountability Act (HIPAA), the federal law that governs how PHI data is accessed, secured, and audited.
Agentic AI changes what it means for software to “touch PHI.” A traditional analytics tool reads data and returns a response. An agentic workspace like Amazon Quick might go further. For example, its chat agents work across both unstructured content, such as clinical notes and appeals letters, and structured data, such as claims and member records. Agents might retrieve data from both unstructured and structured sources, call other systems through connectors, and complete multi-step tasks on a user’s behalf. Connectors are pre-built integrations that let Amazon Quick securely read from and take action in your external systems, such as Slack, Microsoft Outlook, Salesforce, Atlassian Jira, and Microsoft SharePoint. You can also add your own custom tools through Model Context Protocol (MCP). Only connectors authorized within your organization are visible. When a chat agent can both read and act on PHI, you need sufficient governance: deterministic guardrails, a behavioral audit trail of what the agent did, and clear accountability for actions taken without a person in the loop. To support that governance, Amazon Quick exposes ACL-aware retrieval, chat and feedback logging, and controls over what each chat agent is allowed to do.
Amazon Quick is a HIPAA-eligible service. This eligibility applies across the Amazon Quick web, desktop, and mobile clients, subject to the shared responsibility model and your configuration. This post, however, focuses on the capabilities of the Amazon Quick web version, which you access through your browser.
In this post, we start with the foundations: who HIPAA applies to and the difference between HIPAA-eligible and HIPAA-compliant. We then introduce Amazon Quick as a platform and the two data flows for PHI (unstructured and structured). From there, we cover what Amazon Quick provides for regulated environments and what it doesn’t, walk through a fictional health plan (AnyCompany) deployment, and distill the best practices and irreversible decisions you should make up front. We close with a step-by-step implementation guide, a conclusion, and resources for deeper reading.
Who does HIPAA apply to?
HIPAA reaches further than hospitals and clinics. Under the law, two categories of organizations carry obligations, and most AI projects touch both.
Covered entities (CEs)
- Health plans – Health insurance companies, HMOs, employer-sponsored plans, Medicare, and Medicaid.
- Healthcare clearinghouses – Organizations that process nonstandard health information into standard electronic formats.
- Healthcare providers – Doctors, clinics, hospitals, pharmacies, nursing homes, and any provider that transmits health information electronically.
Business associates (BAs)
- A business associate is any person or entity, outside the covered entity’s workforce, that creates, receives, maintains, or transmits protected health information (PHI) on the covered entity’s behalf.
- Common examples include cloud service providers, IT vendors, billing companies, data analytics firms, claims processors, law firms, and consulting firms.
- Subcontractors who handle PHI on behalf of another business associate are themselves business associates.
Covered entities and business associates must both sign a business associate addendum (BAA) before PHI changes hands. After you accept the AWS BAA through AWS Artifact, AWS acts as your business associate for that specific AWS account, and only when you use HIPAA-eligible services like Amazon Quick to process PHI within it. The addendum doesn’t extend to your other accounts, to PHI placed in services that are not HIPAA-eligible, or to how you configure the service. Those remain your responsibility. Always review and confirm the current AWS BAA terms and your obligations with your own legal and compliance teams.
HIPAA eligible is not the same as HIPAA compliant
While HIPAA eligible is an AWS designation, HIPAA compliant is a property of your entire environment. HIPAA eligible means AWS has assessed the service and permits you to use it to process, store, and transmit PHI under a signed AWS BAA. Amazon Quick is a HIPAA-eligible service, and third-party auditors assess it under AWS compliance programs including HIPAA, FedRAMP, PCI DSS, SOC, and ISO. No official HIPAA certification exists for AWS as a cloud service, and AWS itself is not “HIPAA eligible.”
Amazon Quick eligibility serves only as a building block. That alone doesn’t make your application and environment HIPAA compliant. You still need to sign the BAA, classify your data, configure the controls correctly, and own the administrative and physical safeguards HIPAA requires, including workforce training, risk analysis, and breach procedures that AWS doesn’t perform for you. An eligible service such as Amazon Quick, a signed BAA, correct configuration, governance, and your own safeguards is what produces a HIPAA-compliant deployment. Amazon Quick being eligible means you can build a compliant workflow on it. It doesn’t mean that turning it on makes you automatically compliant.
What is Amazon Quick
Amazon Quick is often introduced through its chat agents, but HIPAA eligibility applies to the entire workspace, not to a single feature, so a platform-level view matters for compliance. All capabilities in Amazon Quick are assembled from the following building blocks:
- Chat is the primary interface. A user can pose a question or provide an instruction in natural language, and Amazon Quick decides how to respond.
- Chat agents process every request. This is what you see on the console, under the Chat agents menu. Each chat agent can be configured with instructions, grounded by knowledge sources, and given tools to take action. Amazon Quick ships a default chat agent (My Assistant), and you can create custom chat agents for specific domains.
- Spaces organize the resources a chat agent needs, such as documents, dashboards, datasets, knowledge bases, and action connectors. A space can be shared with a team.
- Integrations connect Amazon Quick to your environment: knowledge bases for unstructured content such as Amazon Simple Storage Service (Amazon S3), Microsoft SharePoint, and Atlassian Confluence; structured data connections that link Amazon Quick Sight to your structured databases, data warehouses, and data lakes; action connectors (built from OpenAPI specifications or Model Context Protocol servers); and extensions (Chrome, Slack, Microsoft Teams, and Microsoft 365).
On top of those building blocks sit the features. The What it draws on column matters for compliance, because it shows which building blocks, and therefore which data paths, each feature draws on.
Note: SPICE is the in-memory query engine of Amazon Quick Sight. A SPICE dataset uses the account default customer managed key at creation, and to import an existing dataset onto a new default key you must perform a full refresh. If your data includes PHI, include SPICE in your encryption strategy (protect it with your customer managed AWS Key Management Service (KMS) key if you use one) and in your data-minimization decisions about what to import, such as querying live or loading a de-identified extract instead.
The same eligibility, BAA, encryption, access control, and audit posture extend across every feature. But as noted at the start, PHI reaches Amazon Quick through two paths, and each is secured differently. The unstructured path runs through knowledge bases, where the documents are controlled by document-level ACLs and evaluated at query time. The structured path runs through Amazon Quick Sight reading your databases and data lakes, where row and column access is controlled by row-level and column-level security. These two data flows carry PHI differently and, as the following section shows, controls are enforced differently in each path.
What Amazon Quick provides for regulated environments
Amazon Quick is HIPAA eligible, and we outline what that means in practice.
Managed infrastructure
Amazon Quick is a fully managed service. AWS operates the underlying infrastructure and is responsible for security of the cloud, verified by third-party auditors as laid out in the AWS Shared Responsibility Model.
Encryption
Amazon Quick encrypts data at rest by default and supports encryption for data in transit.
- Encryption at rest is on by default using AWS owned or AWS managed keys. Registering a customer managed key is optional and is not a HIPAA requirement. If you require direct control over the encryption keys, you can register a customer managed AWS KMS key (requires an Enterprise subscription) for participating resource types, including SPICE datasets, data source credentials, OAuth tokens, and report artifacts. Where no customer managed key applies, AWS encrypts the data with an AWS owned or AWS managed key.
- One nuance to note: User feedback on chat responses, including optional free-text comments, isn’t encrypted with your customer managed key or the key that protects Amazon Quick’s AI-indexed data. User feedback should be treated as a potential PHI surface and governed accordingly.
- For data in transit, Amazon Quick secures encrypted transfers with Transport Layer Security (TLS). For some database connections, you can choose whether the transfer is encrypted, so you should explicitly enable TLS/SSL on those data-source connections rather than assuming it is always on.
Your data does not train the models
Amazon Quick doesn’t use your customer data to train or improve the underlying large language models (LLMs).
Access control and identity federation
Amazon Quick supports role-based access control (RBAC) and single sign-on (SSO) through AWS IAM Identity Center, Microsoft Active Directory, and SAML 2.0 identity providers. For business intelligence (BI) workloads, you can supplement this with row-level and column-level security and run-as roles to limit data access at query time. With these capabilities, you can enforce unique user identification and least privilege.
Audit and monitoring signals
Amazon Quick emits several distinct signals. They aren’t interchangeable, and confusing them is a common audit gap.
- AWS CloudTrail records supported API operations and a documented set of non-API events, such as dashboard views and user-management actions. It captures who did what and when, but not chat message bodies or response content.
- Amazon CloudWatch vended logs deliver the AI-specific records to a destination you control (CloudWatch Logs, Amazon S3, or Firehose). There are five log types: chat conversations (CHAT_LOGS), user feedback (FEEDBACK_LOGS), agent and research hours (AGENT_HOURS_LOGS), index storage usage (INDEX_USAGE_LOGS), and knowledge base file sync (KB_FILE_SYNC_LOGS). This is where “what a user asked and what Amazon Quick answered” lives, not in CloudTrail.
- CloudWatch metrics and alarms provide near-real-time operational monitoring as well.
- The analytics dashboard surfaces usage and adoption for administrators. Note that it can expose detailed query text and full conversation context in the scope of negative-feedback review, so grant access only to autho
Auto-fetched and translated by AI Atlas. All rights belong to the original author.