Wizey B2B FAQ
A FAQ for leaders, IT, security and legal teams: how to discuss integration, the pilot, documentation, data formats, white-label, security and the role of the doctor or clinic — without publishing restricted technical material.
These are public answers. The full API and security documentation is shared after we discuss the project and agree on the scenario.
Pilot, value and the role of the doctor and clinic
These questions help you see where Wizey can strengthen your current product or service, and how to fit the output into your team's work correctly.
Which B2B scenarios is Wizey suited for?
For laboratories, clinics, medical services and patient portals that need to explain lab results, conclusions, discharge summaries, prescriptions and other text-based medical documents in plain language. More in the overview of B2B scenarios.
How does the pilot start?
First we discuss the task, the audience for the output and the available data. Then we agree on the output format, a test set of examples, the evaluation criteria and the feedback process. Pilot terms are on the B2B pilot page.
What role does the doctor or clinic keep?
The partner decides where the output is used: in a patient-facing service, an internal summary, post-visit communication or in preparing questions for a consultation with a specialist.
What are the timelines for launching a pilot?
A typical guide is 2–4 weeks, depending on the scenario, the integration scope, the amount of white-label adaptation and the security team's requirements on the partner's side. We fix exact timelines after assessing the task and the data format.
Integration, data and documentation
Publicly we describe only the general approach. Specific connection schemes, working parameters and technical instructions are shared with the partner's team separately.
What integration options are possible?
We discuss integration with a LIS, HIS, CRM, patient portal, mobile app or an internal workflow. The choice depends on where the output appears. An overview of the approaches is on the integration page.
What is the API integration format?
A REST API with an asynchronous processing model: the request is accepted, and the result is retrieved by task identifier. The approach is resilient under load and convenient for integration with a LIS, HIS and the partner's internal services.
Specific methods, request schemas, fields and connection parameters are shared with the partner's team after we discuss the project and sign an NDA.
Which document formats do you support?
We work with text-based medical data: lab results, discharge summaries, prescriptions, visit notes and text descriptions of studies. PDFs and photos of forms are supported through text recognition (OCR), as well as structured transfer in an agreed format (for example, JSON).
The conversion scope and the recognition points are agreed for the partner's scenario.
What data is needed for a request?
For the algorithms to work, clinical context without personal identifiers is enough: values, descriptions, symptoms and related information. We agree on the set of fields for the scenario so the partner can assemble the request on their side.
When is documentation shared?
The full API and security documentation is shared after we discuss the project. On the public page we do not disclose working connection parameters or restricted material.
Can you do a white-label setup?
Yes. The output format, tone, interface elements and branding are agreed for the specific product. The amount of adaptation affects the pilot scope. Adaptation scenarios are in the B2B use cases.
Security and approvals
Requirements for data, access, result storage, contractual documents and security reviews are discussed during pilot preparation. Publicly we keep only the general level of description, enough to make an initial decision about a meeting. A public overview of the approach is on the security page.
How do you ensure HIPAA and GDPR compliance for personal data?
The approach is built on data minimization: the algorithms do not need the patient's personal identifiers. We help partners design the process so that data on the sending system's side meets the requirements for consent, data localization and the rights of the data subject under HIPAA and GDPR.
The detailed data-handling policy, the set of notifications and the role-separation scheme are shared with the partner as part of the pilot discussion.
Do you depersonalize data before AI processing?
Yes. In the pilot integration, patient identifiers (name, contacts, document numbers) are removed on the partner's side or in a dedicated secure perimeter before being sent to the AI processors. Only clinically relevant context reaches the AI service.
The exact depersonalization process and areas of responsibility are defined for the partner's scenario and documented in the project materials.
Is a Zero-Log mode available?
Yes, a Zero-Log mode is available within the pilot for sensitive environments. The idea is that request contents are not saved to persistent storage; the result may be held for a limited time for retrieval via the asynchronous protocol.
Implementation details, the processing perimeter and storage parameters are discussed with the partner's security team in a private setting and are not published on the site.
Is this a clinical decision support system (CDSS)?
Wizey is a reference and informational product. The service helps structure and explain medical data, but the final clinical decision is always made by the doctor or the medical organization.
How the capabilities are used in clinicians' workflows is agreed within the pilot, taking the partner's internal regulations into account.
Who is responsible for clinical decisions?
Responsibility for clinical decisions and their application stays with the doctor and the medical organization. Wizey provides a tool to prepare context and explain data, but it is not a subject of medical activity and does not issue medical conclusions.
Cost and the next step
Price, timelines, volumes, support and scope of work depend on the scenario. For a public FAQ it matters more to show which questions to prepare for the discussion.
Why is there no fixed pricing grid?
A B2B project can be a lab pilot, a white-label module, an internal summary or a product integration. These options require a different scope of work. More on the B2B terms page.
What to prepare for the first meeting?
It helps to describe the scenario, the document types, the expected output format, the user roles, the approximate data flow and your internal approval requirements.
Can we start without complex integration?
Yes. Sometimes a pilot starts with a limited process to test the quality of the output and the value for the team, and then a deeper connection is discussed.
Still have questions about the B2B pilot?
Use the B2B form to tell us who will use the output, what data you have on input and what format you need on output. We will propose the next step without unnecessary public detail.