A clinical interpretation layer
for laboratory results
TIS, Opinion AI's clinical decision platform, gathers your laboratory results in a single layer and writes every test into the patient's digital twin. AI-driven automated analysis, batch OCR and compliance checks against SUT (Türkiye's reimbursement rules) run throughout this flow. The result reaches the physician interpreted in clinical context and linked to the discharge summary; if a test is missing, a suggestion comes with it.
Lab results are written into
the patient's digital twin
In traditional systems, a lab result stays in a separate PDF. The physician opens the document to interpret it and checks another record to compare it with earlier values. In TIS, all lab records flow into the “Vital & Lab” layer of the patient's digital twin and are interpreted in clinical context.
Upload by document type
Laboratory, pathology, MR/CT/X-ray, consultation, surgery, prescription and committee reports are uploaded as separate document types. PDF, DOC, JPG and PNG files are supported.
Automated analysis
Every uploaded lab result is read by AI, placed in clinical context and automatically written into the relevant layer of the digital twin.
Batch OCR
All image-based documents, including older reports with poor scan quality, are converted to text with batch OCR so that they can be searched and analyzed.
Vital & Lab layer
Results are written into the “Vital & Lab” tab of the patient's digital twin. Trend, abnormal-value and missing-test indicators are generated automatically.
A basis for clinical synthesis
MINA turns hundreds of lab results into a clinical summary. That summary becomes the basis for chronic disease tracking, the allergy profile and risk forecasting.
Live synchronization
The profile updates as soon as a new test result is uploaded; the result goes straight into clinical context without waiting for a batch run.
MINA's support from test
order to result interpretation
MINA is an AI model specialized in SGK (social security) regulations, SUT rules and clinical guidelines, and physicians can ask it questions directly. It checks compliance while a lab order is being planned, analyzes the result when it arrives and suggests any test that is missing.
Order compliance
Planned test panels are checked against SUT rules and policy coverage before the order is placed, and orders that carry risk are flagged.
Result analysis
Incoming lab results are interpreted in clinical context. Abnormal values, whether follow-up is needed and suggested additional tests are presented to the physician.
Missing test suggestions
Tests that are missing for the current diagnosis or clinical suspicion are suggested, and those needed for the medical consistency of the discharge summary are listed separately.
Matching to ICD-10
Lab results are matched to ICD-10 codes. The system checks whether the results clinically support the diagnosis code and suggests an alternative code when needed.
The flow of lab data
to the physician's cockpit
Lab data is pulled automatically from HBYS (hospital information system) and LIS, normalized with ETL and written into the digital twin. It is then presented to the physician and the operations team through an up-to-date cockpit, with no manual intervention needed along the way.
Lab records are exported from HBYS and LIS
All lab order and result records, imaging reports and pathology documents are exported as XML or CSV.
Data is prepared with ETL and OCR
Structured lab results are normalized, and PDF and image documents are converted to text with OCR; missing fields and duplicate records are cleaned up.
Results are written into the digital twin
Cleaned results are added to each patient's “Vital & Lab” layer, and trend and abnormal-value indicators are recalculated.
A clinical synthesis is built
MINA turns the lab data into a clinical summary; chronic follow-up parameters, the risk outlook and the missing-test list are produced at this stage.
Results reach the physician's cockpit
When the physician and the operations team open the cockpit, they find critical lab-based alerts, patients who need follow-up and suggested additional tests ready for them.
Integration and
data security
TIS does not replace your existing LIS and HBYS; it is set up as a layer on top of them, with no changes to those systems.
Transfer via XML or CSV
TIS connects to HBYS or LIS through an XML or CSV export. Because it uses standard formats, integration does not disrupt existing operations and requires no further changes to the system.
Direct database connection
If preferred, a direct read-only connection to the database can be set up. A local agent can also be used for automatic transfer based on the patient number.
Data stays local and is stored encrypted
Data stays inside the hospital, and the database is reachable only from the local network. All connections use HTTPS, and data is stored on AES-256-encrypted disks.
MINA's model evaluation
You can find the task-level evaluation results for MINA v3.7 on the MINA v3.7 page.
Related guides and articles
Talk to us about
your laboratory
In the meeting, we can show you on a sample test panel how TIS integrates with your LIS and HBYS, and how it interprets lab results in clinical context.
POC Request