News
Creating a Checkstatus |
| 04/15/2011 |
| News >> Community News |
Creating a CheckStatus
Attention software developers and/or vendors:
If you are a vendor or maintain your own Practice Management software, it is important for you to ensure that your software’s CheckStatus requests are compliant with UHIN’s Technical Reference Manual (TRM). If you need a copy of this document, please contact the UHIN Help Desk (877-693-3071/ customerservice@uhin.org). Specifically, please reference Chapter 14 (Building a Router Client Application), page 62-63 which states that the required attributes of a CheckStatus are as follows:
•sender_id
•user_id
•user_password
•receiver_id
•transmission_id
Our review has found non-compliant CheckStatus requests that lack a Sender ID or valid Transmission ID. These transactions, besides being unable to complete the CheckStatus function, waste system resources and—in large quantities—place stress on UHINet II. It is important for each developer and vendor to verify that his/her CheckStatuses are compliant.
If you have any questions, please contact UHIN’s Help Desk. You will be referred to the applicable personnel for an answer.
