MedWand Development Suite FAQ's

MedWand Development Suite FAQ's

FAQ's
Timeline and roadmap

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 14th

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

Architecture fit

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.



Licensing and security

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.


Support and commercial terms
What level of technical support is available during the BETA period, and what's the SLA once it exits beta?

All support for our DECL products is available in 1 of 2 ways:
1.  Using the GitHub issues and discussions features at https://github.com/MedWand [preferred]
2.  Creating a support ticket at https://support.medwand.com

SLA for production released DECL’s is determined by negotiated agreement.

 What does the MedWand Developer License require commercially (cost, term, exclusivity) to begin integration testing, separate from an eventual purchase of MedWand hardware/production license?

We will provide a developer license at no charge and can be renewed in 90-day increments.
 
Is there a versioning/deprecation policy for the DECL JS SDK once it reaches production- i.e., how much breaking-change notice would an integrating partner get?

We strive to never have breaking changes, but rather only to add functionality with backwards compatibility. If an Operating System or the Web Serial API requires breaking changes, we will make the necessary changes as quickly as possible and make them available through the appropriate distribution channel. As you know, these channels do not replace previous packages but provide the ability to move to a version at your own pace.
·       Windows: nupkg via NuGet.org
·       Android: aar via Maven Central
·       Javascript: npm package via npmjs.com
 


    • Related Articles

    • MedWand Development Suite Center

      Welcome to the MedWand Developer Suite Documentation and Support Site The MedWand Developer Suite is not free; you can access the software libraries and use them in your own applications to accurately collect and consolidate the data from your ...

    • MedWand Developer Services

      MedWand develops and provides various products and cloud-based services which facilitate and support Telemedicine conferencing via its VirtualCare Platform technology and MedWand Device Developer Suite. MedWand also provides professional services ...

    • MedWand VirtualCare API Executive Overview

      MedWand VirtualCare Examination Platform The MedWand VirtualCare Examination Platform is designed to act as a plug-in module to your existing PMS/HIS/EHR software, a.k.a. the Enterprise Software. It is the Enterprise Software's responsibility to ...

    • MedWand Telemedicine API V2.x User Guide

      Welcome Welcome to the MedWand Telemedicine API Version 2.x MedWand offers a set of pre-built API resources you can use to integrate the MedWand VirtualCare platform with your current system. By taking advantage of our pre-built API resources, you ...

    • MedWand KIOSK Guide

      MedWand KIOSK Interface Guide This guide provides a high-level overview of the MedWand KIOSK software and interface, which is used by non API integrated customers for managing MedWand Exams and their accompanying results. For detailed guides by exam ...