| commit | 0718350fadb42293a4d4599f087e9cc52d81aca0 | |
| author | Ray Magauran <ophthal@users.noreply.github.com> | |
| Mon, 12 Nov 2018 04:59:06 +0000 (11 23:59 -0500) | ||
| committer | Brady Miller <brady.g.miller@gmail.com> | |
| Mon, 12 Nov 2018 04:59:06 +0000 (11 20:59 -0800) | ||
| tree | 47bf4e32257f3acf75ef7d994b3d2f1c185b45b6 | treesnapshot (tar.gz zip) |
| parent | 3311ea0bed03aa182a7032b9b5674e56b8c95c0b | commitdiff |
MedEx api 5.0.2 (#1949)
* Update API
MedEx Calls: on Sign-up, or force (MedEx.php Callbacks, Background_services, cronjob, SMS Bot) or at most q 5 minutes.
Flow Board/Recall Board will not auto-call MedEx but instead pull current state from medex_prefs via new field ‘status’.
If this data is more than 5 minutes old, it will call MedEx for new data. Suggest large practices disable background_services and move to one cron job for the practice.
Signed-off-by: ophthal <magauran@ophthal.org>
* MedEx 5.0.2 DB
Signed-off-by: ophthal <magauran@ophthal.org>
* Flow Board
Now relies on medex_prefs::status rather than making a call across the net to MedEx on each screen that is refreshing their own Flow Board. MedEx data Refresh is handled by cron, background services or push from MedEx if server is remotely accessible by MedEx.
Signed-off-by: ophthal <magauran@ophthal.org>
* Flow Board issues
Signed-off-by: ophthal <magauran@ophthal.org>
* MedEx Bug && Review
MedEx was not recognizing recurrent appointments, now it does.
Delete MedEx_cron.
Instructions to create cronjob in MedEx_background.php.
Signed-off-by: ophthal <magauran@ophthal.org>
* Update API
MedEx Calls: on Sign-up, or force (MedEx.php Callbacks, Background_services, cronjob, SMS Bot) or at most q 5 minutes.
Flow Board/Recall Board will not auto-call MedEx but instead pull current state from medex_prefs via new field ‘status’.
If this data is more than 5 minutes old, it will call MedEx for new data. Suggest large practices disable background_services and move to one cron job for the practice.
Signed-off-by: ophthal <magauran@ophthal.org>
* MedEx 5.0.2 DB
Signed-off-by: ophthal <magauran@ophthal.org>
* Flow Board
Now relies on medex_prefs::status rather than making a call across the net to MedEx on each screen that is refreshing their own Flow Board. MedEx data Refresh is handled by cron, background services or push from MedEx if server is remotely accessible by MedEx.
Signed-off-by: ophthal <magauran@ophthal.org>
* Flow Board issues
Signed-off-by: ophthal <magauran@ophthal.org>
* MedEx Bug && Review
MedEx was not recognizing recurrent appointments, now it does.
Delete MedEx_cron.
Instructions to create cronjob in MedEx_background.php.
Signed-off-by: ophthal <magauran@ophthal.org>