MediSyncD Technologies, LLC · Effective August 5, 2026
CareCueD Compliance Document Package
Draft for professional review: These operational documents are a strong starting point, but they are not legal advice or proof of certification. They should be reviewed by qualified legal, privacy, security, accessibility, insurance, and healthcare-compliance professionals before production reliance.
1. Privacy Notice
This notice explains how MediSyncD Technologies, LLC ("MediSyncD," "we," or "us") may collect, use, disclose, and safeguard information through the public CareCueD website and related business communications.
Information collected
Contact details voluntarily submitted, including name, organization, role, email address, and phone number.
Business inquiries, demonstration requests, pilot-interest information, and correspondence.
Technical information such as browser, device, approximate location, referring page, and usage events when analytics are enabled.
Use of information
Information may be used to respond to inquiries, provide demonstrations, evaluate pilot opportunities, improve the website, protect systems, comply with law, and communicate about CareCueD.
Protected health information
The public website is not intended for submission of protected health information (PHI), resident requests, medical emergencies, or clinical documentation. Do not submit PHI through public forms, ordinary email, or unsecured channels. Any future processing of PHI in a deployed CareCueD environment must be governed by approved data flows, applicable contracts, required Business Associate Agreements, configured safeguards, and facility policies.
Sharing, retention, and choices
We do not sell personal information. Limited information may be shared with service providers acting on our behalf, professional advisers, authorities when legally required, or a successor in a business transaction. Information is retained only as reasonably necessary. Individuals may request access, correction, or deletion, subject to legal and operational limits.
2. Website Terms of Use
The public CareCueD website is provided for informational and business-development purposes. It is not medical, clinical, legal, cybersecurity, regulatory, or compliance advice.
No emergency or clinical use
The public website must not be used to report emergencies, request resident care, transmit PHI, or replace 911, nurse-call systems, clinical judgment, required staffing, or facility procedures.
Product status and claims
CareCueD is under active development. Features, availability, integrations, security controls, pricing, pilot scope, and timelines may change. Anticipated benefits, performance figures, or outcomes are goals or hypotheses unless expressly identified as verified results supported by documentation.
Intellectual property and acceptable use
CareCueD, MediSyncD, related marks, designs, workflows, content, and software are owned by or licensed to MediSyncD Technologies, LLC. Users may not interfere with the website, attempt unauthorized access, introduce malicious code, misrepresent affiliation, or use the site unlawfully.
Disclaimer
The public site is provided "as is" to the extent permitted by law. Missouri law governs these terms, without regard to conflict-of-law principles.
3. Security Overview
CareCueD is being designed using a risk-based security approach appropriate for healthcare workflow technology. This overview describes design intentions and does not represent a certification, guarantee, completed penetration test, or independent audit.
Security priorities
Role-based access and least-privilege permissions
Strong authentication and secure session management
Encryption in transit and, where applicable, at rest
Facility and tenant data separation
Audit logging for material user and administrative actions
Secure development, dependency review, and controlled changes
Backups, recovery planning, and incident-response procedures
Shared responsibility
Security also depends on identity configuration, endpoint and network controls, workforce training, vendor management, facility policies, contracts, and the actual deployed environment.
Claims control
CareCueD must not be described as SOC 2 certified, HITRUST certified, independently penetration-tested, or compliant with a named security standard unless the applicable assessment is completed, current, and supported by evidence.
4. HIPAA-Focused Practices Statement
CareCueD is being designed to support healthcare organizations that may be subject to HIPAA. This statement is not a certification of HIPAA compliance.
Compliance is not software alone
HIPAA compliance depends on the covered entity’s and business associate’s risk analysis, policies, safeguards, workforce practices, documentation, contracts, system configuration, incident handling, and ongoing oversight.
Design considerations
Minimum-necessary access and role-based permissions
User authentication and access review
Audit controls and activity records
Transmission, integrity, and availability safeguards
Incident reporting and response procedures
Business Associate Agreements when legally required
Before PHI is processed
The parties should determine their HIPAA roles, approve the data flow, complete privacy and security review, execute required agreements, configure access, validate integrations, train users, and document downtime and incident-response procedures.
5. Accessibility Statement
MediSyncD Technologies, LLC is committed to making CareCueD’s website and product experiences usable by people with disabilities.
We aim to use clear language, keyboard-accessible controls, visible focus states, sufficient contrast, semantic structure, descriptive labels, responsive layouts, large touch targets, and understandable resident choices. Accessibility is ongoing. No WCAG conformance level should be publicly claimed until appropriate evaluation has been completed.
To report a barrier or request information in another format, contact deaconjason@medisyncdtechnologies.com or 314-220-1274 and describe the page, feature, assistive technology, and problem encountered.
6. Founding Pilot Terms Overview
This overview is for planning and does not replace a signed pilot agreement, Business Associate Agreement, data-processing terms, insurance review, or facility approval.
Proposed structure
Up to 90 days unless the written agreement states otherwise
One unit or another mutually agreed scope
Documented implementation plan, contacts, training, and support
Defined measures such as adoption, acknowledgment, escalation, completion, uptime, and feedback
Weekly review of operational issues and requested improvements
Facility responsibility
The facility remains responsible for resident care, emergency response, staffing, clinical decisions, policies, regulatory duties, user authorization, devices, networks, and workforce supervision.
Data and outcomes
No PHI should be used until roles, safeguards, retention, deletion, permitted uses, and required agreements are approved. Pilot measures are evaluation criteria, not guaranteed outcomes. Public use of a facility name, logo, testimonial, case study, or performance claim requires written authorization and documented evidence.
Exit planning
The signed agreement should address suspension, termination, data return or deletion, transition assistance, and post-pilot commercial terms.
7. Clinical and Emergency-Use Disclaimer
CareCueD is a communication, request-routing, escalation, and workflow-support platform. It is not a diagnostic tool, medical device, clinical decision-support system, or substitute for licensed professional judgment unless a specific regulated use is separately evaluated and authorized.
Emergency use
CareCueD must not be the sole method for reporting or responding to emergencies. Facilities must maintain appropriate emergency procedures, nurse-call capabilities, alarms, staffing, and access to 911 or other emergency services.
Clinical and operational responsibility
Care decisions remain the responsibility of licensed clinicians and authorized facility personnel. Users must follow laws, professional standards, care plans, physician orders, and facility policies. Availability can be affected by power, devices, connectivity, integrations, configuration, maintenance, and third-party services. Facilities must maintain tested downtime and redundant communication procedures.
Implementation safety
Implementation should include risk assessment, controlled testing, staff training, accessibility review, escalation-rule validation, monitoring, and procedures for residents who cannot reliably use the interface.