Overview
This glossary includes terms frequently used by both the HEE Business and the TIS Team.
Domain Vocabulary
HEE/NHS/Revalidation words.
TERM/WORD | Meaning |
|---|---|
| AoMRC: Academy of Royal Medical Colleges | The body that speaks on standards of care and medical education across the UK |
| ARCP: Annual Review of Competence Progression | ARCP process was introduced in 2007. Provides an assessment of a trainee's suitability to progress to their next stage of training or to complete their training program. The process is undertaken annually. The National Guidance regarding the process is described in the ‘Guide to Postgraduate Specialty Training in the UK’ (The Gold Guide) |
| BM: Business Manager | Lead for a Programme of work within HEE |
| CCG: Clinical Commissioning Group | Clinically-led statutory NHS bodies responsible for planning & commissioning of health care services for their local area. They replaced PCTs (Primary Care Trusts) in 2013 & there are now 207 CCGs in England (207) |
| CCT: Certificate of Completion of Training | A CCT confirms that a doctor has completed an approved (see the table below) training programme in the UK and is eligible for entry onto the GP Register or the Specialist Register |
| CESR: Certificate of Eligibility for Specialist Registration | A CESR confirms that a doctor has completed sufficient training outside of an approved UK training programme and is eligible for entry onto the GP Register or the Specialist Register. It is considered equivalent to that needed to achieve a CCT. |
| Collective Reports | A list of trainees who have been in an organisation for the last six months - happens retrospectively and on a six month basis |
| COPMED: Conference of Postgraduate Medical Deans | Provides a focus for those responsible for the strategic overview and operational delivery of postgraduate medical training in the four nations of the UK and by ensuring excellent training, is a key player in maintaining quality of care and patient safety |
| CPD: Continuing Professional Development | Measured in points |
| CPPS: Career, performance & professional support | One of the Hicom add-on modules for Intrepid |
| Deanery | There were 13 deaneries across England, responsible for postgraduate medical training |
| Digital Marketplace | The revised name of the G-Cloud store in which the public sector can commission suppliers to work on digital projects by the Digital Services Framework |
| Doctor's Revalidation | The process by which licensed doctors are required to demonstrate on a regular basis that they are up to date and fit to practice |
| DRN: Deanery Reference Number | Formed of Appointment Year / Speciality code / Type of contract / Deanery or LETB, e.g. "09/CMT/C0001/EE" |
| Employee Liaison Officer | An adviser who visits the revalidation team on a quarterly basis to discuss incidents, revalidations etc |
| Empower | Name of service provision provided by Northgate to London LETB until 2015 |
| e-Portfolio | An integral part of a trainee's education and professional development |
| ESR: NHS electronic staff record | The HR and payroll database used across the NHS |
| Form R | Has 2 parts. Part A is trainee registration form (contact & post info); Part B is self declaration form declaring fitness to practice concerns prior to ARCP |
| Green Files | Files for doctors in difficulty. These are controlled by the professional support manager |
| GMC | General Medical Council |
| GDC | General Dental Council |
| HCS: Health Care Science | HCS have their own LMS(see below) based on a small access database but they are looking at moving to TIS |
| IDT: Inter-deanery transfer | A process in place to help trainees that need to move area due to unforeseen circumstances |
| In house service | To produce a service or system internally rather than from an external source |
| Integrated Assurance Approval | The planning, co-ordination and provision of assurance activities and approval points through the lifecycle of the trainee information management system |
| Intrepid | Name of current provision provided across all LETBs provided by Hicom |
| ISCP: Inter-collegiate Surgical Curriculum Program | The curriculum for 10 surgical specialities and a number of dental specialities |
| ITP: Integrated Training Post | Integrated Training Posts are to allow the GP Trainee, although based in General Practice, to have a variety of other educational attachments outside General Practice. Often half of their time is spent in a Hospital Specialism or other area associated with health care |
| LAS: Locum Appointment for Service | |
| Learners | Learner could include a trainer (i.e. someone who has already completed their training) undertaking a course for CPD |
| LET: Lead Employer Trust | The LET carry out trainee investigations |
| LETBs: Local education training boards | In 2013 the deaneries transferred across to Local Education Training Boards following the enactment of Health and Social Care. The LETB is responsible for the training and education of NHS staff |
| Live Flow | A system that allows Local Education Partners to report in on an incident by incident basis to the revalidation officer and postgraduate dean |
| LMS: Learning Management System | E.g. moodle, an online learning space |
| LRMP: List of Registered Medical Practitioners | You can use the List of Registered Medical Practitioners - also known as the medical register - to check details of all the doctors who are registered with the General Medical Council |
| LTFT: Less than full time | There are a number of reasons why you may want to consider less than full-time training. Spending time with your baby or child is not the only reason. You might be caring for an ill or disabled partner, relative or other dependent, or have a disability or health problem yourself. If you are undertaking certain kinds of professional development it may also be possible to be accepted for LTFT |
| National Deferral Policy | Info around when a doctor can or can't be deferred |
| NDW: National Data Warehouse | /wiki/spaces/TISDEV/pages/57215548 |
Not directly commissioned | The term used to describe training posts that are not managed and where there is no direct relationship with HEE and are predominantly trust based; this may include undergraduate trainees, nursing and midwifery |
| NR: National Repository | /wiki/spaces/TISDEV/pages/57218619 |
| NTN: National Training Number | Formed of Deanery or LETB code / Speciality Code/ Number / Suffix, e.g. LON/002/003/C |
ODS: Organisational Data Service | The Organisation Data Service (ODS) is responsible for publishing organisation and practitioner codes, along with related national policies and standards. We're also responsible for the ongoing maintenance of the organisation and person nodes of the Spine Directory Service, the central data repository used within various NHS systems and services |
| OLAT: Online Learning and Assessment Tool | The HCS e-Portfolio |
| OOPs: Out of Programmes | There are four of them - Experience (OOPE), Training (OOPT), Research (OOPR) and Career Break (OOPC) |
| QRB | See QSB. |
| ORIEL | Recruitment System |
| QSB: Quality Scrutiny Board | Now renamed to QRB |
| Revalidation Recommendation | A recommendation to revalidate - can be made up to four months ahead of revalidation |
RMT: Reconciliation and Medical Trainee | Deanery Reconciliation and Medical Trainee Full File received on Day 1 from ESR |
| ROG: Revalidation Operational Group | The Revalidation Operational Group support the delivery of revalidation for doctors in training to meet the relevant statutory obligations and extra statutory guidance |
| Royal College | A professional body responsible for development and training in one or more specialities, devise curricula |
| RITA: Review of in Training Assessments | ARCP process applies to all Specialty Trainees & replaces RITA which continues to operate for existing Specialist Registrars until they have completed their training |
| School | Verify that curricula are delivered correctly |
| School, medical | University where students perform their undergraduate studies |
| SHA: Strategic Health Authority | An NHS organisation established to lead the strategic development of the local health service and manage Primary Care Trusts and NHS Trusts on the basis of local accountability agreements |
| SIAM: System Integration and Management | Allows an organisation to manage different service providers in a consistent and effective manner across a portfolio of multi-sourced goods |
| SML: Subject Matter Leads | AKA Subject Matter Experts - members of a wider stakeholder group who can assist the Product Owners by providing specialist knowledge on elements of the project |
| SPC: Specialty Program Co-ordinator | The individual that looks after the trainee in their specific locality. They are also involved in ARCPs and act as the trainee's administrator (they fill out e-Portfolio etc) |
| Specialty Teams | The team involved in the educational side of trainee doctors rather than the revalidation side |
| STEP: System-wide Training and Employment Passport | An "online system that will allow the transfer of training and employment information between organisations to support the greater mobility of the healthcare workforce." As of Nov 2019, it appears to still be under development. |
| Streamlining Staff Movements | A collaboration between NHS employers, skills for health and London HR and Workforce Directors which aims to reduce the time and expenditure involved in recruiting and training staff, as well as in the changeover of junior doctors |
| TCS: TIS Core Services | The service that manages the core People, Programmes and Posts entities along with their dependants |
| TIS: Trainee Information System | The web App the TIS Team are building |
| TPD: Training Programme Director | TPD has responsibility for managing foundation or specialty training programmes provided to NHS doctors |
| Trainee | Junior doctor, dentist, pharmacist or healthcare scientist |
Agile Product Delivery/Digital terms
[Bold denotes full form acronym | Italics indicates linked definitions]
| Word/Term | Meaning |
|---|---|
| AC: Acceptance criteria | A pass/fail set of descriptions of how a User Story can be tested to determine whether it has been 'done'. |
| Agile | A project management framework focusing on delivering small products as quickly as possible, then incrementally adding to them. This enables regular user input and 'agility' in embracing changing direction of the project in line with feedback and learning |
| API: Application Program Interface | A set of routines, protocols and tools for building software, and defining how different software components should interact with each other |
| Backlog | The list of everything that could be done by the project team if time was not a factor. This is usually subdivided into the Sprint Backlog and the Product Backlog. Occasionally, there is a further subdivision Next Up, indicating the highest priority items of the Product Backlog to work on, once the Sprint Backlog is complete |
| BDD: Behaviour Driven Development | Aims to help focus development on the delivery of prioritised, verifiable business value by providing a common specification language, that spans the divide between business and tech |
| Blocker | Something that prevents one or more stories being completed. It is the job of the Scrum Master to help remove these blockers |
| Burndown | A chart that shows the amount of effort or number of stories that are in the backlog and how they are being completed over time (usually a Sprint) |
| Confluence | The web application where we store all the project information and documentation that supports the backlog - linked to Jira |
| CQRS: Command Query Responsibility Segregation | Segregating the model used to update information from the model used to read information.  |
CRUD: Create, Read, Update, Delete | |
| Discovery | The first phase of a project approach (before alpha) |
| DBC: Designated Body Code | Most licensed doctors have a connection with one organisation that provides them with an annual appraisal and helps them with revalidation. This organisation is called your ‘designated body’. Only UK organisations can be designated bodies, because the legal rules that determine this only cover the UK |
| DoD / Done: Definition of Done | Sometimes a statement within a User Story, describing what 'Done' looks like, more usually expressed as a set of Acceptance Criteria. DoD can be applied to larger pieces of work than just a User Story. It can be used when working with Sprint Themes (a collection of User Stories around a central subject - either from a user perspective, or focusing on specific area of code) |
| Epic | The highest level of requirement in the backlog - this is too big to be worked on within a Sprint and needs to be refined into one or more User Stories |
| ETL: Extract, Transform, Load | A way of taking data from one place/system and re-presenting it in another |
| Incremental / Iterative development | These terms are often confused, leading to unintentional breakdowns in communication. This article really eloquently explains these two concepts visually. Well worth a read |
| Iteration | See "Sprint" |
| Jira | The web application where we store the backlog, run the Sprints and communicate on progress |
| MMF: Minimal Marketable Feature | An incremental layer that can be added to the MVP and released to the public |
| MVP: Minimum Viable Product | The simplest version of the product that could in and of itself be deployed into a public environment as quickly as possible in order to provide value to the customer and to provide the Agile team with continuous feedback (which can be evaluated, prioritised and fed back into the Product Backlog. Onto this MVP, we layer on MMFs to continually enhance a released product |
| PAG: Process Alignment Group | Cross-HEE group to ensure all local offices adopt a nationalised process to support the SOP (see below) |
| Product Backlog | Those stories that are either: – initial placeholders for work that will be worked on in the future, but haven't been defined sufficiently yet to bring into a Sprint; or – fully formed stories that are not deemed priority items to be worked on in the current Sprint |
| PO: Product Owner | A member of the team that owns the Product Backlog and advises on prioritisation of work. At HEE the PO is also referred to as a Service Manager |
| PR: Pull Request | When a dev requests to pull in new code to the Development environment, for example |
| RITA | What's this? https://acronyms.thefreedictionary.com/RITA |
| Scrum | A project management framework encouraging Agile thinking |
| SM: Scrum Master | A member of the team who facilitates the activities so that the Sprint can complete. Also monitors and reports on progress to the wider stakeholders |
| SOP: Standard Operating Procedures | Agreement as to best practice ways of working across all local offices (Joanne Watson (Unlicensed) / Alistair Pringle (Unlicensed) ??) |
| Sprint | A short period of time (from 2 - 4 weeks) in which a team work on a set of Users Stories that they commit to completing during Sprint Planning. A 2-week Sprint is the most common cycle. Sometimes called an iteration |
| Sprint Backlog | Those stories taken from the Product Backlog that the team has committed to completing, during Sprint Planning, within the current Sprint |
| Sprint Planning | The meeting at the start of each Sprint where all the committed team agree what tasks/stories should be brought into that Sprint |
| Sprint Retrospective | A meeting at the end of every Sprint where the Agile team gather amongst themselves, and analyse what went well, what they could have done better, any impediments to progress, and take actions to be more productive in the next Sprint / remove any impediments |
| Sprint Review | A meeting at the end of the Sprint to review what was achieved - i.e. to celebrate success with stakeholders outside the team, and invite their input into future direction for the project. With a big stakeholder group, this can be split off into a separate meeting for POs and specific Devs to present (sometimes referred to as a 'Show and tell', but which should also invite comments too) |
| SSH | Should be written SSh really - Secure Shell: a cryptographic network protocol for operating network services securely over an unsecured network. The best known example application is for remote login to computer systems by users |
| Standup | The daily meeting at which all committed team members update the team on their progress. Typically by giving a 30 second update on what they did yesterday, what they plan to do today and any impediments they have encountered. The last of these is where they may request assistance from colleagues, or the Scrum Master - which is normally discussed directly after the standup. |
| User Story | Often shortened to just 'Story'. A collection of sentences that capture a single requirement of either a system or a user. This usually follows the format of identifying who the story is for, what it is about and why it is important: As a [who], I want [what], so that [why]. For example: As a bank manager, I want people banking with me to be able to withdraw money from their account no more than the limit of their debit cards, so that I can control overspending on their accounts. A user story that someone can start working on is accompanied by several Acceptance Criteria |
| TDD: Test Driven Development | An approach to development that begins with determining how the 'code' will be tested, then building the code to the tests |
| Velocity | The term used to describe measuring the progress of a Sprint within the team. And the likely ability for a team to complete upcoming work. Note: this is not for presenting to stakeholders outside the project team |
0 Comments