Skip to content

VED-904: Add logic to uplift legacy identifiers#992

Closed
edhall-nhs wants to merge 21 commits intomasterfrom
feature/VED-904-handle-legacy-identifiers-in-batch
Closed

VED-904: Add logic to uplift legacy identifiers#992
edhall-nhs wants to merge 21 commits intomasterfrom
feature/VED-904-handle-legacy-identifiers-in-batch

Conversation

@edhall-nhs
Copy link
Copy Markdown
Contributor

@edhall-nhs edhall-nhs commented Nov 18, 2025

Summary

❗ Breaking Change

⚠️ PLEASE DO NOT MERGE AFTER REVIEW. This must only be merged and released after the data migration as part of VED-893 has taken place

This code can also be removed once DPS has updated the relevant data on their side.

The purpose of this PR is to ensure that we can handle legacy identifier that will be sent to us from DPS via the batch process.

Reviews Required

  • Dev
  • Test
  • Tech Author
  • Product Owner

Review Checklist

ℹ️ This section is to be filled in by the reviewer.

  • I have reviewed the changes in this PR and they fill all of the acceptance criteria of the ticket.
  • If there were infrastructure, operational, or build changes, I have made sure there is sufficient evidence that the changes will work.
  • If there were changes that are outside of the regular release processes e.g. account infrastructure to setup, manual setup for external API integrations, secrets to set, then I have checked that the developer has flagged this to the Tech Lead as release steps.
  • I have checked that no Personal Identifiable Data (PID) is logged as part of the changes.

@github-actions
Copy link
Copy Markdown
Contributor

This branch is working on a ticket in the NHS England VED JIRA Project. Here's a handy link to the ticket:

VED-904

Comment thread lambdas/recordforwarder/src/service/fhir_batch_service.py
JamesW1-NHS
JamesW1-NHS previously approved these changes Nov 19, 2025
Akol125
Akol125 previously approved these changes Nov 19, 2025
JamesW1-NHS
JamesW1-NHS previously approved these changes Nov 26, 2025
@sonarqubecloud
Copy link
Copy Markdown

@dlzhry2nhs
Copy link
Copy Markdown
Contributor

Do we need to close this as superseded by #1022 or okay for now?

@edhall-nhs
Copy link
Copy Markdown
Contributor Author

Yep we can close this PR and reopen if requirements change again 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants