A AWS reference architecture for automated patient intake and eligibility checks in Healthcare. Triggered by new patient form submitted (portal, fax, or referral), Padiso orchestrates 3 specialist agents on Amazon Bedrock AgentCore, reaching ehr (epic / cerner) and your tools through the Model Context Protocol, with budgets, approvals and an audit trail throughout.
Trigger
New patient form submitted (portal, fax, or referral)
Healthcare
Orchestration

Padiso Orchestrator
goals · tasks · heartbeat
Governance
budgets · approvals · audit
Runtime & agents
Agent runtime
Amazon Bedrock AgentCore
Intake coordinator
agent
Claims & billing agent
agent
Scheduling agent
agent
Integrations · MCP
MCP gateway
Your systems
EHR (Epic / Cerner)
Payer eligibility (X12 270/271)
Document store
Trigger: New patient form submitted (portal, fax, or referral)
Intake agent parses the form and structures demographics and insurance into your schema
Eligibility agent sends an X12 270 to the payer and reconciles the 271 response
Records agent writes the verified patient and coverage into the EHR, flagging gaps
Any coverage mismatch is held for staff approval before the chart is finalized
Reached through the Model Context Protocol, scoped and governed.
Amazon Bedrock AgentCore
EHR (Epic / Cerner)
Payer eligibility (X12 270/271)
Document store
AWS deployment
Deployed in your AWS account on Bedrock AgentCore, with IAM scoping, PrivateLink to your VPC, and CloudTrail/CloudWatch for audit and observability.
Start free, or talk to us about putting an agent workforce to work across your operations.