Paperless Dental Office (2026): Forms, E-Signatures, Scanning and IT

The clipboards are still in the rack by the window. A new patient is halfway through the medical history for the third time this year, the front desk is retyping yesterday's forms, and a stack of EOBs and referral letters is waiting beside the scanner. "We're trying to modernize a few things," an office manager wrote on a dentists' forum in March 2026, meaning texting, forms and claims. Plenty of offices that call themselves paperless are in exactly that spot: digital in the chart, paper at the front.

This guide takes that project from the IT side. It covers which forms and signature route each practice system (Dentrix, Dentrix Ascend, Open Dental, Eaglesoft, Curve, Denticon, SoftDent) publishes, how add-on tools such as NexHealth, Yapi, mConsent and Adit connect, what the ESIGN Act actually says, what to scan and what to stop scanning, which scanners the software makers list as working, where the files end up, and a 90-day rollout plan with an acceptance test. Every vendor fact comes from the vendor's own page, read on 6 November 2026.

What does a paperless dental office run on?

A paperless dental office replaces five paper flows: intake and medical history, consent and financial forms, signatures, documents that arrive from outside (EOBs, referrals, ID and insurance cards), and the old paper charts. Each flow has a digital path inside or beside your practice software, and each one depends on a piece of IT that the sales demo never shows.

Many "paperless" projects stall because they treat the five flows as one purchase. They are not. Intake forms are a software decision. Signatures are partly a legal decision and partly a hardware one. Scanning is a process decision with a storage bill attached. The table below is the map this guide follows.

The first two rows are about forms software and are covered next. Signatures, scanning, storage and the rest of the IT side follow.

Which paperless route fits your practice software?

Start with your practice management software, because every system now publishes a forms route of its own, and the add-on market connects to that system through a program on your server or a vendor cloud link. The table records only what each vendor publishes, read on 6 November 2026. "Not stated" means the page does not say.

Two patterns matter more than any single row. First, the software makers now sell forms themselves, so a third-party tool has to earn its place with something the built-in route lacks: Spanish forms, signing any PDF, auto-send rules by procedure code, a kiosk flow, or payments in the same packet. Second, for server systems the write-back runs through a program on your server. Open Dental calls it the eConnector and says it "is used by, and required, for all eServices"; NexHealth calls its program the Synchronizer. If that machine is off, asleep or blocked, forms stop arriving. That is the IT side, and it is covered below.

If you are still choosing between systems, the dental practice management software selection guide covers the hosting question, and the Dentrix vs Open Dental comparison covers the two most common server systems. Of the vendor pages read for this guide, only Open Dental's fee page publishes module prices, which is why its numbers appear above and the others read "Not stated". Whichever route you pick, the server, workstations and imaging bridges it depends on are the layer covered by dental practice management software support.

Digital dental forms compared (2026): the add-on tools

Add-on forms tools sit beside your practice software and send patient answers into it. This guide compares NexHealth, Yapi, mConsent, Adit, Dental Intelligence and Henry Schein One's own Forms, with Jotform as the generic option. The decisive column is not the form builder; it is whether the vendor says, in writing, which fields write back.

Vendor pages read 6 November 2026. Integrations, prices and wording change; confirm the write-back fields, the signature method and the business associate agreement in writing before you buy.

Built into the practice software

Henry Schein One Forms for Dentrix and Ascend, Open Dental Web Forms and eClipboard, Curve Smart Forms, Denticon's digital forms and SoftDent eForms. The data lands in the system's own fields because the vendor owns both ends. The trade-off is fewer options: Open Dental's Web Forms, for example, only handle sheets of type PatientForm or MedicalHistory, and consent forms go through the kiosk or eClipboard instead.

Best for: offices that want one vendor, one support line and no extra program on the server.

Full add-on platforms with named write-back

NexHealth, Yapi and mConsent name the systems they write into and describe the fields. They add auto-send rules by appointment type or procedure code, Spanish forms, text-to-phone completion and signing of any PDF (treatment plans, financial agreements). They install or connect through a sync program, so they add one more moving part on the server and one more business associate agreement.

Best for: offices on Eaglesoft, or any office that needs auto-send, Spanish forms or any-PDF signing.

