A new PRV segment Mapper missing after the HI segment

[imsweb]

A new PRV segment Mapper missing after the HI segment

[angelaszek]

Hello, I submitted a new issue (#65) that will allow custom mapping files to be passed to the parser to accommodate specs that differ from the supported standards. We will be working on it as time is available. I believe this will help address this issue?

[nikhil-javalkar]

Thanks for this !
What would be an estimated ETA for this ?

[ctmay4]

We cannot give any real estimate, but I do not think this will happen any time soon. Simply a case of competing priorities. If you would like to submit a pull request with this feature we would gladly look into it.

[nikhil-javalkar]

Hi @ctmay4 Could you please help us with the access to the repository to create a pull request.

[nikhil-javalkar]

Also @ctmay4 Can we just add the mapping for the missing segment in the desired mapping file and create a pull request for the same just to suffice the requirement for now ?

[ctmay4]

Can you supply an example (with identifiers stripped) of this segment?

@angelaszek can you please comment on this? Is this part of the standard? Have we not seen this segment in any of the files we processed?

[angelaszek]

I don't believe a PRV segment after an HI segment is standard so it's not something we want to include as part of this library. You are welcome to make this change on a local version that you maintain though.

[nikhil-javalkar]

SampleInputFile.txt

Hi @ctmay4 Attached is the sample file we are getting as an input. It has a PRV segment after HI segment which is currently missing in the mapper file.

[angelaszek]

Thank you for the sample.

Based on the screenshot from the ANSI 5010 X222 documentation there needs to be an NM1 segment before the PRV segment for the file to meet the standard. We don't want to make a non-standard change to the mapping file. The update to allow users to provide user-defined non-standard mappings will allow for users to process files that don't meet the standard.