AWS Partner · Deployed on AWS · Available in AWS Marketplace
Concurrence brings the Health World Model and clinically tested AI workflows to the AWS Marketplace. Eligible purchases count toward your AWS commitment.
Concurrence brings the Health World Model and clinically tested AI workflows to the AWS Marketplace. Eligible purchases count toward your AWS commitment.
Available inAWS MarketplaceDeployed on AWSAWS provides the infrastructure, models, and health data services. Concurrence builds on them instead of rebuilding them, and adds what healthcare needs on top: a Health World Model of every patient and clinically tested AI workflows that act on it.
Concurrence runs on Amazon Elastic Kubernetes Service (Amazon EKS) with support for Amazon Redshift and AWS HealthLake. Connect the services your workflows need, with data-access and publication paths configured for your organization.
Read FHIR R4 resources from AWS HealthLake into the Health World Model and write authorized updates back to your data store. Configure the resource types, permissions and validation rules for each workflow.
Amazon Bedrock serves models through the configured AWS-hosted model route, with endpoints and inference profiles selected for your workload. Other model or speech routes require their own hosting and eligibility review.
Component 1
A longitudinal view of the patient, built by unifying every source of healthcare data into a single foundation: EHR records, claims, labs, device data, scheduling, prior conversations, care plans, consent and preferences.
Component 2
Concurrence deploys AI-powered workflows across the patient and clinician journey (intake, scheduling, outreach, documentation, referrals, follow-up, etc.), each with access to the living context in the Health World Model. This lets your organization scale the judgment of expert clinicians and generate interaction-level data that has never been captured.
Component 3
From this data, Concurrence identifies Patient Trajectories that connect specific interventions to specific outcomes. Across millions of them, your organization discovers which care pathways produce the best outcomes for each population.
The Concurrence listing carries the Deployed on AWS badge. Eligible AWS Marketplace purchases can count toward your organization's AWS spend commitment, subject to your agreement and AWS eligibility rules.
Buy through a private offer in AWS Marketplace, inside the AWS account your procurement team already manages, with charges on your AWS invoice. Contract terms, security review and data-access approvals remain part of your procurement process.
We co-sell with AWS, so your AWS account team can join the evaluation. They connect the clinical and operational leaders who want the outcome with the cloud team that owns your AWS relationship and commitment.
Simulate care workflows before rollout.
Create digital twins of every patient in your Health World Model and train your workflows across millions of simulated scenarios. We hydrate your environment with synthetic patient data to test realistic scenarios, edge cases, and user experience before release. Agents must prove their reliability on accuracy, empathy, and harm prevention before a single real deployment.
Connected on AWS
One Concurrence control plane connects your workflows to AWS data services. Bring data from Amazon Redshift and AWS HealthLake into the Health World Model, and publish authorized outputs back.
on AWS
Warehouse queries and analytics.
Authorized queries. Analytical outputs.
on AWS
FHIR R4 resources and write-back.
FHIR R4 reads. Authorized updates.
on AWS
Processing, governance and serving.
Governed reads. Published data products.
on AWS
Governed data access and data products.
Authorized reads. Published outputs.
AWS reference architecture
Concurrence manages tenant configuration, access and workflow orchestration on AWS. The application runtime on Amazon EKS connects to Amazon Redshift and AWS HealthLake through governed reads and authorized outputs.
| AWS data service | Role | Data access and outputs |
|---|---|---|
| Amazon Redshift | Warehouse queries and analytical outputs. | Query authorized warehouse data and publish analytical outputs to Amazon Redshift. Schemas, query permissions, transformations and output destinations are configured for the workload. |
| AWS HealthLake | FHIR R4 data access and authorized write-back. | Read FHIR R4 resources into the Health World Model and write authorized updates back to the HealthLake data store. Resource types, permissions and validation rules are configured for the workflow. |
Data accounts and managed services run outside the Concurrence VPC. Account boundaries, data permissions and Region availability are configured for each deployment.
Model requests use an AWS-hosted route to Amazon Bedrock, with endpoints and inference profiles configured for each workload. This reference uses AWS-hosted application and control services. Other deployment configurations and provider routes require separate eligibility review.
Security & compliance
Independent assessments, plus the AWS-specific controls to review with your security team before PHI goes live.
Visit our security page
Certified for the Concurrence platform. Review the certified scope against your AWS deployment.
PHI processing requires an executed BAA, HIPAA-eligible AWS services, and the required security configuration. Review model-specific retention and processing terms for your selected Amazon Bedrock models.
An independent report covers Security, Availability, and Confidentiality. Review its system boundary and period against your AWS deployment.
EU/DE data residency deployed in production.
Hosting location and model processing location are separate. Amazon Bedrock inference can stay in one Region or use a geographic or global cross-Region inference profile, depending on the model. Review the selected models, inference profiles, and destination Regions with your security team.
Define the data products Concurrence can read and publish, with scoped permissions in your data platform. Storage ownership, lineage, audit and any transfers are reviewed for the selected integration.
We enable read and write integrations with leading EHR and care delivery platforms using industry standard HL7v2 and FHIR interfaces. Based on your team’s use cases, we will scope out the correct integration mechanisms and endpoints. Our team brings knowledge from building 100+ health system vendor integrations.
Concurrence is a healthcare data and AI platform that runs on Amazon Web Services. It unifies patient data into a Health World Model, runs AI workflows across the patient and clinician journey, and identifies Patient Trajectories that connect specific interventions to specific outcomes.
Eligible purchases can count toward an AWS spend commitment you have already made, procurement and billing run through your AWS account, and your AWS account team can support the evaluation alongside Concurrence. Concurrence Data and AI Platform is listed in AWS Marketplace as a software-as-a-service contract, sold by Concurrence and purchased through a private offer. Contract terms, security review and data-access approvals remain part of your procurement process.
The listing carries the Deployed on AWS badge. Eligible AWS Marketplace purchases can count toward an AWS spend commitment, such as a Private Pricing Agreement, and AWS determines eligibility for each product. Pricing, purchase options, and commitment eligibility depend on the current listing and your agreement with AWS.
The Concurrence control plane and runtime run on AWS, managed by Concurrence, with the runtime on Amazon Elastic Kubernetes Service (Amazon EKS). The control plane manages tenant configuration, access and orchestration. Amazon Redshift and AWS HealthLake provide supported data connections; customers can use one or combine them for their workflows. Amazon S3 stores data and application artifacts, and model requests reach Amazon Bedrock through the configured AWS-hosted route. Endpoints, inference profiles, permissions and Regions are selected for each deployment. Other model, speech or external provider configurations require separate review against AWS Marketplace hosting requirements.
AWS requires the product application and control planes to run entirely on AWS. Third-party services that transmit, store or process buyer application data must also run entirely on AWS, with exceptions for content delivery networks, DNS and corporate identity providers. The reference diagrams show an AWS configuration; the listing badge does not establish eligibility for every optional integration or provider route.
Yes. Concurrence supports AWS HealthLake for FHIR R4 resource reads into the Health World Model and authorized write-back to your HealthLake data store. Resource types, Regions, permissions and validation rules are configured for each deployment.
Concurrence supports the following AWS data services individually or together, with the application runtime on Amazon EKS. Amazon Redshift: Warehouse queries and analytical outputs. Query authorized warehouse data and publish analytical outputs to Amazon Redshift. Schemas, query permissions, transformations and output destinations are configured for the workload. AWS HealthLake: FHIR R4 data access and authorized write-back. Read FHIR R4 resources into the Health World Model and write authorized updates back to the HealthLake data store. Resource types, permissions and validation rules are configured for the workflow. Concurrence also supports Databricks and Snowflake on AWS; integration details are scoped with your team.
Hosting location and model processing location are separate. Amazon Bedrock inference can stay in one Region or use a geographic or global cross-Region inference profile, depending on the model. Review the selected models, inference profiles, and destination Regions for your deployment. PHI processing requires an executed BAA, HIPAA-eligible services, and the required security configuration.
Learn more about the Concurrence platform, security and compliance, and global availability.
Read the AWS Marketplace hosting requirements for the Deployed on AWS designation.