Skip to main content

Create a new Table Definition

myAvatar Modeling Forms step 7 of 22
  1. Last updated
  2. Save as PDF

Use the Table Definition form to create tables to store data collected in modeled forms. 

Prerequisite:

  • An envelope must have been created to store the table.
  1. Go to RADplus Utilities > Modeling > Table Definition.
  2. Select the table definition form for the desired parent application. (A version of this form exists for PM, CFMS, CWS, and MSO.)
  3. In the Select myAvatar [parent application] Table window, search for the table name and double-click to open it for editing.
    Note: If your desired table does not exist, the Results read "No matches found, please refine search." You can then select New myAvatar [parent application] Table to create a new table with your search terms as the table name (both SQL and parent system).
  4. Select the envelope from the Table Definition Envelope Selection window, and click OK.
    Note: The Envelope field displays which envelope stores the table. Envelope assignment cannot be changed after the table is filed.
  5. The Table Entity Database field displays the envelope's entity database.
    Note: All tables in the envelope must be connected to the same entity database.
  6. In the Table Name field, enter a title for this SQL table.
  7. In the Table Description field, enter an identifying title for the table.
  8. Make a selection in the Defer Table Compilation to Form Definition field.
    Note:  If Yes is selected, the SQL projection of this table will only be updated when it is filed within a form filed via Form Definition.
  9. In the Is This Table Date or Order of Entry Sorted field, choose how to sort the data:
    Note: The table sort cannot be changed once the table is used in a form.
    • Select Date to create a table that is sorted by the date. This creates a table that groups the data entry with the date entered in the date column each time the form associated with this table is used. This is the required setting if aliasing a date order table, like treatment history or diagnosis.
    • Select Order of Entry to sort data by the order the date is entered in the table. This sorts the entries based on the most recent one updated, whereas date retains the order by the original entry date regardless of when edits are made.
  10. In the Service Documentation Table field, select whether or not to associate data filed in the modeled form to a service or appointment in myAvatar CWS.
    Note: This field is only enabled for CWS Primary/Secondary tables that are episodic and whose envelope's entity database is Client.
  11. In the Column Name of Sort Date field, enter the column name to use with the sort date.
  12. In the Column Description of Sort Date field, enter the column description.
  13. In the Column Label of Sort Date field, enter the column label.
  14. In the Display Future Date Warning field, select Yes to display a message when a future date is entered (Sort Date field).
  15. The Type of Table and Is Table Episode Based fields cannot be changed once a table has been used in a form. 
  16. Choose the Type of Table.
    • Primary/Secondary creates a standard table.
    • Multiple Iterations creates a multiple iteration table.
  17. In the Is Table Episode Based field, select Yes to create a client entity table that requires selecting an episode when the form is opened.
  18. In the Does this table require an associated table for the storage of binary information field, select Yes to create a binary storage table to store pictures, and authentication signatures.
  19. In the Binary Storage Table Name field, enter the binary storage table name.
  20. In the Create Pre-Filing Report Table field:
    • Select Yes to create a SQL table. The table stores data entered in a form before the form is submitted. The SQL table can be included in reports that are launched by report command button objects.
    • The Pre-Filing Report selection is available in the Object Type field (Form Definition form, Object Definition section).
    • Selecting Yes displays the pre-filling report schema in the Pre-Filling Report Schema/Table field.
  21. In the Electronic Signature Validation Control field, select whether or not the system should produce additional tables in the backend.
    Note: If you select Yes, the data being submitted in the table is passed through a SHA2 hashing algorithm. It is then stored as an encrypted string in the field Data_Hash. These tables are for comparison only, to allow you to see if outside sources have changed data where signatures are concerned.
► Additional Sections