top of page




Aspect is a data management platform that handles diagnostic data produced by medical devices in the field. Once the data has been delivered to Aspect, it can be analyzed, reported, and securely stored within the Aspect database. In addition, there are several paths for retrieving data and integrating it into external systems for further analysis.

Clinical devices and external data systems that have a data connection to the Internet, directly or through a cellular connection, can exchange information with Aspect through the Aspect API. The API (application programming interface) is a set of tools that describe the protocol and data format used by Aspect to communicate with devices. In addition to the results of diagnostic tests, the Aspect API can communicate operational data about diagnostic devices, custom data defined by the device manufacturer, and proprietary information about device performance.

The Aspect platform provides a web-based interface to make data available to clinical, operational, and health ministry personnel, as well as to device manufacturers and program funding organizations. All access is controlled by a flexible, secure system of permissions to protect sensitive information while enabling sharing of data when needed.

In addition, Aspect provides several options for exporting data and connecting external systems. Data is delivered by a flexible notification and reporting system capable of simply sending text messages or emailing reports on a schedule or when certain events occur. In addition, Aspect can be integrated into an external data system using a secure query system allowing for data to be requested by and delivered to an external system. Aspect supports communications standards including HL7 as well providing a custom protocol optimized for reduced data usage in low-bandwidth settings.



The Aspect API comprises several elements that together enable integration of instruments in the field with cloud-based or locally-installed Aspect servers.

Processes for Connecting Devices to the Aspect System

The API provides tools for device manufacturers to identify newly manufactured devices to Aspect, as well as features for assigning devices to customers and partners within the Aspect system. For example, a manufacturer may, during a manufacturing functional test, connect a new device to Aspect to verify on-board communication hardware. When the device is shipped to a customer, the manufacturer can use Aspect's administration API to assign the device to the customer; when the device is powered-up in the field, assay results will then be delivered to the customer with no further configuration required. The Aspect API also provides features to configure (and reconfigure) as needed in the field.

Interfaces for Data Delivery and Management

The API provides methods for delivering assay results, sample and patient identification, and device-specific custom fields into Aspect. In addition, meta-information such as workflow state is available to view and update, enabling better quality management. Devices can deliver results as soon as they are available, or queue results for delivery according to schedule or network availability. Data can be delivered using industry standard formats (for instance, HL7/FHIR), or using SystemOne's own format, which is optimized for reduced data transmission costs.

Device Configuration Interfaces

The API includes methods for reading configuration information from a connected device, and delivering configuration changes for remote customer support. Aspect can also assist in enabling critical configuration changes and over-the-air firmware updates by handling day-to-day communication with a device, directing it to a separate secure server to manage updates that fall into "high risk" regulatory categories.

Interfaces to External Systems

The API includes methods for delivering data to external systems, including patient record, EQA, and inventory management. Integration can be accomplished by pull or push, depending on the level and type of integration required.

bottom of page