- This topic has 2 replies, 1 voice, and was last updated 9 years, 3 months ago by
.
-
Posts
-
-
Hi ,
I am doing one BizTalk project using HL7 schema . HL7 accelerator provides the schemas for use. So we create those schema using the tool and then create a project. From the Biztalk orchestration project we reference those schema project and use those schemas. I have a MLLP port wehre HL7 messages are put and Orchestration reads those messages from that port for processing. But the problem comes here.
I have multiplpe hospitals sending their HL7 messages to the same MLLP port for processing. Suppose I have a schema ORM_O01_23_Message for Hospital1(created by the accelerator). The Hospital2 also wants to use the same version of schema ORM_O01_23_Message. But it has a different structure than the created by the accelerator. In this case there is a class of schema structure for same version and type. As hospitals has the fredom to change to a different structure
All HL7 messages comes with the version name with it. So how to handle this type of scenario ? I can not install one Biztalk serverr for each hospital. So I have to use one biztalk server that handles multiple hospitals. Please suggest how to overcome this problem.
thanks
Jit
-
I would first modify the target namespaces on the schemas so there are no conflicts with having multiple schemas with the same root node. Then i would use a listen shape with multiple recieve shapes. The listen shape would allow for the orchestration to listen for different messages matching a schema for any of the recieve shapes in the listen shape. However, you need to change the namespaces for the schemas…
1. Open a project that has the schema
2. Double-click the schema to open it
3. Select the schema node.
4. Right-click and select properties
5. Modify the target namespace property.
-
As I understand these schemas (which has been very little up to now) there is "supposed" to be a standard format/schema and then a section of possible custom data. The trick in this case is to read the standard data the same way in every case but then pass the rest of the data according to another set of rules, say pass thru. However, in practice, as I've heard several Mainframe folks claim that the standards are rarely followed and new ones are created depending on which way the wind blows.
That said. I'll keep this issue in mind and review some internal work to see if I can find anything. I'm interested in a solution as well.
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.