The actual product
Real screenshots. Shipping since 2011.
Not a concept render: this is QliqCHAT as your team would install it today, from the App Store or Google Play.
Replace risky SMS and consumer chat apps with secure texting your whole care operation can run on, with priority flags, requested acknowledgements, image annotation, and every message archived under your control. Because in healthcare, "sent" isn't good enough.
Consumer apps tell you a message was delivered. Clinical communication demands more: the recipient needs to know how urgent it is, and the sender needs to know it was received, read, and acted on. QliqCHAT pairs priority flags with requested acknowledgements, so every critical message carries its urgency on its face and reports its own completion.
Single sign-on via SAML (browser) and OIDC (apps) with SCIM v2 user provisioning from Okta or Microsoft Entra ID, bulk import available, and an intuitive workflow with an embedded user guide.
Provision users automatically via SCIM v2, or bulk-import, with roles and permissions controlling exactly who can message whom, including augmented and agency staff.
One-to-one, unlimited groups, broadcasts, photos, and documents, familiar texting, now encrypted with delivery, read, and acknowledgement states.
Every message archived and searchable under your control, remote lock and wipe for lost devices, and audit trails built automatically.
Connect users by department, team, patient, or topic, no caps.
Circle the wound, arrow the concern, context travels with the image.
The camera is the scanner, discharge packets and signed orders become clean PDFs, sent from the field in seconds.
One-to-many announcements, sender controls who sees responses.
Urgent, ASAP, and FYI tags make triage instant at a glance.
Confirm delivery, reading, and explicit acknowledgement.
Respond from a list of your team's frequently used templates.
Queue handoff notes to land at shift change, not before.
Conversation-centric workflows from referral to discharge.
SAML SSO for browsers, OIDC SSO for apps, SCIM v2 user sync with Okta and Microsoft Entra ID.
Every minute a field clinician waits on a callback is a minute of care lost, and every care detail sent over personal SMS is compliance risk your agency carries. Secure texting fixes both at once.
Your staff's own phones, your organization's rules, with the archive under your control.
RSA 2048-bit and AES-256 encryption at rest and in transit, on every message and attachment.
Password and PIN enforcement, auto-lock on idle, and remote lock & wipe for lost or departing-staff devices.
Isolation from the camera roll, copy/paste restrictions, and admin-controlled message retention periods.
QliqSTOR provides long-term, HIPAA-compliant archival behind your firewall, aligned to your retention policies.
Independently attested controls, HIPAA compliance, and a Business Associate Agreement included.
Client-side archive retains messages as long as you choose, searchable and exportable on demand.
Bi-directional EMR integration · Upload conversations & attachments · HL7 / FHIR / ADT / MDM · SAML, OIDC & SCIM v2 identity
SSO through your identity provider, users provisioned automatically via SCIM v2, your first Quick Messages set up, and an embedded user guide your team can follow without a training week.
Secure Staff Texting is one of six QliqCHAT capabilities that work as one collaboration system:
Standard SMS is unencrypted and carries no access controls, audit trail, or business associate agreement, which is why sending PHI over it exposes your organization to compliance risk. QliqCHAT provides encrypted messaging with a BAA, role-based access, and complete archiving.
QliqCHAT automatically locks after an administrator-defined period of inactivity, and both end-users and administrators can remotely lock and wipe the application data from the admin dashboard, no PHI stranded on a missing phone.
Administrators set an in-app retention period of up to one year, and messages are continuously archived to QliqSTOR, optional, complimentary long-term HIPAA-compliant storage behind your firewall, aligned to your retention policies.
Yes, unlimited groups by department, team, patient, or topic, plus system-wide or department broadcasts. The sender controls whether responses are visible to everyone or just to them.
Read receipts show a message was opened. Request Acknowledgement asks the recipient to explicitly confirm they've seen and accepted the message, with delivery, read, and acknowledged states each time-stamped. Paired with priority flags, it gives urgent clinical messages a provable, closed loop.
Yes, Snap to PDF turns the device camera into a scanner. Multi-page discharge packets, signed orders, and referral documents become clean PDFs sent securely into the right conversation in seconds, with nothing saved to the personal camera roll. Liaisons use it at the hospital bedside; nurses use it in the patient's home.
No. QliqCHAT runs on staff members' own devices while keeping work communication separate, encrypted, and under your organization's control, isolated from the camera roll, with copy/paste restrictions available.
No. WhatsApp encrypts messages, but Meta does not sign a business associate agreement for it, and it lacks the access controls, administrative audit trail, and archiving HIPAA requires, so covered entities cannot use it for PHI. QliqCHAT is HIPAA-compliant messaging with a signed BAA, role-based access, remote wipe, and complete archiving.
Yes. QliqCHAT pairs HIPAA-compliant texting with Caller ID Masking, so therapists and behavioral health staff can call and text clients from personal devices while showing the office number, with every exchange archived. See the Behavioral Health page for the full intake and engagement workflow.
New to secure texting? Get the vendor comparison checklist or read the Ultimate Guide to HIPAA-Compliant Secure Texting.
Not a concept render: this is QliqCHAT as your team would install it today, from the App Store or Google Play.
In a 30-minute demo we'll show secure texting live, priority flags, acknowledgements, and the one-day rollout, and how it grows into patient threads, on-call routing, and EMR sync when you're ready.
