Modeling Overview
Modeling lets you create your own forms to collect data. You can decide what kind of data you want to collect and how you want to organize it. The data you collect with your forms is stored in the EHR and can be used for different purposes. Modeling gives you more flexibility and control over your data collection.
User-defined data collections instruments (DCI):
- You can use your own forms to collect data for myAvatar. These forms are called user-defined DCIs.
- The data you collect with your forms is stored in the same place as the data from the myAvatar product forms.
- You can use different tools, such as SAP Crystal Reports or any SQL report writer, to see and analyze the data in the database.
- To create a new form, you need to follow four steps: administrative, design, development, and test.
- myAvatar has some forms that you can use or modify for your own needs. They are: Envelope Definition, Table Definition, Form Definition, Form Designer (optional) - You need to use them in this order.
Administrative Guidelines
Robust administrative controls prevent adding useless data tables and duplicated data element dictionaries.
-
Determine the area of data collection required. First, you need to figure out what kind of data you are collecting and where you want to store and access it. For example, if you are collecting data for CWS, you can choose to store it in the CDR. This way, you can also access it from PM using the ODBC connection. These choices will affect how you create your form in the next step. (You will use the Envelope Definition form for this.)
- If the data is used for areas such as billing, or financial eligibility, consider putting it in PM.
- If the data is clinical in nature, or will be used primarily by clinicians, consider putting it in CWS.
- If you are going to write reports against this data and PM tables, consider including it in the CDR.
- Create a naming convention for new SQL schemas. You have the ability to create additional areas of organization to store data. For example, you could create a new schema with your agency's name to contain items that your agency has modeled. SYSTEM is the standard area and holds all core items. You may add to the SYSTEM schema, but you cannot move core forms.
- Determine if a grouping strategy is required to organize new tables in logical groups. Envelopes operate in much the same way as file folders. If you are aware that you are going to be dealing with a lot of varied data, you may want to create a system for organizing your data into groups for ease of use.
- Determine DCI data retrieval requirements. These requirements become the basis for the reports created to support them. Reporting requirements may be helpful in the organizational strategy development.
You can define whether or a not a user/user role can access external permissions (the ODBC connection) via the Allow Product SQL Access field (User Definition/User Role Definition forms, Forms and Tables section). - Design how workflow notification functions, if myAvatar CWS modeling is used with workflow management. This is defined at the table level. For example, are you including workflow? Will it be pending draft/final approval?
Design
Detail DCI data elements in forms and SQL table columns:
- Determine if dictionary columns can alias existing dictionaries, alias data from existing columns, or be assigned a new dictionary.
- Determine the DCI structure.
- Determine the workflow and who enters data; the relationship between data collection forms may require multiple forms (e.g. front desk and clinician).
- Determine if the DCI should be sorted by date or order entry. Table aliasing of treatment history or diagnosis requires date. Also, this controls how the data will be stored in the table. For example, order entry will sort the entries based on the most recent one updated, whereas date will retain the order by the original entry date regardless of when edits are made.
- Determine if the DCI should be episode based (client forms).
- Determine if the form should launch a report from the form. If so, select how the report should be sorted.
- Determine how the DCI should display in Chart, if applicable.
Development
- Create the workflow management notification object types (Avatar CWS only).
- Create the envelope.
- Create tables:
- Create the primary table.
- Add table columns.
- Populate dictionaries associated with the table.
- Repeat the process for secondary and/or multiple iteration tables.
- Create the forms. Include all event logic.
- Create associated reports.
- Assign reports to the form.
- Select report parameters.
Test
- Open the form in the BUILD system code to test:
- Data entry for data elements.
- Data element event logic.
- Dictionaries populate properly.
- Workflow management notifications are sent to To-Do lists when the form is filed.
- Reports retrieve desired form data.
- After testing is completed, move the DCI to the LIVE system code.
- Assign user access to modeled forms in the User Role Definition, and User Definition forms.