Normalized claim
Quantified impact: 33%
Amazon Q Developer wrote 33% of the code and developers accepted 31% of suggestions.
Availity Modernizes Healthcare Technology through Collaboration with AWS (Amazon Q for RCM)
Use case typeCode assistantUpdated Jun 13, 2026
Availity, the largest real-time health information network in the U. S., is modernizing its revenue cycle management application on AWS to improve resiliency, security, and performance. The company migrated and phased the RCM application to AWS with help from AWS Professional Services and the Experience-Based Acceleration (EBA) framework, while also upskilling engineers through AWS Training and Certification, AWS Skill Builder, and AWS Cloud Quest. Availity implemented Amazon Q Developer, Amazon Q Business, and Amazon Q in QuickSight to improve development workflows, automate release review analysis, and help non-technical users consume data more easily.
- Organization
- Availity
- Industry
- Healthcare
- Location
- United States
- Published
- May 2026
Reported outcomes
−75%
timeTime & speed
33%quantified impact31%quantified impact2 hourstime30 minutestime4 hourstime
Strategic outcomes
Risk & complianceAchieved FedRAMP-level security postureSpeed & agilityReduced recovery time objectiveSpeed & agilityAccelerated release review processNew product / capabilityImproved claim processing workflow
Catalog median for time & speed deployments: −50% across 312 reported metrics. Compare benchmarks →
Why do we believe this?Outcome claims, sources, and evidence checks
Normalized claim
Quantified impact: 31%
Amazon Q Developer wrote 33% of the code and developers accepted 31% of suggestions.
Normalized claim
Time: 2 hours decrease
Release review meetings were reduced from 2 hours to 30 minutes, a 75% reduction.
Normalized claim
Time: 30 minutes decrease
Release review meetings were reduced from 2 hours to 30 minutes, a 75% reduction.
Normalized claim
Time: 75% decrease
Release review meetings were reduced from 2 hours to 30 minutes, a 75% reduction.
Normalized claim
Time: 4 hours increase
Claim processing time improved from up to 4 hours to about 30 minutes, an 87.5% improvement.
Normalized claim
Time: 30 minutes increase
Claim processing time improved from up to 4 hours to about 30 minutes, an 87.5% improvement.
Normalized claim
Time: 87.5% increase
Claim processing time improved from up to 4 hours to about 30 minutes, an 87.5% improvement.
Why do we believe this deployment?Customer identity, provider attribution, maturity, and source checks
- Customer
- Availity
- Provider
- AWS
- Maturity
- Production
- Linked source
- AWS Solutions Case Studies
Rebuild and modernize a critical Revenue Cycle Management application for resiliency, security, and performance while accelerating development and improving operational efficiency
Customer identity supportedSource describes one deploymentMaturity supported
Primary read
Use case focus
Showing 3 of 4
- 1AI-assisted software development
- 2Workflow automation
- 3Knowledge management
Rebuild and modernize a critical Revenue Cycle Management application for resiliency, security, and performance while accelerating development and improving operational efficiency.
- Migrated the RCM application to AWS using a phased approach with AWS Professional Services and the Experience-Based Acceleration (EBA) framework.
- Upskilled engineers through AWS Training and Certification, AWS Skill Builder, and AWS Cloud Quest.
- Implemented Amazon Q Developer for software development, Amazon Q Business for release management analysis, and Amazon Q in QuickSight for data consumption by non-technical users.
- Amazon Q Developer wrote 33% of the code and developers accepted 31% of suggestions.
- Release review meetings were reduced from 2 hours to 30 minutes, a 75% reduction.
- Claim processing time improved from up to 4 hours to about 30 minutes, an 87.5% improvement.
- Availity achieved FedRAMP-level security posture and reduced Recovery Time Objective from hours to minutes.
Architecture
Availity used a phased migration of its revenue cycle management application to AWS, supported by AWS Professional Services and the EBA framework. The implementation also included AWS Training and Certification, AWS Skill Builder, and AWS Cloud Quest to scale cloud skills across the engineering organization. Amazon Q Developer was used in development workflows, Amazon Q Business was used to analyze committed changes and generate review reports, and Amazon Q in QuickSight was used to improve data consumption for non-technical teams.
Sources & evidence1
Evidence: Medium65/100Evidence strength
- Customer explicitly identified
- Deployment status explicitly supported
- Primary source available
- Quantified outcome available
- Technical implementation details available
Type: Customer StoryPublished: May 13, 2026Publisher: AWSEvidence: PrimaryConfidence: High
AI-generated summary. Verify important details with the linked sources before relying on this case.
Explore related AI use cases
Customer evidence
Provider evidence
Browse the catalog
Was this useful?
Community
Comments
No published comments yet.