Importing data into OpenFIT

Created by Enda Madden, Modified on Thu, 31 Oct at 10:51 AM by Enda Madden

We have extensive experience of importing information into OpenFIT, from heavy duty ETL type processes to the self-service outlined below. OpenFIT administrators can import Case, Client, Appointment, and Survey data into OpenFIT using a flat file format. Below example shows a data dictionary for importing Case, Client, Appointment, and ORS/SRS survey data.



Column NameDescription
Service_Location[Required] Name of the provider location
Provider_FirstName[Required] First Name of the user (clinician) in your system
Provider_LastName[Required] Last Name of the user (clinician) in your system
Provider_Email[Required] Email address (unique and will be the username to login to OpenFIT) per clinician. If the user does not exist in OpenFIT, the process will create one with a default role (Clinician) and password.
Case_ID[Required] An ID used to group sessions for a client(s)
Case_Date[Required, Format (yyyy-MM-dd)] Start Date of this case
Session_ID[Required] Sequential integer ID within the case (1,2,3, etc...) where 1 is the first session (sorted by date ascending) and so on.
Session_Date[Required, Format (yyyy-MM-dd)] The session date (values sorted and linked to Session_ID as described above)
Client_Gender[Required] One of (Male, Female, Transfeminine, Transmasculine, GenderExpansiveNonBinary, TwoSpirit, Questioning, DeclinedToState, AdditionalCategory)
ORS_Skip[Required] One of (Y, N) where Y skips the scores
Total_ORS[Optional, Decimal] Total ORS Score (if individual scores not provided, total will be divided by 4)
Notes[Optional] Text will be saved once the system creates a Case (Episode)

Custom Fields

For custom fields you would add a column for each custom field. Use the custom field name as the column heading. The values supplied should be the values seen in the OpenFIT UI, rather than GUIDs or IDs of the field values. 


For example you have a custom field called Treatment Settings associated with the Episode entity in OpenFIT that had the following values:

  • Outpatient
  • Inpatient
  • Residential
  • Other


The import file would look like this


If you need help with this such as obtaining the custom field name to use then email [email protected]



Large Imports

If this is an initial loading or ETL type migration from another Outcome Measurement system get in touch with us during the planning phase. We may work with you to test the data import within a Sandbox environment before going ahead with a full lead into Production.


The import template file is attached below.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article