RI Witness (CooperSurgical)
- Status
- Available
- Region
- Global
- Vendor
- CooperSurgical
- Data flow
- Patients, partners and cycles: wawa → RI Witness
- Connectivity
- SOAP 1.2 over HTTPS; Site-to-Site VPN or customer-managed public URL
- Set up by
- Clinic account administrator
wawa pushes patients, partners and treatment cycles to RI Witness whenever clinicians create or update a cycle, so the witnessing terminals always show the right person and cycle without re-keying. The flow is one way: wawa to RI Witness.
What is sent
- Patient details: demographics, contact information and address.
- Partner relationships, when the cycle involves a partner.
- Treatment cycle data: protocol, start and end dates, cycle type.
Requirements
- The RI Witness Web Service installed on a clinic server (from the CooperSurgical release bundle). wawa talks to it with SOAP 1.2.
- A network path: Site-to-Site VPN, or a customer-managed public URL restricted to wawa's egress IPs. Any reverse proxy in front must pass SOAP 1.2 requests unchanged.
- Every patient and partner to sync needs an identity-management ID, a last name and a date of birth, and the cycle needs a start date. Anything missing is skipped and logged on the Events tab.
What we need from you
Per RI Witness server (one per site if each site has its own)
| Input | What to give us | Example |
|---|---|---|
| Name | A label for the server | Main lab |
| URL | The web service base address, including any per-clinic sub-path. Don't include /WitnessWebService.asmx; wawa adds it. HTTPS. | https://witness.clinic.internal/RIWitness |
| Username and password | A Basic-auth account for wawa. Both are needed for authentication to be sent. | |
| Default | The server used for clinics without their own assignment |
Per clinic
- Which server serves each clinic, or the default.
For the pilot
- The identity-management IDs of a few test patients, to limit syncing to them before switching on for everyone.
- Your IT contact for the server and network path, and your CooperSurgical contact if the web service is not yet installed.
Setting it up
- Go to Settings → Integrations → RI Witness.
- On Stations, add each server with the inputs above and click Test.
- On Clinics, choose the server for each clinic (blank uses the default).
- On Configuration:
- Enable integration is the master switch; with it off nothing is sent.
- Automatically sync cycles pushes cycles as they are created and updated.
- Patient IDs for auto-sync limits syncing to the listed identity-management IDs (comma- or space-separated). Leave it empty to sync everyone.
A manual sync uses the same rules: the integration must be enabled, automatic sync on, and the patient on the list (or the list empty). Each sync is recorded on the Events tab, with the specific error if one fails.