Does your pump support #openaps?
We'd like the serial protocol to the Carelink USB stick, aka MMT-7305NA.
Decocare is an open source driver for a commercially available device, the
MMT-7305NA. The user’s guide:
http://www.medtronicdiabetes.com/sites/default/files/library/support/carelink_usb_user_guide.pdf
indicates intended use is:
Indications for use The Medtronic CareLink™ USB is indicated for use by patients at home and clinicians in a medical office setting to facilitate communication between Medtronic diabetes therapy management devices that use Paradigm-compatible RF telemetry (MWT1)
-
and a personal computer that uses data management application software.
-
We'd like a document that explains how to use the Contour NextLink as an electronic data interface to the pump.
-
We'd like documentation on various commands: set temp basal, set basal, bolus, retrieve history, check settings, set settings.
- We'd like a document that explains how to use the Contour NextLink as an electronic data interface to the pump.
- We'd like a document explaining how the RF communications with the pump work.[
- We'd like documentation on various commands: set temp basal, set basal, bolus, retrieve history, check settings, set settings.
Hello, my name is $NAME.
I'm currently a customer, and wanted to check on a few things. I'm considering buying this pump, and wanted to check on a few things.
The need and desire to connect medical devices to each other as well as other products, technologies, and systems is growing in the healthcare community. This interconnectivity of various products or systems that includes $MYPUMP.
The $USERMANUAL user manual for $MYPUMP has been reviewed carefully, but it doesn't contain some of information I need to use the device. Can we receive a copy of the documentation missing from published manuals, which would include:
- method of communicating data from device
- often known as the "communication protocol"
- method to test existing features, bolus, basal, verifying that recorded settings are same as input
From http://www.fda.gov/ucm/groups/fdagov-public/@fdagov-meddev-gen/documents/document/ucm482649.pdf
-
Whether the connection is meant to control the operations of another device.
-
The purpose of the interface, including any devices, device types, or software (including the version of the software) with which the device is meant to connect.
-
Whether the data is meant for a specific purpose or user, or simply for anyone to access.
-
Whether the connection is meant to control the operations of another device.
-
Specifications for each interface, as well as the necessary performance and functional requirements from the device related to the sending or receiving of data/control.
-
Summary of the testing performed on the interfaces to verify interoperability claims and any activities required by the user to verify safe operation. “In the case where testing was performed to an interface specification and verified with a representative device, please specify the representative device used,” FDA says.
-
Reference relevant standards used.
-
A description of any fault tolerance behavior, boundary condition testing, or fail safe for critical functions (e.g., delivering energy) that will allow the user to understand how to use the interface correctly.
-
Specify any known limitations (what the user should not do), contraindications, precautions and warnings.
-
Recommended connections or architectures.
-
Recommended settings, or configurations for the electronic data interface.
-
Instructions for IT personnel on how to connect or install and disconnect or uninstall the device.