Identify and tokenize
Detect patient identifiers and replace them with tokens. Keep the identifying information in the encrypted PHI Vault, separate from the approved-content repository used for responses.
Trust in healthcare AI depends on controlling what information the AI can use, how patient data is handled, what actions the system can take, and when a person needs to step in.
Security & compliance
Inside the E1™ architecture
The platform architecture separates patient identifiers from AI processing and records access for review.
Detect patient identifiers and replace them with tokens. Keep the identifying information in the encrypted PHI Vault, separate from the approved-content repository used for responses.
Route de-identified information into the response workflow, with approved knowledge sources and program rules.
Apply role-based access, authentication, and audit logging so teams can review who accessed information.
The response workflow uses approved content, limits what the agent can do, and checks a reply before it reaches the patient.
E1’s Private Vault holds your organization’s approved content for responses. It is separate from the PHI Vault, which protects patient identifiers. Questions outside the approved content receive a configured fallback.
The intent analyzer checks which workflow actions are permitted. Out-of-scope requests receive an approved fallback or move to human support through the configured escalation. A request for a person follows that same route.
A large language model drafts a reply. A small language model checks it against approved information and response rules. Failed drafts are withheld; the configured workflow supplies an approved fallback or routes the request to human support.
See each product’s controls. Capabilities vary by product and implementation.
E1 applies approved-information boundaries, consent, and human escalation to keep automated responses within the organization’s rules.
HXP brings patient preferences and consent into communication decisions, with compliance controls applied throughout the engagement workflow.
EIDM 360 keeps behavioral inferences distinct from facts and preserves the context people need to review an interpretation.
VOCE combines secure audio and video with interaction records that support traceability and review after a conversation.
PIXI retains source context and a human review gate as potential safety information moves toward applicable reporting workflows.
Good questions are the start of a trusted relationship.
Talk with HXT