iCareWeaver
eCW sandbox connection
Sandbox · read only · not a product login
Ready to connect to the eCW sandbox.
Connect your sandbox app
This page only stores Client ID and FHIR base URL in this browser. Launch from eCW to bind a session. It does not write to the EHR.
Use the separate standalone registration
Start authorization from iCareWeaver when eCW did not launch this app with a patient already selected. This uses a separate Client ID and asks eCW to select patient context. It remains read-only.
Continue with standalone sandbox appValues for eCW registration
- App type
- Public · EMR Launch · OpenID: No
- Launch URL
- Redirect URL
Registered read-only patient scopes
Launch requests every registered patient read scope. Encounter Review still ingests only verified resources. ServiceRequest pages are read only when ENABLE_SERVICE_REQUEST_READ=1. Other registered resources stay request-only until a later evidence increment.
Launch received
eCW opened this app in a small frame, so authorization continues in a new tab. You should only need one Continue click.
Token exchange stays on our server. This tab only starts eCW authorization.
Sandbox connection established
Encounter Review is ready
Encounter Review is the product screen for this launched patient. This page is only a developer JSON probe. Opening review keeps this probe tab open.
Open Encounter ReviewSample JSON probe
Choose a resource, then click Read sample data. CareTeam and Device search the launched patient and do not need an id. Binary and Practitioner need an id in the box that appears. These names are not links in Encounter Review.
Required for Binary and Practitioner. Take Binary/{id} from a DocumentReference attachment.url. Take Practitioner/{id} from an Encounter or DocumentReference author/participant. CareTeam and Device do not use this box. Do not paste a foreign URL.
The retrieval audit records advertised CapabilityStatement support, whether this launch token can query each resource, and field/link coverage. It follows search next pages. It does not ingest new types into Encounter Review. Download saves the displayed response. Binary, CareTeam, Device, and Practitioner read scopes are requested only when ENABLE_EXTENDED_PATIENT_READS=1 and those reads are already listed on the eCW app. Probe reads without those scopes return 403. No create, update, or delete scopes are requested. This launch token is patient-level SMART access; it does not prove clinic-wide backend retrieval.