Real Time Information Director User Documentation

Test the new functionality●

For information about these tasks, see the document entitled RTID Extensibility.

Supply Chain Scenario

An early user of RTSC wants to create a message flow in which an SAP order-processing application

sends an IDoc representing an order (ORDERS05) to the hub, where the order is enriched with customer

data and forwarded to a supply-chain visibility application. The outgoing message is not an XML IDoc;

rather, it is a native XML message containing some order information and some customer information.

Let's call it ORDERPLUS.

Implementing a flow like this requires the following customization steps:

Customize the data model to include the customer data required for the outgoing message. (The

data model already includes a mapping for ORDERS05.)

Create metadata for an XML document type called ORDERPLUS. Because ORDERSPLUS is an

XML message, not an IDoc, you add content metadata but not format metadata.

Deploy and test the new metadata.3.

Create a subscription input file. Specify the condition as a change in the table where incoming

orders are stored. Specify the output document type as ORDERPLUS.

Design EAI interfaces that support the transfer of the ORDERS05 IDoc to the NonStop Server and

the transfer of the ORDERPLUS XML message to the subscribing application.

Test the message flow, first using test drivers to rule out EAI interface problems, then using the

EAI facilities for a full end-to-end test.

EHR Scenario

A health authority wants to specify a message flow in which a clinic sends an HL7 message to the EHR

hub whenever a registered patient has a cholesterol screening. Later, if the patient queries the data store

through a web-based eHealth portal, the patient will see a display in which information from the HL7

message is enhanced with other data, for instance, a list of patient's prescriptions for cholesterol-lowering

drugs and, if the patient's cholesterol level is cause for concern, a suggestion to consult his GP about

treatment options.

Implementing a flow like this requires the following customization steps:

Ensure that the data model includes all the data you wish to make available. The starting EHR data

model includes chart entries that include lab test results. It also includes a table listing the

medications for a patient.