This article covers the following datasets:
Note: When pulling a report on cases in Casebook, we have two datasets. The Case-Involvement Dataset is built on a one-to-many relationship database. Using the Case-Involvements Dataset will give you all possible information on the case. The Case Dataset is built on a one-to-one database. Using the Cases Dataset will show you a limited amount of information on the case but is helpful for counting. In the Case Dataset, one row will equal one case.
Note: If you wish to join Service Notes or Service Notes Recipients with Services or Service Enrollments, you can match the datasets on service_id = service_offering_id.
The Intake data table contains information about all Intake Reports in Casebook.
The notes data table contains information about all of your notes in Casebook.
The case_involvements data table contains information about all of your cases and all case involvements. Since one case can have many clients and involvements, one row does not represent one case.
Note: When reporting, please use count distinct on case_id to ensure you are not over-counting the cases.
The People table contains information about all of the person records in your Casebook system. Each record represents one person. The person_id can be combined with other datasets for powerful reporting on your clients.
The service_enrollments data table contains information about all of your services in which clients are enrolled.
Note: Data from service enrollments of type cb Track cannot be combined with cb Engage data. Only service enrollments of type "Internal staff provider" and "External provider/Referred out" will have the matching "case_id".
The providers table contains information about your providers located in cb Track.
Note: Each record does not equal one provider due to one provider having multiple assignees. Use “provider_id” for accurate reporting.
The workflows table contains data for all of your workflows and associated steps.
Note: To tally total workflows, make sure to count distinct "workflow_id". To tally workflow steps, count distinct "workflow_step_id".
The services table contains data on all of your provider services associated with cb Track.
Note: When using service_id and provider_id as a value make sure that the aggregation is set to Count of Distinct Rows for accurate data on each of the topics. The services table only includes data from cb Track services.
Provider Portal User
The provider portal user table contains data on all of your provider portal users associated with a provider in cb Track.
Application Portal User
The application portal user table contains data on all of your application portal users associated with an application in cb Access.
The cases table contains one-to-one relational data on all of your cases in cb Engage.
The people incomes table contains information on incomes from the Person Profile.
Providers Application Portal
Contains information on all provider applications that are submitted through the application portal.
Providers Application Portal Demographics
Contains information on the demographics of applicants who submit applications through the application portal.
People Medical Allergies
Contains information on the medical allergies logged on a person profile.
People Medical Conditions
Contains information on the medical conditions logged on a person profile.
People Medical Insurance
Contains information on the medical insurance logged on a person profile.
People Medical Medications
Contains information on the medical medications logged on a person profile.
People Medical Providers
Contains information on the medical providers logged on a person profile.
Contains information on the service notes logged for a service enrollment.
Note: One row will equal one service note. This dataset can be used to count notes.
Service Notes Recipients
Contains information on the service notes recipients logged for a service enrollment.
Note: One row will equal one service note per person.
Contains information on the schools logged on the Person Profile.
Contains information on all tasks in Casebook.
Contains information on all people relationships in Casebook.
Note: When pulling a report on relationships, you will see two rows per relationship. For example, Row 1 - Jane Doe; Wife, Row 2 - John Doe; Husband. This dataset can be joined to the People Dataset using person_id.