eClinicalWorks

Last reviewed: July 2026

Overview

Integuru's eClinicalWorks integration provides production-ready HTTP API access to eClinicalWorks (eCW), one of the most widely deployed ambulatory EHR platforms in the United States, at <SUBDOMAIN>.ecwcloud.com, covering 5 actions: ecw_create_patient for patient registration, ecw_demographics for demographics and contact management, ecw_sfdp for insurance and sliding-fee workflows, ecw_upload_document for clinical document upload, and ecw_get_doc_folders for document folder retrieval. Integuru is HIPAA-compliant and signs BAAs at no additional cost. Calls complete in under 3 seconds with a 99.9%+ success rate via direct HTTP requests rather than browser automation.

No official developer API for key workflows. eClinicalWorks does not expose a public developer API for the demographic, insurance, and document workflows that clinical operations teams need most. Healthcare engineering teams building on eCW have historically relied on HL7 feeds, manual data entry, or brittle browser automation that breaks whenever eCW updates its interface. Integuru connects to the same internal endpoints the eCW web application uses, providing a stable programmatic surface for the covered actions.

The integration spans the ambulatory clinical and billing workflow: patient registration via ecw_create_patient, multi-sub-action demographics management via ecw_demographics (edit demographics, manage contacts, set responsible party, search providers, handle income calculations), insurance policy management via ecw_sfdp (search carriers, add/update/delete insurance, sliding-fee scenarios), clinical document upload via ecw_upload_document, and document folder listing via ecw_get_doc_folders. See the DrChrono integration for another cloud EHR platform, or browse the full integrations catalogue.

---

Use Cases

Integuru's eClinicalWorks integration covers the patient registration, demographics, insurance, and document workflows that healthcare engineering and clinical operations teams need to automate.

• Patient registration: Call ecw_create_patient with dob, sex (exactly 'Male', 'Female', or 'Unknown'), fname, and lname required. All address, contact, and identifier fields are optional. Phone must be formatted as XXX-XXX-XXXX.
• Demographic edits: Call ecw_demographics with patient_id and action: 'edit-demographics', passing a changes object containing only the fields to update (supports dob, sex, ssn, zip, GrId, city, race, GrRel).
• Contact management: Call ecw_demographics with action: 'add-contact' or 'update-contact' and a contact object. For updates, also pass contact_id. Use emergency_only: true with action: 'get-contacts' to retrieve only emergency contacts.
• Responsible party assignment: Call ecw_demographics with action: 'set-responsible-party' and pass gr_id (guarantor patient ID), gr_rel (relationship code, 1=Self), and is_gr_pt (1=Yes if the guarantor is the patient).
• Insurance carrier search: Call ecw_sfdp with action: 'search-carriers' and a search string to look up carriers. Pass ins_type to filter by insurance type.
• Insurance policy management: Call ecw_sfdp with action: 'add-insurance' and an insurance_data object to add a policy. Use 'update-insurance' with pt_ins_id to modify an existing record. Use 'delete-insurance' with pt_ins_id to remove it.
• Clinical document upload: Call ecw_upload_document with url (public download URL) and patient_id (eCW MRN by default). Pass category (a catId from ecw_get_doc_folders) to file the document in the correct folder. Override the filename with filename or set a display name with custom_name.
• Document folder retrieval: Call ecw_get_doc_folders with patient_id to retrieve all available document category folders for that patient. Returns the catId values used as the category input to ecw_upload_document.

---

Setup Notes

Integuru's eClinicalWorks integration authenticates against https://<SUBDOMAIN>.ecwcloud.com/. Configure your eCW practice's specific subdomain once during Integuru setup; Integuru manages session authentication automatically, including the eCW login cookie flow.

The patient_id used across all five actions is the eCW Account/Chart number (MRN) — the number visible in the eCW UI — by default. Where an id_type parameter is available, pass 'patient_id' to supply eCW's internal patientId instead of the MRN.

For multi-sub-action actions: ecw_demographics requires patient_id and an optional action string controlling the sub-operation; ecw_sfdp requires action as a required field and patient_id for most sub-actions. The ecw_sfdp sub-action 'save-insurance-detail' expects an insurances array of insurance record objects. Full parameter documentation is available for actions marked with the docs badge in the action table above.