Supported Data Types

CareSuite currently only supports five primary data types. Reference this article when building/ troubleshooting your CareSuite survey builds.

This document lists which survey plugin data types are supported in Caresuite. This lists holds true regardless of the tool used to build your survey(s).

Supported Data Types

✅ string

• Status: Fully Supported

• Implementation: Mapped to text type in Caresuite

• Usage: Used for text input fields, names, descriptions, etc.

• Example: <bind type="string" nodeset="/form/field_name"/>

✅ int (Integer)

• Status: Supported

• Implementation: Mapped to number type in Caresuite

• Usage: Used for numeric integer values

• Example: <bind type="int" nodeset="/form/caller_age"/>

✅ date

• Status: Fully Supported

• Implementation: Explicitly handled with date formatting

• Usage: Date fields with formatting support

• Example: <bind type="date" nodeset="/form/BTS_Date"/>

• Note:

  • Special handling in survey.ts with SURVEY_DATE_FORMAT

  • Uses DATE_OPERATORS for querying (equals, after, before, between)

  • Date range queries supported

  • Multiple date format patterns supported in imports

✅ select1 (Single Select)

• Status: Fully Supported

• Implementation: Mapped to select in query builder

• Usage: Single-choice dropdown/radio button fields

• Note:

  • Options array with label/value pairs

✅ select (Multi-Select)

• Status: Fully Supported

• Implementation: Mapped to multiselect in query builder

• Usage: Multiple-choice checkbox/list fields

• Note:

  • Values stored as space-separated string

---

Not Supported / Unclear Support

❓ boolean

• Status: Not Explicitly Supported

• Notes:

  • No explicit boolean type handling found

  • Typically implemented as select1 with "yes"/"no" options

• Workaround: Use select1 type with boolean options

❓ decimal

• Status: Not Explicitly Supported

• Notes:

  • No explicit decimal type found

  • May be handled as number type (which could accept decimals)

  • No specific decimal precision handling found

• Workaround: Use number type

❌ time

• Status: Not Supported

• Notes:

  • No time-only field handling found in codebase

  • Only date type is supported, not time or dateTime

❌ dateTime

• Status: Not Supported

• Notes:

  • Only date type is supported

  • No dateTime parsing or formatting found

  • Timezone handling not implemented for dateTime

• Workaround: Use date type and store time separately, or use string type

❌ geopoint

• Status: Not Supported

• Notes: No geographic point handling found

• Evidence: No geopoint parsing, storage, or display logic

❌ geotrace

• Status: Not Supported

• Notes: No geographic trace/path handling found

❌ geoshape

• Status: Not Supported

• Notes: No geographic shape/polygon handling found

❌ binary

• Status: Not Supported

• Notes:

  • No file upload handling in survey forms

  • No binary data storage for survey responses

  • File uploads exist in other parts of system but not in surveys

❌ barcode

• Status: Not Supported

• Notes: No barcode scanning or handling found

❌ intent

• Status: Not Supported

• Notes: No external application intent handling found

---

Summary Table

Data Type	Supported	Implementation	Notes
string	✅ Yes	text type	Fully supported
int	✅ Yes	number type	Supported
boolean	❓ Partial	Use select1	Not explicit, use workaround
decimal	❓ Partial	Use number	May work but not explicit
date	✅ Yes	date type	Fully supported with formatting
time	❌ No	-	Not supported
dateTime	❌ No	-	Not supported
geopoint	❌ No	-	Not supported
geotrace	❌ No	-	Not supported
geoshape	❌ No	-	Not supported
binary	❌ No	-	Not supported
barcode	❌ No	-	Not supported
intent	❌ No	-	Not supported

---

Recommendations

For New Survey Forms

1. Use supported types: string, int, date, select1, select

2. For boolean values: Use select1 with "yes"/"no" or "true"/"false" options

3. For decimal values: Test if number type accepts decimals, or use string with validation

4. For date/time: Use date for dates only; store time separately if needed

5. For file uploads: Not supported in surveys; use separate file upload mechanisms

6. For geographic data: Store as string or separate latitude/longitude number fields

---

Future Considerations

If support for additional types is needed, please contact your Caresuite POC or send us an email at [email protected]