ECP

ECP typical implementation process:

• Pre‑implementation planning: ECP and the provider define goals, scope (eMAR, EHR, billing, CRM, Move‑Ins), locations, data sources, timelines, and integration needs, often over several weeks to a few months of preparation for multi‑site rollouts.​

• System configuration: ECP configures communities, users, roles, pharmacy interfaces, assessments, and billing rules to match existing workflows and state requirements.​

• Data migration: Resident profiles, medication orders, care levels, and billing data are imported from prior systems or spreadsheets, coordinated with pharmacies where eMAR is involved.​

• Training: ECP delivers intensive training for leadership and super‑users first, then on‑site or virtual training for med aides, nurses, and office staff, often concentrated into one week.​

• Go‑live and stabilisation: Communities go live in a “big bang” or phased model, with ECP providing hands‑on support and a focused stabilization period (typically about a week) to resolve issues and reinforce workflows.​

ECP is designed to be highly configurable and extensible so communities can tailor it to their specific operating model, clinical approach, and tech stack.​

• Configuration within the platform: ECP allows customization of care plans, assessments, and level-of-care structures so providers can align documentation and tasks with their own service packages and regulatory requirements. Billing rules can be configured to automatically handle things like level-of-care changes, prorations, and ancillary charges based on each operator’s policies, reducing manual adjustments while matching local business rules. Communities can also set up their own user roles, permissions, alerts, and report templates, and ECP will help build or upload custom forms if state or operator-specific documentation is required.​

• Customization through integrations and APIs: Beyond in-app configuration, ECP emphasizes “flexibility through integration,” encouraging communities to build a tailored tech stack around the core platform. An Integration Hub, real-time REST and Webhook APIs, HL7, CSV exports, and a broad partner ecosystem (pharmacy, dietary, visitor management, BI, family engagement, etc.) let operators plug in preferred systems, create custom dashboards, and automate cross-system workflows. This combination of configurable workflows plus open integration options means ECP can be adapted to different care models, sizes, and regional preferences rather than forcing a one‑size‑fits‑all deployment.

ECP provides structured implementation support plus ongoing training resources to help new users adopt the platform effectively.​

• Implementation training: New customers are assigned an implementation manager and onboarding team that deliver classroom-style or virtual training during go‑live, often over several concentrated days. Sessions typically cover system navigation, settings, assessments, care plans, eMAR workflows, billing, and task assignment, with hands‑on practice entering data and passing meds in a training or live environment.​

• Ongoing education: After go‑live, ECP offers training videos, webinars (for topics like assessments and care planning), and an online knowledge base for self‑paced learning and refreshers. Many clients also use a dedicated training site/sandbox so staff can practice workflows before working with real resident data, which supports continuous onboarding for new hires.​

• Support channels: ECP backs its training with product support via phone, email, and online resources, helping communities resolve issues and optimize workflows post‑implementation. The software’s ease of use and “three clicks or less” design further reduces training burden, making it easier for staff of varied technical skill levels to become proficient quickly.

ECP implements a full stack of technical and compliance controls to protect resident and financial data.​

• Compliance and certifications: ECP operates as a HIPAA-compliant, cloud-based EHR/eMAR platform and signs Business Associate Agreements with covered entities, committing to safeguard PHI under HIPAA, HITECH, and stricter state laws where applicable. The company has achieved SOC 2 Type II compliance and ONC Health IT certification, demonstrating audited controls around security, availability, confidentiality, and encryption of authentication credentials.​

• Encryption and access controls: All data transmitted to and from ECP is protected with 256‑bit SSL/TLS encryption in transit, and data at rest is encrypted with 256‑bit AES. ECP supports multi-factor authentication, user-specific logins, role-based permissions, and audit logging so organizations can tightly control and monitor who accesses which records and when.​

• Infrastructure and operational security: ECP is hosted on Amazon Web Services and uses a defense‑in‑depth architecture, daily offloaded backups, and multi-location redundancy to help ensure both resilience and data availability. The platform maintains 99.99% uptime targets, performs regular backups and disaster‑recovery planning, and applies industry-standard security controls to its APIs, including encrypted transmission and authenticated access for integrations.

ECP is a cloud-based platform, so updates are released centrally and applied for all customers without local installs or manual patching. Public sources do not publish an exact fixed cadence for the senior-living product, but they show a steady stream of functional releases, such as new AI medication-safety tools and the Integration Hub and Developer Portal launched in 2024–2025, indicating multiple feature updates each year.​

Updates are managed as part of the subscription: ECP deploys new features, performance improvements, and security enhancements on the hosted environment, and customers access the latest version automatically via the web and mobile apps. New capabilities (for example, AI safety checks, new pharmacy integrations, or integration-hub features) are typically accompanied by customer communications, training materials, or webinars so communities understand changes and can adjust workflows with minimal disruption.

ECP treats customer data as belonging to the provider and positions its platform and APIs to make that data portable across systems.​

