Clinical notes ingestion and retrieval pipeline

Well-Architected review Clinical notes ingestion and retrieval pipeline · 2026-10-02 · mode full

Coverage audit

• AWS Well-Architected Framework — 6 pillars, 57 questions, 307 best practices, from the live documentation index, snapshot 2026-10-01 (0 days old).
• Generative AI Lens — 29 questions, 51 best practices, snapshot 2026-10-01.
• Assessed 307 framework BPs and 51 lens BPs: 11 + 5 with diagram evidence, 296 + 46 cannot be determined.
• Evidence sources: architecture diagram (services, boundaries, relationships); cost estimate from the AWS Price List.
• Corpus read from a committed snapshot of the live documentation index (not re-fetched during this review). Re-read it with `archify-aws wa corpus --refresh`. Statuses reflect what the diagram and spec show. Process, configuration and runtime evidence are not observable here, so those BPs are 'Cannot Determine' rather than guessed.

Executive summary

This Well-Architected Framework and Generative AI Lens review of Clinical notes ingestion and retrieval pipeline (standard criticality) assessed the architecture diagram only. 11 of 307 framework best practices and 5 of 51 lens best practices have diagram evidence; the rest are Cannot Determine because process, configuration and runtime evidence is not in the diagram. It found 0 critical, 1 high, 2 medium and 0 low risks. Estimated run cost is $3,373/month (indicative).

11 of 307 framework best practices have diagram evidence (4%); among those, 3 implemented, 2 partial, 6 not implemented. Provisional: scores cover evidenced practices only.

Strengths. Data stores are not placed in public subnets; Managed / serverless services dominate; Automated sensitive-data identification.

Architecture overview

The reviewed architecture is the Diagram tab (9 components, dataflow diagram). Hover a finding to highlight the components involved.

Pillar scorecard

Generative AI Lens scorecard

Score = 1 + 4 × (implemented + ½ partial) ÷ evidenced BPs; shown only when ≥ 3 BPs are evidenced. It reflects evidenced practices, not the whole pillar.

Framework questions

Generative AI Lens questions

Framework best-practice ledger 307 best practices — nothing truncated

Generative AI Lens best-practice ledger 51 best practices — nothing truncated

Findings

High risk (1)

Medium risk (2)

To confirm not drawn, so not counted as gaps

• No AWS KMS shown for data at rest SEC08-BP01 — Manage encryption keys in AWS KMS (customer managed keys where you need key policy, rotation or audit control) and enforce encryption at rest on every data store.
• No detection or audit services shown SEC04-BP01, SEC04-BP02 — Enable CloudTrail (organization trail), GuardDuty and Security Hub, and send logs and findings to a central, access-restricted account.
• No backup or recovery capability shown REL09-BP01, REL09-BP03 — Back up data automatically with AWS Backup (cross-account/cross-Region vault where required) and test restores against your RPO/RTO.
• No infrastructure-as-code or CI/CD shown OPS05-BP04, OPS05-BP10, REL08-BP05, SEC11-BP06 — Define infrastructure as code and deploy through a pipeline with small, reversible changes and automated rollback.
• No cost visibility shown COST01-BP03, COST01-BP06, COST03-BP05 — Set AWS Budgets with alert thresholds, enable Cost Anomaly Detection and cost allocation tags so spend maps to this workload.
• Single-Region model inference GENREL05-BP01 — Plan for throttling and quota limits (retries, queues, provisioned throughput) and consider cross-Region inference profiles or a fallback model.
• Model cost controls GENCOST01-BP01 — Select the smallest model that meets quality targets; use prompt caching and batch inference where possible; track cost per request.
• Agents and excessive agency GENSEC05-BP01 — Limit agent tool permissions (least privilege, deterministic policy at the tool boundary) and add human approval for high-impact actions.
• Model and hosting efficiency GENSUS03-BP01 — Prefer right-sized or distilled models and serverless inference; avoid always-on endpoints for spiky traffic.

Eisenhower prioritization

Prioritized remediation plan

Next steps

1. F-001 No guardrails around model input/output — Apply Amazon Bedrock Guardrails (or equivalent) to prompts and responses: harmful content, PII, prompt attacks and, for RAG, contextual grounding. (ML platform team)
2. Re-run the review after changes, and when the architecture or documentation changes.

Impact × Likelihood matrix from the AWS Well-Architected review skill (Severe+High = Critical; Severe+Medium/Low or Moderate+High = High; Moderate+Medium/Low or Minor+High = Medium; otherwise Low).