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

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

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

A Back-End Applications Interface

This appendix lists the message properties supported by Oracle SOA Suite for healthcare integration.

The appendix contains the following topics:

A.1 Mapping Healthcare IP_MESSAGE_TYPE to SCA Normalized Message Properties

Table A-1 maps the Healthcare IP_MESSAGE_TYPE to SCA normalized message properties.

Table A-1 Healthcare IP_MESSAGE_TYPE to AS11 SCA Normalized Message Property Mapping

SCA JMS

hc.messageId

MSG_ID

hc.replyToMessageId

INREPLYTO_MSG_ID

hc.fromEndpoint

FROM_ENDPOINT

hc.toEndpoint

TO_ENDPOINT

hc.action

ACTION_NAME

hc.documentTypeName

DOCTYPE_NAME

hc.documentProtocolVersion

DOCTYPE_REVISION

hc.documentProtocolName

-

hc.documentDefinitionName

-

hc.messageType

MSG_TYPE

hc.conversationId

-


A.2 Normalized Message Properties

Header manipulation and propagation are key business integration messaging requirements. Like other SOA components such as Oracle BPEL Process Manager, Oracle Mediator, and Oracle JCA, Oracle SOA Suite for healthcare integration relies on header support to solve integration needs. For example, you can preserve a file name from the source directory to the target directory by propagating it through message headers.

Normalized messages have two parts, properties and payload. Typically, properties are name-value pairs of scalar types. To fit the existing complex headers into properties, properties are flattened into scalar types.

Table A-2 lists the predetermined properties of a normalized message for Oracle SOA Suite for healthcare integration.

Table A-2 Properties for Oracle SOA Suite for healthcare integration

Property Name Propagable (Yes/No) Direction (Inbound /Outbound) Data Type Range of Valid Values Description
hc.conversationId

No

Both

String

-

The ID used to relate the message to the message response

hc.documentDefinitionName

No

Both

String

-

The document definition

hc.documentProtocolName

No

Both

String

-

The document protocol

hc.documentProtocolVersion

No

Both

String

-

The document version

hc.documentTypeName

No

Both

String

-

The document type, for example, 850 for an EDI X12 document

hc.fromEndpoint

No

Both

String

-

The trading partner identifier of the sender, for example, the name, such as Acme, or a DUNS number

hc.messageId

No

Both

String

-

A unique message ID, not directly related to ECID. (ECID information is stored in the B2B AppMessage table.)

hc.messageType

No

Both

String

-

Message type values are:

  • Request = 1

  • Response = 2

  • Functional Ack = 9

hc.replyToMessageId

No

Both

String

-

The message ID to which the sending message is replying

hc.toEndpoint

No

Both

String

-

The trading partner identifier of the receiver, for example, the name, such as Acme, or a DUNS number.