What is the current anticipated projected release dates
for the different DECL languages?
Developer-Suite-Windows:
WPF Released to Production on August 7th
WinUI Scheduled Beta 1 release week of September 21st
Developer-Suite-Android : Scheduled Beta 4 release week of September 21st
Developer-Suite-Javascript-Remote : Production released August 28th
Developer-Suite-Javascript : Scheduled Beta 2 release week of September 7th
Developer-Suite-iPadOS:
Beta 1 released August 28th
Scheduled Beta 2 release week of September 21st
MedWand also documents a "VirtualCare API" (REST/JSON) built around a
device → mobile client app → MedWand cloud → Enterprise Software flow. Is that the path you'd actually recommend for
embedding vitals capture into a browser-based video conferencing product, or is the DECL JS SDK (direct browser-to-device via Web Serial)
the intended path for this use case?
The MedWand "VirtualCare API" is designed for customers who do not already have a software and/or conference solution they want to continue using. If you have a software/conference solution that you intend to continue using, then using our DECL libraries is the correct solution for you.
The DECL SDK uses the Web Serial API, which only works in Chrome/Edge, requires HTTPS, and requires a user gesture plus per-origin permission grant to select the device. For a video conferencing web app to use this, does the permission need to be granted from within that app's own origin? Are there known conflicts if the browser tab or another
application already holds the device's serial port?
We cannot make any guarantees about how a browser implements the Web Serial API, but only that our JS DECL will work with the Web Serial API. As you know, browser vendors make changes without notice at their own discretion and do not follow the same notification process as Operating Systems vendors. It is not advisable to have multiple browsers/tabs attempting to access single connections devices like the serial port, camera, or microphone. The ability for simultaneous connections to a device is Operating System and browser controlled.
Is there a Bluetooth or Web Bluetooth path for any of these sensors, or is Web Serial
(wired) the only supported browser transport in the beta?
No The MedWand device is Serial over USB-C only. Third-party Bluetooth devices that are integrated into our own MedWand VirtualCare applications are not supported in our DECL libraries.
The sample code embeds MW_DECL_LICENSE and MW_DECL_PUBLIC_KEY directly in client-side JavaScript, visible to anyone via browser dev tools. What is exposed if someone copies these values out of a deployed page - can they be reused elsewhere, rate-limited, or
tied to a specific origin/domain?
This is only sample code for providing DECL usage guidance. We assume that a customer using our DECL has their own procedures for handling secrets. We provide no guidance regarding security implementations.
The core library file (MWSDK.Javascript.js) ships fully minified with no source map. Is a non-minified or source-mapped version available under NDA for
a security review, given this will run in a context handling patient vitals
data?
Once our Beta program is complete, there will be source-mappings. Currently our Beta program is only for those willing to work with our sample application for guidance. When we do release to production, we will be releasing the source map.
Does the DECL SDK transmit any data off the local device at all, or is
all cloud/API communication handled separately by the integrating application?
The only API call our SDK will make is during a firmware update check/install that you will control. This is a requirement of our FDA clearance. The firmware update check portion of our DECL products will become available in the final beta releases.
What Compliance documentation exists for this SDK and any
associated cloud services it may depend on?
Our SDK does not rely on any third-party cloud services. The integrating platform is responsible for their own infrastructure compliance.