The system is built around the concept of templates. Templates are a way for you to design the main entities in the system (devices, organizations, caregivers, users and patients – see below) and build your own functionality of care around them. Templates are a no-code way to teach the system how key entities should look and how they should operate:
Devices - How they operate, how they are provisioned, how they connect to the system and how the system should connect and operate them. Among other things, the user can specify what configuration parameters the device should use, what status messages it can send, what commands can be received and what other system entities they should be mapped to (for example, organizations, caregivers, patients, etc.).
Patients – How a patient needs to be defined in the system, what information should be provided when provisioning a patient, what type of observations (e.g. biomarker measurements) should be observed for them, and what set of capabilities they should be allowed.
Organizations – What data points you want to keep about the organizations you work with, including the identity of your account owner in the Organization.
Organization Users – What are the types of organization users, how a user type should be defined and how they are expected to work with the system. BioT comes preinstalled with several initial Organization User templates: Organization Admin (to be used for users who are allowed to perform anything in the scope of their organization), Organization Operator (a user without administrative permissions), Manufacturer Admin (for use by you, the manufacturer, to control the entire system), Manufacturer Operator, and BioT Support (for use by BioT technical support personnel when called to assist).
Caregivers - What data points you want to keep about caregivers (physicians, nurses, etc.) , including their relationships to other entities, such as patients.
Templates are the way for you to customize the system (without using code) for any use case you want to provide. They allow you to build basic entities (devices, organizations, users, patients, and caregivers) and teach the system how they should behave, to cater for the use case. Once templates are defined, you have defined the work flow of the system for the use case and can start ongoing operations with the system, using the built-in portals. You can further customize the system and build your own portal using the no-code Portal Builder, or integrate BioT to your own UX applications using the BioT SDK.
All of BioT’s templates enable you to add unique capabilities of your own. The template structure is dynamic and not fixed, and allows you to fully adjust the data model so it includes parameters and behaviors you want to add. This is done via simple UI configuration.
The operational portals enable you and your clients, the healthcare organizations, to manage the full set of capabilities you designed around your devices and the rest of the system entities.
There are two types of operational portals in BioT (both are fully customizable through Portal Builder as explained below):
- Manufacturer Portal – This is the portal you use as a manufacturer, to manage your entire fleet of devices and your customer organizations.
- Organization Portal – This is the portal you provide to the customer organizations that are using your devices. This is the portal each organization will use when working with your system. Every organization sees their own unique portal, and each organization user has access to the specific functionality they are allowed to use within their own organization.
The BioT Console is a third portal provided by BioT. It allows you, the device manufacturer, to configure the entire BioT PaaS to your needs, and essentially design the workflows, entities, and the look and feel of the entire system.
The BioT Console is comprised of 2 major functionalities:
The template definition sections – This is where you design the different entities in the system (devices, organizations, users, patients, and caregivers). You can build several templates of the same type of entity. For example, you may have several device templates each corresponding to a different device.
The Portal Builder – Here you design the look, feel and functionality of BioT’s OEM portals that you can provide as OEM to your customers. The Portal Builder enables you to customize the operational portals to your needs.
In the following sections you can find the BioT Console capabilities and the main concepts around which it is built.
Updated over 1 year ago