After the demo
Evaluate the complete encounter in your own scenario.
Use the same simulated or de-identified encounter, devices, roles, network conditions and record destination for every shortlisted option. Agree the pass criteria before the demonstration, then compare like for like.
Six steps
What a fair evaluation tests.
These steps come from LifeBot’s own evaluation method. They apply equally to any supplier you are comparing.
- 01
Identify the exact system
Record the DREAMS version and build, enabled modules, endpoint arrangements, equipment models and agreed services. Compare the proposed delivered configuration, not a collection of brochure capabilities.
- 02
Walk through patient-side work
Demonstrate the required capture, documentation, review and local-save steps. Record which data is entered manually and which is received through a supported device interface.
- 03
Demonstrate the remote clinical role
Show authorised Command participation and each required shared view or media function. Identify who controls the encounter and who documents the consultation.
- 04
Test loss and recovery
In an agreed, safe scenario, show which local functions remain available, what happens to the remote session, and the documented steps for reconnection and record reconciliation.
- 05
Prove receipt of the record
Trace local saving, submission and received-record availability as separate events. Show Matrix review and, where contracted, delivery to the named receiving system.
- 06
Close equipment and operational gaps
Confirm connectors, power, consumables and compatibility. Name the owners of access administration, training, support, maintenance and acceptance sign-off.
Requirements brief
What to bring.
These inputs define what the proposed configuration needs to demonstrate. Rough answers are fine at the start.
| Topic | Information to provide |
|---|---|
| Mission and locations | Care settings, mobility, geography and operating hours |
| Users and roles | Patient-side staff, remote clinicians, records users and administrators |
| Clinical capability | Monitoring, examination, imaging and treatment equipment |
| Systems and quantities | The required Link, Core, Command and Matrix roles |
| Consultations | Clinical coverage and expected simultaneous use |
| Information | Documentation, hospital APIs, records and retention needs |
| Infrastructure | Network services, hosting, power and physical installation |
| Support | Training, maintenance, spares, consumables and service contacts |
Evidence to retain
Agree it before. Record it during and after.
Agree before the demonstration
- Equipment, software role, source and installed version, and interfaces
- Scenario, authorised participants and required information
- A safe loss-and-recovery scenario and applicable procedures
- Acceptance criteria and responsible functions
- Training, support, maintenance and record custody
Record during and after it
- Exact configuration used, and changes from the proposal
- Capture, shared views, local save, submission and receipt observations
- Separate network, application and record-reconciliation results
- Evidence, exceptions, corrective actions and decision owner
- Named responsibilities and unresolved configuration items
If you measure setup time, task completion or cost, define the method and compare equivalent scope. A demonstration observation is not a claim of clinical validation, and no benchmark, savings or clinical-outcome result is asserted here.
Request a demo
Start with a demo. Then evaluate with your team.
Book a demonstration with sample data: patient-side work, the remote clinician joining, local work during an outage and the record arriving. Online, on site in Türkiye or at ICMM 2026.