Eclipse EHR software is a practice management and electronic health record system built primarily for chiropractic and multidisciplinary clinics. The vendor describes it as a unified platform for documentation, scheduling, billing, and patient communication, with both a legacy desktop product and a newer cloud product [1][2]. The two products are not identical: the vendor maintains separate documentation for ECLIPSE and ECLIPSE EHR Cloud, including distinct data-conversion rules and feature gaps [4][5]. For a practice evaluating the software, the practical question is less whether Eclipse is a chiropractic EHR and more which deployment model, conversion path, clearinghouse arrangement, and API surface fit a specific clinic's existing workflows. This guide uses primary vendor documentation to explain those distinctions and to outline a concrete evaluation approach without inventing clinical outcomes or unverified performance claims.

Product Scope and the Desktop-Cloud Distinction

Eclipse positions itself as a chiropractic-first system that also serves physical therapists, acupuncturists, and group practices [1][3]. The vendor states that the product began inside a chiropractic and multidisciplinary practice and evolved into one of the first chiropractic EHRs in the country [3]. The current marketing materials describe a cloud platform accessible from any device, with drag-and-drop scheduling, custom SOAP notes, automated billing, and integrated patient communication [1][2]. These are vendor descriptions of intended functionality, not independently verified performance metrics.

A critical distinction for evaluators is that ECLIPSE and ECLIPSE EHR Cloud are separate products with separate documentation. The vendor's FAQ explains that each product provides unique features and that the cloud version excels when a practice wants to use internet-based patient interactions such as integrated email, text messaging, and click-and-pay options [5]. The knowledge base also lists features that are not yet functional in the cloud product, including bulk payments, bulk scanning, chat, DrFirst prescription integration, insurance tracers, and legacy kiosk functionality [4]. A practice migrating from the desktop product should therefore verify which specific workflows it depends on before assuming parity.

Documentation, Billing, and Clearinghouse Constraints

The vendor describes documentation tools built around chiropractic charting, including customizable SOAP note templates and macros intended to reduce repetitive data entry [1][6]. A testimonial on the vendor site attributes time savings to the system's form-filling features, but such statements are individual customer accounts rather than measured outcomes [3]. The documentation pages also list scheduling features such as multi-appointment booking for care plans and automated email and text reminders [2][6]. These are product capabilities described by the vendor, not guarantees of reimbursement or compliance. The vendor's knowledge base also documents contact-preference behavior: when a contact type is marked as primary, ECLIPSE EHR Cloud updates the patient's contact preferences, and the scheduler's quick-launch view displays the patient's primary contact information [8]. This is a documented workflow detail, not an independent assessment of compliance.

Billing documentation shows specific clearinghouse dependencies. The cloud product supports electronic billing via ANSI 837 and paper billing on the CMS-1500 form, with electronic billing enabled for Alveo, Carisk, and Infinedi [4]. The FAQ states that a practice can still choose any clearinghouse, but a fee-based option applies if the practice does not use one of the available partners [5]. The vendor also notes that ECLIPSE and the cloud product do not have the same third-party interfaces [5]. For a practice with an existing clearinghouse relationship, this is a concrete cost and workflow variable that should be confirmed directly with the vendor.

Questions to Ask Before a Cloud Migration

Request a written list of features that are not yet functional in ECLIPSE EHR Cloud and compare it against your current daily workflows, including bulk payments, bulk scanning, chat, DrFirst integration, insurance tracers, and legacy kiosk functionality [4]. Confirm whether your clearinghouse is Alveo, Carisk, or Infinedi, or whether a fee-based option applies for your existing clearinghouse [4][5]. Ask for the standard data conversion inclusion and exclusion lists in writing, and request a custom conversion quote if you need historical encounters, ledger entries, or documents transferred [5]. Finally, request current API documentation for the specific product version you are evaluating, since the published Patient API guide describes the desktop application [7].

Data Conversion and Migration Mechanics

The vendor began converting data for existing ECLIPSE users in March 2023, according to its knowledge base [4]. The standard conversion includes patients, patient cases, conditions, attorneys, insurance companies, providers, procedure codes, billing profiles, referral sources, user-defined data such as adjustment types, and encounter templates [5]. The standard conversion specifically excludes alerts, appointments, documents, encounters, ledger entries, and bills [5]. A custom conversion can include some or all of the excluded data, but the vendor describes this as time- and personnel-intensive and quotes a fee based on factors such as database size [5].

This exclusion list matters for continuity planning. A practice that relies on historical encounter documents or ledger entries would need to budget for a custom conversion or accept that those records will not transfer automatically. The vendor also warns that manually added unsupported items such as tables or formatted text in edit boxes may prevent encounters from printing in the cloud version [4]. These are documented limitations, not hidden defects, but they require a practice to inventory its existing data before migration rather than assuming an automatic transfer.

API Access and Interoperability Surface

Eclipse publishes a Patient API Developer Guide describing a FHIR-based interface aligned with the 170.315(g)(10) Standardized API certification criterion [7]. The API uses OAuth 2.0 for authentication and returns patient search and patient data responses in FHIR release 4 JSON [7]. Documented resources include Patient, AllergyIntolerance, CarePlan, and CareTeam endpoints [7]. The developer guide states that the documentation is provided as-is with no warranties expressed or implied [7]. This is a technical integration surface, not a certification claim that the product has achieved a specific ONC certification status.

The API documentation describes access to patient health records stored in the ECLIPSE EHR desktop application [7]. This raises a practical question for cloud evaluators: whether the same API surface applies to ECLIPSE EHR Cloud or whether the documented endpoints are specific to the desktop deployment. The source does not answer that question directly. A practice planning third-party integrations should request current API documentation for the specific product version it is evaluating, rather than assuming the desktop API guide describes the cloud product's capabilities.

A Concrete Evaluation Scenario for a Multi-Provider Clinic

Consider a hypothetical chiropractic group with three providers, one front-desk staff member, and an existing desktop ECLIPSE installation. The practice wants to evaluate whether moving to ECLIPSE EHR Cloud would reduce administrative work without disrupting its current billing flow. A documented evaluation would begin by listing the features the practice currently uses and checking them against the cloud product's known gaps, such as bulk payments, bulk scanning, chat, and DrFirst integration [4]. The practice would then identify its current clearinghouse and determine whether it is Alveo, Carisk, or Infinedi, or whether a fee-based alternative would apply [4][5].

The practice would also inventory its historical data against the standard conversion inclusion and exclusion lists [5]. If the practice needs historical encounters or ledger entries in the cloud product, it would request a custom conversion quote. The practice would also review the vendor's hardware guidance, which states that ECLIPSE EHR Cloud runs in any browser on any device and that faster devices with more RAM generally perform better [8]. The vendor also documents that ECLIPSE EHR Cloud is not customized for individual offices and that feature requests are considered based on their benefit to the entire user base [8]. This is a product-policy constraint, not a performance claim, and it matters when a practice expects vendor-specific workflow changes. Finally, the practice would test the documented workflows that matter most, such as multi-appointment scheduling for care plans and automated reminders [2][6]. This scenario is a suggested evaluation method, not a claim that any specific practice has completed such a migration or achieved a particular result.