This Guidance shows how to use generative artificial intelligence (generative AI) to summarize patient histories and identify likely medical conditions and diagnosis codes. Patient-provider interactions capture multiple types of documentary details, such as patient profile, clinical notes, and laboratory work. By juxtaposing this data with historical diagnosis knowledge bases and analyzing it with generative AI foundation models, you can generate summaries of likely medical conditions. You can then recommend these summaries and relevant International Classification of Diseases, Tenth Revision, Clinical Modification (ICD-10-CM) codes to providers, helping then improve patient care.
Note: [Disclaimer]
Architecture Diagram

[Architecture diagram description]
Step 1
Source data can come in many different forms, such as the Fast Healthcare Interoperability Resources (FHIR) format. If it is already in FHIR format—for example, if it is coming from an electronic health record (EHR)—it can be directly sent to AWS HealthLake through synchronous FHIR APIs or through asynchronous bulk imports.
Get Started

Well-Architected Pillars

The AWS Well-Architected Framework helps you understand the pros and cons of the decisions you make when building systems in the cloud. The six pillars of the Framework allow you to learn architectural best practices for designing and operating reliable, secure, efficient, cost-effective, and sustainable systems. Using the AWS Well-Architected Tool, available at no charge in the AWS Management Console, you can review your workloads against these best practices by answering a set of questions for each pillar.
The architecture diagram above is an example of a Solution created with Well-Architected best practices in mind. To be fully Well-Architected, you should follow as many Well-Architected best practices as possible.
-
Operational Excellence
Amazon CloudWatch collects and tracks metrics for AWS resources like Lambda, Amazon Bedrock, and Amazon Comprehend Medical in real time. Using CloudWatch logs, you can monitor your systems and applications, identify concerns early, and proactively troubleshoot and remediate issues.
-
Security
AWS Identity and Access Management (IAM) provides fine-grained access control to AWS services and resources under conditions you specify, supporting the principle of least privilege. Lake Formation helps you centrally govern and secure data and globally share it for analytics and machine learning. It also delivers fine-grained data access control, down to the row and column level, so you can provide users with specific data access. Additionally, AWS CloudTrail lets you record API calls made within your AWS account and provides an audit trail that you can use for compliance. Finally, Amazon Comprehend Medical detects protected health information in clinical text, supporting privacy protection.
-
Reliability
This Guidance uses managed services with high built-in reliability, such as Athena, HealthLake, Amazon Bedrock, Amazon Comprehend Medical, and AWS HealthScribe. As another example, Amazon S3 is designed to provide 99.999999999 percent durability and 99.99 percent availability of objects.
-
Performance Efficiency
This Guidance provides high performance, helping you deliver impactful patient care. For example, serverless services like HealthLake, Amazon Comprehend Medical, and AWS HealthScribe provide managed scaling that doesn’t rely on any custom engineering in your code.
-
Cost Optimization
This Guidance optimizes costs by using serverless services like Athena and Amazon Bedrock. Serverless services charge only for the resources used, so you don’t have to pay for idle server capacity. And because they automatically scale to handle varying loads, they reduce costs during low-traffic periods and support efficient resource use during peak times. These services also offer various cost optimization mechanisms. For example, Amazon S3 Lifecycle policies and Amazon S3 Intelligent-Tiering provide lower-cost storage options. Finally, serverless services shift operational responsibilities to AWS, lowering your total cost of ownership by empowering developers to focus on code rather than infrastructure maintenance.
-
Sustainability
This Guidance’s use of cloud-native serverless services—like Lambda, Athena, and Amazon Bedrock—can reduce a workload’s carbon footprint by 88 percent. This empowers you to pursue your environmental, social, and governance goals. Additionally, Amazon S3 enables data archival, and Lake Formation enables data classification so that you can define how long health records are retained. As a result, you can more easily achieve regulatory compliance while optimizing energy expenditures related to storage.
Related Content

[Title]
Disclaimer
The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.
References to third-party services or organizations in this Guidance do not imply an endorsement, sponsorship, or affiliation between Amazon or AWS and the third party. Guidance from AWS is a technical starting point, and you can customize your integration with third-party services when you deploy the architecture.