ITIBlank: Difference between revisions
mNo edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
==1. Proposed Workitem: == | ==1. Proposed Workitem: Cross-Enterprise Service Bus (XSB)== | ||
* Proposal Editor: | * Proposal Editor: Don Jorgenson | ||
* Editor: N/A | * Editor: N/A | ||
* Date: N/A (Wiki keeps history) | * Date: N/A (Wiki keeps history) | ||
| Line 11: | Line 11: | ||
==2. The Problem== | ==2. The Problem== | ||
The proposed Cross-Enterprise Service Bus (XSB) profile is intended to meet the need for a message-based layer or framework, compatible with Web Services, that is constrained to meet the interoperability requirements of healthcare documents/messages in transit and that facilitates basic document/message integrity and confidentiality, security/privacy auditing and invocation of access control services. | |||
==3. Key Use Case== | ==3. Key Use Case== | ||
The XSB profile would allow the large class of healthcare use cases that require message-based transport of documents/messages to be implemented with much of the required security and privacy functionality provided by implicit service invocations during transport layer processing. | |||
==4. Standards & Systems== | ==4. Standards & Systems== | ||
Uses, extends or constrains: | |||
:• SAML | |||
:• ATNA | |||
:• XUA | |||
:• HL7-SOA PASS | |||
:• WS-Trust | |||
:• WS-Federation | |||
:• WS-Addressing | |||
:Supports or enables: | |||
:• XCA | |||
:• XACML-based Policy Engines | |||
:• XDS.b | |||
==5. Discussion== | ==5. Discussion== | ||
The proposed XSB profile could be considered a message-based extension or supplement to the connection-based ATNA profile. It also supplements and provides additional context for XUA. | |||
The HL7-SOA Privacy, Access and Security Services (PASS)-Functional Models are scheduled for ballot January, 2008. The IHE XSB profile would provide the constrained, real world technical specification anticipated in the illustrative Web Service-based use cases provided in the PASS functional specification. | |||
An XSB is not an Enterprise Service Bus nor is it an SOA implementation. | |||
Revision as of 16:20, 8 October 2007
1. Proposed Workitem: Cross-Enterprise Service Bus (XSB)
- Proposal Editor: Don Jorgenson
- Editor: N/A
- Date: N/A (Wiki keeps history)
- Version: N/A (Wiki keeps history)
- Domain: IT Infrastructure
2. The Problem
The proposed Cross-Enterprise Service Bus (XSB) profile is intended to meet the need for a message-based layer or framework, compatible with Web Services, that is constrained to meet the interoperability requirements of healthcare documents/messages in transit and that facilitates basic document/message integrity and confidentiality, security/privacy auditing and invocation of access control services.
3. Key Use Case
The XSB profile would allow the large class of healthcare use cases that require message-based transport of documents/messages to be implemented with much of the required security and privacy functionality provided by implicit service invocations during transport layer processing.
4. Standards & Systems
Uses, extends or constrains:
- • SAML
- • ATNA
- • XUA
- • HL7-SOA PASS
- • WS-Trust
- • WS-Federation
- • WS-Addressing
- Supports or enables:
- • XCA
- • XACML-based Policy Engines
- • XDS.b
5. Discussion
The proposed XSB profile could be considered a message-based extension or supplement to the connection-based ATNA profile. It also supplements and provides additional context for XUA. The HL7-SOA Privacy, Access and Security Services (PASS)-Functional Models are scheduled for ballot January, 2008. The IHE XSB profile would provide the constrained, real world technical specification anticipated in the illustrative Web Service-based use cases provided in the PASS functional specification. An XSB is not an Enterprise Service Bus nor is it an SOA implementation.