>
>The fields (segments) can map to whatever field in the data tables. They are in fixed position in the HL7 data (text) stream. Meaning, I may not always have 7 rows, but when I see "PDI" at the beginning of a line, I know that there will be x number of fields to follow. Many will be empty, but the delimiters will still be there. It may be more complex than that - haven't read Greg's reply yet - but for the billing piece I'm working on at the moment, I think that's pretty much it.
>

A segment is an entire line...for example, you would call it a PID segment, if it starts with PID. The segment contains fields, which are most likely called "elements".

In EDI, there is a larger subdivision called a transaction set (or a document). So, for example, a purchase order document will be mapped to purchase order header records and line item records (and perhaps other tables, too). But the information that will go into the order header record is spanned across multiple segments (lines, not fields) in the EDI document. The purchase order number comes from a segment starting with "BEG". The requested ship date in a DTM segment. Shipto location in N1 segment. And so on.

So does each HL7 segment map to one record in a table? Or do several HL7 segments work together to map to a record in a table?