| Administrator |
The RippleDown Client where a high level user can manage projects and control user access/permissions for all RippleDown applications and functions. |
| Attribute |
Name representing each element or data item of a patient record.
-
Primary attribute: Sent from the Online Information System.
-
Derived attribute: Created from primary attributes using a formula, list or some custom calculation (e.g. panic/delta attribute).
|
| Audit Trail |
Repository for documentation of all edits to Attributes, Comments and Rules |
| Auditor |
The RippleDown client application where cases flagged for data entry errors are reviewed. |
| Autovalidation |
Release of cases from RippleDown without manual review. The degree and level of autovalidation can be set by rules in the Knowledge Base. |
| Case |
Set of data for a patient that will be interpreted by a Knowledge Base. |
| Cornerstone |
A case against which a rule has been built. These are stored in the project as references to cross check new rules against. |
| Comment |
The output of the project and shown in the Validator screen. |
| Condition |
A logical statement of either ‘true’ or ‘false’ used in creating rules. For example: glucose >=5.5 and can refer to current and/or previous cases. |
| Data Extraction |
A form allowing you to specify what cases to export to an Excel spreadsheet, and what data within the case to export. |
| Episode |
The set of results for a patient at a particular time on a particular day. |
| Expert |
Medical staff member directing the objectives and outcomes of the project. |
| Feature |
Higher level characteristic of a case. |
| Knowledge Base |
This is the project or database containing the rules used for case interpretation for each clinical or operational domain. |
| Knowledge Builder |
Application used to create the rules and maintain the Clinical Knowledge Base. |
| LabQ |
RippleDown’s tool for data mining and export. |
| Objective |
A housekeeping tool for maintaining high quailty records. |
| Project |
A knowledge base specific to a clinical domain. |
| Project Explorer |
Documentation of the project showing the history of the Knowledge Base. |
| Queues |
A list of case spending review by a Validator or Auditor user. There are three types of queue:
-
Default queue: Each project has a default queue which holds cases that need to be reviewed prior to release.
-
Special purpose queue: These are queues defined in the Knowledge Builder to hold particular types of cases, rather than sending these cases to the default queue.
-
Copy queue: These are special purpose queues set up for the Validator only. A copy of the case is put on this queue, rather than the original. Cases approved on a copy queue are deleted and not sent to the Online Information System.
|
| Report |
The output of a Knowledge Base, i.e. the set of comments given for a case. |
| Rule |
A set of conditions to create an action, for example to ‘add’, ‘delete’ or ‘replace’ comments. |
| Rule Wizard |
The set of steps to guiding the rule building process in the Knowledge Builder. |
| Validator |
The RippleDown client application used to review interpretations prior to release to the Online Information System |