Page Content:
Placements - Field Validation
Groupings should be as follows:
- Trainee Name (1) & National Post Number (2) as title
- Location: (3) - (6)
- Programme: (7) - (10)
- Status: (11) - (15)
| Field Sequence | Field name (V10) | DR field | Reference table | Example value | Other fields available in DR | Type (free text, drop down, check box) & Interaction | Mandatory (Y/N) | Validation / Error Messaging | Filter (Y/N) | Search (Y/N) | Sort (Y/N) | List (S) / Detail (D) | Notes |
| 1 | Trainee Name |
|
|
|
| - pre-populated (part of person record)
| Y |
|
|
|
|
| ONLY APPLICABLE IN PLACEMENT MANAGER |
| 2 | National Post Number |
|
| EOE/RGT00/030/STR/001 |
| | Y | Must be a post that already exists. | N | N |
|
|
|
| 12 | Status |
| | |
| - derived from dates
- Past: start date = before "today" + end date = before "today"
- Current: start date = before "today" + end date = after "today"
- Future: start date + end date = after today
| Y | derived |
| | | | |
| - can be overwritten
- add multiple
| Y | derived |
| | | | |
|
|
|
|
|
| Other sites (optional) |
| Site |
|
| - Drop down
- Smart search
- + or - button
| N |
|
|
|
|
|
|
REMOVE | ITP Post | | | tick box | | | N | | | | | | Get Russel to check data. Do we need to record ITP posts? |
| 13 | Managing Local Team Change to "Owner" |
| | | | | | | |
|
|
|
|
|
REMOVE | Region | | | | | | | | | | | | agreeing to remove. |
| 7 | Grade |
| |
| - derived from post
- drop down
| Y | derived but can be overwritten |
| | | | | | |
| - derived from post
- drop down
| Y |
derived - derived from post, can be overwritten
|
| | | | - add multiple
- at least one specialty must be added
- editable
|
|
|
|
|
|
9 | Other specialties | | Specialty | General Medicine | | derived from postdrop down
| N |
restricted to options from specialty ref table | | | | | other sites to work in the same way as other speciality. |
REMOVE | Sub Specialties | | | Paediatric neuroscience | | drop down | N | restricted to options from specialty ref table | | | | | |
| 3 | Date From (START DATE) |
| | | |
|
|
|
| | Y | date from must be before the date to. |
| | | | | | | | |
|
|
|
| | Y | date to must be after date from |
| | | | |
| Placement Type | Sick Leave |
|
| - drop down (from reference table)
| Y | restricted to options from placement type ref table |
| | | | |
|
|
|
|
|
REMOVE | Honorary | | | Tick box | | | | | | | | | No SMLs use this tick box. check with Russel. |
| 5 | Whole Time Equivalent |
| | |
| - free text
- number values only
| Y | must be a number between 0 and 1, Default value = 1 |
| | | | | Clinical | |
| - drop down
- derived from Post
- add multiple
| N |
must | must be a clinical supervisor |
Educational | | | Not Mandatory. | REMOVE | must | 10A | Educational Supervisor | | | Brian Boomsuckle | | - derived from Post
- drop down
|
| ed SMLs agree that Programme membership is more common sense. Need historical info.Need historical info Should be placed alongside Clinical Supervisor |
| 15 | Training Description |
| | |
|
|
|
| - free text
- max 100 characters
| N | N/A |
| | | | | | | | | | |
|
|
|
|
|
REMOVE | LTFT Confirmation Start Date | | | | | calendar picker | N | | | | | | need to change wording. This means that the funding has been agreed. |
REMOVE | Slot Share | | | tick box | | | N | | | | | | can we derive this from 2 trainees being in a concurrent placement. |
REMOVE | MIP (Months In Post) | | | 6 | | | | | | | | | Can we remove?
Explore to make more useful.
|
REMOVE | SLA Received Date | | | | | calendar picker | N | | | | | | no one uses. get Russel to check. |
| 16 | Added Date |
| N/A | DD/MM/YYYY | - | | Y | - derived from "today's date" where a post is newly linked to a trainee
- non-editable
|
|
|
|
|
|
| 17 | Amended Date |
| N/A | DD/MM/YYYY | - | | Y | - derived from "today's date" where details have been altered within a placement
- stops where either a trainee is removed from a Post or the placement ends
- non-editable
|
|
|
|
|
|
| 18 | Comments | vwPlacement: Comments | N/A |
|
| - Freetext
- Allow special characters.
- No Character limit as first increment
- Alistair Pringle (Unlicensed) - No limit as the first increment, suggestion is to look at the maximum size comment recorded on Intrepid and work our way back as a future increment.
| N |
| - | - | - | - |
|
Placements - Bulk Import Validations
| Column Heading | Add/Update/Matching Criteria | Mandatory | Rules |
|---|
| Surname* | Matching Criteria | Yes | Must match exactly the Surname a Current or Inactive Person record on TIS |
| GMC Number | Matching Criteria | Yes (unless GDC number or Public Health number has been entered) | Accepted value is 7 digits. Must match exactly the GMC Number of a Current or Inactive Person record on TIS. The Surname, Forenames and GMC number for each row must match exactly a single TIS person record |
| GDC Number | Matching Criteria | Either a GMC number, GDC number or Public Health number must be entered | Must match exactly the GDC Number of a Current or Inactive Person record on TIS. The Surname, Forenames and GDC number for each row must match exactly a single TIS person record |
| Public Health Number | Matching Criteria | Either a GMC number, GDC number or Public Health number must be entered | Must match exactly the Public Health Number of a Current or Inactive Person record on TIS. The Surname, Forenames and Public Health number for each row must match exactly a single TIS person record |
| National Post Number* | Matching Criteria | Yes | Must match exactly the National Post Number of a Current or Inactive Post on TIS. Ingore Post with a status of DELETE In an placement update scenario, Date From and Date to should match to the dates on the person record against the existing matching NPN. You can't update dates using the placement import. Dates can only be updated manually in the system. If you take dates out of the matching criteria then there is no way of knowing which placement you want to update as people can have many placements in the same site. In an Add scenario, i.e. where a placement is being added to a person, the values on the template will be inserted to person records. Due to the limitation of the placement import to do an update, a Bulk Placements Update using TIS_IDs has also been developed for this purpose. |
| Date From* | Matching Criteria/Add | Yes | Format must be dd/mm/yyyy. Date from must be before date to |
| Date To* | Matching Criteria/Add | Yes | Format must be dd/mm/yyyy. Date from must be before date to |
| Placement Type* | Update | Yes | Accepted values should match to one of the Placement type reference table |
| Placement Status* | Update | Remove as this get automatically populated based on the dates entered |
|
| Site* | Update | Yes | Accepted values should match to one of the CURRENT SiteKnownAs values Site reference table |
| Other Sites | Update (replace all existing values) | No | - Semicolon separated to add multiple
- Accepted values should match to one of the SiteKnownAs from Site reference table and are CURRENT
- Valid sites accepted by the upload would be only those attached to the Parent post.
| Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 |
|---|
| key | TISNEW-2899 |
|---|
|
|
| WTE* | Update | Yes | Accepted values should match to those that are deemed valid from the FE i.e. any number between 0 and 1 inclusve. |
| Grade* | Update | Yes | Accepted values should match to one of the Grade reference table |
| Specialty1* | Update | Yes - | Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 |
|---|
| key | TISNEW-1860 |
|---|
|
| Accepted values should match to one of the Specialty reference table When specialty column is populated on the template, we clean the 'Specialty', 'Other specialties' and 'Sub specialty' held on TIS against the matching placement (GMC Number, National Post number, Date from and To matches against placement record on TIS), start fresh and populate with the values from the template. The Main specialty and/or Other specialty and/or Sub-specialty cannot have the same value. |
| Specialty2 | Update | No | Accepted values should match to one of the Specialty reference table When specialty column is populated on the template, we clean the 'Specialty', 'Other specialties' and 'Sub specialty' held on TIS against the matching placement (GMC Number, National Post number, Date from and To matches against placement record on TIS), start fresh and populate with the values from the template. The Main specialty and/or Other specialty and/or Sub-specialty cannot have the same value. |
| Specialty3 | Update | No | Accepted values should match to one of the Specialty reference table When specialty column is populated on the template, we clean the 'Specialty', 'Other specialties' and 'Sub specialty' held on TIS against the matching placement (GMC Number, National Post number, Date from and To matches against placement record on TIS), start fresh and populate with the values from the template. The Main specialty and/or Other specialty and/or Sub-specialty cannot have the same value. |
| Sub specialty | Update | No | Accepted values should match to one of the Specialty reference table When specialty column is populated on the template, we clean the 'Specialty', 'Other specialties' and 'Sub specialty' held on TIS against the matching placement (GMC Number, National Post number, Date from and To matches against placement record on TIS), start fresh and populate with the values from the template. The Main specialty and/or Other specialty and/or Sub-specialty cannot have the same value. |
| Clinical Supervisor | Update | No | TISDEV-4458
|
| Educational Supervisor | Update | No | TISDEV-4458 |
| Comments | Update | No | TISDEV-4692 |
Placements - Bulk Update using TIS_Placement_IDs validations
| Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 |
|---|
| key | TISNEW-196 |
|---|
|
| Column Heading | Add/Update/Matching Criteria | Mandatory | Rules | Applicable for Update (Y/N) |
|---|
| TIS_Placement_ID* | Matching Criteria | Yes | Must match exactly to an Existing PlacementID on TIS. | Y |
| Intrepid_Placement_ID | Update | No | Must match an existing Intrepid_Placement_ID in Intrepid. (Extraction process handled outside of TIS) If there is an Intrepid_Placement_ID value already held on TIS, but a value has been specified on the template, then the import should ignore and throw an error. | Y |
| National Post Number | Update | No | Must match exactly the National Post Number of a Current or Inactive Post on TIS. Cannot be edited if the Placement Esr Status is EXPORTED
| Y (only if Placement Esr Status is not EXPORTED) |
| Date From | Update | No | Format must be dd/mm/yyyy. Date from must be before date to | Y |
| Date To | Update | No | Format must be dd/mm/yyyy. Date from must be before date to | Y |
| Placement Type | Update | No | Accepted values should match to one of the Placement type reference table | Y |
Placement Status | Update | No | ? | N |
| Site | Update | No | Accepted values should match to one of the CURRENT SiteKnownAs values from Site reference table | Y |
| Other Sites | Update (replace all existing values) | No | - Semicolon separated to add multiple
- Accepted values should match to one of the SiteKnownAs from Site reference table and are CURRENT
- Valid sites accepted by the upload would be only those attached to the Parent post.
| Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 |
|---|
| key | TISNEW-2899 |
|---|
|
|
|
| WTE | Update | No | Accepted values should match to those that are deemed valid from the FE i.e. any number between 0 and 1 inclusve. | Y |
| Grade | Update | No | Accepted values should match to one of the Grade reference table | Y |
| Specialty1 | Update | No | Accepted values should match to one of the Specialty reference table When specialty column is populated on the template, we clean the 'Specialty', 'Other specialties' and 'Sub specialty' held on TIS against the matching placement, start fresh and populate with the values from the template. The Main specialty and/or Other specialty and/or Sub-specialty cannot have the same value. | Y |
| Specialty2 | Update | No | Accepted values should match to one of the Specialty reference table When Specialty column is not populated but Specialty 2 and 3 are populated, then these are added to the 'Other specialties' of the matching TIS placement record. The Main specialty and/or Other specialty and/or Sub-specialty cannot have the same value. | Y |
| Specialty3 | Update | No | Accepted values should match to one of the Specialty reference table When Specialty column is not populated but Specialty 2 and 3 are populated, then these are added to the 'Other specialties' of the matching TIS placement record. The Main specialty and/or Other specialty and/or Sub-specialty cannot have the same value. | Y |
| Sub specialty | Update | No | Accepted values should match to one of the Specialty reference table There's only 1 sub specialty in the placement, so when Sub specialty is populated, it replaces the existing one. The Main specialty and/or Other specialty and/or Sub-specialty cannot have the same value. | Y |
| Clinical Supervisor | Update | No | TISDEV-4458 Accepted value is the registration numbers of the Clinical Supervisors. | Y |
| Educational Supervisor | Update | No | TISDEV-4458 Accepted value is the registration numbers of the Educational Supervisors. | Y |
| Comments | Update | No | TISDEV-4692 Freetext accepted. | Y |