| Author |
Message
|
| simon.starkie |
 Posted: Tue Aug 19, 2003 11:50 am Post subject: Anyone have an X12 parser? |
 |
|
Disciple
Joined: 24 Mar 2002
Posts: 180
|
I want to be able to serialise individual elements with an X12 message and then transform these elements into an XML document. A Custom MQSI/WMQI/WBI parser would probably be the most efficient way to dealing with this. Unless there is another way.
Thanks. |
|
| Back to top |
|
 |
| warrenpage |
| Posted: Tue Aug 19, 2003 6:25 pm Post subject: ??? |
|
|
Acolyte
Joined: 19 Feb 2002
Posts: 56
Location: Australia
|
| Um Simon that is what the KPC does. Why dont you give me a call? |
|
| Back to top |
|
|
| simon.starkie |
| Posted: Thu Feb 22, 2007 12:11 pm Post subject: Does WMB6 support X12 then? |
|
|
Disciple
Joined: 24 Mar 2002
Posts: 180
|
Does WMB6 support X12?
If not, is there a custom parser for X12 available for WBI6?
And for completeness, are there any issues with porting a custom HL7 parser to WMB6?
Thanks. |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Feb 22, 2007 3:05 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
WMB supports both X12 and HL7. You can buy message sets for X12 from the IBM Dublin team ( email dubadapt@ie.ibm.com ) and there is an 'ESB for HL7' available for HL7 parsing and transformation via IBM services.
I think the message sets for HL7 may be available separately in the v6 PowerPack release with 6.0.2.
I don't advise porting a custom HL7 parser to WMB unless you find that the HL7 message sets are deficient in some way. Part of the value proposition of WMB is that it relieves you of the burden of maintaining custom code. |
|
| Back to top |
|
|
| simon.starkie |
| Posted: Thu Mar 15, 2007 1:48 pm Post subject: |
|
|
Disciple
Joined: 24 Mar 2002
Posts: 180
|
Hi Kimbert,
Thanks very much for the excellent suggestion for X12.
I think it should be relatively easy to implement an MRM metadata solution providing we are dealing with standard HIPAA X12 EDI data 
I have already contacted Dublin and received more information which is quite encouraging so I'm excited about that.
As for the HL7 parser, I think we may have to continue with the custom one that Neil developed for us 6 years ago...mainly because we are at the mercy of the HL7 we receive from various sources (some read the HL7 spec, some read the HL7 spec upside down, some didn't read the HL7 spec at all) so we probably cannot use an MRM solution based on so-called industry standard HL7 schemata...the custom parser lets us avoid this problem by simply parsing any HL7 onto leaves on the parser tree and from there we slog it out with ESQL. |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Mar 15, 2007 3:39 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| ...we are at the mercy of the HL7 we receive from various sources (some read the HL7 spec, some read the HL7 spec upside down, some didn't read the HL7 spec at all) |
You and everyone else. I realise that you have a working HL7 parser, so you would probably need a good reason to change. However, the 'ESB for HL7' solution tackles those variations in usage very elegantly using a canonical HL7 tree. All incoming messages are transformed to the canonical structure before any processing is performed. Mappings are provided for many of the known variations in usage, and the programming model is flexible enough to cope with new ones.
It also provides custom TCP/IP adaptors implemented in Java ( not using TCP/IP support pack) and integrates with Tivoli monitoring software for message tracking. Quite a complete package.
It has been doing this for a few years now, and I reckon it is nicely positioned to transition to using HL7 v3 as the canonical structure. |
|
| Back to top |
|
|
| simon.starkie |
| Posted: Mon Sep 22, 2008 2:46 pm Post subject: |
|
|
Disciple
Joined: 24 Mar 2002
Posts: 180
|
| We ended up using WTX aka Webshphere Transformation Extender (formarly know as Mercator). |
|
| Back to top |
|
|
|
|
