HTTP to United Health Care

This topic has 3 replies, 3 voices, and was last updated 15 years, 2 months ago by Kathy Riggle.

Creator

Topic
July 28, 2009 at 7:55 pm #51085

Kathy Riggle
Participant

All –

We seem to be all jumping through the same hoops… Is anyone using the HTTPS Real-Time to communicate with United Health Care Connectivity Director? Are you using the HTTP Protocol on the engine, or have you written your own?

Any help is always appreciated!

Kathy
Creator

Topic

Viewing 2 reply threads

Author

Replies
- July 28, 2009 at 9:32 pm #68734
  
  Jim Kosloskey
  Participant
  
  Kathy,
  
  We are attempting (and have been for nearly a year) to connect to UHC using their ‘real time’ facility.
  
  The latest I got from the vendor of the software UHC is using is there appears to be a bug. That is recent information and has yet to be really determined.
  
  We are using the https protocol (and I have attempted to use TclCurl) all end up with the same issue.
  
  If you email me I am willing to give you my telephone # and we can chat.
  
  email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
- July 29, 2009 at 7:03 pm #68735
  
  Jeff Egan
  Participant
  
  On a related topic, are you sending 278N’s to UHC?
  
  If so, are you generating the UHC 278 from an ADT message (A01)? If not, what is your source data?
  
  If you are starting from an ADT, would you mind sharing your Xlate file?
  
  Thanks.
- July 29, 2009 at 7:27 pm #68736
  
  Kathy Riggle
  Participant
  
  Jeff –
  
  Not by our choice necessarily, but yes, we are using an A01 and converting it into the 278 requested by UHC. We have not successfully passed this to UHC, so chances are, this is not final!
  
  If you want me to e-mail the *xlt, let me know.
  
  Kathy
Author

Replies

Viewing 2 reply threads

The forum ‘Cloverleaf’ is closed to new topics and replies.