B2B Integration

Looking for feedback from users using HIPAA Compliance Check or HIPAA Data Compliance Utility on potential new content for the pack

  • 1.  Looking for feedback from users using HIPAA Compliance Check or HIPAA Data Compliance Utility on potential new content for the pack

    Posted 7 days ago
    We are evaluating the impact of three recent AHA! submission in the area of HIPAA validation.  Looking for feedback from healthcare customers as to usefulness of new support for :


    1. Add the HIPAA 834 318 and 277DRA transaction to the HIPAA pack = ITX-I-178

    The state of New York is requiring insurance carriers to use the 834X318 and 277DRA transactions. These transactions are currently not in the HIPAA pack. This appears to be needed in other states as well for PACDR.
    Which of you needs the 5010 318?
    Which of you needs the 5010 277DRA Ack?

    https://watsonsupplychain.ideas.aha.io/ideas/ITX-I-196

    2. WTX Type Tree needed for X12 6020 275 (X314 TR3 for HIPAA)

    We have a need for a type tree for the X12 6020 275 transaction. Specifically the HIPAA voluntary TR3 X314 implementation. It is a HIPAA transaction, though not mandated, but the HIPAA Pack doesn't have a tree.

    Is anyone planning to use the 6020 version of the clinical attachment? = ITX-I-100

    https://watsonsupplychain.ideas.aha.io/ideas/ITX-I-100

    3. ITX HIPAA Compliance Check - Include validation of NPI number = ITX-I-99

    Enhance the HIPAA Compliance Check to validate that the NPI number in the X12 transactions is a valid format. NPI Must be 10 characters long, starting with a 1 or 2 and the first 9 digits are used to calculate the 10th character, as a check digit.

    Do you need NPI (Luhn) checking?
    Does this need to be configurable?
    https://watsonsupplychain.ideas.aha.io/ideas/ITX-I-99



    ------------------------------
    Stephanie Fetzer
    Product Manager, IBM Sterling Transformation Extended
    HCL
    ------------------------------