Page Comparison

1.

Currently when a placement is withdrawn (via the bin/delete interaction), it is hard deleted from TIS. If the placement has previously been exported to ESR (Applicant Export), then a withdrawal notification is generated and sent to ESR. When a new placement is created, and we have a matching POS/POR on TIS for the NPN, it gets exported as a new Applicant if the start date is >2 days within 13 weeks window.

Current implementation.

2.

ESR definition of Withdrawal (NHS0098):

These notifications will be sent by the Deanery/HEE Local Office systems to the MSO Role when an applicant previously created has subsequently been withdrawn from the position and a replacement applicant is required.

TIS understanding validated with ESR:

2’ - “Update to Medical Rotations – Applicant Withdrawn”

This is sent in the notification file of a future trainee that has withdrawn and not someone who is already in post. This means where the Projected Start date on the placement is within 3 months 13 weeks in the future and greater than 2 days AND the DPN is one of the POS records we would have received in an earlier RMT file.

Current implementation.

3.

With this new lifecycle status if a placement is in DRAFT, I am assuming that it is not an actual placement with any of the status of CURRENT/PAST/FUTURE, is this correct?

No. See above.

4.

Under which circumstances would a placement need to be changed from APPROVED to DRAFT?

FUTURE placements amendments and creations ONLY.

5.

If a placement is set from APPROVED back to DRAFT (for whatever reason), is the expectation that it will be at some point be set back to APPROVED? As I believe that we would not want to create a process where we would end up with a number of placements sitting in DRAFT, either because they are Invalid or they have since re-created a new placement with APPROVED status.

The expectation is that they should be moved back to APPROVED or Deleted.

Reporting – to flag these in NDW. (James Harris )

6.

If we do go down the route of considering letting ESR know via a withdrawal notification that a placement has been changed to DRAFT from APPROVED (i.e. a POS/POR exist on TIS and ESR, and previously exported to ESR based on the start date of >2 days within 13 weeks window) and is equivalent to the existing withdrawal (bin/delete) interaction, Then if re-approved, I assume similar interaction as in (73) above is expected, i.e. re-setting to APPROVED from DRAFT means a new Applicant Export. Although this might be a duplicate.

It’s not a withdrawal per se.

7.

If we choose not to let ESR know about any of the DRAFT/APPROVED lifecycle status changes, then all placements DRAFT or APPROVED should be treated the same way by the ESR interface. (i.e. as in (73) above using the same rules regardless of whether the lifecycle is DRAFT or APPROVED)

This is the route we are going for.