HIPAA training and applicable BAAs
Staff receive HIPAA training. BAAs are used with the firm and covered AI services where applicable, including eligible Google Vertex AI arrangements. Training and a BAA are distinct parts of the handling framework.
Security
Confidential work. Controlled access.
Your firm defines what staff may access and what requires approval. Telamanis supports confidential PI work through trained people, approved workspaces and supervised production, with information-handling boundaries agreed before work starts.
Workspace and handling
Confidential work starts with an approved workspace.
These are operating practices for engaged client work. Their application to your role and information sources is confirmed during onboarding.
Cloud and VPN access
Staff perform client work through approved cloud/VPN arrangements and authorized systems. Permissions, information sources and task boundaries are aligned to the engagement.
No local client-data storage
Client information stays in the approved workspace rather than being stored locally. The workflow specifies where records, drafts, status and reviewed outputs belong.
Monitoring scope
Supervised work includes activity oversight.
Work monitoring includes screenshots at 10-minute intervals and activity oversight. The engagement must align that practice with the firm鈥檚 information-handling requirements.
Know what can appear in a capture
A work-screen capture can contain information visible during an assignment. Confirm the monitored workspace and information boundaries before giving access to confidential records.
Confirm authorized reviewers
Agree which roles may review monitoring records and which access boundaries apply. Review authority should be clear to the firm and the assigned staff.
Confirm retention and handling
Confirm the retention, storage, access and removal arrangements for monitoring records in the operating policy before work starts. This public page does not publish a fixed retention period or an unrestricted reviewer-access promise.
AI and human review
AI works within the approved data and review boundary.
Tool availability does not authorize every type of client information or every AI service.
Approve the service and source
The engagement identifies approved tools, sources and applicable agreements. Covered-service eligibility and BAA scope must match the actual use; a general tool name is not a blanket authorization.
Review the output
Staff check extracted facts, summaries and drafts against sources and escalate gaps. Attorneys retain legal judgment and final work-product approval.
Define the handoff
Specify where the reviewed output is stored and who receives it next. Agreed manual transfers and actual software integrations are distinguished. Explore the applications.
Public and engaged-client boundaries
The public website is separate from client work.
An inquiry or public Vera interaction does not create an approved client workspace.
Contact and review forms
Share firm operations and system needs only. Do not submit client case details, patient names, SSNs, DOBs, medical records or claim/policy numbers. Contact Telamanis.
Public Vera
Use the public research experience without confidential client information. Firm-data connections require the configured engagement sources and permissions described in the approved scope. Vera鈥檚 role and boundaries.
Before production begins
Confirm roles, access, agreements, permitted data, monitoring arrangements, review and escalation. See the getting-started path and website Privacy Policy.
Define the requirements for your firm.
Start with the role, approved workflow and operating boundaries. We confirm the support and prerequisites in your engagement scope.
Request Your Systems Review