eClinicalWorks
Two steps your eCW administrator completes so SutureHealth can sync signed documents into the chart.
How a signed document is matched to the patient, filed in the chart, and turned into a claim is in the post signature sync overview. The steps below are what your eClinicalWorks administrator completes so that sync can run for your practice.
eClinicalWorks + SutureHealth
Connecting eClinicalWorks (eCW) with SutureHealth takes two steps from your eCW administrator. After those are done, the SutureHealth team finishes the remaining setup.
What we need from you
1. Approve the SutureHealth app in eClinicalWorks
Your eCW administrator approves the app in the eClinicalWorks Developer Portal:
- Log in to the eClinicalWorks Developer Portal.
- Search for SutureHealth FHIR API.
- Approve and activate the SutureHealth app for your practice.
2. Provide your practice's FHIR R4 base URL
We also need your practice's FHIR R4 base URL. It looks similar to:
https://fhir4.eclinicalworks.com/fhir/r4/XXXXXX
Your eCW administrator may be able to locate this URL in your eCW environment. If it is not there, eClinicalWorks Support can provide it.
Once we have these two items
Send both of these to [email protected]:
- Confirmation that SutureHealth FHIR API has been approved and activated
- Your practice's FHIR R4 base URL
After we receive both, SutureHealth completes the remaining integration setup.
Questions
If your eCW administrator needs help locating the FHIR R4 base URL or approving the SutureHealth FHIR API, contact eClinicalWorks Support.
Updated 11 days ago