Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Current Connection AS-IS diagram

Drawio sketch
mVer2
simple0
zoom1
inComment0
pageId4198629408
custContentId4206559234
diagramDisplayNameAS-IS
lbox1
contentVer1
revision1
baseUrlhttps://hee-tis.atlassian.net/wiki
diagramNameAS-IS
pCenter0
width1293
links
tbstyle
height1003

Pain Points/Challenges/Successes

  1. A wider API issue is that the disconnections via TIS reval happen after refresh but connections are added the next day.

  2. When a trainee connects/disconnects and we receive an email notification if we need to take action we have to do this via GMC Connect or wait until the next day. Only disconnect via TIS if picking up the GMC notification email the following day. Disconnect using GMC connect if on the same day

  3. To be fair even if we can use TIS connections without GMC Connect we can't do that for reccomendations as some essential information isn't part of the API

  4. Slow TIS system

Questions/Assumptions/Key Points

Raised by

...

Assumptions/ Key Points

Question

Raised by

Assumptions/ Key Points

Question

Raised by

Key Points:

 

 

Key Points:

 

 

Priorities arranged in order

Key Point Everyone on the discrepancies spreadsheet should be on TIS -Reval discrepancies

 

 

Key Point: The following are the list of different doctors the summary page:

  1. ADs which they don't do anything with

  1. Connected but not in a programme with the LO

  1. Doctor in two programmes which is an anomaly 

  1. Visitors  which they don't do anything with

  2. In a programme with LO but not connected because they have not got license to practice

  1. Foundation doctors in a programme but not connected because of issue with their placements. We need to determine how discrepancies works with doctors in placement - Only few is showing up. Because of this issue, they have to keep a separate spreadsheet for foundation.

 

 

Key Point: If not in a programme but connected, go into programme in TIS- ADMIN  through the link in Reval. and if their programme are in the feature - they will be disconnected but if the programme is current Nothing is done. Some of the doctors might be in a current programme in another LO so they have to be disconnected.  This doctors tend to connect themselves several time when disconnected but an email is sent to tell them to stop until the start date.Some region give them a lieu way of few days

BULK  used in change over- August - Feb. They manully select and unselect doctors before submitting - Sorting is required here. If failed go to failed and investigate 

FILTER  not in use because  it's only programme name - Suggesting - GMC Number, programme owner, GMC submision date -- suggest all to be filterable

SORTING - in the five except for names - just all

Fileds to be added: Admin, Specialty- May never be possible if no programme, Programme start and end date, Note (Y/N)

Source of spreadsheet: Create their own discrepancies spreadsheet and update when they see any.

Current Connection: Don't use daily but sometime is used is when notification is received that a doctor is connected but supposed not - just search the doctor and disconnect  and many do it through GMC connect

Priorities arranged in order

  1. Performance - there is spreadsheet back - not confidence

  2. Filtering/Sorting - It will help to identify doctors clearly especially with DB and programme.

  3. Hide: Ability to hide Visitor, AD, Military etc

  4. ‘Note’ Field be added to the summary page. as it will solve the problem of going into individual doctors details to know if doctor has a note or not

  5. Exporting- To investigate current connection - to use for TIS -Admin. To manage connection and programme through VLOOKUP

Template

View file
nameQueried connections.xlsx
View file
nameQueried connections.xlsx