Interweave Portal - Ideas
This portal provides an open platform for user feedback and product change requests. Anyone can add an idea and remain as a Guest, but please consider signing up so that others can see who has created the ideas!
Note: this is a public facing web portal, any text here can be viewed by anyone over the internet, so please consider carefully the content you wish to share and please do not post anything of a sensitive nature.
Thanks, Nick. I have raised this issue as a service request - https://yhcrservice.atlassian.net/browse/ICR-2878
I've added your name to the ticket, so the service desk may be in touch for more information.
I think it's important this is handled as a service desk issue. The functionality already exists, it just needs to be optimised to load quicker. As such, I'm going to archive this idea so it can be progressed with the service desk.
Hi, having done a bit more testing this seems to vary quite a lot in the range of 19-45s to load fully. There seems to be a lot of variance depending on the patient data and also some sort of caching - the first time viewing a patient is always longer and if I clear my browser cache there is often a ~10s white screen before the 'login' box first appears so the first open normally takes over 35s.
Comments received from Nick White at YSFT:
Doing some quick testing it seems to take between 15-25s to fully load each time which I think is a bit of an improvement but I would still consider to be ‘slow’. I’m not sure how much time can be reduced given the retrieving data stage being reliant on responses from other services.
A quick breakdown of the time spent as an example is
2s – generating link in CPD and opening browser
3s - logging in
7s – completing login
12s – retrieving data (documents taking the longest)
Comparing this to the prior timings it looks like there are improvements in the jwt retrieval and the ‘login’ portion of this, completing login seems about the same and retrieving data is longer but probably based on the data retrieved (documents took 12s but most others were complete within 4s)
4-6s to generate link in CPD (creating, validating + retrieving jwts) (5.8,4.5,3.6,3.8)
4-5 secs on ‘login’ screen
5-10s on ‘completing login’
2-4s after log in with the boxes and demographics loading while data is retrieved
One of the major improvements that was to be made was to the idling behaviour of the system where if it we didn’t send a request for a while (e.g. overnight) then calls to the portal would take significantly longer while it ‘warmed up’ which I will have to check in the morning. Looks like we’re headed in the right direction though.
Looking at the associated ICR ticket, this issue appears to have been resolved. If this is still an issue, please let me know and I will amend the status.
this is now being actioned under support and linked to a change request https://yhcrservice.atlassian.net/browse/ICR-2120
hi
is there a way York could analyse the response times from the various calls in the process of launching the portal? there will be things under our control, e.g. issuing the JWT, but other things will be within the York network?