...
- In line with the Code of Practice, Applicants are input into TIS at least
3monthsmonths13 weeks before they are due to start their next training placement. - ESR becomes the master for Applicant data at the point a record is successfully created – no further changes to the application record can be made by TIS once it has been created within ESR. As such, changes to person details (such as Address) and projected hire and end dates will be dealt with manually within ESR.
- The presence of a DPN is a condition of release for the Applicant Record provided this hasn’t been sent before, but should not be considered a trigger for subsequent transfer for the applicant record.
- TIS always sends Applicant data to ESR, if the following conditions are met:
- There is a matching DPN between ESR and TIS
- The Doctor in Training record is completed in TIS with ALL mandatory fields
- There is between
3 months13 weeks and 2 days before the Projected Hire Date - The post is a hosted OR lead employer position
- TIS will never resend the Applicant data into ESR, even if the previous application failed to load successfully. It was noted during the meeting that this assumption will cause support issues and needs reviewing, as Intrepid had a function to ‘resend’ applications.
- TIS does not accommodate a process where applicant data can be manually ‘resent’ by the user, so Applicants that fail to load within ESR may have to be manually keyed in via the Direct Hire process in ESR. See above point for concerns.
...