We recently released a feature in which a state can correct the SSN for a practitioner and migrate over all of their records, including their privileges, under a new provider id. The system does not currently update the transaction records which tracks the status of transactions as recorded in Authorize.net. After a state migrated over a number of practitioners to corrected SSNs/provider ids, the weekly report that is generated with transaction information failed to lookup the profile information of several of these practitioners that purchased privileges earlier in the week, as the provider ids listed on the transaction record were for the pre-SSN correction provider ids. The affected rows show the first and last name of these practitioners in the report with UNKNOWN, all other row information is still included and the reports are still sent out.
In order for these records to align, the SSN correction flow needs to be able to lookup transactions per compact/transaction id in the transaction history table. As part of this change, we need to add a GSI to the transaction history DynamoDB table, with the partition key of the GSI being the existing compact field and the sort key being the existing transactionId field. This will allow us to lookup the specific transaction in question for each privilege record being migrated over and then perform an UPDATE call on the licenseeId field to the new provider id. Read and write permissions will need to be added to the ingest lambda function for the transaction history table.
Notes
Questions
Assumptions
Estimate
Tasks
Implementation Notes
We recently released a feature in which a state can correct the SSN for a practitioner and migrate over all of their records, including their privileges, under a new provider id. The system does not currently update the transaction records which tracks the status of transactions as recorded in Authorize.net. After a state migrated over a number of practitioners to corrected SSNs/provider ids, the weekly report that is generated with transaction information failed to lookup the profile information of several of these practitioners that purchased privileges earlier in the week, as the provider ids listed on the transaction record were for the pre-SSN correction provider ids. The affected rows show the first and last name of these practitioners in the report with
UNKNOWN, all other row information is still included and the reports are still sent out.In order for these records to align, the SSN correction flow needs to be able to lookup transactions per compact/transaction id in the transaction history table. As part of this change, we need to add a GSI to the transaction history DynamoDB table, with the partition key of the GSI being the existing
compactfield and the sort key being the existingtransactionIdfield. This will allow us to lookup the specific transaction in question for each privilege record being migrated over and then perform an UPDATE call on thelicenseeIdfield to the new provider id. Read and write permissions will need to be added to the ingest lambda function for the transaction history table.Notes
Questions
Assumptions
Estimate
Tasks
Implementation Notes