Medical Data Acquisition - Product Comparison - MediCollector

Product Comparison

MediCollector BEDSIDE

$1,600

MediCollector SERVICE

$2,000

MediCollector CLI

$400

Description	A desktop application running on a Windows computer. Connects directly to (only) 1 device using cables. Records and/or streams data.	Runs in the background as a Windows Service. Connects directly to (only) 1 device using cables. Records and/or streams data. Intended for continuous long-term operation or embedding into 3rd Party systems.	Runs from command line on Windows computers. Connects directly to (only) 1 medical device using cables. No user interface. Returns the current values of all numeric signals to a text file. Is intended for embedding into 3rd party applications that want to poll data.
Benefits	Portable Low-cost Easy to install. No training or professional services required. Can begin acquiring data quickly Does not touch LAN network De-identified data collection	Can run invisibly in background Continuously record/stream data Does not touch LAN network De-identified data collection	Can run invisibly in background Very easy to deploy and embed into 3rd party systems Able to quickly poll for latest values Does not touch LAN network De-identified data collection Easy to update/maintain
Use Cases	Researchers who want to record vital signs for a clinical study Medical device companies who want to validation test their device AI/Analytics companies who want to gather data for building/testing algorithms	Medical device manufacturers that want to retrieve waveforms into their own device/system Large scale research group who wants to continuously record from a large number of beds Hospital who wants to continuously stream vital signs into an EMR/HIS system using HL7	Integator who wants to retrieve vital signs into an EMR/HIS system at click of a mouse CDS developer who wants to occasionally poll vital signs to run an algorithm
Licensing	1 license required per device driver per computer	1 license required per device driver per computer	1 license required per device driver per computer
Connections	Connects to (only) 1 medical device.	Connects to (only) 1 medical device.	Connects to (only) 1 medical device.
Automation	Auto-launch capability can be enabled using a configuration file. Because it runs as a Windows application (with a GUI), a user must be logged in to Windows to execute.	Auto-launches when the computer starts up. No login necessary.	Runs on-demand. Executes when the command line is executed, and then stops. Useful for polling of values.
Signals	Waveforms and numerics. (Except GE Solar/Dash devices which can only access numerics)	Waveforms and numerics. (Except GE Solar/Dash devices which can only access numerics)	Numerics only. No waveforms.
Auto-launch	Auto-launch can be enabled using a configuration file [ More Details about Interface / API ]	Because it runs as a Windows Service, the recording/streaming will launch when computer powers up (no login necessary)	No. Must be executed on-demand (e.g. polling).
User interface	Rich user interface for management, viewing data, annotating, exporting, etc.	The service itself has no user interface. But it comes with a separate Service Manager application with a rich GUI for management, viewing data, etc.	No graphical user interface. Command line only.
Interface / API	Can be auto-launched Streams data out via TCP/HL7 [ More Details about Interface / API ]	Auto-launches Runs invisibly and automatically for embedding into 3rd party systems Streams data out via TCP/HL7 [ More Details about Interface / API ]	Runs invisibly Command line can be called from any external application Data returned to a CSV text file [ More Details about Interface / API ]