Frequently Asked Questions
Quick answers on pilots, compliance posture, and AI-assisted documentation workflow.
How does SyncSOAP support HIPAA workflows?
SyncSOAP is built around HIPAA-aligned architecture, but actual compliance depends on the customer deployment, the signed BAA, vendor contracts, access controls, retention policies, and operational procedures. Current validation is limited to mock and non-PHI workflows.
How long is encounter data retained?
Encounter data is designed for short-term operational storage and is removed according to the configured retention policy for the deployment.
How does the AI generate SOAP notes?
The AI processes encounter transcripts and optional approved clinical inputs to draft a structured SOAP note for clinician review and editing.
Does the AI make diagnoses or treatment decisions?
No. SyncSOAP is designed to support documentation only; licensed clinicians remain responsible for all diagnosis, treatment, and clinical decision-making.
Is demo mode safe for real patient data?
No. Demo mode is intentionally separated from production and should only be used with fake or de-identified sample data.
What security controls are in place?
SyncSOAP uses encryption in transit, managed service identity and Secrets Manager-backed secret handling in production, access controls, passkeys, and audit logging. Workforce devices should also use full-disk encryption and screen locking.