In BioT, Templates are core building blocks used to define the data model that supports your medical IoT solution. A template provides a structured schema for entities such as Devices, Patients, Caregivers, Generic Entities (custom types defined by your needs), Etc.
Templates enable centralized control over your system's structure, separating data modeling from configuration logic. This allows organizations to evolve their system architecture in a scalable, manageable, and compliant way.

What Can Be Defined in a Template

Each template allows you to define the structure and metadata of the entity it represents, including:

• Fields: Add any number of fields to describe your entity.
• Field Type: Specify the data type (e.g., string, number, date, etc).
• Mandatory Fields: Indicate whether a field is required.
• PHI Tagging: Mark fields that contain Protected Health Information (PHI) to comply with privacy regulations.
• JSON Field Name: Define the field's identifier as it appears in BioT APIs.
• Analytics DB Field Name: Specify the corresponding field name in the Analytics Database (ADB), if enabled.

Templates are primarily created and managed in the BioT Console. However, for teams with CI/CD pipelines or DevOps processes, templates can also be managed programmatically using the BioT APIs.