build date: 2016-07-21 10:51 PM
build tag: oscar15BetaMaster-428
Client browser: Firefox
Client OS: Ubuntu
Preconditions:
See https://sourceforge.net/p/oscarmcmaster/bugs/4368/ for a specific instance where new UI fails to indicate that EMR data lookup failed.
Steps to reproduce:
See https://sourceforge.net/p/oscarmcmaster/bugs/4368/ for a specific instance where new UI fails to indicate that data lookup failed.
Expected Result:
If EMR data access fails, the doctor should be notified that the data access failed rather than concluding that no data exists. Especially important for ongoing concerns.
Observed:
Nothing presented in the browser to indicate missing EMR data which is a safety issue. In the case of https://sourceforge.net/p/oscarmcmaster/bugs/4368/ Firebug reveals that a 500 internal server error occurred.
Please attach relevant log entries, screenshots
Other details:
How do we close this one? 4368 has a fix now
Jens had some suggestions and may bring this up at the technical meeting. Until successful communication has occurred with the REST interface, the application should indicate (maybe with colour) that data access hasn't occurred yet. It is a more general UI issue than just the problem with 4368. The doctor needs to be aware of which parts of the summary page have been successfully populated with data and which parts are potentially missing critical information.
sounds like maybe a feature request which needs to be better described
Yes, I said that as well but Jens felt it was a bug. Will carbon-copy him.
Last edit: Raymond Rusk 2016-07-26
This is a classical safety hazard in information systems where the software does not indicate the difference between "no data" and "no connection to data". It's not a feature. It really is a safety bug.