Compliance & Data Practices
Clear boundaries for website inquiries and applications, and a separate assessment of the safeguards, access and agreements required for client work.
Public website
The website submission boundary
The public site is not an operational healthcare system. Share only the business context needed for a conversation, or relevant recruitment information through Careers.
Read the Privacy notice for data handling and the Security page for application safeguards and their limits.
Separate business and recruiting forms
Business forms collect organizational inquiries. The Careers form collects applications for HR, with an optional PDF CV. Neither channel is for patient intake.
No patient information
Do not submit patient or protected health information.
A saved reference, not a service commitment
A successful form receipt confirms database storage, not staff review or email delivery. Unavailable storage does not produce a success receipt. Follow-up and any operational engagement require a separate process.
Before operational work
Engagement-specific assessment
Operational safeguards, access boundaries, and contracting requirements are assessed for each engagement. No blanket assurance replaces that review.
What work is assigned?
Define the workflow, information inputs, output, ownership, exceptions, and escalation path.
Which systems and access are required?
Identify approved systems, minimum access, role boundaries, and the responsible client or provider owners.
What contractual requirements apply?
Assess the planned work, information involved, responsibilities, and required agreements before operational access begins.
How will the work be reviewed?
Agree on status reporting, exception handling, escalation, and the cadence for operational review.
Begin with business context only.
Use the public form to describe the organization and workflow. Do not include patient or protected health information.