122/204/2021 2022 - This issue has been resolved in reported after the Noah ES Cloud Release v . 1.3.0 released Dec. 20th, 20213 released Jan 26, 2022 and is under investigation by HIMSA.
HIMSA has recently become aware of an issue saving data in Noah ES that is unique to Noah ES customers.
...
HIMSA has placed a high priority on this issue and expects to make a fix in the near future. We do not presently have a specific date but any updates to this issue will be made on this page.
Symptoms of the problem
Saving an action to Noah ES for a patient that has had a recent fitting or measurement throws an error
Can verify by viewing session browser to check for recent actions
Impacts all modules and each module will present different error messages
What Causes the Problem
A conflict between the current calendar day and the UTC day/time which Noah ES uses to support businesses with locations in multiple time zones.
If actions are saved at a time later in the day there may be a problem where the UTC time has moved into the next calendar day and the mismatch prevents the saving of data
The problem will remain for another 24 hours and then it will be possible to save more data to the impacted patient record. The problem will only occur when data is saved between late afternoon and evening. The exact times will depend on your time zone.
| Expand | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
Short Term Workaround
If presented with an error saving to Noah ES, adding a new patient record is a good SHORT-TERM workaround.
...