| OES ID | Ninja ID | Samurai ID | Name | Domain | Published |
|---|---|---|---|---|---|
No accounts found.
Select an EHR to view tools
| # | Name | Type | Match | Value | Conditions | ||
|---|---|---|---|---|---|---|---|
|
|
EHR #
| Last Customer Info Sync | |
|---|---|
| Last Customers Full Download | |
| Last Appointments Full Download |
Nulls last_customer_info_sync, last_customers_full_download, and last_appointments_full_download, so the next sync re-downloads all patients and appointments from the EHR.
EHR #
| Last Historic Sync | Complete |
|---|---|
| Last Daily Sync | |
| Last Monthly Sync | |
| Single Day Syncs |
|
Sets last_historic_project_up_sync to null, so the system will re-download all historic data.
Add dates to single_day_project_up_sync. Each day in the range will be queued for reprocessing.
Paste multiple date ranges, one per line. Format: M/D/YYYY - M/D/YYYY or M/D/YYYY for single days.
Per-account override for the historic Project UP loop. Each resume batch covers batchSize × chunkSize days before saving progress and exiting. Lower values mean smaller per-call payloads (avoids RevEHR endpoint timeouts on huge practices) and more frequent checkpointing. Leave blank to use defaults (chunkSize=7, batchSize=12).
| Task ID | |
|---|---|
| EHR GUID |
|
| Created At (UTC) | |
| Updated At (UTC) | |
| Sent to EHR At (UTC) | |
| Completed At (UTC) | |
| Retry Count | |
| Parameters | |
| Error |
| Uploaded (UTC) | Data Group | File Type | Rows | Size | Status | File Name |
|---|---|---|---|---|---|---|
Clears sync watermarks for ALL ACTIVE accounts of the selected EHR type so they perform a FULL re-sync of patients, appointments and insurance on the next sync cycle. Stagger by EHR type to avoid overloading the backend.
Every active server-based EHR (OfficeMate, FoxFire, Crystal, Compulink) and whether its extractor is holding a long-poll open. A practice only appears as polling once its connector is on a version that has the command channel.
| Uploaded (UTC) | File Type | Rows | Size | Status | File Name |
|---|---|---|---|---|---|
| Timestamp (UTC) | User | Action | Entity Type | Entity ID | Changes |
|---|---|---|---|---|---|
| Property | Diff (removed added) |
|---|---|
|
| Property | |
|---|---|
|
Vendor documentation, integration capabilities, and live changelogs
API integration coming soon. View vendor changelog →
| EHR | |
|---|---|
Mask*.cs), not editable here.
Snapshot .
What are masks?
| Practice domain | Masks |
|---|---|
| No practice matches. | |
Internal reference content for EHR onboarding + support.
| Title | Axis | Section | Tags | Status | Updated |
|---|---|---|---|---|---|
Live version + installer for the desktop EHR Connector. Used by Compulink, Crystal, FoxFire, and OfficeMate practices.
The EHR Connector is the desktop installer the practice runs on their Windows server. It bridges the practice's local PMS database to EyeCarePro's cloud.
Used by:
Cloud connectors (AcuityLogic, Eyefinity, Revolution, UpRise, OD Office Pro) do NOT need this installer.
Need an older release? Enter the version number (e.g. 4.91, 4.90). The download URL is constructed from the version using the standard installer filename pattern. If the version doesn't exist, the browser will show a 404 — no harm done.
Where to find a needed version: the per-account Connector Ver column on Dashboard → EHR Connections, the EHR Connector Versions report, or Graylog logs from the practice's connector machine.
Per-version history of the on-prem desktop extractor (eyecarepro-extractor) — the client that reads the practice's PMS and uploads to the cloud. Newest first. Built from the extractor's git release tags; connector / scheduler / patient-comms changes are in the release notes alongside.
Plain-English log of behaviour-affecting changes in the cloud connector (ehr-connector), the scheduler (exam-scheduler), and patient communications (patient-communication). What changed and how it affects you or a practice. (Desktop extractor changes are in the card alongside.)
Click Open full release notes for the dated log (newest first). To add an entry: Edit on GitLab (devs) or Suggest review (anyone) on that article.
C:\ProgramData\EyeCarePro\DataLog.txt on the connector machine for first-sync entries.force_update_check for their EHR — connector will check for an update on the next sync.oes.patientengage.ai, a different host from the one the connector syncs with, so a practice can sync perfectly and still never update. Up to v5.01 the connector fails that download silently — no log line on their machine and nothing on our side — so a blocked host and "already up to date" look identical. Ask them to allow oes.patientengage.ai, or update the connector by hand. From v5.02 the connector falls back to fetching the files from the sync host and logs the failure.| Location | Service URL | Result | |
|---|---|---|---|
| Waiting... Testing... |
| Location | Status | |
|---|---|---|
| Waiting... Syncing... |
Syncing ... This may take a few minutes.
Syncing availability data... This may take a few minutes.
Syncing appointments... This may take a few minutes.