Skip Headers
Oracle® Fusion Middleware Healthcare Integration User's Guide for Oracle SOA Suite
11g Release 1 (

Part Number E23486-06
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Go to next page
PDF · Mobi · ePub

H B2B and Healthcare Domain Topology Best Practices

The Oracle Healthcare Adapter entitles healthcare customers to use both the SOA Suite for Healthcare integration solution for HL7 interfaces and the B2B solution for all X12 HIPAA EDI interfaces.

This appendix describes the best practice for deploying them in separate domains.

H.1 Deploy HL7 and X12 HIPAA EDI interfaces in Different Domains

From deployment perspective, it is best to install HL7 interfaces (implemented using SOA for Healthcare) and X12 HIPAA EDI interfaces (implemented using the B2B infrastructure) in separate domains for the following reasons:

Additionally, if an enterprise is already using a domain for their B2B transactions, it should not upgrade that domain for use as healthcare domain for HL7 transactions too. Instead the enterprise should create an separate domain for HL7 transactions.

The single exception to this policy is the case where the enterprise dumps both X12 HIPAA and HL7 documentation in the database. For example, when adding and/or updating HL7 and X12 HIPAA docs in an EPDR (enterprise patient data repository).

Figure H-1 shows an example SOA healthcare topology that demonstrates the use of separate domains for B2B and Healthcare. The load balancer uses HTTP to route B2B transactions to the B2B domain and uses TCP to route Healthcare transactions to the Healthcare domain.

Figure H-1 Example of SOA Healthcare Topology Using Separate Domains

Description of Figure H-1 follows
Description of "Figure H-1 Example of SOA Healthcare Topology Using Separate Domains"