@stephan-head
Forum Replies Created
-
AuthorReplies
-
September 17, 2008 at 10:08 am in reply to: x12 278 and United Healthcare – anyone doing this? #62966Jim Kosloskey wrote:
Stephen,
Thanks for that update.
Did they give any indication as to the scope of changes to the Companion Guide?
Sorry. They didn’t.
September 16, 2008 at 12:34 pm in reply to: x12 278 and United Healthcare – anyone doing this? #62964Jim Kosloskey wrote:I am still early in the review of the 5010 specification for UHC versus the 4010 version.
Here is what I have noted:
1. It appears there are only minor layout differences which actually affect the needs of UHC. Some of what could be troublesome expansions such as repeating Data Elements do not seem to be required.
2. They have switched the roles of the 2000A and 2000B Loops. 2000A was the Payer and 200B was the Requester. Now they are reversed. A minor annoyance.
3. The value from GS08 needs to also be in ST03. Depending on your point of view this can be trivial or cause some consternation. Many will simply hard code both entries (the GS in arguments to a Tcl proc or in the Tcl proc itself – the ST03 in the Xlate). Personally I find that a maintenance issue waiting to happen. I am leaning towards modifying my envelope building proc to allow usage in other than the Outbound Tps context (I was kind of thinking I would need to do that anyway); deploying the proc pre-xlate; and then using an Xlate proc to extract the value set for the GS08 and COPY it to the ST03.
Since I have designed this integration to be as Table driven as possible, some of the issues I have found don’t pose any great hardship.
Thus far it looks like the 5040 variant (which is what we need to use in Cloverleaf(R) 5.6 to get a 5010 variant) is not significantly different than the 4010 such that I am using a copy of the Xlate pointed at a replication of the 5040 variant. I have not had to make any serious changes yet.
I am only at the 2000B Loop with the real meat yet to go.
At this time we are not planning on doing FTP to/from UHC and that is the only connection mechanism (other than Clearing House) offered by UHC at this time. I will continue to work on the message structure and other non-connection related pieces until there is a real-time connection environment ready from UHC.
Many of you who decide to use FTP will get ahead of me easily and hopefully I will learn from your experience.
I expect the real time connectivity
We started looking at the 5010×216 specs yesterday and noticed the same thing. Thanks, Jim for keeping us up to date on these issues as they arise. Before upgrading to 5.5, we ran 5.4.1 under 5.4 ML6 without any issues. Charlie, after I posted this; I got to thinking about it and realized that was it. Do you have IP Sockets installed for CICS? If so, you attach the transid to a port and Cloverleaf communicates with that port. On the mainframe side, the receiving transid needs to stay “resident” or always “listening”. The mainframe sending doesn’t. On CL, that thread would remain “OPENING” until the message is sent. At least that’s how it works with HealthQuest 2000 from McKesson and the mainframe OS, Z/OS. Time changes on November 4th at 02:00 to be exact. A lot depends on your OS. Older versions of AIX would need to be manually changed as would Windows 2000 and below. Sorry, I can’t speak of Linux.
Have you installed REV2? A few of the Microsoft patches caused changes in the OS security in Windows 2003. REV2 fixed this. Maybe the same patches effected XP as well. 5.4.1 works like 5.5. We don’t the same HIS, but do have RALS here and what I have seen, it’s pretty much a standard HL7 interface. The only issue (minor) was that they expected a medical record # and location identifier in PID:3. The following ADT messages were support A01, A02, A03, A04, A06, A07, A08, A11, A12, A13, A17, A31, and A34. Thank you so much for the information and example. Have you checked Microsoft’s website for what was included in SP2? There are quite a few patches included that address security. You may be getting “hit” with one of those. No, there was no shutting down of threads or processes. The fix I suggested is for the Client only. You will still have to do the Server pieces recommend by Quovadx, if you haven’t done so. The other question about GMT, I’m sorry; but I don’t see that on my PC. I am running XP with the DST fix installed from Microsoft.
See my response to thread – Thread time stampe shown wrong -
AuthorReplies
