Standard Companion Guide - Magellan provider website

More documents

Recommendations

Info

MAGELLAN BEHAVIORAL HEALTH COMPANION GUIDE3 MBH Specific Business Rules & LimitationsThe documents included below will clarify the loops, segments, and data elements for eachtransaction type that must be used for MBH.Information will be provided to explain when conditional data must be used for MBH and toidentify those codes and elements that do not apply to MBH. This information is designed to helpa submitter complete each transaction.The information contained in these transaction-specific companion guides does not contradict anyrequirements in the corresponding HIPAA Implementation Guide.3.1 MBH 997 Companion Guide (tbd)3.2 MBH TA1 Companion Guide (tbd)3.3 MBH 270/271 Companion Guide3.4 MBH 276/277 Companion Guide3.5 MBH 277U Companion Guide3.6 MBH 278 Companion Guide3.7 MBH 820 Incoming Companion Guide3.8 MBH 834 Incoming Companion Guide3.9 MBH 835 Outgoing Companion Guide3.10 MBH 835 Incoming Companion Guide3.11 MBH 837 Institutional Incoming Companion Guide3.12 MBH 837 Institutional Outgoing Companion Guide (tbd)3.13 MBH 837 Professional Incoming Companion Guide3.14 MBH 837 Professional Outgoing Companion Guide (tbd)Revised: April 21, 2004 HIPAA X12 (004010 + Addenda) Version 1.16 Page 19 of 30
MAGELLAN BEHAVIORAL HEALTH COMPANION GUIDE4 Testing with MBH4.1 Certification and Testing OverviewMBH will focus testing on interfaces with direct trading partners. This testing will follow the 7types of testing as defined in the document named Testing_whitepaper082602.pdf which can befound on the WEDI-SNIP website. The WEDI SNIP website URL as listed in the Referencessection above.MBH has defined a Type 8 test that involves transactions communicating successfully into corehost systems. This would be the final phase of testing prior to signoff on the interface.TBD4.2 Detailed description of testing phase4.3 Separation of Test and ProductionMBH has an isolated testing process. This test process will be used to initially certify a giventransaction version between two trading partners, to verify changes to that version, and to verifysubsequent versions.Pilot or pre-production transmissions must follow these test requirements.A test file being sent to MBH must meet the following requirements.4.3.1 Interchange Header Test SettingTransaction should be constructed using the test indicator ISA15 set to “T” for Test. (Productionfiles will have “P” in this element.)4.3.2 Test EncryptionTransaction should be encrypted using the test encryption key and PGP software encryption.4.3.3 Test LogonTransaction should be transmitted using the test logon ID and password. This will place the file ina test folder. Work with your designated MBH EDI Analyst to receive logon ID and password.4.3.4 Type of test dataTransaction data should represent valid transaction records without using Personal HealthInformation (PHI). One level of testing should use data that is meaningful to the MBH test hostsystem. These tests must be coordinated with MBH EDI Analysts, who will coordinate withinternal core business system analysts.Revised: April 21, 2004 HIPAA X12 (004010 + Addenda) Version 1.16 Page 20 of 30
Page 1: HIPAA TRANSACTION STANDARDCOMPANION
Page 6 and 7: MAGELLAN BEHAVIORAL HEALTH COMPANIO
Page 23: MAGELLAN BEHAVIORAL HEALTH COMPANIO

Standard Companion Guide - Magellan provider website

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?