Patient Registration Without Manual Data Transfer
During the initial visit, a registration desk employee transfers information from the passport into the medical information system: full name, date of birth, document series and number, issuing authority code, and other details.
Tevian IDP is a document recognition solution that extracts passport data from scans and photographs. The passport recognition result is sent to the MIS and used to automatically populate the patient record.
The employee only needs to compare the recognized values with the document and confirm that they should be saved.
- Less manual entry. The operator checks ready-made values instead of filling in every field from scratch.
- Fewer typos. Passport data can be checked before the patient record is saved.
- Faster patient registration. The data appears in the MIS form as part of the registration desk’s familiar workflow.
How Passport Recognition Works
The employee scans the passport or takes a photo of the document with the workstation camera.
After the image is uploaded, Tevian IDP identifies the document type and launches the corresponding processing workflow. If different types of documents may be submitted, the system classifies them and identifies the passport for further recognition.
The system then checks the document’s readability, recognizes the text, and extracts the required passport data: full name, date and place of birth, passport series and number, issue date, issuing authority code, and other details. The extracted values are converted into a structured format and checked for completeness and format validity.
After processing, the data is sent to the MIS to populate the patient record. The employee only needs to compare the result with the document and confirm that it should be saved.
Integrating Tevian IDP with the MIS
Tevian IDP connects to the existing medical information system through an API. The set of fields to be transferred and the processing route are configured for the specific MIS.
Users do not need to switch to a separate application. Image upload, passport text recognition, result verification, and saving are performed in the medical system’s working interface.
The solution can be deployed within the healthcare organization’s infrastructure. In this case, document recognition and image processing are performed inside the customer’s environment.
Results for the Registration Desk and the Patient
Less manual entry. The operator checks ready-made values instead of filling in every field from scratch.
Verification before saving. Passport data is saved only after it has been checked by an employee.
A Single Workflow. Passport recognition becomes part of the familiar patient registration process in the MIS.
Existing Patient Record Search. The extracted data can be used to search for the patient in the database before creating a new record. The logic for searching, updating, or creating a record is configured on the medical information system side.
Let’s Discuss Integration with Your MIS
Tell us which medical information system your organization uses and which passport data needs to be transferred to the patient record.
FAQ
In this workflow, Tevian IDP checks document readability, recognizes the data, and validates the completeness and format of the extracted values. A registration desk employee compares the result with the original passport before saving the data to the patient record.
This depends on the integration settings and the healthcare organization’s policies. The passport image may be deleted after recognition or sent to the MIS if storing the scan is part of the customer’s internal process.
The system checks image quality and flags fields that could not be recognized with sufficient confidence. Wear, folds, glare, shadows, blur, or obscured fragments can affect the result, so questionable values are checked manually by an employee before being saved to the patient record.
Processing time depends on image quality, the integration configuration, and the deployment infrastructure. The expected time for a specific MIS is determined during integration design and testing.
Yes. Access is determined by the integration settings, the MIS role model, and the healthcare organization’s internal policies. Processing can take place within the customer’s environment, and the passport image does not have to be stored after recognition.
