| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Need pointers on MessageSet |
« View previous topic :: View next topic » |
| Author |
Message
|
| hiitsjam |
 Posted: Sun Jun 10, 2012 1:04 am Post subject: Need pointers on MessageSet |
 |
|
Newbie
Joined: 20 May 2012
Posts: 4
|
Hi experts,
Lately I have been learning WMB 7.0 by my own. Currently, I am working on message transformation. I have tried simple examples from IBM's Infocenter and from other blogs etc and they have worked for me so far. Now, I am taking it to the next level of complexity wherein I am trying to transform an EDI based 834 transaction (healthcare Benefit Enrollment) file based on HPAA 4010 standards. I have even seen one such example X12 Message Flow and Message set (EDI 850 transaction file for Order Processing, quite similar to the one that I am trying) that comes with Infocenter. I have been able to run IBMs example successfully. I am trying to dig little deeper to understand how things work as far as transformation is concerned. I have few questions where I need some clarifications from you experts
Before I can do such a message transformation from 834 transaction file to XML (lets say) I need to create a message set. Now, as I understand, Message Set is all about definitions and the definition file that I have for EDI 834 transaction set that HIPPA has defined is quite large. I have an SEF file which acts as a definition for any incoming 834 transaction set. As per my experience with WMB so far, I think, WMB does not support SEF file from where I can create my message set. The possible options that WMB supports from where message set can be careate automatically are :
C Header
COBOL
Corba IDL File
Database Definition File
IBM Supplid Message
SCA Export or Import
WSDL File
XML DTD
XML Schema File
Clearly, it doesn't show any option to create message set directly from SEF file. Now, since SEF file is quite large and also it requires very deep understanding of the HIPPA 834 transaction, I would not like to create message set manually to avoid any possible errors.
I have converted the SEF definition into its corresponding xsd file (by using Stylus Studio X14 XML Enterprise) and I am trying to create MessageSet using this xsd file.
Question # 1 : Is it the rigt way of doing it?
Question # 2 : If above is not true, then what is the best possible way of creating the MessageSet for these Industry standard formats (like HIPAA 837 transaction set) ?
Question # 3 : While I tried to create MessageSet using the xsd file (one I got after converting the sef file into xsd using stylus software), MB Took failed saying Referenced file contains errors, but when I open this xsd with stylus or XML Oxygen editor, I don't see any error. Not really sure what is going on. I looked into the logs (Windows event viewer, didn;t find anything worth exploring)
I am having trouble posting the url of my xsd (incase if you want to look). MQSeries.Net has a requirement that I need to have at least one post before I can submit any url link ( this is my first post by the way). I will share the xsd if you guys need to have a detailed look.
Any pointers here will highly be appreciated.
Thanks in advance
Jameel |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Sun Jun 10, 2012 2:57 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Excellent first post!
I can't answer all of your questions. But, in general, if you have a message definition that is not in a format that broker will automatically process, you have essentially two choices - Convert it to a form that Broker will process
- Manually define the message definition
.
The second choice is the slower and more error prone. There are a couple of variants on the first choice: write code to convert the format, and manually convert the format. For example, you might choose to write a cobol copybook from the field definitions or an XSD or whatever.
Your error about referenced file means that Broker doesn't like one of the included files in the main xsd, or it can't find the included file in the xsd.
The best thing to do is import your XSD into a Broker toolkit project (you likely already have) and then right-click on it, and Validate it. This will then produce errors and warnings in the problems view that you can troubleshoot. |
|
| Back to top |
|
|
| kimbert |
| Posted: Mon Jun 11, 2012 4:07 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
I agree with mqjeff - your question is very nicely explained.
| Quote: |
| Question # 1 : Is it the rigt way of doing it? |
It's probably the best option. You are going to need an xsd from which to create your message definition file, and that was a perfectly reasonable way to get the xsd without having to create it manually.
| Quote: |
| Question # 2 : If above is not true, then what is the best possible way of creating the MessageSet for these Industry standard formats (like HIPAA 837 transaction set) ? |
There is no importer for SEF files - you will need to add the physical properties manually. A couple of points, though.
a) HIPAA has a *lot* of rules in addition to the basic physical format of the data. Are you aiming to parse and *validate* ( against all HIPAA rules ), or just parse?
b) when a format specification gets as large as this, it can be easier to write an importer to create the message definitions, even if one does not already exist. That's not an option for WMB v7/MRM but it is definitely an option for WMB v8/DFDL. That's one of the advantages of having an open standard for data formats...
Taking that last point a little further...you might want to consider how much time to invest in learning MRM when DFDL is already available.
| Quote: |
| MB Toolkit failed saying Referenced file contains errors |
I'd need to see the full text of the error(s) in order to diagnose that. |
|
| Back to top |
|
|
| hiitsjam |
| Posted: Wed Jun 13, 2012 1:05 pm Post subject: |
|
|
Newbie
Joined: 20 May 2012
Posts: 4
|
Thanks mqjeff & kimbert for your help. Your pointers really helped me to get into the root of the problem.
Basically the problem was, the generated xsd (which was transformed using the Stylus tool from the SEF file) contained the same element name (e.g REF-Ref-ASegmentType ) more than once, and hence the problem. Commenting out the multiple occurences helped me to resolve the problem. Code fragment from my xsd is shown below :
| Code: |
<xsd:element name="INS-Ins-ASegmentType" type="INS-A"/>
<!-- <xsd:element name="REF-Ref-ASegmentType" type="REF-A"/>
<xsd:element name="REF-Ref-ASegmentType" type="REF-A" minOccurs="0"/>-->
<xsd:element name="REF-Ref-ASegmentType" type="REF-A" minOccurs="0" maxOccurs="5"/>
<!-- <xsd:element name="REF-Ref-ASegmentType" type="REF-A" minOccurs="0"/>-->
|
After my xsd issue was resolved, I was able to successfully create MessageSet. I have also been able to transform the EDI 834 message into XML (but there seems to be some issue in the transformed XML, though it is a valid XML but the messages were not transformed the way it should have been). This should be due to some issues within the messageset itself. I am looking into it. Hopefully, I would be able to resolve it, but in general I got the overall idea of message tranformation. My sincere thanks to you guys for helping/pointing me in the right direction.
| Quote: |
a) HIPAA has a *lot* of rules in addition to the basic physical format of the data. Are you aiming to parse and *validate* ( against all HIPAA rules ), or just parse?
|
Yes, it is true that, HIPAA has lots of rules and they are pretty complex in nature. My aim is to make sure that, the incoming EDI message gets parsed properly, and then validate the message against the rules as defined by HIPAA.
Apart from this, I also read it in some thread on mqseries.net that, IBM sells the readymade message sets for these kind of industry standard formats(e.g message sets for all the HIPPA transaction files , for SFWIT based messages etc). Is it true?
Thanks once again for your time.
Jameel[/quote] |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jun 13, 2012 1:16 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| hiitsjam wrote: |
| Apart from this, I also read it in some thread on mqseries.net that, IBM sells the readymade message sets for these kind of industry standard formats(e.g message sets for all the HIPPA transaction files , for SFWIT based messages etc). Is it true? |
There's a healthcare connectivity pack that should cover HIPAA - kimbert will correct me if I'm wrong on that... 
There are category 1 supportPacs (paid, supported) that cover SWIFT, at least last I remember. |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Jun 14, 2012 1:36 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
The HCP provides excellent support for HL7, and goes a long way beyond simple parsing and writing of HL7 messages. But it doesn't include support HIPAA.
IBM does provide WMB-compatible industry packs for EDI and HIPAA though - a quick search should turn them up. |
|
| Back to top |
|
|
| hiitsjam |
| Posted: Thu Jun 14, 2012 7:05 am Post subject: |
|
|
Newbie
Joined: 20 May 2012
Posts: 4
|
Thanks mqjeff and kimbert for your sharing your knowledge.
Rgds
Jameel |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
