Skip to main content

Privacy and control

Understand the controls behind the care journey

A clinical workflow needs clear authority, defined data boundaries and an honest account of what has been verified. Pexify's design brings those questions into the product model, from a proposed action to the record of its outcome.

The platform is in development. This page describes design principles and deployment questions, not a completed security assessment or regulatory certification.

Keep clinical authority with the care team

AI can help prepare documentation and proposed work. The practitioner remains responsible for clinical decisions, and authorized staff act within the responsibilities defined by the practice.

The intended approval process makes the proposed action, patient context and relevant source information available for review. Patient-facing execution requires the appropriate authorization. Editing a proposal and approving an action are deliberate steps.

Approve the actual communication

For reviewed outbound messages, the control model binds execution to the exact approved content and authoritative recipient. A changed draft or recipient should not silently inherit an earlier approval.

Illustrative workflow. Product design in development. Availability is confirmed directly with the team.

Define who can see and act on the information

The Pexify model separates practice and practitioner authority and constrains patient access to the authorized scope. The relevant questions are practical: who can open the patient context, review the proposal, approve the action and inspect its history?

Those permissions, including administrative access and support access, need verification in the deployed configuration. A visual role diagram is useful for discussion, but it does not replace testing and a documented access model.

Illustrative workflow. Product design in development. Availability is confirmed directly with the team.

Review storage and processing separately

Pexify's architectural direction prioritizes clinic-controlled clinical information and limited central data custody. The approach includes the practice's Microsoft environment, but the complete processing path must be reviewed for the proposed deployment.

Where the source record is stored does not answer every data question. Transcription, AI inference, operational logs, backups and support processes may have different access or retention arrangements. Each needs to be included in the review.

  1. Source information

    Confirm where recordings, documents and clinical records are held and who controls access.

  2. Processing

    Identify every service that receives information for transcription or AI output, including its region and contractual settings.

  3. Persistence and support

    Establish what is retained in logs, temporary stores and backups, and how authorized support access works.

Evaluation questions for a proposed deployment.

No absolute "never leaves" or zero-retention claim is made here. Those statements require evidence for the complete production data flow.

Make uncertain outcomes visible

A workflow can reach a point where the result of an outbound operation is unclear. Pexify's intended approach records that uncertainty and calls for reconciliation before another attempt, rather than blindly repeating the action.

The team also needs to distinguish queueing, acceptance by a sending service and completion of the underlying care-plan milestone. These are different facts. Clear status language helps the reviewer decide what evidence is still needed.

Explore controlled actions

Establish the deployment boundary before using patient data

The proposed configuration should be reviewed with the people responsible for clinical use, information security, privacy and contracting. A useful review should resolve the following questions.

  1. Which workflows and capabilities are included in the confirmed scope?

  2. Where is information stored, processed and retained across the full service chain?

  3. Who can access patient information, approve actions or provide support?

  4. Which processors, contractual terms and regional settings apply?

  5. How are review decisions, execution outcomes and unresolved exceptions recorded?

  6. What evidence and acceptance checks are required before patient data or outbound actions are enabled?

Applicable legal and contractual requirements depend on the practice and proposed deployment. A product design description does not establish compliance.

Ask about the configuration your practice needs

Tell us the jurisdictions, existing systems and review requirements that your proposed use would involve. The conversation should establish the relevant scope and the information needed for a responsible evaluation.

The website privacy notice explains how business inquiry and website information are handled. Product data processing must be addressed through the actual deployment and its agreements.

Talk to Pexify

Please do not send patient information through this website.