Yes. Our Windows Mobile platform sports a SIP interface, but up until this point we have not had much demand for a full VoIP client. This same SIP interface is ready for streaming H.264 video negotiation should a customer wish to explore this.
Yes, but that probably isn’t the best place to implement. The heartbeat is best used to move pointers such that if one was making a video stream available as a resource/sensor, other subscriber endpoints could know that it was available via the heartbeat. An endpoint that wished to consumer the stream would do so via the above referenced SIP stack. Video will likely be implemented as a BTAC plugin and then expose the service to others via the heartbeat.
Possibly. BTAC is not a Patient Record system, does not manipulate data, and is not a medical data management tool. We merely “collect and push” data. However, there is some gray area around our plugin interface which is requiring that we look into this question. Devices, such as PulseOx, heartrate monitors and other bio-telemetry sensors are examples of products that do need this FDA approval.
BTAC does have some ability to provide “network awareness” inside of buildings, tunnels, and hulls of ships. The BTAC software runs on Commercial Off The Shelf smartphones from any carrier. If the smartphone sports WIFI capability and WIFI is turned on, the BTAC software will also report proximity to wireless access points (WAP). The caveat being one would need to have some level of signal intelligence as to where a specific WAP was inside of a structure, or, teams can carry in small puck-sized WIFI beacons that broadcast a signal that is tied to a CONOP and designated placement location.
BTAC is a software solution that can ride on any mobile device that supports Windows Mobile 5/6, Windows XP/Vista/7 laptop, or Android 2.2 or above. If the hardware can provide alternative exfil methods and can assign an IP address, BTAC will work provided the device is using one of the operating systems described above.