HIPAA-aware design
Privacy and access controls are part of the product design from the start.
Security & control
Serious controls. Clear language. No fear marketing.
OneSource OS is designed around HIPAA-aware safeguards, organization-level separation, role-based access, and human review for important actions.
Security posture
Access before assistance
Luma only works with information the user is allowed to see. When access is not allowed, Luma gives a clear refusal.
Built-in privacy protection
A privacy layer helps prevent unsafe access and disclosure across the experience.
Human review for important actions
Luma can prepare a recommendation or draft. An authorized person reviews important actions.
Human-approved messaging
Messages remain drafts until an authorized person approves them.
Traceable work
Sensitive actions are recorded so they can be reviewed.
Layered protection
Sessions, encryption, uploads, and access controls work together to protect the workspace.
How OS is designed to keep work in bounds
Practice and organization separation
Each organization has its own operational workspace. One practice's information is not another practice's search result.
Role-based access
People see the work that matches their role and assignments. When access is unclear, the safe response is a clear refusal.
Minimum necessary information
Summaries and access messages avoid exposing sensitive details that are not needed for the task.
Sources and change history
Recommendations point to their supporting information. Proposed changes are shown for review before they are saved, and sensitive actions remain traceable.
Human review
A recommendation is a starting point for review. Important actions identify what would happen, which records are affected, and who must approve them.
When access is unclear
If identity, role, or organization context cannot be confirmed, Luma protects the information and explains that it cannot provide access.
OneSource OS workspace · sample information
Access-aware review
Show the boundary without exposing the protected record
A sample workspace shows how access, review, and traceability remain visible.
Sample information is used here; no client records are shown.
OneSource OSSample workspace
Access-aware reviewShow the boundary without exposing the protected record
Sample dataWorkspaceNorthstar Behavioral Health
AuthorizedSensitive detailProtected from this role
Access limitedReview eventReason recorded
Audit entryAccess response example
Access-aware refusal
Good: I cannot access that information under your current role.
Avoid: I can see that patient is in another practice, but you do not have access.
The first response protects people and practices by ending the inquiry without confirming sensitive information elsewhere.
Access limited
Company security & technology stack
HIPAA posture, MFA, BAAs, and the day-to-day technology environment (Microsoft, SharePoint, Zendesk, Telzio, RingCentral, Retell AI, BastionGPT, and OneSource OS) are documented on the company Security & technology page — kept separate from OS product access controls.
Ask a security and control question
Tell us which access, review, communications, or data-handling boundary matters to your evaluation.