Angle 1 — `existing-reference-repos`
Generated at build time from
research/aws-demo-catalog/sources/existing-reference-repos.mdin the repo — edit the source, not this page.
Date: 2026-09-04. Scout output for research/aws-demo-catalog/brief.md, angle 1. Every catalog reference is to catalog-v0.md by item and tier.
Summary
AWS-official public code now covers the AI layers of the catalog far better than the core workflows. The strongest finds are: the GenAI IDP Accelerator (U4 Tier 1+2, one-click, pushed today), the 2026 "Amazon Connect Health" sample family (U3 Tier 1+2 with HealthLake write-back; U6 patient verification), sample-healthcare-agents (U4 Tier 2 prior-auth / eligibility / coding agents on AgentCore + Strands, CDK, pushed 2026-09-03), sample-healthscribe-bedrock-clinical-analysis (U3 Tier 1+2 on CDK), the LZA-for-Healthcare configuration (F0, but organisation-only), and the multimodal health data Guidance (U5 Tier 1+3, notebook-driven). Nothing AWS-official demonstrates U1 Tier 1 (patient portal + native mobile app), U2 Tier 1 (device → IoT Core → Flink → InfluxDB/Iceberg remote patient monitoring), phone-paired HealthKit/Health Connect/BLE ingestion on a current Amplify generation, AgentCore Gateway MCP tools over telemetry (U2 Tier 2), Greengrass v2 edge scoring without SageMaker Edge Manager (U2 Tier 3), or any of the Tier 3 healthcare-specific models newer than 2022. Several otherwise-relevant repos depend on retired services (Pinpoint, Bedrock Agents classic, A2I/Ground Truth, SageMaker Edge Manager, IoT Analytics) and are flagged below. Workshop Studio pages are JavaScript-only and could not be read by the fetch tool; workshop titles are recorded from the search index with that caveat. Licenses are MIT-0 unless noted; the one non-permissive find is aws-security-reference-architecture-examples (CC-BY-SA-4.0).
Repo metadata (pushed_at, license, archived, stars) was retrieved from the GitHub REST API on 2026-09-04 unless stated otherwise. "Pushed" is the GitHub pushed_at field, i.e. last commit push to any branch.
Table A — artefacts found, by catalog item and tier
Coverage scale: full = deploys the catalog tier's workflow end to end; partial = several components wired together but missing major pieces; component = one service or pattern only. Deploy story: empty→running = documented IaC path from a fresh account to a working system; semi = IaC plus manual console steps or an external prerequisite (e.g. an existing Connect instance, an org); snippet = notebooks/CLI only.
F0 — HIPAA-ready landing zone
| Artefact | Maintainer | Pushed / version | IaC / stack | License | Tier(s) | Coverage | Deploy story | Notes |
|---|---|---|---|---|---|---|---|---|
| aws-samples/landing-zone-accelerator-on-aws-for-healthcare | aws-samples | pushed 2026-06-18; latest release v1.9.0-e dated 2025-11-29 (README) | LZA YAML config (global/security/organization/network) executed by the LZA engine (CloudFormation + CodePipeline + CDK) | MIT-0 | F0 | full for org-level F0: Config rules from the "Operational Best Practices for HIPAA Security" conformance pack, SCP scp-hlc-hipaa-service.json restricting to HIPAA-eligible services, Security Hub, GuardDuty, CloudTrail, KMS, centralised VPC endpoints, Transit Gateway | semi: requires AWS Control Tower with Management/Audit/LogArchive accounts and an OU tree (Infrastructure, HIS, EIS); README states it is "not designed for single-account deployments"; ~US$400–500/month idle (README) | Answers brief open question 2: this F0 example assumes an organisation. Macie, WAF/Shield, IAM Identity Center, tagging not confirmed in README summary — check config files before claiming. AWS Industries blog "Introducing Landing Zone Accelerator for Healthcare" (undated in results) is the announcement. |
| awslabs/landing-zone-accelerator-on-aws | awslabs (AWS Solutions) | pushed 2026-09-03; 825 stars | CDK (TS) engine; CloudFormation launch | Apache-2.0 | F0 | component (the engine the healthcare config runs on) | semi (org required) | Deployable AWS Solution; docs at docs.aws.amazon.com/solutions/latest/landing-zone-accelerator-on-aws/. |
| aws-solutions/aws-control-tower-customizations (CfCT) | aws-solutions | pushed 2026-07-01; 416 stars | CloudFormation + CodePipeline | Apache-2.0 | F0 | component | semi (org required) | Confirms Control Tower is still the actively maintained landing-zone path as of 2026-07 (angle 2 owns the formal status question). |
| aws-samples/aws-security-reference-architecture-examples | aws-samples | pushed 2026-09-04; 1,152 stars | CloudFormation (via CfCT) and Terraform | CC-BY-SA-4.0 (LICENSE file, fetched 2026-09-04; GitHub reports NOASSERTION) | F0 | partial (Security Hub, GuardDuty, Macie, Config, CloudTrail org patterns) | semi (org required) | Non-permissive: flag for open question 5. Do not fork; can be linked. |
| aws-samples/deploy-conformance-pack-for-aws-startup-security-baseline | aws-samples | pushed 2025-03-28 | CDK | MIT-0 | F0 | component (single-account conformance-pack deploy pattern; not the HIPAA pack) | empty→running (single account) | Only single-account F0-style pattern found; swap in the HIPAA pack template. |
| awslabs/aws-config-rules — Operational-Best-Practices-for-HIPAA-Security.yaml; docs page Operational Best Practices for HIPAA Security | awslabs / AWS docs | retrieved 2026-09-04 | CloudFormation conformance pack | (repo) | F0 | component | n/a | The pack name catalog-v0 asks to VERIFY still exists under this name (angle 2 confirms formally). |
| aws-samples/sample-hipaa-assistant | aws-samples | pushed 2026-07-08 | Go CLI + MCP server; reviews CloudFormation/Terraform; optional Bedrock | MIT-0 | F0 (portal chapter aid) | component | n/a (tool, not infra) | Flags HIPAA Security Rule gaps with eCFR citations; explicitly "does not guarantee compliance". Useful as an F0 chapter demo of evidence generation. |
| aws-samples/sample-hipaa-serverless-medical-reimbursement | aws-samples | pushed 2026-07-16 | SAM | MIT-0 | F0 / U4 Tier 1 | component (per-domain KMS envelope encryption, TLS-only queues, audit) | empty→running | Illustrative, "not a certified HIPAA solution" (README). |
| Guidance for Workload Isolation on AWS (page) | AWS Solutions Library | retrieved 2026-09-04 | — | — | F0 | component | — | Surfaced by search only; not read in depth. |
| HIPAA Quick Start (2017, "quickstart-compliance-hipaa") | formerly aws-quickstart | What's New 2017-08 | CloudFormation | — | F0 | — | — | Not found in any AWS org; only a personal fork survives. Treat as retired; do not link. |
U1 — Patient portal + companion mobile app
| Artefact | Maintainer | Pushed | IaC / stack | License | Tier(s) | Coverage | Deploy story | Notes |
|---|---|---|---|---|---|---|---|---|
| aws-samples/aws-healthlake-smart-on-fhir | aws-samples | 2024-03-16 | CDK (TS); HealthLake + Lambda token verifier + Secrets Manager; external OAuth2 (ORY) | MIT-0 | U1 Tier 1 | component (SMART-on-FHIR HealthLake datastore; no UI, no Cognito) | empty→running | Closest official pattern for "patient reads their own FHIR record". |
| aws-samples/sample-intelligent-security-for-healthcare-apis | aws-samples | 2026-08-14 | CloudFormation + deploy script; API Gateway, Lambda FHIR processor, Cognito MFA, DynamoDB RBAC, EventBridge, Bedrock anomaly/sensitivity classification, Comprehend Medical PHI redaction, Bedrock Guardrail | MIT-0 | U1 Tier 1 (API/auth layer) + cross-cutting compliance | partial | empty→running (10–15 min per README); HealthLake optional | Good fork target for the U1 API boundary and the "compliance evidence" chapter. |
| aws-samples/serverless-patient-engagement-stack | aws-samples | 2025-04-01 | CDK (TS); API Gateway HTTP, Lambda, DynamoDB streams, EventBridge scheduler, Amazon Pinpoint, Amazon Connect | MIT-0 | U1 Tier 1 (reminders) / U6 | partial (backend only, no UI) | semi (Cloud9 + Connect auto-config) | Uses Pinpoint (catalog rule 4, VERIFY item) — cannot be linked as-is. |
| aws-samples/aws-patient-digital-front-door | aws-samples | 2024-04-25 | Python; Bedrock Knowledge Bases + OpenSearch Serverless; no IaC in README | MIT-0 | U1 Tier 2 | component | snippet | Member-experience RAG, not a deployable portal. |
| aws-samples/extract-medical-insights-from-amazon-healthlake-with-bedrock | aws-samples | 2024-11-05 | Python chat app; Bedrock text-to-SQL/FHIR over HealthLake | Apache-2.0 | U1 Tier 2 / U5 Tier 2 | partial (clinician/analyst-facing, not patient-facing) | semi | Permissive but not MIT-0; fine to fork. |
| aws-samples/sample-bedrock-agentcore-healthcare-s3vectors | aws-samples | 2026-07-16 | AgentCore + S3 Vectors multi-agent clinical decision support | MIT-0 | U1 Tier 2 (assistant pattern) | partial (not patient-facing; no FHIR tools) | not verified | README notes HIPAA/de-identification emphasis (search summary). |
| aws-samples/sample-healthcare-agent-with-agentcore-on-aws | aws-samples | 2026-08-03 | AgentCore CLI deploy (no CDK); AgentCore Runtime + Bedrock Llama 3.1 70B + SageMaker Bio-ELECTRA endpoint + OpenSearch; smolagents | MIT-0 | U1 Tier 2 + Tier 3 (a SageMaker endpoint called by the agent) | partial (medication Q&A; no UI/portal) | semi | Demonstrates "agent calls a custom SageMaker model" — the Tier 2→3 bridge. |
| aws-samples/aws-amplify-cdk-iot-ble-swift-app | aws-samples | 2026-08-04 (but README references CDK v1.105, CocoaPods → pre-Gen-2 Amplify, CDK v1) | CDK v1 + Amplify iOS (Gen 1-era) + Cognito + IoT Core MQTT + S3 | MIT-0 | U1 Tier 1 mobile / U2 Tier 1 device pairing | component | semi | The only AWS-official "phone reads BLE sensor → IoT Core" sample; stack is stale. AWS Mobile blog "Bluetooth Low Energy (BLE) IoT mobile application with AWS Amplify, AWS IoT and Swift" is the companion post. |
| aws-samples/aws-iot-proxy-mobile-app-android | aws-samples | 2020-08-13, archived | Android BLE→MQTT proxy | MIT-0 | U2 Tier 1 device pairing (Android) | component | — | Archived; structural reference only. |
aws-samples org search amplify gen2 | — | retrieved 2026-09-04 | — | — | U1 Tier 1 mobile | — | — | Zero repositories in aws-samples match "amplify gen2" in name/description. GitHub topic amplify-gen2 (retrieved 2026-09-04) lists 14 community repos, none AWS-owned; one is React Native/Expo (mattenarle10/expo-amplify). Angle 3 owns the Amplify library question; the finding here is only that no AWS-official Gen 2 healthcare or mobile sample exists. |
| vintasoftware/aws-healthlake-cognito-api-gateway-infra | community (Vinta) | not fetched | HealthLake + Cognito + API Gateway | not verified | U1 Tier 1 | component | not verified | Lead only; label as community if used. |
| Workshops (Workshop Studio; titles from search index, pages not fetchable): Amazon HealthLake Workshop with code in aws-samples/healthlake-workshop (MIT-0, pushed 2026-01-29, archived); SMART on FHIR with AWS HealthLake; AWS HealthLake Patient Matching with AWS Entity Resolution | AWS | index retrieved 2026-09-04 | — | — | U1 Tier 1 (FHIR store), U5 Tier 1 | component | event/own account (unverified) | HealthLake workshop teaches create datastore → import Synthea → export → QuickSight dashboard (aws.amazon.com/healthlake/getting-started, retrieved 2026-09-04). |
U2 — Remote patient monitoring from connected devices at scale
| Artefact | Maintainer | Pushed | IaC / stack | License | Tier(s) | Coverage | Deploy story | Notes |
|---|---|---|---|---|---|---|---|---|
| aws-solutions-library-samples/guidance-for-aws-iot-greengrass-foundations | AWS Solutions Library | 2026-07-23 | CDK v2 (TS); Greengrass Core, Thing Groups, policies, S3; CodeCatalyst blueprint option | MIT-0 | U2 Tier 1 (gateway) | component | empty→running | Guidance page: aws.amazon.com/solutions/guidance/aws-iot-greengrass-foundations/. |
| aws-samples/aws-greengrass-ec2-device-farm | aws-samples | 2026-08-30 | CDK v2; simulated heterogeneous Greengrass fleet on EC2 | Apache-2.0 | U2 Tier 1 (simulated fleet for demos) | component | empty→running | Useful to demo "fleet" without hardware. |
| aws-samples/aws-iot-greengrass-v2-using-aws-cdk | aws-samples | 2024-08-15, archived | CDK; Greengrass v2 real-time ingestion | MIT-0 | U2 Tier 1 | partial | — | Archived. |
| aws-samples/aws-iot-fleet-provisioning | aws-samples | not fetched | Python reference client | not verified | U2 Tier 1 (fleet provisioning) | component | snippet | Issue #13 discusses Greengrass v2 support. |
| aws-samples/ingesting-iot-data-into-amazon-s3-using-amazon-kinesis-data-firehose | aws-samples | 2023-05-10, archived | CloudFormation; IoT rule → Firehose → S3 | MIT-0 | U2 Tier 1 (cold path) | component | — | Pre-Iceberg. |
| aws-samples/transactional-datalake-using-amazon-datafirehose-iceberg | aws-samples | not fetched | CDK; Firehose → S3 Iceberg (CDC source, not IoT) | not verified | U2 Tier 1 / U5 Tier 1 (Iceberg landing) | component | not verified | Lead; the Firehose→Iceberg pattern with CDK. AWS Big Data Blog 2025-07 "Optimize industrial IoT analytics with Amazon Data Firehose and Amazon S3 Tables with Apache Iceberg" is the IoT-specific writeup (surfaced via aggregator; original not fetched). |
| Timestream for InfluxDB + IoT Core sample | — | searched 2026-09-04 | — | — | U2 Tier 1 (hot path) | none found | — | Only awslabs/amazon-timestream-tools (tools) and the AWS Database Blog "Features and workflows with Amazon Timestream for InfluxDB 3" (undated in results). No aws-samples repo wires IoT Core → InfluxDB with CDK. |
| aws-solutions-library-samples/guidance-for-enhancing-smart-products-through-device-telemetry-and-amazon-connect | AWS Solutions Library | 2026-07-23 | IoT Core telemetry → Amazon Connect | MIT-0 | U2 Tier 1 alerts → U6 | component | not verified | Adjacent: "device telemetry triggers a contact-center action". |
| aws-samples/flink-keyed-random-cut-forest-example | aws-samples | 2025-12-19 | Java; Managed Service for Apache Flink + Kinesis Data Streams; per-key (per-patient) RCF model kept in Flink state; built-in data generator; no IaC (console steps) | MIT-0 | U2 Tier 3 (per-patient anomaly detection) | partial | semi | Exactly the "per-patient RCF" pattern in catalog U2 Tier 3, minus SageMaker and IaC. AWS Big Data Blog "Real-time anomaly detection via Random Cut Forest in Amazon Managed Service for Apache Flink" is the companion. |
| aws-samples/flink-industrial-anomaly-detector; aws-samples/amazon-sagemaker-anomaly-detection-with-rcf-and-deepar | aws-samples | not fetched | Flink RCF; SageMaker RCF/DeepAR notebooks | not verified | U2 Tier 3 | component | snippet | Leads. |
| aws-samples/amazon-sagemaker-feature-store-streaming-inference-msk-kda | aws-samples | 2024-01-04 | Flink (then "KDA") streaming aggregation → Feature Store → SageMaker XGBoost endpoint | MIT-0 | U2 Tier 3 ("real-time endpoint called by Flink") | partial | semi | Pattern match for Flink→SageMaker; fraud domain, pre-rename naming. AWS Architecture Blog "Real-time in-stream inference with Kinesis, SageMaker, Flink" references kda-flink-ml async-I/O sample. |
| aws-samples/amazon-sagemaker-deepar-mlops-pipeline-cdk | aws-samples | 2025-04-10 | CDK; DeepAR MLOps with serverless orchestration | MIT-0 | U2 Tier 3 (deterioration forecasting) | component | empty→running | Generic time-series; not health data. |
| aws-solutions-library-samples/guidance-for-deploying-ai-agents-to-device-fleets-using-aws-iot-greengrass | AWS Solutions Library | 2025-10-27 | Greengrass v2 + Strands Agents + local small language models | MIT-0 | U2 Tier 3 (edge inference on Greengrass v2) | component (LLM at edge, not a quantised scoring model) | not verified | The only current Greengrass-v2 ML/agent Guidance found. |
| aws-samples/greengrass-v2-sagemaker-edge-manager-python | aws-samples | not fetched | Greengrass v2 + SageMaker Edge Manager | not verified | U2 Tier 3 (edge scoring) | partial | — | Edge Manager discontinued 2024-04-26 (docs: SageMaker Edge Manager end of life, retrieved 2026-09-04; AWS recommends Greengrass v2 + ONNX). Cannot be linked as-is. |
| aws-samples/amazon-sagemaker-aws-greengrass-custom-timeseries-forecasting | aws-samples | 2021-03-03, archived | Greengrass (v1-era) + IoT Analytics + SageMaker | MIT-0 | U2 Tier 3 | partial | — | Uses IoT Analytics and Greengrass v1 (retired list). Structural reference only. |
| cleverdevil/healthlake | community | 2022-06-08, archived, no license | Apple HealthKit export → S3 data lake | none | U2 Tier 1 (HealthKit ingest) | component | — | Only HealthKit→AWS repo located; unlicensed and archived. The "Apple Watch HealthKit → MQTT/X.509 → IoT Core → SQS → Lambda → DynamoDB → Flutter dashboard" repo that search summaries described could not be found on the remote-patient-monitoring topic page (fetched 2026-09-04) or by direct search — treat as unverified. |
| awslabs/aws-sdk-ios-samples IoT-Sample/Swift; AWS IoT Device SDKs page (lists AWS IoT Device SDK for Swift, MQTT 5) | awslabs / AWS docs | retrieved 2026-09-04 | Swift MQTT + Cognito identity | Apache-2.0 (SDK samples) | U2 Tier 1 device pairing | component | snippet | Angle 3 owns the recommendation; recorded here as the available sample code. |
| AgentCore Gateway MCP tools over telemetry | — | searched 2026-09-04 | — | — | U2 Tier 2 | none found | — | Nearest generic: aws-samples/sample-strands-agent-with-agentcore (reference architecture), aws-samples/sample-aws-ops-agentcore-gateway-search (Gateway with 268+ AWS operations as tools), aws-solutions-library-samples/guidance-for-multi-agent-orchestration-using-bedrock-agentcore-on-aws. None expose time-series/telemetry queries as typed tools. |
U3 — Ambient clinical documentation
| Artefact | Maintainer | Pushed | IaC / stack | License | Tier(s) | Coverage | Deploy story | Notes |
|---|---|---|---|---|---|---|---|---|
| aws-samples/sample-amazon-connect-health-unified-clinical-workflow | aws-samples | 2026-08-31 | CloudFormation (3–4 sequential stacks); Amazon Connect + Amazon Connect Health (ambient documentation, SOAP, medical coding), HealthLake FHIR R4 write-back, "Amazon Bedrock Agents" for care-manager NL queries, Bedrock Guardrails, ECS Fargate Flask, Kinesis Video Streams, CloudFront/S3 UIs embedded in Connect Agent Workspace | MIT-0 | U3 Tier 1 + Tier 2 (+ U6 adjacency) | near-full (capture → note → coding → HealthLake DocumentReference; human review in workspace) | semi: requires a registered Amazon Connect instance and Connect Health domain; medical coding is "gated preview" | The README names "Amazon Bedrock Agents" for the care-manager workspace — verify whether that is Bedrock Agents classic (retired list) before linking; the Connect Health features themselves are current. Amazon Connect Health GA 2026-03-05, us-east-1/us-west-2, "HIPAA-eligible" per What's New. |
| aws-samples/sample-amazon-connect-health-point-of-care | aws-samples | 2026-03-31 | CloudFormation; Connect Health ambient documentation + patient insights; HealthLake longitudinal record; Bedrock pre-visit narrative; SNS SMS; ECS Fargate (Flask REST + Java WebSocket); 3 CloudFront distributions; optional Cognito | MIT-0 | U3 Tier 1 + Tier 2; U1 Tier 2 (patient insights) | partial→full for note generation | semi (needs Connect Health access, HealthLake datastore with data) | Earlier sibling of the unified-workflow sample. |
| aws-samples/sample-healthscribe-bedrock-clinical-analysis | aws-samples | 2026-04-07 | CDK; AWS HealthScribe real-time streaming + Bedrock "12 specialist agents"; Lambda, ECS Fargate, Step Functions, DynamoDB, S3/CloudFront, Cognito, ACM; React + Vite + Cloudscape | MIT-0 | U3 Tier 1 + Tier 2 | partial→full (no HealthLake write-back documented; no Comprehend Medical coding step named) | empty→running (deploy.sh + frontend script; needs an ACM certificate) | Best stack-spine match for U3 (CDK, Fargate, React/Vite, Cognito, CloudFront). |
| aws-samples/aws-healthscribe-demo | aws-samples | 2025-04-08; 60 stars | Amplify Gen 1 (package.json fetched 2026-09-04: aws-amplify ^6.14, no @aws-amplify/backend), React 19 + Cloudscape, Cognito, S3; HealthScribe → Comprehend Medical ontology linking (ICD-10-CM / SNOMED CT / RxNorm) | MIT-0 | U3 Tier 1 (+ the Comprehend Medical linking step) | partial | semi: docs/deploy.md uses Amplify console + CodeCommit (CodeCommit stopped onboarding new customers in 2024; verify before relying on it) | Most-starred HealthScribe sample; UI patterns worth borrowing, deploy path stale. |
| aws-samples/medical-transcription-analysis | aws-samples | 2023-07-18; 94 stars | CDK; Transcribe Medical streaming WebSocket + Comprehend Medical; React | MIT-0 | U3 Tier 1 (pre-HealthScribe path) | partial | empty→running (yarn deploy) | Older; the "Transcribe Medical where HealthScribe is unavailable" fallback. |
| aws-samples/enhancing-patient-and-clinician-experiences-with-healthscribe | aws-samples | 2026-01-13 | not fetched | MIT-0 | U3 Tier 2 | not verified | — | Lead. |
| aws-samples/sup-hcls-generate-clinical-notes-with-ai | aws-samples | 2024-07-23 | HealthScribe / Bedrock / Transcribe | MIT-0 | U3 Tier 1–2 | not verified | — | Search index says it includes a Transcribe+Bedrock alternative for regions without HealthScribe. |
| aws-samples/amazon-comprehend-medical-fhir-integration | aws-samples | 2024-01-22, archived; 54 stars | Comprehend Medical entities → FHIR resources | MIT-0 | U3 Tier 1 (FHIR mapping) | component | — | Archived. |
| Tier 3 evaluation: aws-samples/healthcare-LLM-as-a-Judge (date truncated in API result), aws-samples/eval-genai-techniques-clinicalreport (2024-04-15) | aws-samples | as noted | notebooks | MIT-0 | U3 Tier 3 (evaluation harness) | component | snippet | No fine-tuned note-quality/coding classifier on SageMaker found. |
U4 — Intelligent document intake
| Artefact | Maintainer | Pushed | IaC / stack | License | Tier(s) | Coverage | Deploy story | Notes |
|---|---|---|---|---|---|---|---|---|
| aws-solutions-library-samples/accelerated-intelligent-document-processing-on-aws ("GenAI IDP Accelerator") | AWS Solutions Library | 2026-09-04; 302 stars; CHANGELOG top v0.6.6 | CloudFormation/SAM one-click (us-east-1, us-west-2, eu-central-1) with CDK and Terraform alternates; Pattern 1 = Bedrock Data Automation end-to-end, Pattern 2 = Textract OCR → Bedrock classify/extract/assess; built-in human review (custom, not A2I); evaluation framework with MLflow; web UI behind Cognito + WAF; MCP via AgentCore Gateway (Quick Suite integration); IDP CLI agent chat | MIT-0 | U4 Tier 1 + Tier 2 | full (generic): intake → extract/classify → confidence-gated review → summarise; no Comprehend Medical / HealthLake / Macie | empty→running | Answers the Textract-vs-BDA sub-question from the repo side: both are first-class in Sept 2026 (BDA is the default pattern; Textract remains for OCR-first). No retired service found in README/CHANGELOG. |
| aws-samples/aws-ai-intelligent-document-processing | aws-samples | 2026-05-04; 244 stars | Linked from Guidance for Intelligent Document Processing on AWS (retrieved 2026-09-04), whose architecture is AgentCore Runtime + Strands multi-agent (Orchestrator / Automation / Trainer / Troubleshooter) + AgentCore Identity/Gateway/Observability + Textract + ECS dashboard | MIT-0 | U4 Tier 2 | partial→full (generic) | not verified from repo | The Guidance's Well-Architected "Security" text explicitly points to Comprehend Medical PHI redaction for clinical text. |
| aws-samples/sample-healthcare-agents | aws-samples | 2026-09-03 | CDK (TS); Amplify-hosted React + Cognito; AgentCore Runtime (Lambda) + Gateway tools; Strands SDK; HealthLake FHIR R4; Comprehend Medical; AWS B2B Data Interchange (EDI 837P); CDS Hooks | MIT-0 | U4 Tier 2 (prior-auth packet assembly, eligibility, medical coding, claims assembly/submission, appeals) | full for Tier 2; Tier 1 intake not included (starts from clinical data, not PDFs) | empty→running (config.yaml with HealthLake datastore ID, cdk deploy --all) | Closest match to catalog U4 Tier 2 wording. Note there is also an archived sibling sample-strands-agents-for-healthcare-and-life-sciences (2026-01-23). |
| aws-samples/sample-smart-prescription-reader | aws-samples | 2026-03-31 | CDK (TS) Nx monorepo; Textract + Bedrock (Claude/Nova) extract → evaluate → correct; Step Functions; Lambda; DynamoDB; AppSync; Cognito; KMS; React + Cloudscape | MIT-0 | U4 Tier 1 + Tier 2 (single document type) | partial | empty→running (pnpm install, nx deploy) | Healthcare-specific, stack-spine-adjacent (AppSync rather than REST). |
| aws-samples/sample-scalable-intelligent-document-processing-with-amazon-bedrock-data-automation | aws-samples | 2026-07-28 | CDK (Python); BDA + Step Functions + SQS + Lambda; human review via SageMaker Ground Truth / A2I | MIT-0 | U4 Tier 1 | partial | semi (manual workforce + A2I workflow setup) | Uses A2I and Ground Truth (retired list). Cannot be linked as-is; the accelerator above supersedes it. |
| aws-solutions-library-samples/guidance-for-multimodal-data-processing-using-amazon-bedrock-data-automation | AWS Solutions Library | 2026-03-25; 66 stars | BDA over documents/images/audio/video | MIT-0 | U4 Tier 1 | component | not verified | Generic BDA Guidance. |
| aws-samples/aws-ai-phi-deidentification | aws-samples | 2025-04-23 | CDK single-command; React UI; Textract OCR → Comprehend Medical PHI detection → bulk redaction | MIT-0 | U4 Tier 1 (PHI step) / U5 Tier 1 (de-identification pipeline) | partial | empty→running | The only deployable de-identification pipeline found. |
| aws-samples/amazon-textract-idp-cdk-constructs | aws-samples | 2024-04-29 | CDK constructs (TS) | MIT-0 | U4 Tier 1 | component | — | Stale (16 months). |
| Guidance for Ingesting PDF and Image Files to AWS HealthLake (page, diagram PDF) | AWS Solutions Library | retrieved 2026-09-04; undated | CloudFormation; Lambda + S3 + HealthLake (Textract mentioned) | — | U4 Tier 1 → HealthLake | partial | no sample-code link on page | Architecture only. |
| Blogs: Build an agentic AI healthcare claims pipeline with Amazon Bedrock and AWS HealthLake (ML blog, 2026-06-29: CMS-1500 → BDA → Strands agent on AgentCore → FHIR Claim in HealthLake); Prior authorization for medical claims using Strands Agents (Industries blog, undated in results) | AWS blogs | as noted | — | — | U4 Tier 1+2 | design references | — | Code for the claims-pipeline post was not located as a standalone repo (search pointed to the HCLS agents toolkit). |
| Workshop: "Intelligent Healthcare Systems: FHIR, AI, and AWS HealthLake" (Workshop Studio) | AWS | index retrieved 2026-09-04; page not fetchable | — | — | U4 Tier 1 → U5 | per index: CMS-1500 claims and SOAP notes → queryable FHIR | unverified | Angle 4 should confirm module list. |
U5 — Population health analytics and risk models
| Artefact | Maintainer | Pushed | IaC / stack | License | Tier(s) | Coverage | Deploy story | Notes |
|---|---|---|---|---|---|---|---|---|
| aws-solutions-library-samples/guidance-for-multi-modal-data-analysis-with-aws-health-and-ml-services; Guidance page now at docs.aws.amazon.com/solutions/multi-modal-data-analysis-with-aws-health-and-ml-services/ | AWS Solutions Library | 2024-12-17 | CloudFormation one-click (SageMaker domain) + sequential notebooks; HealthOmics + HealthLake + HealthImaging → Lake Formation → Athena → QuickSight; SageMaker Feature Store; AutoGluon-Tabular; real-time endpoint; Synthea coherent dataset | MIT-0 | U5 Tier 1 + Tier 3 | partial→full (governed lake + dashboards + risk models) but notebook-driven, QuickSight-era naming (Quick now), no S3 Tables/Iceberg, no de-identification step | semi | Guidance page has 10-step architecture and Well-Architected pillars (retrieved 2026-09-04, undated). Closest existing thing to the U5 chapter. |
| aws-solutions-library-samples/guidance-for-patient-entity-resolution-with-aws-healthlake (Guidance page) | AWS Solutions Library | 2025-09-11 | HealthLake + AWS Entity Resolution | MIT-0 | U5 Tier 1 (master patient index) | component | not verified | Companion workshop exists (see U1 row). |
| aws-samples/aws-ai-phi-deidentification | aws-samples | 2025-04-23 | see U4 | MIT-0 | U5 Tier 1 (de-id) | partial | empty→running | — |
| aws-samples/sample-s3-annotations-healthcare-data-lineage | aws-samples | 2026-07-08 | not fetched | MIT-0 | U5 Tier 1 (lineage/governance) | not verified | — | Lead. |
| aws-samples/extract-medical-insights-from-amazon-healthlake-with-bedrock | aws-samples | 2024-11-05 | see U1 | Apache-2.0 | U5 Tier 2 (NL analytics over HealthLake) | partial | semi | Text-to-SQL; predates Quick. |
| aws-samples/aws-ml-readmission-prediction | aws-samples | 2022-04-18 | SageMaker notebooks, HPO, real-time inference pipeline; README claims HIPAA-eligible services | MIT-0 | U5 Tier 3 (readmission risk) | partial | snippet | 4+ years old. |
| aws-samples/amazon-sagemaker-data-wrangler-hospital-readmission-prediction | aws-samples | 2021-10-25 | Data Wrangler workshop, UCI diabetic dataset | MIT-0 | U5 Tier 3 | component | snippet | Stale. |
| aws-samples/amazon-healthlake-patient-outcome-prediction | aws-samples | 2022-09-06, archived | HealthLake + SageMaker, Synthea | MIT-0 | U5 Tier 3 | partial | — | Archived. |
| aws-samples/ai-ml-sagemaker-multi-model-pipeline | aws-samples | 2022-10-23 | SageMaker Pipelines on diabetic patient data | MIT-0 | U5 Tier 3 | component | snippet | Stale. |
aws-samples/sample-Adverse-Drug-Reaction-Prediction-Using-AWS-HealthLake-and-AWS-Clean-Rooms-Part1 / Part2; sample-PredictPatientsAdverseDrugReactionsUsingAWSCleanRoomsMLandCloudFormation (2026-05-25) | aws-samples | 2026-07-09 | HealthLake + Clean Rooms ML; CloudFormation variant | MIT-0 (one sibling has no license) | U5 Tier 3 (cross-org risk model) | not verified | — | Newest healthcare ML samples; Clean Rooms angle is outside the catalog spine. |
| Generic MLOps spine: aws-samples/amazon-sagemaker-pipeline-deploy-manage-100x-models-python-cdk (2026-07-28, MIT-0, CDK; Pipelines + Model Registry + quality checks); aws-samples/regulated-mlops-using-amazon-sagemaker; aws-samples/mlops-e2e | aws-samples | as noted | CDK | MIT-0 | U1/U2/U3/U4/U5 Tier 3 (Pipelines, Registry) | component | empty→running | Reusable Tier 3 scaffolding; no healthcare data. Clarify-successor question is angle 2's. |
| aws-samples/aws-healthcare-lifescience-ai-ml-sample-notebooks | aws-samples | 2025-12-16; 116 stars | notebooks | MIT-0 | U5 Tier 3 | component | snippet | Notebook library; not a deployment. |
| AWS ML Blog "Population health applications with Amazon HealthLake – Part 1: Analytics and monitoring using Amazon QuickSight" | AWS | 2021 (LinkedIn share dated 2021) | Glue + Athena + QuickSight | — | U5 Tier 1 | design reference | — | Dated; QuickSight is now Quick (dossier). |
U6 — Patient engagement contact center with AI agents (light pass per brief default 7)
| Artefact | Maintainer | Pushed | IaC / stack | License | Tier(s) | Coverage | Deploy story | Notes |
|---|---|---|---|---|---|---|---|---|
| Amazon Connect Health (product page; What's New 2026-03-05) | AWS (product) | GA 2026-03-05 | Managed: patient verification (GA), ambient documentation (GA), appointment management / patient insights / medical coding (preview); us-east-1, us-west-2; "HIPAA-eligible" | — | U6 Tier 1 + Tier 2; U3 | product, not repo | — | Changes the U6 build decision: identity verification and scheduling are now first-party features rather than Lex+Lambda code. |
| aws-samples/sample-healthcare-realtime-eligibility | aws-samples | 2026-03-03 | Lambda integrating Real-Time Eligibility into Connect Health | MIT-0 | U6 Tier 1 | component | not verified | — |
| aws-samples/sample-Nova-Sonic-AgentCore-Healthcare-Call-Center | aws-samples | 2026-05-21 | CDK (Python); AgentCore Runtime + Nova 2 Sonic speech-to-speech; Cognito; DynamoDB; SNS escalation; WebSocket audio; no Amazon Connect | MIT (not MIT-0; permissive) | U6 Tier 2 (outbound appointment agent) | partial | empty→running (deployment guide in docs/) | Modern agent stack; not a contact-center integration. |
| aws-samples/sample-amazon-connect-bedrock-agent-voice-integration | aws-samples | 2025-11-18 | CDK (TS); Connect → Lex → Bedrock Agents classic (action groups) → Lambda → DynamoDB; Nova Micro | MIT-0 | U6 Tier 1+2 (booking assistant) | partial | empty→running (issues a phone number) | Uses Bedrock Agents classic (retired list). Cannot be linked as-is; structure (Connect+Lex+CDK) is reusable. |
| aws-samples/voice-enabled-patient-diary | aws-samples | 2024-08-27 | Lex + Connect outbound calls; patient-reported outcomes | MIT-0 | U6 Tier 1 | partial | not verified | Lex version not verified (Lex V1 is retired). |
| aws-samples/amazon-connect-with-amazon-lex-genai-capabilities; aws-samples/omnichannel-experience-bot-with-bedrock-and-lex | aws-samples | not fetched | Connect + Lex + Bedrock | not verified | U6 Tier 2 | component | — | Leads (generic). |
| aws-solutions-library-samples/guidance-for-connecting-automated-inputs-to-contact-centers-on-aws | AWS Solutions Library | 2025-11-18 | IoT / IVR inputs → contact center | MIT-0 | U6 ↔ U2 | component | — | Adjacent. |
| Workshops: Getting started with Amazon Connect; Amazon Connect forecasting, capacity planning, and scheduling; amazon-connect/amazon-connect-workshops | AWS / amazon-connect org | index retrieved 2026-09-04 | — | — | U6 Tier 1; Tier 3 (demand forecasting is a Connect product feature, not SageMaker) | link-out candidates | — | No healthcare-specific Connect workshop found. |
P0 — Education portal
| Artefact | Maintainer | Date | What it is | Relevance |
|---|---|---|---|---|
Workshop Studio (catalog.workshops.aws); discovery moved to builder.aws.com/build/workshops per What's New 2025-11-18; workshops.aws/categories/* now 301-redirects there (observed 2026-09-04) | AWS | 2025-11-18 | AWS's own learn-by-deploying platform | Both the old category pages and the new Builder Center listing are JavaScript-rendered and returned no content to the fetch tool; angle 4 owns structure. Healthcare workshop titles located via search index: Amazon HealthLake Workshop; SMART on FHIR with AWS HealthLake; Intelligent Healthcare Systems: FHIR, AI, and AWS HealthLake; AWS HealthLake Patient Matching with AWS Entity Resolution; an "introduction workshop on generating clinical notes using AWS HealthScribe, Amazon Bedrock and Amazon Transcribe" (title only, URL not located). |
| aws-samples.github.io/amazon-bedrock-agents-healthcare-lifesciences (repo aws-samples/amazon-bedrock-agents-healthcare-lifesciences, pushed 2026-09-03, 268 stars, MIT-0; 36+ agents on AgentCore + Strands despite the "bedrock-agents" name; CloudFormation shared infra; life-sciences focus, no provider-side agents) | aws-samples | 2026-09-03 | A GitHub-Pages docs site generated from the repo ("Developer Guide", agent catalog, skills/MCP servers usable from Claude Code / Kiro / Quick) | The clearest AWS example of portal content generated from the repo itself — the P0 "content from README/ADR" pattern. Linked from the Health AI Hub as "Life Sciences Toolkit". |
| AWS Health AI Hub | AWS (EMEA) | retrieved 2026-09-04, undated | Applications / Lab / Knowledge; nine partner use cases plus the LS toolkit | Comparator for P0; mostly partner products, not deployable repos. |
| healthcare.awsaccelerators.com/healthcare-demos.html | AWS (NHS-oriented) | retrieved 2026-09-04, undated | Eleven generative-AI healthcare demos (symptom checker, MedSpeak, care plans, PHQ-9/GAD-7 screening, etc.) | Comparator: a demo portal, but no GitHub/deploy links on the page. |
| Any public "education portal" repo for this purpose | — | searched 2026-09-04 | — | None found; P0 is build-new by definition. |
Table B — catalog items and tiers with NO good public example (new-work value)
| Item / tier | What was searched | Closest thing found | Verdict |
|---|---|---|---|
| F0, single-account "empty account → HIPAA baseline" | aws-samples/awslabs/aws-solutions + Solutions Library for HIPAA/landing zone/conformance pack | LZA-for-Healthcare (organisation-only, US$400–500/mo idle); startup-baseline conformance-pack CDK sample (not HIPAA pack) | No example. New work: single-account CDK stack (KMS, CloudTrail, Config HIPAA pack, Security Hub, GuardDuty, Macie, VPC endpoints, WAF) with LZA as the optional org extension (brief open question 2 default). |
| U1 Tier 1 patient portal + iOS/Android app | aws-samples "patient portal/engagement", Amplify Gen 2 samples, HealthLake+Cognito | SMART-on-FHIR HealthLake (no UI); healthcare-APIs security sample (API layer); zero aws-samples Amplify Gen 2 repos | No example. Highest demonstration value in the catalog. |
| U1 Tier 2 patient-facing assistant over the patient's own FHIR data via AgentCore Gateway tools | AgentCore + HealthLake + MCP | Clinician-facing chat (text-to-SQL, 2024); AgentCore medication agent (no FHIR); Industries blog on an open-source HealthLake MCP server (lead, not fetched) | No example. |
| U1 Tier 3 no-show / adherence model | SageMaker + appointment | nothing | No example. |
| U2 Tier 1 RPM end-to-end (X.509 devices → IoT Core → Kinesis → Flink → Timestream for InfluxDB + Firehose → Iceberg/Athena → alerts → app) | aws-samples, Solutions Library IoT Guidance, Marketplace | Components only (Greengrass foundations Guidance, EC2 device farm, archived Firehose→S3, Firehose→Iceberg CDC sample); Marketplace partner offerings (not code) | No example. Second-highest demonstration value. |
| U2 phone-paired devices HealthKit / Health Connect / BLE → IoT Core | aws-samples, community | CDK-v1/Amplify-Gen-1 BLE Swift sample; archived Android proxy; archived unlicensed HealthKit→S3 | No current example. |
| U2 Tier 2 telemetry as typed MCP tools on AgentCore Gateway | AgentCore Gateway samples | Generic Gateway samples (AWS ops, protein tools) | No example. |
| U2 Tier 3 Greengrass v2 edge scoring with a SageMaker-trained model, post-Edge-Manager | Greengrass ML samples | Edge-Manager sample (service discontinued 2024-04-26); IoT-Analytics sample (archived); Strands SLM-at-edge Guidance (LLM, not scoring) | No current example. |
| U3 Tier 3 note-quality / coding-suggestion classifier | SageMaker + clinical notes | LLM-as-a-judge notebooks | No example (evaluation harness partially covered). |
| U4 Tier 3 document-type classifier / denial-risk model on SageMaker | IDP + SageMaker | Accelerator classifies with Bedrock, not SageMaker | No example. |
| U5 Tier 1 governed lake on S3 Tables/Iceberg + Quick + de-identification | HealthLake export, Iceberg, Quick | Multimodal Guidance (Lake Formation + Athena + QuickSight, notebooks, 2024-12) + separate de-id sample | Partial only; integration is new work. |
| U5 Tier 3 readmission / chronic-risk model on current SageMaker (Pipelines, Registry, Feature Store) | aws-samples healthcare ML | All healthcare readmission samples are 2021–2022; generic MLOps CDK is current | Stale only. |
| U6 Tier 1 Connect + Lex V2 + Cognito identity without retired components | Connect samples | Voice sample uses Bedrock Agents classic; Connect Health now provides patient verification as a product | Partial; likely resolved by linking to Connect Health rather than building. |
| P0 | — | Repo-generated docs site (HCLS agents toolkit) as a pattern | Build new (expected). |
Retired-service dependencies found (catalog rule 4)
| Repo | Retired dependency | Consequence |
|---|---|---|
| aws-samples/serverless-patient-engagement-stack | Amazon Pinpoint | Cannot link as-is (Pinpoint is the catalog's VERIFY item; angle 3 confirms lifecycle). Fork for CDK/EventBridge structure only. |
| aws-samples/sample-amazon-connect-bedrock-agent-voice-integration | Bedrock Agents classic (action groups) | Cannot link as-is. |
| aws-samples/sample-scalable-intelligent-document-processing-with-amazon-bedrock-data-automation | SageMaker A2I + Ground Truth | Cannot link as-is; GenAI IDP Accelerator supersedes. |
| aws-samples/greengrass-v2-sagemaker-edge-manager-python; aws-greengrass/aws-greengrass-component-examples (sagemaker-edge-manager folder) | SageMaker Edge Manager (EOL 2024-04-26) | Cannot link as-is. |
| aws-samples/amazon-sagemaker-aws-greengrass-custom-timeseries-forecasting | IoT Analytics, Greengrass v1 | Archived; cannot link. |
| aws-samples/sample-amazon-connect-health-unified-clinical-workflow | README says "Amazon Bedrock Agents" for the care-manager workspace | Verify classic vs AgentCore before linking; rest of the repo is current. |
| aws-samples/aws-healthscribe-demo | Amplify Gen 1 + CodeCommit deploy path | Not on the retired list, but the deploy path is stale; verify CodeCommit availability (new-customer onboarding stopped 2024). |
| aws-samples/amazon-bedrock-agents-healthcare-lifesciences | Name suggests classic Agents, but README (fetched 2026-09-04) states AgentCore + Strands | Safe; name is historical. |
Gaps — searched for and not found
- Any AWS-official Amplify Gen 2 sample (web or native mobile) in aws-samples with a healthcare framing; aws-samples org search returned 0 repos for "amplify gen2".
- An AWS-official HealthKit / Health Connect → AWS ingestion sample; only an archived community HealthKit→S3 project.
- The community "Apple Watch → IoT Core → Flutter dashboard" repo repeatedly described by search summaries; not present on the
remote-patient-monitoringtopic page and not found by direct query. Treated as unverified. - An IoT Core → Timestream for InfluxDB sample with IaC.
- An AgentCore Gateway sample exposing time-series or telemetry tools.
- A sample-code link for "Guidance for Ingesting PDF and Image Files to AWS HealthLake".
- A HealthScribe workshop URL on Workshop Studio (title only, via search index).
- Workshop module content: all
catalog.workshops.aws,workshops.aws/categories/*andbuilder.aws.com/build/workshopspages are JS-rendered and returned no content; workshop rows above carry titles/URLs from the search index only. Angle 4 should verify from a browser. - The LZA healthcare docs page on docs.aws.amazon.com returned only a title; facts were taken from the aws-samples README instead.
- Any healthcare readmission/no-show/denial-risk SageMaker sample newer than 2022.
Notes for the comparator
- Fork candidates with stack-spine fit (CDK TS / Fargate / React / Cognito / CloudFront):
sample-healthscribe-bedrock-clinical-analysis(U3),sample-healthcare-agents(U4 Tier 2),sample-smart-prescription-reader(U4, AppSync variant),sample-intelligent-security-for-healthcare-apis(U1 API layer, CloudFormation),guidance-for-aws-iot-greengrass-foundations(U2 gateway). - Link-out candidates: GenAI IDP Accelerator (U4 Tier 1+2 generic; one-click), LZA for Healthcare (F0 org extension), multimodal health Guidance (U5), Amazon Connect Health product + samples (U6 Tier 1; U3 alternative path), HealthLake workshops (U1/U5 FHIR basics).
- Build-new with real demonstration value: F0 single-account, U1 Tier 1+2 (portal + mobile + patient-scoped agent), U2 Tier 1–3 (the whole RPM pipeline), all Tier 3 healthcare models, P0.
- Provenance labels (brief open question 1): everything in Table A is AWS-official except
vintasoftware/...andcleverdevil/healthlake, both marked community. - License flags (open question 5):
aws-security-reference-architecture-examplesis CC-BY-SA-4.0 (non-permissive);sample-Nova-Sonic-AgentCore-Healthcare-Call-Centeris MIT (attribution required, permissive); several are Apache-2.0 (permissive);cleverdevil/healthlakehas no license.
Source list (retrieval or publication dates)
GitHub REST API (api.github.com/repos/..., api.github.com/search/repositories?q=org:...), all retrieved 2026-09-04, for every repo metadata row above.
READMEs fetched 2026-09-04: landing-zone-accelerator-on-aws-for-healthcare; sample-amazon-connect-health-unified-clinical-workflow; sample-amazon-connect-health-point-of-care; serverless-patient-engagement-stack; aws-patient-digital-front-door; sample-healthcare-agent-with-agentcore-on-aws; sample-hipaa-assistant; sample-Nova-Sonic-AgentCore-Healthcare-Call-Center; aws-amplify-cdk-iot-ble-swift-app; sample-healthcare-agents; aws-healthlake-smart-on-fhir; aws-healthscribe-demo (docs/deploy.md and package.json); accelerated-intelligent-document-processing-on-aws (README, CHANGELOG); flink-keyed-random-cut-forest-example; guidance-for-multi-modal-data-analysis-with-aws-health-and-ml-services; sample-smart-prescription-reader; amazon-bedrock-agents-healthcare-lifesciences; sample-intelligent-security-for-healthcare-apis; sample-hipaa-serverless-medical-reimbursement; sample-scalable-intelligent-document-processing-with-amazon-bedrock-data-automation; medical-transcription-analysis; sample-healthscribe-bedrock-clinical-analysis; guidance-for-aws-iot-greengrass-foundations; sample-amazon-connect-bedrock-agent-voice-integration; aws-security-reference-architecture-examples (LICENSE).
AWS pages: Amazon Connect Health What's New (2026-03-05); Amazon Connect Health product page (2026-09-04); Workshops in Builder Center What's New (2025-11-18); Guidance for IDP on AWS (2026-09-04); Guidance for Multi-Modal Data Analysis (2026-09-04); Guidance for Ingesting PDF and Image Files to AWS HealthLake (2026-09-04); SageMaker Edge Manager end of life (2026-09-04); Operational Best Practices for HIPAA Security (2026-09-04); AWS IoT Device SDKs (2026-09-04); Health AI Hub (2026-09-04); healthcare.awsaccelerators.com demos (2026-09-04); HealthLake getting started (2026-09-04); Introducing Landing Zone Accelerator for Healthcare (blog; date not captured); Build an agentic AI healthcare claims pipeline (2026-06-29); Prior authorization using Strands Agents (date not captured); Quick Start HIPAA What's New (2017-08).
GitHub topic pages fetched 2026-09-04: remote-patient-monitoring, amplify-gen2.
Workshop Studio URLs (titles from search index, 2026-09-04; content not fetchable): HealthLake Workshop 498fdbc5-…; SMART on FHIR 542c1a0f-…; Intelligent Healthcare Systems da0cf4f5-…; Patient Matching 23c3858d-…; Getting started with Amazon Connect d1f03aa4-…; catalog.workshops.aws/amazon-connect-optimization.