Page History
...
Aggregation options for a non-numeric variable such as Diagnosis are Existence (Yes/No), Count: Number of Concepts, Count: Number of Dates, Count Number of Encounters, Count Number of Facts, Count Number of Providers, Date (First), Date (Most Recent), Most Frequent Concept (Codes)
Aggregation options for concepts that support numeric values such as labs include Average, Min, Max, etc. in addition to all the functions available to normal variables
Aggregation Options | Explanation |
Existence (Yes/No) | Whether the patient has an observation of this concept. This is the default option. |
Count: Number of Concepts | Total number of concepts |
Count: Number of Dates | Total number of dates for the participant |
Count: Number of Encounters | Total number of encounters for the participant |
Count: Number of Facts | Total number of observations |
Count: Number of Providers | Total number of providers for the participant |
Date (First) | Date of earliest observation |
Date (Most Recent) | Date of the most recent observation |
Count | Total number of observations |
All Concepts (Names/Text) | All concept names are listed |
Most Frequent Concept (Names/Text) | Most frequent concept name |
All Concepts (Codes) | All concept codes are listed |
Most Frequent Concept (Codes) | Most frequent concept code |
Minimum Value | Minimum value of all numeric values observations |
Maximum Value | Maximum value of all numeric values observations |
Median Value | Median value of all numeric values observations |
Average Value | Average value of all numeric values observations |
Mode (Most Frequent Value) | Most frequent value for numeric, enum, blob observations |
List of All Values | List of all values for numeric, enum, blob observations |
Preview and Save Table
Table Design can be previewed to get a preview of the data export file that will be generated.
...
- User logs into webclient and creates and runs a query.
- In the Run Query dialog box, select one or more User created Data table definition Request checkboxes and click run query
- Emails are automatically sent - one to the requester's e-mail, to inform them the request has been made; and one to the specified manager user to inform them to run the user's export request. The query name (in previous queries) is tagged with the query master id, so it can be identified by the manager.
User created Data Export - Manage Data Export
...
Requests (Manager process)
User created Data Export - Data Request Manager (Manager process)
...
Generate data file
The manager logs into the webclient and finds the query from their e-mail by locating the query master id, which is now part of the title of the previous query.
The manager user then re-runs the previous query. In the Run Query dialog, the manager selects the requested export option in the Data export breakdown list.
Info It is very important to put the original query master id (or some other identifier that links the export to the request) into the query name. The export letter will contain the query name, and this is the only way to trace the export back to the original request. (Currently there is no way to tie the export directory to the data requester query_master_id.) If the data manager runs the query as a query-in-query, the query name will automatically be populated with this identifier.
The data export runs in the background and the file is generated in a specified folder
- An e-mail is sent to the manager that can be forwarded to the requesting user, to inform them that their export is available and to provide retrieval info.
...
