Frequently Asked Questions (FAQ) for Developers

TIP

The following list contains frequently asked questions from our client developers. If you cannot find an answer below, please feel free to contact PanopticAI customer service to schedule a meeting or consultation, as per your contract terms.

1. What are the minimum requirements for implementing the Vitals™ SDK?

Please refer to Introduction page for detailed information.

2. Which platforms does the Vitals™ SDK support?

The SDK supports iOS, Android, Windows, and MacOS.

3. How long does it take to integrate the Vitals™ SDK into my project?

Integration time varies depending on the complexity of your project. Most integrations take approximately 1-2 days. For more complex solutions, please contact us for a personalized estimate.

4. Does Vitals™ SDK retain patient data?

Data security is paramount at PanopticAI. Vitals™ is designed with robust security and data protection measures in place. We do not store any personally identifiable information within our system. All data is encrypted and anonymized both during transmission and while at rest in storage. When integrated with Electronic Patient Records (EPR), a unique "test request ID" token is used to securely identify patient readings without retaining any personal data. Furthermore, all data is promptly deleted from our servers immediately after processing and transmission to Amazon Web Service (AWS).

5. Which SDK(s) are most widely used by PanopticAI's customers?

Among PanopticAI's customers, the JavaScript SDK is the most widely used, followed by the React SDK and the Flutter SDK.

6. When does an API call get counted? Will it count when the signal quality is lower than 60?

API calls will be counted if the Vitals™ Cloud Service returns a successful response to the Vitals™ SDK, irrespective of signal quality.

7. Is there a retry mechanism for HTTPS requests to the Vitals™ Cloud Service? Will the retry requests be counted as another API call once again?

In Web SDKs, including JavaScript, React, and Vue SDKs, no retry mechanism is included. However, in Mobile SDKs, that is the React Native, Flutter, and Android SDKs, they do not have a built-in retry mechanism for iOS, whereas on Android platform, they will retry once. An API call will be counted only upon successfully receiving a response, ensuring that double-counting does not occur.

8. Are all the SDKs actively maintained? How frequently are updates released for the SDKs?

All the SDKs listed in the Introduction page are actively maintained. The update frequency is driven by reported bugs, operating system upgrades, and the introduction of new features.

9. Is a specific environment required to reliably conduct Vitals™ Health Assessment using the Vitals™ SDK?

As long as the environment aligns with our Best Practices for VHA and user can pass the Conditions Check with good Signal Quality, a reliable Vitals™ Health Assessment can be conducted with Vitals™ SDK. Please refer to our Software Development Guide for the recommended Vitals™ Health Assessment workflow for further details.

10. Can I personalize the vital signs returned from the Vitals™ Cloud Service?

Results from the Vitals™ Cloud Service cannot be personalized, they are returned in full to the Vitals™ SDK based on your subscription plan. However, you have the flexibility to selectively display or hide specific parts of these vital signs returned.

11. Can I customize the user interface?

Yes, Vitals™ SDK enables flexible user interface design and styling. While you have complete control over its implementation, we strongly recommend following our Software Development Guide for the suggested components to incorporate into the user interface. This approach guarantees adherence to best practices, ensures accurate scan results, and enhances the overall user experience.

12. Is the conditions check tailored for all SDKs, devices, cameras, and operating systems?

The conditions check relies on general formulas applicable to all SDKs, devices, cameras, and operating systems. While not tailored for every scenario, a Signal Quality value is provided to ensure collected signals meet the quality standards necessary for accurate vital sign measurements.

13. Does the Vitals™ SDK continuously monitor network conditions?

No, the Vitals™ SDK does not monitor network conditions continuously. In the Analyzing Data stage, if there is no network connection, the HTTPS request will fail, triggering an error. Please refer to Scan Vital Signs for guidance on error handling.

14. Do Vitals™ SDK come with an embedded camera component? Can we use our own camera and directly transmit data to the Vitals™ Cloud Service?

Vitals™ SDK includes an integrated camera component named Vital Sign Camera. For details, please consult the Vital Sign Camera page. We do not currently support direct data transmission to the Vitals™ Cloud Service, please utilize the Vital Sign Camera component instead.

15. Does Vitals™ SDK offer continuous monitoring capabilities? Can facial scanning be carried out for longer than 30 seconds?

Vitals™ SDK does not offer continuous monitoring and the facial scanning is restricted to 30 seconds. Nevertheless, we are actively engaged in related research.

16. How can I draw a static hint area to guide users on positioning their face correctly within the camera frame to meet the "centered" and "distance" conditions?

Please refer to Scan Conditions page for the detailed descriptions of the "centered" and "distance" conditions for your reference to draw the static hint area.