I'm attempting to streamline a process for renaming PDF documents received from multiple vendors to conform to a specification provided by an EMR vendor for ingestion. Things like Document ID, Document Type, Date of Service, Account Number, MRN, etc. all must be included in the filename at defined offsets and lengths. Most of the required values can be extracted from the inbound file's name and the few remaining are static values that would be the same (or handled via a lookup table based on source) for all documents. The inbound and outbound filenames are essentially fixed-width records with each value appearing at a specific offset and space-padded on the right when needed.

I'd like to model the output format in something that can be used in the DTL editor, subclassing the Ens.StreamContainer class and extending it to represent the individual filename field elements as properties that can have values mapped to them. The properties would have a MAXLEN attribute set that matches each individual field width. I would then override the OutputFilename property as calculated to assemble the fields in the correct order, offset and length. I'd like to be able to refer to each property's MAXLEN attribute programmatically to perform that assembly.

Since these PDFs may come from many sources, I don't think I need to worry much about modeling each inbound filename format; I'd simply use $EXTRACT to obtain the needed values. But having a template for the outbound filename would be a significant time saver and simplify things for those that will eventually have to take over supporting this integration.

Any thoughts on how this might be accomplished would be very much appreciated!