Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

3 cases:

  1. Doctor exists in GMC and TIS (and gmc details match up) - this works fine ✅

  2. Doctor exists in GMC only - an error is thrown when trying to fetch details for the non existent doctor in TIS ⚠️

  3. Doctor exists in TIS only - an error is thrown when trying to fetch notes for the non-existent doctor in reval (and would also be thrown when fetching connection history) ⚠️

Current Operation

  • Two connection URLS are called on page load

    1. /api/trainee/{gmcId} - This appears to populate the sidebar

    2. /api/connection/{gmcId}

Proposal 1

Proposal 2

Proposal 3

from("direct:trainee")
    .multicast(AGGREGATOR)
    .parallelProcessing()
    .to("direct:trainee-details")
    .to("direct:traineenotes-get")
    .to(// gmc doctor endpoint)
from("direct:trainee-details")
    .setHeader(OIDC_ACCESS_TOKEN_HEADER).method(keycloakBean, GET_TOKEN_METHOD)
    .setHeader(AggregationKey.HEADER).constant("programme")
    .toD(serviceUrl + API_TRAINEE);
from("direct:traineenotes-get")
    .setHeader(AggregationKey.HEADER).constant("notes")
    .toD(coreServiceUrl + API_TRAINEENOTES);
from(/*"direct:gmcdoctorendpoint"*/)
    .setHeader(AggregationKey.HEADER).constant("doctor")
    .toD(coreServiceUrl /*gmcDoctorEndpoint*/);
  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.