TIS: Ghost ProgrammeMemberships and how to handle them.

What is a “Ghost Programme Membership”?

A Programme Membership will appear in the database and, so far, very similar to another, but it will not be visible to the user in Admins UI - it is a “ghost”. Slack/Email alerts have been configured to be triggered when TIS data is left with a “Ghost” Programme Membership.

What’s the problem?

These ProgrammeMemberships cannot be managed by Admins but are visible and have an impact on other TIS sub-systems, including causing Connection discrepancies where there shouldn’t be one and misleading information and instructions for TIS Self-Service users.

What do I do about them?

1. Use the PersonId and UUID provided in the Alert to find the offending Programme Membership(s).

   • If you log on to Admins UI, and go the the “Edit Programmes” tab for the PersonId, you will notice that the Programme Membership(s) is/are not visible

2. If possible, find the user that submitted the latest change to the Programme Membership

   • Search TCS logs for the PersonId in the logs to find the audit event (e.g. “AuditEvent: type=tcs_updateProgrammeMembership user=firstName.LastName@nhs.net")

   • It will have occurred in the hour/day before the alert depending on how frequently the alert is set to check.

3. Delete the incorrect programme membership and curriculum membership from the database. Not all maintainers have the permission to delete these records. Ask your Lead Dev to clear up the data.

4. Contact the user with the details of the Programme Membership(s) which have been deleted.