Report Generator

2025-10-28 | 📑 0 words | ⏱ 0 mins | 🧾 History | ✍ Tom D'Roza | 🔑 Ross Buggins

🚧 This page has less that 200 words. So it looks like this page is still under construction.

Known Issues / Todo

• ⛅ This page is draft and is subject to rapid change, and may not be fully accurate or complete

Full Screen

Events Consumed

• GenerateReport - reporting-generate-report - uk.nhs.notify.digital.letters.reporting.generate.report.v1
  • Produced By: code: Report Scheduler

Events Produced

• ReportGenerated - reporting-report-generated - uk.nhs.notify.digital.letters.reporting.report.generated.v1
  • Consumed By: code: Report Sender

Diagrams

c4code-mesh-statusreporter-generator

C4:

Link to this diagram directly: /nhs-notify-digital-letters/diagrams/c4code-mesh-statusreporter-generator.html

Decisions

1. ReportSchedulder lambda publishes a GenerateReport event for every known client
2. The event data payload contains the senderId so the ReportGenerator lambda knows which trust to generate a report for.

architecture-beta
    group reportGenerator(cloud)[ReportGenerator]
    service generateReportEvent(aws:res-amazon-eventbridge-event)[GenerateReport Event]
    service sqs(logos:aws-sqs)[ReportGenerator Queue] in reportGenerator
    service reportGeneratorLambda(logos:aws-lambda)[Report Generator] in reportGenerator
    service s3(logos:aws-s3)[Reports] in reportGenerator
    service reportsdb(aws:arch-amazon-athena)[Reports] in reportGenerator
    service reportGeneratedEvent(aws:res-amazon-eventbridge-event)[ReportGenerated Event]

    generateReportEvent:R --> L:sqs
    sqs:R --> L:reportGeneratorLambda
    reportGeneratorLambda:T <-- B:reportsdb
    reportGeneratorLambda:B --> T:s3
    reportGeneratorLambda:R --> L:reportGeneratedEvent