Page Comparison

The following states reflect the GMC-defined states; 

...

1. If a doctor is deferred and it is “approved” by GMC and the doctor will stay in Under notice tab with a new GMC due date: BA mind: Any approved doctor (either defer/revalidate) by GMC; the doctor is expected to move away from the under notice tab to ‘All doctors' tab by GMC. It now depends on when GMC move the doctor back to 'Under Notice’ with a new submission due date.

   1. If GMC status is “approved” for the deferral revalidation, in the Recommendation summary page the doctor’s GMC status should be “empty”? BA mind: If in ‘all doctors’ tab, Yes but if still ‘under Notice’ the GMC status should still have the ‘approved’

   2. If GMC status is “rejected” for the deferral revalidation, in the Recommendation summary page the doctor’s GMC status should be what? BA mind: If in ‘all doctors’ tab, Empty but if still ‘under Notice’ the GMC status should still have the ‘Rejected’.

2. If a doctor is “revalidate” (non deferral recommendation type) and it is “approved” by GMC, during the nightly sync job (UnderNotice= value “Yes”, “No”, “On Hold”) will the doctor be moved away from “Under Notice” tab? BA mind: I want to think so and I don’t think our system wait for the night sync, the status refresh is updated at some hours intervals, I want to think moving doctors away from under notice depend on GMC not our system. Our system only get the update from GMC.

3. By the checkRecommendationStatus api we are enquiring GMC for recommendation status several times a day and if the GMC provides us the Status “Approved” or “Rejected” and the doctor will stay under notice until the nightly sync job runs; BA mind: I want to think moving doctors away from under notice depend on GMC not our system. Our system only get the update from GMC

4. References to past ticket: 1.

   Jira Legacy
   server System JIRA serverId 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 key TIS21-2545

   2.

   Jira Legacy
   server System JIRA serverId 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 key TIS21-2120

   3.

   Jira Legacy
   server System JIRA serverId 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 key TIS21-2075

   5.

   Jira Legacy
   server System JIRA serverId 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 key TIS21-2086

   6.

   Jira Legacy
   server System JIRA serverId 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 key TIS21-987

Rob Pink You might want to verify my answers with Users

Adewale Adekoya Rob Pink For your kind perusal.

...