Front-office suites where forms are one module

Adit and Dental Intelligence sell forms inside a wider suite (scheduling, reminders, payments, analytics). If you are also shopping for those, the forms module comes along; if not, you are paying for a suite to get forms. Online booking is its own decision, covered in dental scheduling software compared, and texting and recall tools in dental CRM software for practices.

Best for: offices replacing several front-office tools at once.

Generic form builders

Jotform and similar tools make good forms quickly, but the answers do not land in the chart unless someone builds and maintains an integration. Jotform's own FAQ says connections run "via Zapier and open API". For a dental office that means retyping or a custom link that nobody owns when the person who built it leaves.

Best for: a non-clinical form (job application, vendor intake) that never needs to reach the patient record.

Are e-signatures on dental consent forms valid?

In general, yes. Under the federal ESIGN Act, a signature "may not be denied legal effect, validity, or enforceability solely because it is in electronic form" (15 U.S.C. 7001(a)(1)). What a dental office has to get right is not whether a touchscreen signature counts, but whether it can show who signed, when, and which document version.

That is where the capture method matters. Open Dental's manual is unusually frank about it: "Signatures created using a mouse or clicking the signature box are still valid electronic signatures, but with a mouse signature or click alone, it is not possible to verify the person signing." Signing with a stylus records "information about the plotted points", and each signature is linked to the data it applies to: "if the data changes, the signature is invalidated or cleared". A Topaz pad, a tablet with a stylus, or a form app that texts a one-time code to the patient's phone before showing the form (eClipboard's "Require patients to complete authentication before showing sheets" sends a 6-digit code) each add evidence of who signed.

The HIPAA Security Rule does not have an e-signature section, but four of its technical standards apply to the systems a forms and signature workflow runs on. 45 CFR 164.312 requires "Unique user identification", "Automatic logoff" of an idle session, "Audit controls" that "record and examine activity in information systems", and "Person or entity authentication". Read with your compliance advisor, that maps onto the project like this: every team member signs in as themselves on the tablet and the practice software, the kiosk locks itself between patients, the forms tool keeps a log of who imported what, and patient identity is checked at check-in or by code before a form is signed.

Record retention is set by your state dental board, not by the forms vendor, so ask the board for the period that applies to patient records. What the federal rules do fix is the six-year retention of your own policies and documentation: 45 CFR 164.316 says to "Retain the documentation required by paragraph (b)(1) of this section for 6 years from the date of its creation or the date when it last was in effect, whichever is later", and 164.530(j) says the same for Privacy Rule documentation. Your signature policy and the procedures around it are the kind of documentation that rule covers; ask counsel whether your consent templates and form versions belong on the same schedule.

What should you scan, and what should you stop scanning?

Scan what arrives on paper and belongs in the patient record; stop printing things only to sign and scan them; and stop scanning paper your software already holds electronically. For old charts, scan active patients on demand before their next visit, archive the rest under your retention rule, and never start a project to scan every chart in the building.

Scanning is where many paperless projects quietly fail, because it has no natural end. The decision table below gives each kind of paper a rule.

Three habits keep the scanning queue short. Set the scan to the record, not to a desktop folder, so nothing has to be renamed and moved later. Scan at the moment the paper is handled (payment entry, check-in), not in a Friday batch. And give every kind of document one image category, so the chart does not become a folder of "Document 1" to "Document 40".

Scan settings matter for storage and for readability. Open Dental's recommended defaults are "Documents: 150 dpi", "Photos: color, 300 dpi", grayscale for documents, and a JPEG quality of about 40 after scanning ("A typical setting is 40"); single pages save as JPEG and multi-page scans from a document feeder save as PDF. Those settings are per workstation, so the scanning PC has to be set up once by whoever installs the scanner.

Which scanner should a dental office buy?

Buy a sheet-fed scanner with an automatic document feeder, duplex scanning and a TWAIN or WIA driver, from a model your practice software maker lists as working. A network model lets several workstations scan without swapping cables. Avoid scanners that only scan to PDF through their own software, because dental software expects to drive the scanner itself.

Keep a flatbed only if you still scan film, photos or odd-sized items; for everything else the document feeder does the work.

TWAIN is the reason the driver matters more than the brand. The TWAIN Working Group describes its purpose as "to provide and foster a universal public standard which links applications and image acquisition devices". Your practice software talks to the scanner through that standard (or Windows' WIA), so Open Dental's advice applies to every system: "If the scanner doesn't work outside of Open Dental, it will not work inside of Open Dental", and if it came without a TWAIN or WIA driver, "install a generic TWAIN driver".

Open Dental's scanners page lists models "known to work for duplex (multi-page) scanning": the Ricoh (formerly Fujitsu) fi-8170, fi-8270 and fi-8040, and the Epson DS-320 and WorkForce DS-510. It also lists problems: the DocketPORT 488 ("Multi-page scanning doesn't work") and the Fujitsu ScanSnap, which "does not have a flatbed for radiographs" and "uses OCR (Optical Character Recognition) and advanced software to scan directly to PDF instead of JPG". As an example of a current network model's published spec, Brother's ADS-4300N lists two-sided scanning "up to 40ppm", an "80-page capacity auto document feeder", a "built-in Ethernet network interface", driver support for "TWAIN, WIA, ISIS, and SANE", and scan destinations including a Windows network folder and SFTP. Check the current list for your own software before ordering, because the makers change model numbers often.

Two driver rules from the field. A dental-only IT provider wrote on an MSP forum in January 2025 that the "majority of our calls are about scanners" and advised: "Don't update .net, twain, drivers for the first 3 months." Open Dental says the same more carefully: newer drivers "can cause unpredictable scanning results (Open Dental hanging after one scan, or Open Dental taking up 50% of the CPU waiting for the scanner, etc.)", and "installing an older more stable driver can sometimes fix the issue". Treat scanner drivers like dental software: pin the version that works, and change it on purpose, not through automatic updates. If the front-desk printer is also misbehaving, the dental office printer troubleshooting guide covers the Windows side of the same desk.

Where do scanned documents and signed forms actually live?

In a server-based system, scanned documents and signed forms live in a folder on your server, not inside the database. Open Dental stores them in the A to Z folder; Dentrix keeps them in the Document Center. Cloud systems hold them in the vendor's cloud. In every case the store grows forever and must be in the backup.

This is the fact that catches offices a year after going paperless. The database backup that IT reports as "successful" every night may not include the document folder, because the images are files beside the database, not rows inside it. Open Dental's manual says the A to Z folder (default name OpenDentImages) is "typically found on the C drive of the server" and describes it as 26 lettered folders plus folders "for email attachments, email images, EOBs, forms, provider images, reports, sheet images, and wiki images", and warns: "Once recognized by Open Dental, do not rename or move the files, or Open Dental will not know where to find them." Storing images inside the database was an older option that "Most users did not use" and that "is not available for new users".

Dentrix sizes the problem for you. The Dentrix System Requirements 2026 (Henry Schein One, April 2026) says that for a dedicated Dentrix server "40 GB is an estimate for the space that might be needed for patient images or patient records that are stored in the Dentrix Document Center", that systems being upgraded "should have at least 60 GB of free space", and recommends "more than 10 percent free space on all physical drives". Treat those as starting points: an office that scans every EOB and photographs every insurance card will pass them.

How to estimate your own growth without guessing: scan twenty real documents at your chosen settings, read the folder size, divide by twenty, and multiply by the pages you expect per month (EOBs, referrals, cards, consents). Add intraoral and extraoral images separately, because they dwarf scanned paper. Then ask your IT provider for three numbers in writing: free space on the drive that holds the document store today, the date the store will fill at the current growth rate, and whether the nightly backup job includes that folder. The dental software system requirements guide covers the server sizing behind those numbers, and the dental data backup guide covers how to prove a restore.

The federal floor for that last question is explicit. 45 CFR 164.308(a)(7)(ii)(A) requires a "Data backup plan" to "create and maintain retrievable exact copies of electronic protected health information", and (B) a "Disaster recovery plan" to "restore any loss of data". A signed consent that exists only in a folder outside the backup set is hard to call a retrievable exact copy. Ask for a test restore of one scanned document, not just the database. If a scan or signed form has already gone missing, how to restore a deleted patient file or X-ray walks through the recovery order.

For cloud practice systems the storage question moves to the vendor, but two local pieces stay: the scanner still needs a Windows PC with a driver, and the office still needs an export path. Ask the vendor how you would get every signed PDF and scanned document back, in bulk, with patient identifiers, if you ever leave.

The IT side: tablets, Wi-Fi, kiosks and the connector on your server

Behind every forms tablet IT sets up four things: a device enrolled to the practice software and locked to the app, Wi-Fi where the tablet is used, a connector service on the server that stays on, and clocks that agree. When forms stop arriving or a tablet fails, the fault is usually one of those four, not the forms software.

The connector. Open Dental's eConnector "is used by, and required, for all eServices to facilitate communication between Open Dental's secure servers and the office". It installs on the server and creates its own firewall rule ("OpenDental EServicesListener"); if the rule is not created, Open Dental says to "run the eConnector as an admin". When a tablet and the server are on the same local network, traffic stays local; "When the networks differ, traffic is sent via Open Dental HQ instead", which means a tablet on the guest Wi-Fi works, but by a longer route. NexHealth's Synchronizer and the sync programs of other add-ons play the same role. Whoever owns the server has to know these programs exist, exclude them correctly in antivirus, and check them after Windows updates. The service also needs the right account: Open Dental's troubleshooting page suggests updating the eConnector service "to match the server's administrator credentials, rather than running the service as a Local System account" when check-ins crash.

Device enrolment. "Each tablet needs to be enabled in Open Dental before it can be used for eClipboard", through Device Manager, where staff can also see each device's last eClipboard login and disable it with one click. That list is your tablet inventory: a lost or retired tablet is disabled there, and the person who manages dental employee IT onboarding and offboarding should own it. Lock the tablet to the app (Open Dental's setup page says to enable Guided Access on iOS or Pin Windows on Android), and on a Windows kiosk set the close password.

Wi-Fi. Open Dental's troubleshooting page records a failure that surprises every office the first time: "Some offices have reported issues using eClipboard in radiograph labs. The same radiation shielding that blocks X-rays will interfere with Wifi connections." Lead-lined operatories and pano rooms need their own access point or a wired alternative, and the waiting room needs coverage that holds when ten phones join. Put patient-facing tablets on their own network segment, separate from the server and imaging PCs, with access to the connector only. If the signal already drops, start with why dental office Wi-Fi keeps dropping; if the office is new or being refitted, plan the access points inside the dental office network setup.

Clocks. eClipboard will not find today's appointment if the server and the tablet disagree about the date: "Verify the date and time is correct to their time zone on the server, and the mobile device (iPad/Tablet)." The same applies to the time stamp on every signature. Sync both to a time source and check it after a daylight-saving change.

Hardware choices. Open Dental's eClipboard 25 app needs iOS 15 or Android 7 at minimum and recommends a 10-inch or larger display; it does not run on Windows tablets, while the Windows Kiosk runs on a PC or Windows tablet. Buy a wipeable case and a stand, keep a spare tablet enrolled, and put the scanner on a PC that stays on. The computers themselves are a separate purchase; the dental servers and workstations page describes the machines Legend supports. Email is the one paper replacement to keep off the tablet: patient documents go through the practice software or the forms tool, never as attachments, and the HIPAA email for dental offices guide explains why.

Accounts. Mobile Settings in Open Dental hold the credentials every tablet uses to reach the database; forms tools have their own admin accounts. Record both in the practice's account list, and keep the forms vendor logins in the same password manager your staff accounts already use, so they are changed when a team member leaves.

How do you roll out a paperless dental office in 90 days?

Run it as a 90-day project with one owner at the front desk and one on the IT side: inventory the paper, choose the forms route, prepare the server, Wi-Fi, tablets and scanner, pilot with one provider for two weeks, then go live with a rule for old charts. A five-step acceptance test decides when it is finished.

1. 1. Weeks 1 to 2: count the paper. For two weeks, tally every piece of paper by type (new-patient packets, history updates, consents, EOBs, referrals, cards, printed treatment plans). The tally sets the scanner size, the storage estimate and which forms to build first.
2. 1. Weeks 3 to 4: choose the route and sign the agreements. Pick the built-in route or an add-on using the tables above. Get the write-back fields, the signature method and the export path in writing. Sign the vendor's business associate agreement before anything is installed. Decide which staff account the installer will use and when it will be removed.
3. 1. Weeks 5 to 6: IT preparation. Server: check free space, confirm the document folder is in the backup, install the connector or sync program as the vendor documents, add the antivirus exclusion. Network: survey Wi-Fi in the waiting room and every operatory, including lead-lined rooms; create the tablet segment. Devices: enrol tablets, lock them to the app, set the kiosk password, time-sync everything. Scanner: install the model your software lists, set the document defaults on the scanning PC, pin the driver.
4. 1. Weeks 7 to 8: build and pilot. Build the new-patient packet, medical history update and the three most common consents, with mobile layout where the system needs it. Pilot with one provider's schedule: every new patient gets the text link, every returning patient reviews history on the tablet, every consent is signed on screen. Staff review each form before import; Open Dental's import screen exists for a reason ("Always verify any data with the patient and make sure the correct rows are flagged before you import").
5. 1. Weeks 9 to 10: fix and extend. Fix what the pilot found (usually form wording, Wi-Fi in one room, and a driver), then extend to every provider. Switch EOB and referral handling to scan-at-the-moment.
6. 1. Weeks 11 to 12: go live and set the chart rule. Remove the clipboards. Publish the old-chart rule: scan essentials before the next visit for active patients; archive inactive charts under the retention period your state board sets. Schedule the first quarterly check of storage growth and backup contents.

The acceptance test. On a real appointment, with the vendor on the phone if needed: (1) a new patient completes the packet on their phone and the demographics, medications and allergies appear in the chart without retyping; (2) a returning patient updates history on the tablet in a lead-lined operatory without a drop; (3) a consent signed on the tablet opens from the chart with the signer's name, date and time, and shows as invalid or re-signed after an edit; (4) an EOB scanned at payment entry opens from the claim; (5) IT restores one scanned document from last night's backup to a test location. Pass all five and the office is paperless; fail one and the project is not done.

What to verify before you sign

Before you sign with any forms, signature or scanning vendor, verify these items in writing. They are the points where the demo and the first month differ most.

• • Write-back fields, by name. Which fields land in the chart automatically (demographics, insurance, medications, allergies, conditions), which need staff review, and which arrive only as a PDF.
• • Your exact practice software and version. The vendor names your system on its site, and the version you run is supported. Henry Schein One's Forms page, for example, requires "the latest version of Dentrix or Ascend".
• • The signature method and its evidence. Stylus or pad, time stamp, invalidation on edit, and whether the signed PDF shows the signer's identity check.
• • The server-side program. What installs on the server, which ports or firewall rules it needs, which account it runs under, and who restarts it after updates.
• • Business associate agreement. Signed before installation; covers the vendor's sub-processors; names what happens to your data at termination.
• • Export at exit. How you get every signed PDF and every scanned document back in bulk, with patient identifiers and dates, and in what format.
• • Price lines. Per location or per provider, texting fees for links sent to phones, kiosk or tablet licences, OCR for cards, set-up fees, and the minimum term. Open Dental is the one vendor here that publishes module prices on its fee page; for the rest, get the quote in writing.
• • Devices. Which tablets and operating system versions are supported, whether Windows tablets work, and which signature pads are named.

What to ask your IT provider about going paperless

How Legend Networking can help

Legend Networking is a Dallas-based dental IT company that has served over 3,500 practices since 2004. Legend supports the IT environment for the practice software Dentrix, Eaglesoft, Open Dental and Archy, and for the imaging systems DEXIS, Vatech, Carestream, Planmeca/Romexis and Dolphin Imaging, which is the layer every forms tool, signature pad and scanner connects to.

Offices outside Texas can find their market under dental IT support in your city; practices nationwide are supported remotely.

The author, Ian Lynch, has 22 years in dental IT and oversees the NOC, onsite dispatch and client technology roadmaps. Legend holds a 4.8 rating from 173 Google reviews. You can see the kind of groundwork a front office starts from in a practice opening that covered technology integration and practice workflows. If going paperless is part of a wider review of who looks after your server, software and network, start with managed IT services for dental practices; the wider technology picture for a practice is in dentist office technology explained.