Eldermark API Integration & Workarounds

Overview

Eldermark is a senior living management platform used by ^[1] for clinical and billing operations. Attempts to automate data workflows (exports, custom CRM integrations) have been blocked by Eldermark's lack of a public REST API. This article documents the problem, current workarounds, and evaluated long-term solutions.

The Core Problem

Eldermark does not expose a reliable API, which prevents:

Automated data exports (e.g., scheduled Excel/CSV pulls)
Custom workflow triggers (e.g., pushing a new resident from a sales CRM into clinical/billing)
Integration with external tools (email platforms, automation pipelines, etc.)

Web scraping and browser automation (e.g., bot-driven UI navigation) were explored as alternatives but proved unreliable due to session state inconsistencies — the application renders differently depending on login context, sidebar state, and cookies, making scripted navigation brittle.

"Those things work great if you're doing something that's not particularly complicated... It works really good if you're going to do something like log into your Gmail and download something, where it's always in the same place. But this just wasn't that." — Mark Hope

Eldermark's reluctance to open an API is likely intentional: exposing one would reduce platform stickiness and allow clients to replicate core functionality externally.

Current Workaround

Manual weekly export by the client.

The Cordwainer contact (Bodo) has been asked to manually export the required Excel file from Eldermark on a weekly or biweekly basis and send it to the team. This is a stopgap while longer-term solutions are evaluated.

Owner: Karly Oykhman (coordinate with Cordwainer contact)
Limitation: Not scalable; dependent on client discipline; no real-time data

A formal API access request has also been submitted to Eldermark support. Approval is considered unlikely but worth pursuing.

Long-Term Solutions Evaluated

Option 1: Eldermark API Access (Requested)

Mark submitted a REST API access request to Eldermark support. If granted, this resolves the integration problem entirely — exports and workflow triggers could be placed on a cron schedule with no manual intervention.

Status: Pending. Low probability of approval based on Eldermark's known posture toward third-party API access.

Option 2: Welcome Home CRM

Welcome Home is a senior living sales CRM that Claude identified as having a documented, well-maintained REST API. It also lists Eldermark as an integration partner.

Tradeoff: Even with Welcome Home handling the sales/prospect pipeline, clinical and billing data would still need to be manually entered into Eldermark. Given Cordwainer's low resident turnover (~1–2 move-ins per month), this may be acceptable.

Assessment: Viable as a sales CRM layer, but does not eliminate the Eldermark data-entry problem.

Option 3: Custom HIPAA-Compliant CRM Build (Recommended)

Build a purpose-built CRM tailored to Cordwainer's workflows, replacing Eldermark's CRM module for sales/prospect management and potentially expanding to cover clinical and billing over time.

Proposed scope (initial):
- Custom fields and pipeline stages matching Cordwainer's resident journey
- Email integration (replacing MailChimp)
- Automation flows (follow-ups, status changes, notifications)
- HIPAA-compliant infrastructure (encrypted, access-controlled)
- API-first design for future integrations

Estimated cost: ~$2,500 (one-time build)

Advantages:
- Full control over features and data model
- No recurring SaaS licensing fees
- Extensible — billing, clinical modules can be added later
- Eliminates dependency on Eldermark's CRM entirely for sales workflows

Remaining gap: Clinical and billing data would still require manual entry into Eldermark unless/until Eldermark opens an API or a full replacement is built.

Next step: Karly to propose this option to Bodo, framing it as a value-add engagement. Suggest starting with the sales CRM layer (~$2,500) and positioning the clinical/billing replacement as a future phase.

Key Constraints

Constraint	Detail
HIPAA compliance	Any custom build must meet HIPAA standards (encryption at rest/transit, access controls, audit logging)
Eldermark clinical lock-in	Nursing and billing workflows are deeply embedded in Eldermark; full replacement is a larger project
Low resident volume	~1–2 move-ins/month makes some manual data bridging tolerable in the short term
Elementor/WordPress not involved	This is a standalone CRM build, not a WordPress integration

Manual export workaround approved as interim solution — see ^[2]
Welcome Home evaluated but not selected as primary recommendation
Custom build proposal to be sent to Bodo by Karly

^[3]
^[4]
^[5]