AI explanations for labs
The patient gets a clear explanation of their results, and the laboratory adds a digital service to the patient portal or to the result delivery.
Public integration overview
API & integration with Wizey
A breakdown of how the B2B version of Wizey plugs into a LIS, EHR, CRM, patient portal or medical product. This page describes the general approach without publishing the sensitive technical specification.
We publicly show the scenarios, the general process and the questions to align on. We share the full specification after we discuss your project.
Overview
An API as a medical-analysis layer
Wizey takes text-based medical data and returns a structured result for the scenario you choose: a patient report, a summary for the physician, an internal card, material for an operator or a white-label output. Detailed examples are collected in the overview of B2B use cases.
We support integration from any stack: Python, JavaScript, Go and others. The data perimeter is described in the Security section; the launch format and timelines are in the pilot terms.
LIS EHR CRM patient portal mobile app white-label
Scenarios
What you can connect
The API does not force a single product format. The B2B version is tuned to the user role, delivery channel, level of detail and the partner's regulations. More in B2B use cases →
Summaries for physicians
Short, structured context across lab results, discharge summaries, prescriptions and free-text study reports.
Patient reports
Plain-language materials after a visit, an examination or a document upload, with questions to raise during the consultation.
White-label & embedding
Wizey connects as an analytics module inside an app, a telemedicine service or a patient portal — with your own brand and tone.
Process
How the general process works
On the site we show only the high-level process. The technical connection details are aligned separately with the partner's team.
You send text data
Lab results, reports, discharge summaries, prescriptions or a study description in an agreed format.
You choose a scenario
A patient explanation, a physician summary, an internal report, white-label or a custom process.
You get the result
A structured response with the depth, tone, blocks and delivery format you need.
You embed it in the product
The result is returned to the portal, EHR, LIS, CRM, app or your team's workspace.
Before connecting
What we align before connecting
To keep the pilot fast and useful, we lock down not only the technical integration but also the business goal, the user role and the data requirements up front.
Data format
Which text-based medical data is sent, how it has been recognized and which fields are needed for a quality result.
Roles & access
Who sees the result: patient, physician, operator, administrator, product team or an internal service.
Security perimeter
How data is transferred, how access is restricted, where the result is stored and which documents your security team needs.
Response format
Report structure, tone, terminology, disclaimers, branding and the depth of explanations.
Test launch
Which examples we take into the pilot, which metrics we watch and how we decide on scaling.
Commercial model
Volumes, scenarios, support and pilot timelines are discussed individually. Volume, SLA and the legal perimeter are fixed in the pilot agreement, with no public limits.
FAQ
Common integration questions
Short answers to the questions teams usually ask before a pilot. Full regulations are shared with partners after we discuss the scenario.
Which text-based medical data is sent during integration?
During the pilot we agree on the list: lab results, reports, discharge summaries, prescriptions or a study description. The specific set of fields and the recognition quality are determined before connecting and fixed in the general process.
Who sees the analysis result?
Roles are agreed in advance: patient, physician, operator, administrator, product team or the partner's internal service. The role drives the delivery format, the tone and the depth of explanations.
How is the security perimeter described?
We agree on how data is transferred, how access is restricted, where the result is stored and which documents the partner's security team needs. The full perimeter specification is shared after we discuss the project.
Can the response format be customized?
Yes. Report structure, tone, terminology, disclaimers, branding and the depth of explanations are tuned to the partner's scenario, including white-label output.
How does the test launch work?
We take a limited set of examples, agree on metrics and gather feedback from the medical, product and operations teams. Based on the pilot results we discuss scaling.
Need a specification for your scenario?
Describe the task on the B2B page. We will clarify the scenario and the data perimeter, then hand over the documentation your team actually needs.