Last updated March 26, 2013 21:33, by SureshSharma
Feedicon  

Official Oracle SOA Suite Health Care Samples

Updated 11g R1(11.1.1.6.0) Samples

Sample Description
hcfp-101-ADT_A03_MLLP1.0This sample walks through the steps to setup an End to End HL7/MLLP Interface Scenario Using JDev Healthcare Adapter to exchange an ADT_A03 document over the MLLP1.0 Exchange from design, deployment, runtime testing and Monitoring perspective. This scenario addresses the use-case with one source endpoint (Admission) and one target endpoint (Laboratory) to handle ADT_A03 messages without any modification. You can read additional documentation here.
hcfp-102-ADT-MLLP1.0This sample walks through the steps to setup an End to End HL7/MLLP Interface Scenario Using JDev Healthcare Adapter to exchange an ADT_A04 document over the MLLP1.0 Exchange from design, deployment, runtime testing and Monitoring perspective.
This scenario addresses the usecase with one source endpoint (Admission) and two target endpoints (Laboratory and Pharmacy) to handle ADT_A04 messages without any modification. The message to Pharmacy would be transformed from 2.3.1 to 2.5 version. Additional docs may be found here.
hfcp-103-ADT_A04_MLLPThis Sceanrio addresses the usecase how to create a simple end-to-end HL7/MLLP application using JMS Internal Delivery Channel. It uses one source endpoint and two target endpoints for handling ADT messages by using the generic message type. User will create three JMS queues for receiving and sending messages to and from the three endpoints.. Additional documentation may be found here.
hcfp-104-HIPAA-Composite_270_271This sample demonstrates usage of composite and B2B to send and receive HIPAA messages. You can download additional documentation here
hcfp-107-ADT_MLLP10This sample walks through the steps to setup an End to End HL7/MLLP Interface Scenario using JDev JMS Adapter to exchange an ADT and ORM documents over the MLLP1.0 Exchange from design, deployment, runtime testing and Monitoring perspective.
This scenario addresses the usecase with one source endpoint (Admission) and three target endpoints (Laboratory, Pharmacy and Radiology) to handle ADT and ORM messages without any modification.
The message to Radiology would be transformed from ADT 2.3 to ORM 2,4 version.
This usecase also addresses how to handle routing of messages based on conditions using BPEL switch. Additonal project documentation may be viewed here.