Skip to content

[POC] u-254565 — React medical form scanner with barcode-based PDF naming #6

Description

@Tom-Dynamsoft

Case & Customer

Field Value
Case ID u-254565
Company Damingsoft
Contact Tom Jerry (developer)
Deal Stage Not specified
Deadline End of June 2026
Sales Rep Not specified

Use Case

Web application that scans medical intake forms using a desktop ADF scanner, reads Code 128 barcodes on the scanned forms, and saves the documents as PDF to the server using the barcode text as the filename. After successful upload, the server notifies the client, and the uploaded document is displayed as a clickable link. Clicking the link opens the document in an embedded Document Viewer for review.

SDK Requirements

Field Value
SDK Product(s) Dynamic Web TWAIN (DWT), Barcode Reader (DBR), Document Viewer (DDV)
Specific Types Code 128 barcodes
Input Source Desktop scanner with auto-document feeder (ADF), 60 ppm
Volume/Performance Batch scanning via ADF — up to 60 pages per minute

Technical Environment

Field Value
Platform Web (frontend) + Python (backend)
Framework React (frontend), Flask or FastAPI (backend — Render.com compatible)
Language JavaScript/TypeScript (frontend), Python (backend)
Hosting/Deployment Render.com for quick demo hosting
Browser/OS Requirements All mainstream browsers (Chrome, Edge, Firefox, Safari)

Special Requirements

  • Scanned documents saved as PDF, named using barcode text extracted from the form
  • Server-side upload endpoint (Python) that receives the PDF and saves it with the barcode-derived filename
  • Server returns success notification to the client after upload
  • After upload, display the document as a clickable link in the UI
  • Clicking the link opens the document in Dynamsoft Document Viewer (DDV) for viewing

Integration Points

  • React frontend ↔ Python backend REST API for PDF upload and document listing
  • DWT scans pages → DBR reads Code 128 barcode → PDF saved with barcode text as filename → uploaded to server
  • DDV embedded in frontend to view uploaded documents

UI / Branding

No branding — use anonymous/default styling.

Known Constraints

  • Must be hostable on Render.com for quick demo purposes
  • Server-side script to be built by PT engineer (not provided by customer)

TBD Items

  • Specific Python framework preference (Flask vs FastAPI) — PT engineer to decide based on Render.com compatibility
  • Document storage strategy on server (local filesystem vs cloud storage)

Notes from Sales

Customer is a developer (Tom Jerry) looking to build this POC themselves. They need a working reference implementation to get started.


Created via /poc-sample-builder intake on 2026-05-13

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    poc-requestPOC sample request from sales

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions