Overview
Two Types of Dataflow
Jump to Section:
Pull From a Specific Form
Dataflow can be created to pull a field from a specific form.
Field to Field Correspondence
Dataflow is a field-to-field correspondence. It is able to carry information from a field in a source document (i.e.. Treatment Plan) over to the same field in a destination document (ie. Progress Note).
Flow Linearly Through a Set of Forms
Dataflow can be set up to flow linearly through a set of forms. For example, a specific field can flow from a DA to a Tx Plan to a Progress Note to a Discharge Summary.
NOTE: In a case like this, if you open the Progress Note without a Treatment Plan on file, data will not flow from the DA to the Progress Note. The documents must be created in the determined order for data to flow effectively.
One Source Document to Several Destination Documents
Dataflow can flow from a field in a source document to the same field in several destination documents.
Several Source Documents to One Destination Document
Dataflow will allow different fields from various source documents to populate into the corresponding fields in a single destination document. For example, a Progress Note can have the Diagnosis field populate from the Diagnosis field in a DA and the Goals field populate from the Goals field in a Treatment Plan.
Exceptions
Typically, dataflow can only flow between like fields (edit fields, checkboxes, drop downs). There are a couple exceptions to this rule:
- You can have a check box selection flow into a text field.
- You can have edit fields in an add table flow into a drop-down.
Add Tables
You can have multiple additions to one field in an add table dataflow into a drop down menu (a list of options). This gives you the ability to choose what option you are documenting on at that point in time. This is common for dataflowing Problems, Objectives and Methods from a Treatment Plan to a Progress Note.
What Dataflow Can't Do
NOTE: If you would like to compile and summarize information from many fields into a single field (for example, compiling and averaging the Session Outcome Ratings over the course of a client's treatment), this may be something you can achieve through a clinical report, either the Raw Data Report (Report 2060) or a custom report. Please create a Customer Support case and include the details of what you are wanting to compile and report on.
Pull From Any Form
Dataflow can be created to pull from any form. In this type of dataflow, the designated field (such as diagnosis) will flow from the most recently created, active form for that client, within that program, regardless of order in which the forms are completed.
For example, if a Treatment Plan is created on April 1st, the Progress Note created on April 2nd will pull the diagnosis info from the Treatment Plan. If a Diagnostic Assessment is then created on April 3rd, the diagnosis would pull from the April 2nd Progress Note.
IMPORTANT: When creating documents with pull from any dataflow, you will want to make sure there is only one document per program per date for the client. If there is more than one document for a client and both documents have the same program and same form date, the system will not know what form to pull information from.
NOTE: There is an exception to the program rule with pull from any. When you add a clinical document within a specific program and there is not a source document within that program with the dataflow section, the system will look to other forms outside of that programs for that dataflow field.
Request Dataflow Setup or Modifications
The fields that flow from one document to the next and the order of the documents depends upon how your forms were created in conversation with your Forms Consultant. If you need to request modification or would like to setup new dataflow, please create a Customer Support case and include the following:
- Which form numbers you are looking at.
- Which fields you want to dataflow.
- In what sequence would you like data to flow (between documents).