Managing loops within segments


1 comment

  • Avatar
    Don Zoeggerle


    I see this more as a 837I question rather than EdiFabric's. The representation of the transaction is driven by the official structure of 837I, hence in this particular case you have:

    1. AllHI - which means that there is a collection of HI segments, all being allowed at this same position in any order. They are however different, the context of each being based on the values of the first two data elements.

    2. The allowed HI segment HI_OtherDiagnosisInformation is repeatable, and all repeatable EDI items (loops, segments, data elements) are represented as typed lists.

    So the implementation of 1) and 2) leads to how the class is designed. Why would you need reflection\helper method\switch to access items in a list ?

    Comment actions Permalink

Please sign in to leave a comment.