Overview

The seca analytics 125 platform is an advanced software solution designed by seca, a leading provider of medical measuring systems and scales, to enhance the evaluation and management of patient data. This platform integrates seamlessly with seca's range of measurement devices, allowing healthcare professionals to collect, analyze, and interpret vital health statistics with precision. It offers comprehensive tools for the assessment of body composition, nutritional status, and overall health, thereby facilitating informed clinical decisions. Seca analytics 125 supports various functionalities, including trend analysis, graphical data representation, and customizable reporting, ultimately aiming to improve patient outcomes through detailed and accurate health insights.

The seca analytics 125 platform is interfaced with ClinSpark via SparkPlug. The interface is delivered transparently through the ClinSpark core application with all device interactions taking place via a ClinSpark forms. The device follows an Initiate Collection > Collect on Device > Upload Results workflow with a single ClinSpark form facilitating all of the required steps.

Installation

SparkPlug 24.2 (or later) and ClinSpark 24.2 (or later) is required for the seca analytics 125 device integration. All of the required software to interface with the seca mBCA 554 device is included in the SparkPlug installation and no additional installation or software is required.

The device profile must be provisioned into the target ClinSpark environment. Both the seca analytics 125 platform and SparkPlug must be configured correctly (detail below) to enable the two systems to connect and exchange data. Additionally, the asynchronous job to populate received data as study form data must be added to Administration > Support > Async Job Management in the target environment. Lastly, the seca device should be configured to allow manual entry of Waist Circumference due to current limitations of the provided seca API.

Configuration

As noted above, SparkPlug must be fully configured with the required elements to enable interconnectivity via the seca API. Overall SparkPlug administration and configuration is outside of the scope of this document, but those configuration elements specific to the seca analytics 125 platform are detailed below:

API URL

The API URL to a valid seca analytics 125 endpoint must be configured in SparkPlug > Administration > Settings > seca > API URL. This URL is established & provided by seca.

Open

Configuring the seca analytics 125 API URL

Tenant Secrets

For each ClinSpark site that utilizes the seca analytics 125 integration, a valid Tenant ID must be established on the seca analytics 125 platform. A given ClinSpark Site ID can be determined by opening the site details in Administration > Sites and observing the Id displayed at the end of the URL.

Open

Finding a ClinSpark Site ID in ClinSpark

In addition to seca establishing the Tenant, a public and private key pair are generated and provided. Both this seca Tenant name and the public and private key pair must be configured in SparkPlug > Interfaces > seca. When configuring the Tenant in SparkPlug, the tenant name entered must match the Tenant configured in seca.

Additionally, the Org URL for the site as configured in ClinSpark must be established in SparkPlug.

Collection Workflow & Forms

Collection of seca analytics 125 body composition data using the seca mBCA 554 follows a device enrollment / initialization > On-Device Collection > Data Returned to ClinSpark via SparkPlug workflow. Additionally, to facilitate downstream workflows in ClinSpark, returned data is synchronized from Volunteer Monitoring Data to Study Forms via an asynchronous job. The workflow is detailed below:

1. The device is successfully enrolled and data collection is initiated in ClinSpark by invoking the seca analytics 125 platform via a ClinSpark form containing the minimum required parameters (see seca analytics 125 Device Interface Documentation | Form Design) and having the prerequisite subject demographics included as part of the request.

2. The study participant is welcomed on the screen of the scale and steps on to perform the collection.

3. Waist circumference and height (when stadiometer is not connected) values are manually entered on the device during collection.

4. Data is returned to ClinSpark as Volunteer Monitoring Data.

5. Data populated as Volunteer Monitoring Data is asynchronously returned to the study form as Study Form Data.

Device Enrollment / Initialization

Demographics / Study Metadata

Prior to invocation, the seca analytics 125 platform requires a set of input demographics and study metadata be established to support the generation, processing and analysis of seca data as well as customization of the welcome message presented to the study participant. The required demographics that must be established prior to invocation are DOB, Race, Sex, Ethnicity (optional, see seca analytics 125 Device Interface Documentation | Race Mapping below).

Race Mapping

Due to limitations of race / ethnicity functionality within the seca analytics 125 platform, it was necessary to establish a hardcoded race mapping between the ClinSpark ‘Race Name’ and the seca provided ‘Ethnicity’ value. The mapping rules are presented below as a table.

Device Invocation

