Implementation Guide BBS version 1.0.0-alpha.2

This IG is currently under development and can not be considered stable and ready for use. For questions and change requests regarding this IG, please create a ticket op the Servicedesk.

1 Technical Design – Beeldbeschikbaarheid 1.0.0-alpha

1.1 1. Scope and Purpose

1.1.1 Purpose

This Technical Design (TD) describes the architectural approach for cross-community exchange of medical imaging information.

The design focuses explicitly on:

• Cross-community imaging exchange
• Gateway-to-gateway interoperability
• Federated exchange between healthcare communities

1.1.2 Out of Scope

The following aspects are explicitly out of scope:

• Internal systems and workflows within healthcare organizations
• Internal storage mechanisms
• Local technical implementations
• Vendor-specific architectural choices

This TD defines how communities interoperate — not how they implement internally.

---

1.2 2. Architectural Principles

This section describes the guiding architectural principles.

1.2.1 Community Boundaries

• Each community is autonomous
• Internal implementation freedom is preserved
• Communities are responsible for their own data governance

1.2.2 Gateways

• Gateways function as trust anchors
• Gateways act as the interoperability boundary
• All cross-community interaction occurs via gateways

1.2.3 Separation of Concerns

• Internal architecture is separated from external interoperability
• The TD does not prescribe internal registry or storage mechanisms
• Only externally exposed capabilities are specified

---

1.3 3. Cross-Community Federation

This section describes the federated architecture model.

1.3.1 Cross-Community Query

• Queries are performed via community gateways
• Cross-community querying is based on XCA principles
• Gateways are responsible for forwarding and responding to queries

1.3.2 Imaging Context

• XCA-I applies in imaging-specific contexts
• No SOAP transaction-level details are specified in this document
• No RAD-75 transaction descriptions are included

This TD defines architectural positioning, not transaction specifications.

---

== 4. Ret