RealTime Server

Top  Previous  Next

The HIPAA RealTime Server can be used in conjunction with any HIPAAsuite Responder application to provide MIME/SOAP functionality as described in CAQH CORE Phase II. This means the Claim Status Responder will be CAQH CORE compliant, being able to answer 276 Real-Time and Batch mode messages in both SOAP and MIME formats. The source data for a claim's status can be the HIPAA Claim Master's tables or a separate set of claim tables.

 

To respond to SOAP or MIME 276 Claim Status requests, the HIPAA RealTime Server must be configured to use the same database as the HIPAA ClaimStatus Responder. This serves to provide the RealTime Server with information such as the Trading Partner’s ID and credentials. If the incoming SOAP/MIME request’s SenderID is not the Trading Partner ID associated with a username/password, the message will be rejected. The following is a part of the RealTime Server's configuration window:

 

RTS-DBSetup

The Database used by the RealTime Server must be the same used in the ClaimStatus Responder.

 

The name specified in the HIPAA RealTime Server’s Server ID field is the name that will be used to identify you or your organization in the SOAP and MIME Sender/Receiver ID fields.

RTS-DBSetup-SenderID

This will be your identifier when sending/receiving SOAP or MIME messages.