Device enrollment & initialization is initiated via ClinSpark form by clicking on the seca analytics 125 button on an integration-enabled form. Once the button is clicked, the user is prompted to confirm their intent to begin enrollment / collection.

Device Selection

In the event that there is only a single seca device configured for the current ClinSpark site, the device will be readied for collection and values will be returned to the TENANT_ID, DEVICE_ID, and REQUEST_ID form items. In the event that the seca tenant has more than one device associated, SparkPlug will prompt the user to select the device on which the collection should be performed.

Errors During Enrollment / Initialization

For errors encountered during device enrollment / initialization, see https://foundryhealth.atlassian.net/wiki/spaces/DOCS/pages/edit-v2/4646437132#Errors-%2F-Troubleshooting.

Collection on Device

Once the device has been successfully enrolled / initialized, the device will be readied for collection, and the study participant will be welcomed on the device screen.

After the Study Participant stands on the device and collection begins, manually entry of waist circumference (and optionally height when the stadiometer is not connected) becomes possible.

After device collection and manual entry are completed on the device, the collection is complete and results will be returned to ClinSpark (see seca analytics 125 Device Interface Documentation | Data for details)

Form Design

As detailed in the description of collection workflows, the seca analytics 125 uses a single collection form to facilitate data collection. The form incorporates both clinical and ancillary device parameters that receive result data and enable further workflows.

At a minimum, a seca analytics 125 collection form must include MEASUREMENT_ID and MEASUREMENT_DATETIME. If these parameters are not included on the form, invoking the integration will fail.

Device Profile / Parameters

The seca analytics 125 Device Profile implements both clinical result parameters and supporting parameters that capture device / measurement metadata. As noted in Form Design, the device integration does not allow for any configuration parameters to control device behavior - all device configuration is done directly on the device itself. For all Clinical Parameters, both a Value as well as Unit parameters are provided as the units used by the device are not controlled by the integration (but instead by the device itself).

Clinical Parameters

Other Device Parameters

Data

Volunteer Monitoring Data

Data collected on the device is return to ClinSpark as Volunteer Monitoring Data via SparkPlug. In addition to the parameterized results, raw JSON data is returned to enable seca Widget based reporting.

Study Form Data

After data is received from the seca analytics 125 platform as Volunteer Monitoring Data, an asynchronous job polling the database for new seca result data populates the data to the seca analytics 125 collection form’s Items as Study Form Data.

Reports / Dashboards

• Transfer Data Report

• Site Report

• Bioimpedance Analysis Visualizations Dashboard (seca Widgets)

Errors / Troubleshooting

Demographics Errors

'Device Not Ready' Errors

seca Tenant Configuration Errors

Notes

Known Limitations

• It is currently possible in ClinSpark to start a seca measurement on a form that already has a status of “Complete”, meaning measurement data has been populated via the async job. If a second measurement would be invoked from a “Complete” form, it's possible that the enrollment data (TENANT_ID, DEVICE_ID, & REQUEST_ID) would be inaccurate for the measurement data saved to the form. TENANT_ID would be the same because the data would be collected for the same site. And more than likely DEVICE_ID would match as well if the site only has a single device. But in this scenario, the REQUEST_ID would be wrong as it would reflect an identifier for requesting a measurement that has yet to be acquired.

• Currently, measurements that are “Weight Only” are not able to be sent / transferred through ClinSpark. These weight measurements would need to be manually captured on a scale independent of device invocation and entered onto the form manually.

• The seca mBCA 554 device will timeout if a subject does not step on the platform within 5 minutes of measurement start. We set the threshold to 10 minutes to allow for a 5-minute grace period in the event a subject stands on the platform moments before timeout. Measurement acquisition should not take more than 5 minutes. This threshold is used to prevent processing records that are too old to be considered for data posting.

• If a Volunteers Demographics are updated following a measurement all past measurements will retain the data as calculated prior to the change. As each invocation and measurement is sent to the seca analytics platform ClinSpark sends the volunteer details as a “snapshot in time” so retrospective data will not be updated within past forms collected via ClinSpark.

• In scenarios where a scale is not reserved for a specific person / measurement prior to device invocation it has been noted that Date of Birth may be requested following the collection workflow. Seca calls this the “anonymous workflow” and confirmed that this can be caused by error conditions in pushing Demographics to the device. In these instances, the recommendation is to start the collection workflow again. If the condition is seen in numerous consecutive invocations, please review demographics and contact the help desk.