🏢Company

Every agency, or organization that uses the Fieldworker app is captured as a company in the system. This is where the company-specific attributes are captured, and stored, but also where settings and configuration can be used to align the Fieldworker system and processes to a specific company's business practices. The admin users can update company-specific settings.

Company – This is the master table keeping all details about the company. There is always going to be a single record corresponding to every company that signed up with Fieldworker. Some of the information is available to be maintained by the users directly, other information may be managed by FW team. Almost all of this information is visible via the company page, some fields are not editable via the company page.

[com_id] [int] IDENTITY(2000,1) NOT NULL, PK

[com_name] [varchar](150) NOT NULL,

[com_is_active] [bit] NULL,

[subscriptionPlan] [int] NULL, Managed by FW

[payCycle] [varchar](20) NULL, Managed by company

[com_taxid] [varchar](20) NULL, Managed by company

[payerId] [int] NULL, Managed by company

[trialStartDate] [datetime] NULL, Managed by FW

[trialEndDate] [datetime] NULL, Managed by FW

[subscriptionStartDate] [datetime] NULL, Managed by FW

[subscriptionEndDate] [datetime] NULL, Managed by FW

[startoftheWeek] [int] NULL Managed by company

Dropdowns – This table contains all customization details for a company to align FW with the processes at the company. Almost all of the FW functionality uses this table to display options and choices available to an enduser. Most of this information and defaults selections can be updated (and managed) via configuration and settings pages. Some of the changes are not easily changeable without the loss of information and potentially historical details. It is strongly advised to consider the ramifications of the changes before making changes.

[ddID] [int] IDENTITY(1,1) NOT NULL,

[EntityName] [varchar](255) NULL,

[EntityValue] [varchar](255) NULL,

[CompanyID] [int] NULL, FK

[is_Active] [int] NULL

Is_active values

0 - exist in default and being used

1 - exist in default but not used

2- deleted soft

3 - new type being used

4 - new type not being used by the company

0 and 1 cannot be deleted my users since they are in default

Stored proc in the onboarding will insert the dropdowns with 0 status content being populated from defaults table.

GENERIC:

Currency: ["USD","INR"]. npm library

frequency: ["Hourly", "Monthly"] manifest file

empType: ["Admin", "Manager", "Support Coordinator”, Fieldworker”] npm library

customerType: ["Organization", "Individual"] manifest file

states: ["New Jersey", "New York", "Texas" ] npm library

COMPANY SPECIFIC:

EMPLOYEE:

empLevel: ["Support Coordinator", "Admin", "Support Coordinator Supervisor”, “Manager"]

empStatus: ["Full Time", "Contract", "Temp"]

CUSTOMER:

customerStatus: ["Active","Dormant","Prospect"]

TASKS:

taskType: [“Checklist ","Planning”, “Eligibility Determination", "On-boarding", "Unusual Incident", "Home Visit", "Visit", "Phone Call", “Administration”, “IT Support”, “Marketing”, “Internal Meetings”, “SC Management”, “Training”, “SC Supervision”]

CONTACTS:

designation: ["Support Coordinator", "Admin", "Support Coordinator Supervisor”, “Manager"]

contactType: ["Patient", "Family", "Support", "Friend", "Spouse", "Service Provider", “Guardian”]

contactStatus: ["Active", "Dormant", "Prospect"]

LOCATION:

locStatus: ["Active", "Inactive"],

locType: [ "Office", "Home", "Rehab Center", "Service Provider Location"]

Settings – This table contains all information about subscriptions of a company either from a regional coverage perspective (state), from a program perspective, and from a functionality perspective. The data in this

[settings_id] [int] IDENTITY(1,1) NOT NULL,

[company_id] [int] NOT NULL, PK

[feature_id] [int] NOT NULL,

[state_id] [varchar](2) NULL,

[added_by] [int] NULL,

[added_on] [datetime] NULL,

[feature_value] [varchar](50) NULL

The State will be captured as in their common 2 char abbreviations.

The following feature ids will be used to identify various features.

EVV 11

Time Management 12

Document Center 14

Form Builder 15

BI & Reporting 16

Tele Health 17

State 99

Defaults – This table will keep all default values supported by Fieldworker. Default rows inserted in dropdown table at the time new company signup are read from here. All default dropdowns for configuration will be sourced from here. Any new values added during configuration will only be saved in their respective target tables, dropdown, settings etc.

[defaults_id] [int] IDENTITY(1,1) NOT NULL,

[feature_type] [varchar](50) NOT NULL,

[feature_value] [varchar](50) NOT NULL

[feature_id] int NOT NULL,

[state_id] [varchar](2) NULL

[added_by] [int] NULL,

[added_on] [datetime] NULL

Configuration / settings

1. Defaults table entries are managed by FW team. They should be confirmed before/after every major deployment.

2. Every time a new company is onboarded, the values from the Defaults table are used to populate dropdowns table.

3. Most of the data in Dropdowns ia managed by users.

4. Settings table is populated based on the choices made via configuration screens.

5. Data in Payer, ProcedureCode, and billingrates tables are maintained by FW team.

6. Data in Company table is partially populated by system, partially managed by users via company page.

feature_type	feature_value	State
currency	USD	NJ
currency	INR	NJ
empType	Admin	NJ
empType	Manager	NJ
empType	Support Coordinator	NJ
empType	Fieldworker	NJ
customerType	Organization	NJ
customerType	Individual	NJ
states	NJ	NJ
states	AZ	NJ
empLevel	Fieldworker	NJ
empLevel	Admin	NJ
empLevel	Supervisor	NJ
empStatus	Full Time	NJ
empStatus	Contract	NJ
empStatus	Temp	NJ
customerStatus	Active	NJ
customerStatus	Dormant	NJ
customerStatus	Prospect	NJ
customerStatus	Transferred Out	NJ
taskType	Checklist	NJ
taskType	Planning	NJ
taskType	Eligibility Determination	NJ
taskType	On-boarding	NJ
taskType	Unusual Incident	NJ
taskType	Home Visit	NJ
taskType	Visit	NJ
taskType	Phone Call	NJ
taskType	Administration	NJ
taskType	IT Support	NJ
taskType	Marketing	NJ
taskType	Internal Meetings	NJ
taskType	SC Management	NJ
taskType	Training	NJ
taskType	SC Supervision	NJ
designation	Support Coordinator	NJ
designation	Admin	NJ
designation	Supervisor	NJ
designation	Manager	NJ
contactType	Patient	NJ
contactType	Family	NJ
contactType	Support	NJ
contactType	Friend	NJ
contactType	Spouse	NJ
contactType	Service Provider	NJ
contactType	Guardian	NJ
contactStatus	Active	NJ
contactStatus	Dormant	NJ
contactStatus	Prospect	NJ
locStatus	Active	NJ
locStatus	Inactive	NJ
locType	Office	NJ
locType	Home	NJ
locType	Rehab Center	NJ
locType	Service Provider Location	NJ
frequency	Hourly	NJ
frequency	Monthly	NJ
frequency	Bi-monthly	NJ

Salary type Hourly NJ

Salary type Monthy NJ

Payroll Frequency Weekly NJ

Payroll Frequency Bi-Weekly NJ

Payroll Frequency Monthly NJ

Payroll Frequency Semi-Monthly NJ