| Author |
Message
|
| venky |
 Posted: Fri Oct 11, 2013 8:51 am Post subject: Parsing 837 and 835. |
 |
|
Master
Joined: 08 Jul 2003
Posts: 205
|
Hi All, What are the options for parsing an 837, 835 record without building a message set.
my understanding:
1. use the HIPPA pack with WTX node. This requires the WTX design studio, WTX for integration server and the HIPPA Pack. Doesn't require the WTX runtime.
2. Just with message broker: can't parse this without building a message set.
3. The WMB connectivity pack for HL7 doesn't have a parser for 837/835.
Please clarify/confirm the above.
Thanks,
V. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Fri Oct 11, 2013 8:57 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
What does it mean "parse"?
What does it mean "without building a message set"?
Please clarify/confirm the above. |
|
| Back to top |
|
|
| venky |
| Posted: Fri Oct 11, 2013 9:05 am Post subject: |
|
|
Master
Joined: 08 Jul 2003
Posts: 205
|
| Hi - I'd like to understand the options for parsing 837/835 without building a message set manually. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Fri Oct 11, 2013 9:11 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Oct 11, 2013 9:12 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| venky wrote: |
| Hi - I'd like to understand the options for parsing 837/835 without building a message set manually. |
I'd doublecheck that the WMB healthcare connectivity pack hasn't been enhanced to include these messages.
And then I'd weigh the development effort of building a message definition manually - particularly when there are almost certainly similar models available to use as templates - against any of the other options.
And then I'd go back and I'd make sure you know *exactly* what you mean by "parse". It might just mean "turn into a logical tree", and it might actually mean "perform full, deep, business validation of the logical contents".
And you're wrong that you can't parse this without building a message set. WMB is a Turing complete development environment. You can do anything you want with it, in any way you want to. |
|
| Back to top |
|
|
| venky |
| Posted: Fri Oct 11, 2013 9:54 am Post subject: |
|
|
Master
Joined: 08 Jul 2003
Posts: 205
|
Thanks all for the response.
The requirement is not only parse into logical tree, but also to validate the content of the message.
when you say >>And you're wrong that you can't parse this without building a message set. >>
Are you referring to DFDL ?
My understanding : out of the box just with WMB 8, I don't think there is a ready to go 'parse and validate' component for 837 and 835s.
so given the requirement and the above understanding, I think:
WTX node with WTX HIPPA pack is the way to go - is this correct ?
Thanks,
V |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Oct 11, 2013 10:41 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
I would never use WTX for anything.
That's just me.
You can certainly use a Java library "out of the box" to parse and validate these things.
You can certainly write ESQL code to parse a BLOB message manually, "out of the box".
Again, go back to the business value. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Fri Oct 11, 2013 11:14 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Cloud-based free web service to validate your EDI documents : http://www.etasoft.com/lval.html
Of course, you could write your own validation rules. EDI has been around forever. There is plenty of documentation, although the effort would not be trivial.
mqjeff is right on the money : avoid WTX at all costs.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
|
|
