Stream: fhircast-github
Topic: docs / Issue #34 Dirty flag should be part of context
Github Notifications (FHIRcast) (Jul 11 2018 at 08:04):
jmehlbrech opened Issue #34
it seems to me that an everyday-scenario for such a context is to have a "dirty flag".
Suppose a smart-on-fhir app runs within an EMR. User changes data in the app - which should be setting a "dirty flag". The EMR usually displays such a status with a marker to the user.
This would also be important because before the EMR decides to switch the context - the app get an event asking to save or discard data ...
Github Notifications (FHIRcast) (Nov 20 2018 at 22:03):
isaacvetter commented on Issue #34
Hi @jmehlbrech!
Apologies for the ridiculously late response.
This sounds like a potentially powerful integration feature, but comes at the risk of violating a separation of concerns.
Why wouldn't the app simply save the modified data - either to it's own data store, or by writing to the EHR in lieu of communicating this as part of the context synchronization?
Isaac
Github Notifications (FHIRcast) (Nov 21 2018 at 07:29):
jmehlbrech commented on Issue #34
Hi Isaac,
thanks for coming back to this - I fully understand that this point might come to late for a first release.EMR and app are connected through the context, e.g. with an encounter.
The EMR doesn't know if data in the app was changed - and nowadays users expect to be asked (in a common ui) if they want to save or discard data.
So suppose the user attempts to switch to a different encounter. Wouldn't he/she expect to be asked for save/discard? Since only the EMR knows about all unsaved data - it makes sense to ask for that in a central place, i.e. the EMR. Also many EMRs indicate with ui specific unsaved data.
This feature targets integrating apps seamlessly..
Hope this helps ..
Joerg
Last updated: Apr 12 2022 at 19:14 UTC
