Data minimization
Default reminder templates can avoid unnecessary clinical details in SMS messages and lock-screen previews.
Care Messaging is being built for care-related workflows, so security, consent and data minimization are part of the product architecture—not an afterthought.
Default reminder templates can avoid unnecessary clinical details in SMS messages and lock-screen previews.
Production data should be encrypted in transit and at rest using modern, supported protocols and managed keys.
Caregivers, staff and administrators should only see the recipients and controls appropriate to their role.
Security-relevant actions and reminder events can be recorded to support review and accountability.
Production SMS enrollment will include appropriate consent, verification and STOP/HELP handling.
Healthcare deployments can use infrastructure and messaging vendors that support the required contractual and security obligations.
For customers subject to HIPAA, a production service may need a combination of appropriate vendor agreements, business associate agreements, policies, access controls, training, incident procedures, secure configuration and documented risk management.
Care Messaging will only describe a production configuration as HIPAA compliant after those controls and agreements have been implemented and verified for the applicable service.
Recipients and caregivers should call 911 or the appropriate local emergency service for urgent or emergency situations.
Care Messaging does not prescribe medications, change dosages or replace instructions from qualified healthcare professionals.
A text confirmation indicates what the recipient reported. It does not independently verify that medication was taken.
SMS delivery and user responses can be delayed or unavailable. Care Messaging should not be used as a sole safety monitoring system.
Tell us about your use case through early access so the production architecture can be evaluated against the right requirements.