Web API upgrade
Scheduled Maintenance Report for AgileMD
Completed
The AgileMD Web API v4 has been fully deployed. Goodnight everyone! Please contact support@agilemd.com with any questions.
Posted Apr 16, 2017 - 01:52 PDT
Update
Final verification and testing is ongoing. Primary web and EHR-integrated services are operating normally. We expect to provide another update at 1:30am PT.
Posted Apr 16, 2017 - 01:07 PDT
Verifying
We are conducting final verification across all services. We expect to provide another update at 1am PT.
Posted Apr 16, 2017 - 00:37 PDT
Update
We are continuing to patch and verify application updates. We expect to provide another update at 12:30am PT.
Posted Apr 16, 2017 - 00:03 PDT
Update
We are tracking down a particularly nasty bug that is affecting a very limited set of resources. Some clients will continue to receive cached content. Changes to content and account settings may not take immediate effect. We expect to provide another update at 11:30pm PT.
Posted Apr 15, 2017 - 23:02 PDT
Update
We continue to squash identified bugs. Some clients will continue to receive cached content. Changes to content and account settings may not take immediate effect. We expect to provide another update at 11pm PT.
Posted Apr 15, 2017 - 22:29 PDT
Update
We have identified a few bugs related to the the application upgrades that we need to fix. In the meantime, some clients (EHR, Android, and iOS) will receive cached content. Changes to content and account settings may not take immediate effect. For urgent support, contact support@agilemd.com. Stay tuned for updates. Expect another update at 10:30pm PT.
Posted Apr 15, 2017 - 22:03 PDT
Update
We have successfully updated our web applications including the reader, reviewer, and authoring tools available on https://www.agilemd.com and are now beginning verification activities. In parallel, we will now update our EHR-integrated applications to use the new AgileMD Web API (v4). We expect to provide another update at 10pm PT.
Posted Apr 15, 2017 - 21:36 PDT
Update
We have completed the database migration. We are now releasing updated versions of each application to use our new AgileMD Web API (v4) rather than the old (v3). We expect to provide another update at 9:30pm PT.
Posted Apr 15, 2017 - 21:00 PDT
In progress
Database migration is proceeding as planned. We have also completed our preparation for application deployment. We expect to provide another update at 9pm PT.
Posted Apr 15, 2017 - 20:00 PDT
Update
We have started working on our planned maintenance. Work will proceed through four phases:

1. Database migration
2. Application deployment
3. Traffic migration
4. Final verification

Phase 1, database migration, begins now. During this time, please avoid editing content and changing account settings; changes made before 10pm PST may not take effect immediately. For urgent support, contact support@agilemd.com. Stay tuned for updates.
Posted Apr 15, 2017 - 19:01 PDT
Scheduled
We will be performing a major upgrade to AgileMD's core Web (HTTP) API and conducting a large database migration. We expect the observed outage to last between 1 and 3 hours.

To enable a host of planned platform and application upgrades, we are moving much of the primary account and content data into a bigger, more performant database. In addition, we are expanding the capabilities of the AgileMD Web API to service growing needs of our mobile and EHR-integrated customers. We currently service about 500k requests per day and expect to be well over 1M per day by year's end.

Normally, our team deploys code on a continuous basis. Almost every day, one application or another receives a production upgrade; new features and bug fixes are safely released without any downtime. However, this change is much larger and much more complex. Like any good flight-plan, we have developed a detailed checklist and tested the migration many times in our QA (quality assurance) environment. At several points during the execution of that checklist we must halt all inbound requests to avoid data corruption. At these points, downtime is unavoidable – new accounts cannot be created, resources cannot used within the EHR, and all mobile apps will stop syncing resource changes. So, during the maintenance window, we ask that you sit back, avoid changing your content and department settings, and wait for the all clear from us. If you must make an emergency change (for example, a critical pathway must start order a new drug), please contact your account representative or email us at support@agilemd.com – we will have extra team members available to manage emergency issues on a case-by-case basis.
Posted Apr 10, 2017 - 09:27 PDT