Integrations overview
Beyond the self-service API and webhooks, wawa connects directly to the systems a fertility clinic runs: laboratories, ultrasound and imaging servers, time-lapse incubators, witnessing systems, cryostorage, pharmacies, accounting and calendars. These are managed integrations: wawa builds and operates the connector, and you provide access, data and a named contact.
Moving to wawa from another EMR? See Migrating your data.
Integrations
| Category | Integration | Region | Status | Data flow |
|---|---|---|---|---|
| Imaging | DICOM / DICOMweb | Global | Available | Studies in; worklists out (Orthanc) |
| Imaging | GE ViewPoint | Global | Available | Through the DICOM integration |
| Laboratory | HL7 v2 lab interface | Global | Available | Orders out; results in |
| Laboratory | The Doctors Laboratory (TDL) | EU | Available | Request forms out; results in |
| Laboratory | Australian Clinical Labs | AU | Available | Results in |
| Laboratory | Dynacare | CA | In development | — |
| Laboratory | Labcorp | US | In development | — |
| Laboratory | LifeLabs | CA | In development | — |
| Laboratory | Blood analysers (Meditecs) | CA | In development | — |
| Laboratory | HealthLink | AU | In development | — |
| Laboratory | Sonic Healthcare | AU | In development | — |
| Laboratory | GENNET (GNT Labs) | EU | In development | — |
| Embryology | EmbryoScope | Global | Available | Patient out; embryo data in |
| Embryology | CHLOE (Fairtility) | Global | Available | Gradings, scores and images in |
| Witnessing | RI Witness | Global | Available | Patients and cycles out |
| Witnessing | Matcher | Global | In development | — |
| Cryostorage | TMRW | Global | Available | Two-way |
| Cryostorage | Cryohexagon | EU | In development | — |
| Pharmacy | Stork | EU | Available | Prescriptions out |
| Pharmacy | DoseSpot | US | Available | Embedded e-prescribing |
| Pharmacy | MIMS and eRx | AU | In development | — |
| Finance | Xero | Global | Available | Accounting out |
| Finance | Adyen | EUUSCAAU | Available | Payments and payouts |
| Calendar | Microsoft Outlook | Global | Available | Two-way |
| EMR | Accuro | CA | Available | Two-way |
| Reporting | HFEA PRISM | EU | In development | — |
| Reporting | ANZARD | AU | In development | — |
| Reporting | BORN | CA | In development | — |
| Devices | Label printers | Global | Available | Print from the browser |
| Identity | Single sign-on (Google, Microsoft) | Global | Available | Staff sign-in |
| Identity | Enterprise SSO and SSO or two-factor enforcement | Global | In development | — |
Region shows where an integration can be used, using the codes of our regional hosts; Global means every region.
In development means the integration is being built or certified and is not generally available. Contact support if you are interested, and tell us what else you need to connect; the requirements show what we will ask for. New integrations are announced in our newsletter.
How wawa connects
Most integrations use one of three models. Your choice affects what you need to prepare.
| Model | Use when | You provide |
|---|---|---|
| Vendor cloud | The system is a SaaS service (CHLOE, Xero, most labs) | An account or API credentials for wawa |
| Private: Site-to-Site VPN | The target is on your internal network | A VPN-capable firewall, an IT contact, and each target's private IP and port |
| Public: customer-managed | You publish the target on the internet yourself | A public URL per target, an allowlist of wawa's egress IPs, and responsibility for securing it |
See Connectivity.
In all three, wawa initiates the connection and polls for new data. The exception is file-based delivery, such as some lab results, where your system deposits files in storage wawa provides and credentials for it.
Integration patterns
Most integrations follow one of these patterns, which determines what we need from you:
| Pattern | What it is | Examples |
|---|---|---|
| Vendor cloud API | wawa calls a vendor-hosted API | Adyen, Microsoft Outlook, Xero, CHLOE |
| Lab results feed | HL7 v2 results delivered as files or through a vendor API, optionally with electronic orders | TDL, Australian Clinical Labs |
| Clinic device or server | wawa reaches hardware or software inside the clinic over a VPN or a customer-managed public URL | DICOM / Orthanc, EmbryoScope, RI Witness |
| Vendor client software hosted by wawa | The vendor's only interface is its own client software, which wawa runs on its infrastructure | Secure clinical messaging networks |
| Batch file reporting | A registry or reporting body accepts scheduled file submissions rather than an API | National registry reporting |
| Document workflow | A document is exchanged instead of a system connection | Stork (prescriptions by email) |
How an integration project runs
| Phase | What happens | Done when |
|---|---|---|
| 1. Kick-off | Agree scope, a pilot clinic and named owners on both sides. Commercial terms with the vendor, where needed. | Contacts named |
| 2. Discovery | Written answers on transport, environments, identifiers and sample data. | Dependencies listed with lead times |
| 3. Access and connectivity | Credentials, certificates and the network path are in place. | Test Connection passes against the real system |
| 4. Build and configure | wawa configures or builds the connector, switched off. Runs in parallel with phase 3. | Ready for testing |
| 5. Vendor certification | Only where the vendor runs a certification programme. | Vendor sign-off |
| 6. Clinic testing | Clinic staff run a written test plan on test patients. | Clinic sign-off |
| 7. Go-live | Enabled for the pilot clinic; one real transaction verified end to end. | First live transaction verified |
| 8. Hypercare | Close monitoring after go-live, then handover to support. | Handover |
Adding a second clinic to an integration that is already live repeats only phases 3, 6, 7 and 8.
Almost all elapsed time in phases 3 and 5 depends on the clinic's IT team or the vendor: firewall changes, account creation, certification queues. Start the connectivity conversation at kick-off, not close to go-live.