DataFor general and university hospitals and hospital networks
The request form is read before the sample reaches the lab.
On the ward, a paper lab request is scanned. DataSnap reads the barcode on the patient label and the name of the requesting doctor, and a member of staff only checks what is uncertain. Everything runs on the hospital's servers. Patient data only goes to the cloud if you choose that yourself, per step in the workflow.
Where you can start
Six paper flows in a hospital.
Post and supplier invoices
Invoices from medical suppliers that still arrive on paper or as a PDF. DataSnap recognises the supplier by the VAT number, checks the amounts and gets the invoice ready for accounts.
Lab requests
Paper request forms from the wards and from GPs. DataSnap reads the barcode on the patient label and the fields. A form with an unreadable field goes to a member of staff.
Delivery notes
The notes from a delivery go through the scanner in one stack. The barcode on each note splits the stack, and the order number goes into a field of its own.
Patient records and consent forms
Signed consent forms and paper documents for the record become searchable PDF/A. You can make review mandatory for every form.
The duty to keep records
You keep a patient record for at least 30 years. DataSnap creates PDF/A-2b, the format for long-term preservation, and delivers it to your own archive.
Cabinets full of old records
Your own team or a scanning bureau scans the old paper records. A separator sheet with a barcode marks where each record begins.
Data protection
Patient data stays on the hospital's servers.
Health data falls under Article 9 of the GDPR. That is why recognition, including the AI, runs on your own servers. If you only use the desktop and the Windows service, we process none of your documents. We do not have ISO 27001 certification yet, and the external penetration test is planned. The current status is on our trust page.
- Processing on your own servers. Text recognition and AI run in your own data centre, without the cloud.
- You choose what goes to the cloud. If you add the portal or the phone app later, you decide per step in the workflow which documents go to the cloud. We sign a data processing agreement with you for that.
- Who approved what. For each value you see which member of staff checked it and when.
- Signed updates that the service installs itself, without admin rights.
We build integrations with your patient record system when you need them
As standard, DataSnap delivers a PDF/A and the data as XML to a folder, by e-mail, over SFTP or FTPS, or sends the data straight to the API of your software. Your electronic patient record (EPR) or archive system picks them up from there. If you need a direct integration, we build it, to a standard such as HL7 or FHIR or on your supplier's own software.
Who has a say
What each decision-maker in the hospital wants to know.
- IT director
- A Windows service on a hospital server. Updates are signed and need no admin rights.
- DPO · information security
- Patient data stays on your servers. You choose per step in the workflow what may go to the cloud.
- Medical records
- PDF/A-2b, tested with veraPDF. A retention period per document type.
- Finance director
- A fixed price per campus, €8,500 a year. A page read on your own server costs nothing extra.
One package per campus
8 scan stations, the portal with 50 users and 40 phone users for €8,500 a year, excl. VAT, with updates and support. A second campus costs €6,900. Included each year: 50,000 documents in the cloud and 500 GB in the archive. What runs on your own servers is unlimited.
Demo
See DataSnap at work on documents from your own sector.
In 30 minutes we scan a stack of samples, such as an application form or a delivery note, and you see how each value is read and checked. You know the price up front.