How to choose a design pattern when your customer' requirements are still a bit hazy

I have a flat file containing person "Records" which I get from a service provider. Each line in the file represents a Type of Record. A person Record consists of numerous records, but always the types '001' and '099'. Other records are added to a person entry based on incident.

Example.

000 # Start of doc.
001 # Person begin.
...
n Records (n > 001 && n < 099)
...
099 # Person end.
001 # Person begin.
...
n Records (n > 001 && n < 099)
...
099 # Person end.
001 # Person begin.
...
n Records (n > 001 && n < 099)
...
099 # Person end.
999 # End of doc.

Apart from the Record Type on each line there are other data contained within fixed positions.

Example

0010308952872          01000000000000 K1995-03-01

Based on an incident the Records on each person is generated dynamically by the service provider.

My approach, so far, is to define an .XSD per type of record and use schema binding classes. My problem is that there are still no requirements in regards to what types of records are relevant based on the type of incident. I would just grab a phone and call the person responsible, but working for the public sector makes planning a b****.

Does anyone have any suggestions to which software pattern could adhere most to this type of problem statement? Any sharing of experience would be much appreciated :}