Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Trying to build a field mapping table
Message
From
06/06/2008 12:31:07
 
 
To
06/06/2008 11:25:41
Jay Johengen
Altamahaw-Ossipee, North Carolina, United States
General information
Forum:
Visual FoxPro
Category:
Other
Environment versions
Visual FoxPro:
VFP 9 SP2
Miscellaneous
Thread ID:
01322108
Message ID:
01322121
Views:
13
>Ok, hopefully I can make this easy enough to understand.
>
>Essentially, there is a text file that has one line per "Segment" which is comprised of delimited values.
>
>So, you might have this as one of the segments:
>
>
>AAA*Y**42*Y~
>
>
>These will be parsed apart and inserted into a table like this:
>
>
>Loop   Segment  Field001  Field002  Field003  Field004
>2000A  AAA      Y                   42        Y
>
>
>Pretty simple so far. The issue I have is that there could be combinations of the same segments, and I need to create a driver table that contains all the possibilities. This table will be used to actually populate the different tables that support our application.
>
>I think something like this might work:
>
>
>Loop  Segment Field   Value MapToDataField                  Usage
>200A  AAA     Field01 Y     SomeTable.SomeField        Response Code - Yes
>200A  AAA     Field01 N     SomeTable.SomeField        Response Code - No
>200A  AAA     Field02       (none)                     Qualifier Code (not used)
>200A  AAA     Field03 04    SomeTable.SomeField        Rejection Reason Code - Authorized Quantity Exceeded
>200A  AAA     Field03 41    SomeTable.SomeField        Rejection Reason Code - Authorization/Access Restrictions
>200A  AAA     Field03 42    SomeTable.SomeField        Rejection Reason Code - Unable to Respond at Current Time
>200A  AAA     Field03 79    SomeTable.SomeField        Rejection Reason Code - Invalid Participant Identification
>200A  AAA     Field04 C     SomeTable.SomeField        Follow-up Action Code - Please Correct and Resubmit
>200A  AAA     Field04 N     SomeTable.SomeField        Follow-up Action Code - Resubmission Not Allowed
>200A  AAA     Field04 P     SomeTable.SomeField        Follow-up Action Code - Please Resubmit Original Transaction
>200A  AAA     Field04 R     SomeTable.SomeField        Follow-up Action Code - Resubmission Allowed
>200A  AAA     Field04 S     SomeTable.SomeField        Follow-up Action Code - Do Not Resubmit; Inquiry Initiated
>200A  AAA     Field04 Y     SomeTable.SomeField        Follow-up Action Code - Do Not Resubmit; We Will Hold Your Request
>
>
>I want to know that I'm on the right track as there are many Segments and possible field values for each one; I don't want to spend 20 hours building something that I will have to tear apart and rebuild later.
>
>Any suggestions appreciated.

How flexible do you want to make this?

Will you be parsing all the HIPAA transactions?
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform