Click to Enlarge

The UltraPort MS SQL Schema Engine Main Window


For more information on possible issues you may encounter when using MySQL see Troubleshooting MySQL.


To access the MySQL Database Schemas section click the MySQL Schemas button on the toolbar in the Main Window to open the MySQL Schemas Section. From there you click the button that says Click Here to Create a New HL7 Database Schema (if creating a new schema) OR click the small Edit button next to an existing schema to modify an existing MySQL schema. This will open up the MySQL Schema Properties window (see below).


UltraPort MySQL database schema profiles are basically a set of information and instructions which tell the schema engine processors:


How to connect to the MySQL Server Database which contains (or will contain) the schema tables (see creating schema tables)

Whether the schema tables have been created or not (see verifying schema tables)

Which HL7 vendor/version definition to use7 when creating and verifying the database schema tables

Whether to allow the schema engine to perform database maintenance or not

Schema Warning levels


Click to Enlarge

MySQL Database Schema Properties



Walk-through: Creating a MySQL database schema profile


Prefix. This is a 2 to 4 character value which you choose. It must begin with a letter (A-Z) and is not case-sensitive. When the program creates the SQL database tables it will preface the name of each one the value you enter here followed by an underscore. Example LAB1_HL7Data or LAB1_SEGMENT_PID_A. This is important because it allows you to either a) create multiple schemas within the same SQL database and/or b) create the schema tables right within your OWN SQL database without fear of overwriting any of your own database tables. **IMPORTANT: With MySQL you should ALWAYS insure that there are NO other database objects in your MySQL database with names that begin with the Prefix. This means that if you choose AAA as your Prefix you must not have any database tables, views, triggers, etc with names that begin with AAA.

Profile Name. Since you can create many different schema profiles, each one must have a different name. It's a freeform value and allows you to easily identify your schema in the list of schemas displayed in the main window.

HL7 Version. This one is important and should be carefully considered. Click the button next to the field to select the HL7 Vendor Definition to use as the basis for the schema. We recommend strongly that you create your OWN HL7 vendor definitions and select them here. See Before You Begin and HL7 Vendor Definitions for more information.

NEW in version 6.0. You can direct the Schema Engine to create your Schema Tables using the MyISAM storage engine. This can be helpful when troubleshooting problems.


Starting in Schema Engine version 5.1 you select whether to to use "Native" or ODBC connection to your MySQL database.


Choose MySQL Connection Type

Choose MySQL Connection Type


Using the Native MySQL Connection


Using the ODBC MySQL Connection


Once you've completed filling out this page you should verify that you've entered everything correctly by clicking the 'Test the Connection to the Database' button.


When clicked, the system will validate your entries and attempt to connect to MySQL using them. NOTE: If you typed something in wrong you might have to wait for as long as the value you selected for the Database Connection Timeout for the system to respond. If everything is correct then you can save your schema profile, but you're really not done yet. Keep reading for your next steps. Obviously you can't actually DO anything unless you create your schema tables (click here for the how-to). If you're new and are evaluating the UltraPort Schema Engine then you can just jump in and start experimenting with what it's capabilities are, however, before you actually try and implement the Schema Engine you should read the Before You Begin section thoroughly.


Other W7eb Resources: Downloads


Your next steps: Creating Schema Tables or setting up the database maintenance plan and entering your schema warnings settings.