Matching 27x Request and Responses In Electronic Data Interchange Between HMSA And Its Partners Matching 27x Request and Responses recommendations are given to facilitate electronic documents transmission. The matching of a 27x request transaction with its response, it is recommended that a unique trace number be submitted in TRN02 at the patient level (Subscriber or Dependent loop) and, … Read More →
Batch And Real-Time Transactions Guidelines for HMSA EDI Partners Batch And Real-Time Transactions should adhere to the guidelines given in the today’s post. HMSA will respond to a batch request within eight hours. If the request is for non-HMSA requests (ie, BlueCard or FEP) the transaction must be routed to another entity outside of HMSA and may … Read More →
HMSA EDI Mapping Guidelines (File, Functional Group, Transaction Set, and Claim Rejection) HMSA EDI Mapping Guidelines are given for business partners transmitting electronic transactions to HMSA. HMSA EDI Mapping Guidelines cover the following points – File, Functional Group, Transaction Set, and Claim Rejection. A file level reject occurs when an error is detected in the interchange control header … Read More →
Submitting Electronic Transactions to HMSA (General requirements) Submitting Electronic Transactions to HMSA partners should remember that each transmission to HMSA should have a unique Interchange Control Number (ISA13). HMSA will use this number to determine if it is a duplicate file. HMSA will only accept one interchange (ISA/IEA) per input file from a submitter. There … Read More →