Merged
Conversation
markpullan
requested changes
Feb 26, 2026
...cture/terraform/components/reporting/scripts/sql/views/request_item_plan_status_smsnudge.sql
Show resolved
Hide resolved
...cture/terraform/components/reporting/scripts/sql/views/request_item_plan_status_smsnudge.sql
Show resolved
Hide resolved
...astructure/terraform/components/reporting/scripts/sql/views/request_item_status_smsnudge.sql
Show resolved
Hide resolved
|
markpullan
approved these changes
Feb 26, 2026
sidnhs
approved these changes
Feb 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Description
Create three new views for SMS Nudge requests. Include originating request details by using the SMS Nudge billingRef.
Context
Currently, all SMS Nudges appear as originating from a single umbrella client (“SMS Nudge”), which obscures the true originating service (e.g., GP Reg, CSMS). This prevents accurate reporting, billing attribution, and source-level analytics.
To address this, we first need to extract the originating identifiers into the Athena data model. These identifiers will also serve as the foundation for downstream reporting outputs, including the Nudge-specific view required for Power BI.
Test evidence
request_item_status_smsnudge_staging
request_item_status_smsnudge
request_item_plan_status_smsnudge
Type of changes
Checklist
Sensitive Information Declaration
To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.