# SOAP mandates - what each ecosystem requires

What each SOAP ecosystem requires and which building blocks satisfy it - IHE, CDC IIS, NHS Spine and Helsenett.

Every ecosystem - a national health network, a public registry, a trade exchange - publishes its own profile that fixes the SOAP version, the security mechanisms, the packaging and often the addressing headers. Connecting requires meeting the profile in full.

Each page below covers one ecosystem - what its specifications mandate, and which of Zato's [building blocks](https://zato.io/docs/dev/soap/index.html#the-building-blocks) satisfy it. In every case the combination is configuration in the Dashboard: a version dropdown, checkboxes, a security definition - never protocol code.

| Ecosystem | What it mandates | Where it applies |
| --- | --- | --- |
| [Healthcare document exchange (IHE)](https://zato.io/docs/dev/soap/mandates/healthcare-ihe/index.html) | SOAP 1.2 + MTOM + WS-Addressing + signed SAML | TEFCA, eHealth Exchange, gematik ePA, Swiss EPD |
| [Immunization registries (CDC IIS)](https://zato.io/docs/dev/soap/mandates/cdc-iis/index.html) | SOAP 1.2 + TLS + credentials in the message body | U.S. state and city registries |
| [NHS Spine](https://zato.io/docs/dev/soap/mandates/nhs-spine/index.html) | ebXML MHS over mutual TLS | Health and care systems in England |
| [Norwegian Helsenett](https://zato.io/docs/dev/soap/mandates/norway-helsenett/index.html) | ebXML MHS with per-payload signing and encryption | Health messaging in Norway |

Because each mandate is a combination of independent blocks, the same knowledge transfers - a connection that satisfies IHE differs from one that satisfies CDC IIS only in which boxes are ticked and which definition is attached.

## Learn more {#learn-more}

- [SOAP integrations](https://zato.io/docs/dev/soap/) - Envelopes, versions and Python objects instead of XML
- [SOAP as Python objects](https://zato.io/docs/dev/soap/python-objects/) - Build requests and read responses with dot access, no schemas
- [SOAP security](https://zato.io/docs/dev/soap/security/) - WS-Security, credentials in the body and client certificates
- [MTOM and SwA attachments](https://zato.io/docs/dev/soap/attachments/) - Binary content out of the envelope and into MIME parts
- [SOAP tutorial](https://zato.io/tutorials/soap/calling.html) - Call any SOAP service with Python objects, start to finish