• Data ownership: ECP acts as a HIPAA Business Associate and explicitly frames itself as a hosted EHR/eMAR provider processing PHI on behalf of healthcare organizations, which remain the Covered Entities and ultimate owners/controllers of resident and clinical data. Its privacy policy states that it does not sell, rent, or lease customer lists to third parties, and any sharing with service partners is limited to functions like support, mailings, or analytics under strict confidentiality obligations.​

• Portability and access: ECP exposes data through multiple export and integration paths, including CSV exports, an Integration Hub, and documented APIs and webhooks, allowing customers and partners to pull data into other EHR, pharmacy, BI, accounting, or property-management systems. Blog and API documentation emphasize a “commitment to data ownership” and the importance of open, standards-based connectivity so senior living communities can maintain control of their information and move or replicate it as needed across their broader tech stack

ECP offers a per‑subscription, per‑active‑resident pricing model that is inherently scalable, but detailed commercial terms for scaling up or down are only visible in individual contracts and not fully published. Still, several concrete data points and market norms indicate how scaling typically works with ECP.​

• ECP bills per active resident rather than per licensed bed, so costs increase or decrease automatically with census rather than a fixed bed count, which makes scaling with occupancy more granular and financially aligned. Operators can add new communities, care lines, or modules (for example, adding Billing or Move‑Ins later) under their master agreement, with pricing adjusted based on the additional locations or features; this is reflected in third‑party descriptions that emphasize ECP’s suitability from single-site homes to large multi‑community portfolios. Because ECP is cloud-based, technical scaling (more users, more residents, more pharmacy connections) does not require new on‑premise infrastructure, and organizations can expand usage simply by provisioning new users and sites and updating their subscription.​

• Downward scaling is more constrained by contract terms than by technology. User and review sites note that ECP commonly uses multi‑year contracts, with at least one review explicitly referencing being locked into a three‑year agreement, which implies that reducing overall commitment (for example, cancelling modules or large chunks of licensed volume) mid‑term may require negotiation or wait until renewal. Within the term, however, the per‑active‑resident model means that if census drops, the billed amount tied directly to active residents also declines, giving some built‑in flexibility even when the contractual term length is fixed.​

• For significant changes—such as adding or removing communities, shifting billing models, or expanding into new service lines—ECP generally handles these as commercial amendments or new orders under the main MSA, coordinated through an account manager. In practice, the precise rights to scale up or down (minimums, floors, ramp schedules, true‑up mechanisms, and what can be reduced only at renewal) are governed by the signed order forms and subscription agreement, so procurement teams should negotiate explicit scaling language—especially around minimum resident counts, adding/removing sites, and notice periods—before signing.

Public sources do not expose ECP’s full commercial contract, so exact renewal and cancellation terms can vary by deal and must be confirmed in the MSA/order form. Available data points and market norms indicate the following patterns.​

• Contract length and renewal: ECP is typically sold as a subscription (per community and/or per resident) with an initial term, commonly 12 months or multi‑year for larger operators. Like most SaaS in this segment, contracts frequently include auto‑renewal language, meaning the agreement renews for successive terms (often one year) unless the customer gives written notice of non‑renewal within a defined window before the term end (industry‑standard windows are usually 30–90 days, though the exact notice period for ECP is not publicly specified).​

• Cancellation and termination: Mid‑term cancellation is generally not allowed without cause in healthcare SaaS unless negotiated; buyers are usually committed for the full term and remain responsible for contracted fees even if they stop using the software, which aligns with how ECP is positioned on reseller/aggregator sites as a contracted, per‑resident platform rather than a pure month‑to‑month tool. Early termination for cause (for example, material breach that is not cured within a specified period) would normally be governed by the MSA, but the specific ECP cure periods, refund rights, or penalties are not disclosed publicly and must be reviewed in the signed contract.​

• Data access at end of contract: Because ECP emphasises customer data ownership and provides CSV exports and APIs, communities can export their resident, clinical, and billing data when transitioning off the platform, subject to the timelines and mechanisms defined in the agreement. Privacy‑policy language also indicates that ECP retains data only as long as reasonably necessary for the purposes described or as required by law, implying that post‑termination data retention and destruction follow agreed contractual and regulatory requirements.​

• In practice, renewal terms, notice periods, any price‑increase caps, and off‑boarding/export support are commercial points that ECP typically negotiates per customer; a procurement review of the specific order form, MSA, BA Agreement, and any SOWs is required to know the binding renewal and cancellation conditions for a given deployment.​

ECP meets several key healthcare IT and data-security compliance standards.​

• Healthcare and interoperability standards: ECP is ONC Certified Health IT under the 2015 Edition Cures Update, with ECP Version 8.0 certified for criteria including electronic health information export, encryption of authentication credentials, and multi-factor authentication. This ONC certification confirms that ECP’s EHR/eMAR meets U.S. federal requirements for functionality, interoperability, and security, enabling participation in health information networks and regulatory programs.​

• Security and privacy frameworks: ECP has achieved SOC 2 Type II compliance, demonstrating that an independent auditor has verified the effectiveness of its controls for security, availability, and confidentiality over time. The platform is also described in vendor materials as operating in a HIPAA-compliant manner for protected health information in senior living and long-term care environments, aligning with healthcare privacy and security expectations.​