...
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.
seca analytics 125 is a device integration utilizing SparkPlug 24.2. SparkPlug 24.2 is currently not available for early-phase implementations but is in development to be released to all customers in the near future.
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 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 https://foundryhealth.atlassian.net/wiki/spaces/
...
DOCS/pages/edit-v2/4646437132#Form-Design) and having the prerequisite subject demographics included as part of the request.
The study participant is welcomed on the screen of the scale and steps on to perform the collection.
Waist circumference and height (when stadiometer is not connected) values are manually entered on the device during collection.
Data is returned to ClinSpark as Volunteer Monitoring Data.
Data populated as Volunteer Monitoring Data is asynchronously returned to the study form as Study Form Data.
Device Enrollment / Initialization
...
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 https://foundryhealth.atlassian.net/wiki/spaces/DEVDOCS/pages/edit-v2/4646437132#Race-Mapping below).
| Info |
|---|
This integration supports partial DOB enrollment configurations introduced in ClinSpark 24.1. See https://foundryhealth.atlassian.net/wiki/spaces/DOCS/pages/4335697921/ClinSpark+24.1#Updated-Enrollment-Configurations-for-Subject-DOB for details. |
...
For errors encountered during device enrollment / initialization, see https://foundryhealth.atlassian.net/wiki/spaces/DEVDOCS/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 device collection and manual entry are completed on the device, the collection is complete and results will be returned to ClinSpark (see https://foundryhealth.atlassian.net/wiki/spaces/DEVDOCS/pages/edit-v2/4646437132#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.
...
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 . In these cases, it has been noted that Date of Birth may be requested following the collection workflow. Seca calls this the anonymous workflow “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.