Questions about PatientCompanion?

We believe in transparency and informed decisions.


Below are answers to common questions about our platform, security, and implementation. Don't see your question? We'd love to hear from you.

How is this different from a call button?

Traditional call buttons only signal that a patient needs help. PatientCompanion allows patients to communicate what they need before staff enter the room. This helps route requests more efficiently and reduces unnecessary interruptions.

Do patients need to download an app?

No. Patients can use PatientCompanion directly through their mobile web browser on their personal device; no app download, no account creation, and no setup required. In some units, PatientCompanion is also available on hospital-owned, mounted tablets that are pre-configured and managed by the facility’s IT team.

What devices does PatientCompanion work on?

PatientCompanion works on personal smartphones via the mobile web, as well as hospital-owned devices such as mounted bedside tablets. It is device-agnostic and does not require specialized hardware.

What data does PatientCompanion collect?

We do NOT collect personal health information (PHI) or personally identifiable information (PII). The platform only processes the information a patient chooses to share in order to communicate their needs (ex. Glass of water, blanket, etc.). That information is then delivered to the appropriate care team and handled according to your organization’s hosting, access, and retention policies.

How do I know this platform is secure?

All communication is encrypted in transit and at rest, and deployment is reviewed with your IT team during implementation. Whether hosted in a Canadian cloud environment or on-premises, access controls, network policies, and compliance requirements are defined and approved by your organization.

Can this integrate with our existing systems?

PatientCompanion is designed to work alongside your existing systems. During implementation, we review your current environment (including EHRs, nurse call systems, and communication tools), preferences, and policies to determine appropriate integrations or standalone operation.

What's the implementation process like?

Implementation begins with a discovery conversation to understand your clinical workflows, technical environment, and security requirements. From there, we collaborate with IT and clinical leadership on configuration, testing, training, and rollout at a pace that works for your organization.

Still have questions?

Every facility has unique needs and concerns. We'd rather have a conversation than give you a generic sales pitch.