openhealthcare / elcid

elCID deployment for UCLH
http://elcid.openhealthcare.org.uk
Other
7 stars 3 forks source link

Reload data in background #25

Closed michaeledwardmarks closed 10 years ago

michaeledwardmarks commented 10 years ago

Once we have multiple users - how will we push new data to users

E.g 1) I am looking at the Micro list 2) Gabriele is also looking at it and alters something

Short of me pressing F5 to manually refresh how will we push Gabrieles changes to me?

davidmiller commented 10 years ago

Currently they're not actively pushed. This is on a roadmap somewhere.

Currently, more completely:

if you try to edit an episode that someone else has altered since you loaded it, this will fail and send you a message. You can then refresh the patient, but it loses your edit.

GabPoll commented 10 years ago

@davidmiller when you say not actively pushed - does that mean that lists with live updating of new patients are not updated on someone else's screen unless they refresh - what if the second (viewing) user clicks on another list, and then goes back to the one they were on - that's a refresh in a way - will this include the new patients?

@davidmiller when does the system consider editing an episode simultaneously? i.e. if one person is entering antimicrobials and the other entering diagnoses simultaneously (i.e. different modals), will that go through ok? I'm envisaging that the only real headache is if someone has written a long piece of free text, and then that gets lost.

michaeledwardmarks commented 10 years ago

@davidmiller We should discuss this tomorrow

@GabPoll and me just tested this.

Some thoughts: 1) Could we reload the data when we save a modal (guess this depends how long this takes from a user experience point of view) 2) Could we reload the data when we flick between different tag views?

Some kind of update driven refresh is what we need......happy to discuss practicalities tomorrow.

GabPoll commented 10 years ago

@davidmiller I suspect the system may be like this in order to minimise simultaneous loading / processing (i.e. keep it speedy - i.e. noticeable lag when switch to single patient view, which isn't there when flicking between tabs).

Would a possible easy solution be for user to receive alert that another user is editing that particular patient, suggesting a refresh / switch to single patient view to see those updates?

GabPoll commented 10 years ago

Generally though, the good thing is that simultaneous entries into a patient are cumulative. So the risk is duplication of effort. Frustrating but much less so than a user unknowingly rendering a patient "read-only" for all other users (and the latter potentially losing any entry made).

michaeledwardmarks commented 10 years ago

I think this can be closed at this time