This section examines the database schema that is needed to generate LabResult messages. This database schema consists of the following database tables:

• The status tables that have been defined for your message definitions;
• The tables that are generated from the table grammars that you have specified;
• A group table that is generated from the table group that you created.

Because your VMD file contains two message definitions, two status tables are defined:

• PatientRegister for the Patient Register message, and
• LabResults for the Lab Results message.

As you saw in Basic Database Schema, a status table contains two fields: MESSAGE_ID, which specifies a unique identifer for an outgoing message, and STATUS, which is the current status of the message. When STATUS is W, an outgoing message is waiting to be sent.

The database schema also contains the data tables that have been generated from the table grammars that you have specified. These data tables have the same structure as the tables in your VMD file, except that two fields have been added:

• MESSAGE_ID, which is a unique identifier representing the message that will be generated from this data;
• PARENT_ID, which contains the identifier of the row of the parent group table with which this data is associated, if this table is part of a table group.

In this example, three data tables have been generated: PatientRegistration, LabResult and LabOrder.

Finally, because your VMD file contains one table group named ResultGroup, your database schema contains one group table, also named ResultGroup. This group table contains the following fields:

• MESSAGE_ID, which is a unique identifier representing the message that will be generated from this data;
• PARENT_ID, which contains the identifier of the row of the parent group table with which this group is associated, if this table group is a subgroup of another table group;
• GROUP_ID, which uniquely identifies one row (group of data) in the group table.

In the following section, you will see how all these tables interact with one another.