Files, diagnostics and output in VetConnect

Uploading, selecting an existing file, linking it to a clinical record and generating a PDF are different actions. Check active clinic and patient first; a phone filesystem path proves no clinical association.

File Manager and camera

1. Open main Files or the file entry in patient/customer/examination.
2. For a new file, use the device picker/camera and grant requested OS access when appropriate. For an existing file, use the selector.
3. Watch each queue item. Shared File Manager uses multipart for eligible files above 30 MiB, up to 2 GiB. Prescription, task, invoice and diagnostic sources may impose narrower rules.
4. Retry or cancel the failed file individually. Recovery requires the same content; the same name/path with different content cannot continue the old upload.
5. Verify its link to the target record. Appearing in Files alone does not establish examination or order linkage.

Deletion has its own permission and performing-clinic restriction. Recheck bulk targets. Favorites/recent views grant no ownership or sharing access.

Diagnostic intake and OCR

Open Add result from patient or examination. Manual values, OCR and file upload are different sources. Select the patient before file work. If opened from an order, keep its fixed patient, examination and requested diagnostic scope.

Wait for upload/background completion; recover interrupted work from tasks/history. Review values, units, reference ranges and abnormal flags before clinical confirmation. Uploaded raw content or extracted text is not a confirmed result. Device is currently disabled in normal mobile creation; it is not interchangeable with generic file upload.

Pending correction and confirmed result can be displayed separately. Signed examinations retain their linked signature-time revision. A newer general result does not rewrite an older signed examination. Diagnostic lifecycle.

Imaging and screen handoff

Open an eligible image from diagnostic detail. DICOM/web viewer paths depend on device/version support; a thumbnail is not a full raw viewer. Check image patient and associated order.

Supported photo/screen handoff requires an available computer and the same user/clinic. Prescription, task, invoice and File Manager have different count/file constraints. Resolve ongoing mobile save/upload decisions before continuing on the computer; handoff does not silently save unfinished work.

PDF, sharing and regulatory files

PDF actions in sale, prescription, vaccine, treatment, epicrisis or diagnostic detail open preview. Check patient, source clinic, date, signature and document type before using share/output. Preview signs no record and automatically sends nothing. Viewing and exporting have separate access.

Sharing uses the same validated PDF content. Do not continue with a stale preview after account/clinic changes. For failures, check access and record state and reopen the existing document; do not recreate financial or clinical records. Track loading, page navigation and native sharing completion separately for large documents.

ATS/İTS/medication exports generate workbooks rather than PDFs. Mandatory gaps can block download; offered temporary correction does not update permanent patient data. HBS connection is unavailable on mobile while workbook generation remains a separate capability. Regulatory export.

Synthetic check and recovery

Upload a harmless PDF/image for a test patient, select it and link it. Reopen the list and check filename/patient. Retry the same queued file after a network failure rather than creating a duplicate. If camera access is denied, inspect device settings or use the file picker when offered. Native camera, share and DICOM acceptance needs separate testing on the actual app/device version.