Interpreting sync status

The last read and last write timestamps show how fresh the data in NexHealth is. A short gap means the data is up to date and matches the schedule in the health record system. The timestamps refresh all the time. A gap that moves between 0 and 20 minutes during the day is normal.

Downtime

Server-based systems. The office manages the hardware that runs the database. Syncing happens only when the server is on. Expect downtime when the office is closed. Depending on how the office runs its server, that can be every night or every weekend.

Cloud-based systems. The office uses the health record system through a web browser. The sync relies on user activity in the Chrome extension. The last read and write timestamps update only while office staff are logged in to both the Chrome extension and the health record system. They also have to be working in the schedule. Expect downtime overnight, on weekends and on holidays. It can also happen during lunch breaks or long staff absences.

For the best performance, install the Chrome extension on as many workstations as possible.

Monitoring

To monitor sync status, poll GET /sync_status. You can also check status in the Developer Portal.

The most common causes of unexpected downtime depend on the type of system.

Server-based systems. The NexHealth services may no longer be on the server where you installed them. This often happens when antivirus software quarantines or deletes the files. The office may also have replaced its physical server. In both cases, you need to reinstall the services on the server. To prevent this, we strongly recommend that you allow NexHealth services in antivirus and firewall settings before the install.

Cloud-based systems. The office may not have the Chrome extension on enough workstations. Install it on every workstation where staff change the schedule. See Chrome Extension installation. Each sync has its own token, which you can find in the portal.

How to fix a sync that is down

Server-based sync. If a sync has been down for a long time and needs a reinstall, use the self-installer at nexhealth.com/download. A reinstall needs a new product key. For now, only the NexHealth support team can generate product keys. Developers cannot create them in the Developer Portal.

To request a new product key, email [email protected] with the name of the institution. Product keys are unique to each institution. Start a separate email thread for each request and check that you use the right key for each install.

Cloud-based sync. If a cloud-based sync has been down for some time, the office likely does not have the Chrome extension on enough workstations. Ask the office to install the Chrome extension and sign in to it. That restores the sync.