This is where the jargon gets explained. If you find an answer unclear, tell us — an answer that isn’t understood is not an answer.
Three levels of proving that software works as intended. IQ (Installation Qualification) shows that the installation was done correctly, OQ (Operational Qualification) that the functions work correctly, and PQ (Performance Qualification) that the system behaves as expected in real usage scenarios. When an auditor asks “how do you know?”, these records are the answer. Today these three levels are in place for Labdata LIMS.
An acronym for data integrity principles: data must be attributable (it is clear who did it), legible, contemporaneous, original and accurate. The “+” adds complete, consistent, enduring and available. In practice: who changed a record, when and why stays in the system, and the old value is never deleted.
Depending on your preference, the installation runs on your own servers or on servers we host. On your own servers, the data stays in your infrastructure; installations we host run on servers in Turkey. Either way, every organisation gets a separate installation; data from different organisations never sits in the same database.
Yes. The installation runs on your own servers or on servers we host, as you prefer; the choice is yours and does not change how the product behaves. For an installation on your own servers, the infrastructure needed is clarified in the scoping call; for installations we host, we operate the servers.
We reply to messages the same day; a message that arrives in the evening or at the weekend is answered by the next business day at the latest. If you choose “Support for an existing installation” as the subject, your message is flagged in its subject line and handled with priority.
No — and that is deliberate. Records are not deleted; they are corrected or deactivated. The old value, the person who made the correction and the reason remain. A record that can be deleted does not count as evidence in an audit. Physical disposal happens only when the retention period ends, and it leaves a trace.
It depends on the scope; we don’t give a duration before the call. The output of the scoping call is the scope in writing, and the time estimate comes from it. A duration given before the call either won’t hold or will force the scope to fit it.
Which data can be migrated and which needs to be set up again becomes clear in the scoping call — it depends on the product and on the current state of your data, so we don’t say before the call.
Yes. When you request a demo, we show the product with your own scenario; working through an example from your everyday work is more useful than a ready-made demo script.
A change to a standard is reflected in the system through configuration or a version upgrade. For Labdata LIMS, the mapping between standard clauses and screens is kept in writing: when a clause changes, the affected screens are read from this mapping and the validation records are produced again.
Today the product interfaces are in Turkish. This website is available in English and Turkish, and you can contact us in English.
Write to us. If your question will help others too, we add it to this page.
We reply the same day.