Digitising Old Paper Files: A Selective Backfill Plan for Returning Patients
Choose what to scan, transcribe and clinically verify when digitising paper files, with identity controls, a workload model and a reconciled pilot.
A clinic patient number should identify one person's local record consistently over time. Keep it distinct from a visit number, queue token, invoice reference and any national health identifier. Choose a readable format, preserve old references during migration and define how suspected duplicate files are reviewed. The number helps staff find a record; it does not replace identity verification or grant access to that record.
Indian clinics designing a UHID or file-number system, digitising paper registers or combining records from more than one location.
A patient may attend many times, receive several bills and bring reports from other providers. If the clinic creates a new 'patient number' for every visit, staff lose the stable reference needed to find the longitudinal record. If it uses the queue token as the file number, tomorrow's queue can reuse a number that already means someone else.
Define the units explicitly. The patient reference identifies the local person record; the encounter reference identifies a particular episode or visit; the receipt reference identifies a payment document. These may appear together on a printout, but they serve different purposes. Staff should be able to explain which reference a patient should quote when asking for an old file.
The term UHID is used in different systems. Do not assume a format supplied by one hospital is globally unique or interchangeable with another clinic's identifier. Record the issuing organisation alongside any outside reference. Two unrelated clinics can legitimately have a file called 000124; the issuer is part of the meaning.
A patient's changed phone number, address or name should normally be handled as an update to their verified record, not as a reason to invent a new person. Maintain the history and correction route supported by the system. The clinical identity decision must come before a tidy numbering scheme.
On a narrow screen, scroll the table horizontally to read all columns.
| Reference | Question it answers | Common mistake to avoid |
|---|---|---|
| Local patient number | Which person record within this issuing clinic or organisation? | Treating the same digits from another clinic as the same identity |
| Encounter or visit reference | Which attendance or care episode? | Replacing the stable patient reference on every return |
| Queue token | Whose turn is represented in this session's queue? | Using a reused token as proof of patient identity |
| Invoice or receipt reference | Which financial document or payment record? | Assuming a document number uniquely identifies a person |
| ABHA number | Which participant identity in the ABDM context? | Treating it as a local bill number or automatic permission to read records |
An illustrative format such as CLN-000124 is easy to recognise and quote. The prefix can identify the issuing system, while the numeric portion supplies the local sequence. Choose the length from realistic growth and the software's capabilities, not because a particular example looks professional.
If six digits are used from 000001 through 999999, there are 999,999 possible nonzero sequence values. At a fictional 12,000 new registrations per year, dividing 999,999 by 12,000 gives about 83.3 years of nominal sequence capacity. This is only a planning calculation: reserved numbers, imported records and actual allocation rules can reduce available capacity, and return visits should not consume a new patient number.
Do not encode sensitive or changeable facts into the identifier merely to make it informative. A diagnosis, sex marker, phone number or birth date can expose information or become inaccurate. A short non-sensitive issuer prefix is different from a miniature demographic record embedded in every file number.
Preserve leading zeros and test how the reference behaves in exports, spreadsheets, printing, search and spoken communication. A spreadsheet treating 000124 as the number 124 can damage a round trip if the receiving system expects the full string. Ask staff to read an example aloud and enter it from a printed card; avoid easily confused characters where the chosen format allows.
Changing the clinic's public brand or moving premises should not automatically renumber every patient. Decide whether the identifier's issuer remains the same and retain a documented mapping where a genuine system transition requires a new reference. A cosmetic rebrand should not break a patient's old appointment card.
WHO's May 2007 patient-identification guidance supports using at least two identifiers and matching the patient to the intended care. It is international safety guidance, not an Indian rule prescribing the format of a clinic UHID. The clinic needs an approved identification process suited to its patients and services.
A patient quoting a number may have brought a relative's card. A shared family phone number may return several people. Ask appropriate identifying questions and resolve uncertainty before opening or changing the clinical record. Do not use a leading question that simply invites agreement with the name already on the screen.
Provide a workable route for missing cards, uncertain dates of birth, similar names and local-script spelling differences. Those situations are reasons for careful resolution, not for silently inventing a birth date or selecting the first search result. Where uncertainty remains, record it and use the clinic's approved temporary-identification process.
A printed barcode or QR representation can reduce typing, but a successful scan proves only that a value was read. It does not prove the card belongs to the person at the counter, that the record is the right one, or that the operator is authorised to see it. Include the human verification step in the workflow.
Source: WHO Collaborating Centre: Patient Identification, May 2007
The Ministry of Health and Family Welfare's February 2024 explanation describes ABHA as a random 14-digit health identifier and states that its creation is voluntary. That dated explanation provides identity context; it is not evidence that a particular clinic application has a working ABDM integration.
A clinic can maintain its own stable patient reference while recording an appropriately verified external identifier through the supported process. The relationship should be a deliberate link to the correct person, with the issuing system clear. Do not overwrite the local file number simply because an ABHA number becomes available later.
Ask the vendor how an incorrect linkage is corrected and what evidence is retained. Treating a national identifier as authoritative without checking the local patient association can spread a registration error across more records. Likewise, possession of an identifier should not be presented as permission to retrieve every document associated with it.
Keep registration usable when a patient does not have the external reference available, subject to the clinic's applicable process. The operational objective is accurate identity and continuity. This guide does not determine scheme eligibility, current requirements of a particular government programme or the legal basis for a specific data exchange.
Source: MoHFW/PIB: Update on Ayushman Bharat Digital Mission, 6 February 2024
Before importing a paper register, identify the issuing clinic, old reference format and any previous resets. A sequence that restarted each year may require year plus number to identify the old file. Store the original reference as an alias with its source, rather than assuming that the digits alone identify one person.
Use a migration crosswalk that links the source file to the destination patient record only after the association is verified. A file with uncertain ownership remains an exception. Two old files may belong to one person, but that conclusion should follow review rather than matching a phone number or approximate name alone.
In an original example, 500 source files include 480 straightforward verified associations and 20 files requiring investigation. The 20 are not automatically 20 duplicate people. After review, some may represent duplicates, some different patients and some unresolved records. Report '480 mapped, 20 under review' until the evidence supports a more specific conclusion.
For an approved duplicate resolution, preserve the original references, relevant history and trace of the correction through the supported process. Decide which record becomes the continuing record and how staff find it from either old number. Never delete one file merely because two records look similar on a reception search.
Create a synthetic set with two similar names, two people sharing a phone, a changed surname, an old paper alias and identical local digits issued by different clinics. Test registration, search, document output and retrieval using each reference. Include one unresolved duplicate that must remain visible without an automatic merge.
Test allocation when two reception stations register different patients at nearly the same time. The system should produce its supported unique references without requiring staff to reserve numbers in a separate notebook. If a registration attempt has an uncertain outcome, recover the original record before creating another patient simply to obtain a fresh number.
Check whether the visible reference is copied into a URL or public QR code and what access that route permits. A hard-to-guess number is not an access-control policy. Use a synthetic unauthorised account in an approved test environment to confirm the expected refusal rather than probing real patients' records.
Keep the format decision, migration crosswalk and exception process together. The best numbering system is one staff can use reliably while preserving identity over time. Its value comes from consistent meaning and correction, not from an elaborate prefix.
A fictional reception search returns a father and adult daughter under the same family phone. Their local patient references differ, and each has separate visits. Staff confirm which person is attending before selecting the record. When the daughter later changes her number, her existing patient reference and history remain intact. The clinic does not merge the pair or create a new person because the contact detail changed.
Use these prompts in your clinic’s own notes. Record the result, responsible person and next action for each item.
Use a readable, stable format supported by the software and unique within its defined issuer scope. Document what the number identifies, preserve leading zeros and test migration and retrieval. No particular prefix is universally required by this guide.
The stable patient reference should continue to identify the person, while a separate encounter reference identifies the new visit. Creating a new person record on each return fragments the history.
It is a poor sole key because families can share phones and numbers can change. Use a stable patient reference and the clinic's approved identity checks, with a route for ambiguous matches.
They serve different identifier scopes. A supported, verified linkage can coexist with the clinic's stable local reference. Do not treat the external number as a bill reference or automatic authority to access records.
Investigate the association before merging. Preserve source references and relevant history, use an authorised correction process and keep unresolved identity questions visible.
Updated on . Original identifier design and fictional capacity examples. The dated ABHA reference is background, not a current programme-eligibility determination or proof of ABDM integration. No independent clinical or legal review is claimed.
International patient-safety guidance; not an Indian identifier-format mandate.
Dated official explanation of ABHA identity; not a clinic software integration or scheme-eligibility assessment.
Choose what to scan, transcribe and clinically verify when digitising paper files, with identity controls, a workload model and a reconciled pilot.
Evaluate record separation across clinics using synthetic identity, search, document and permission tests; distinguish branch sharing from independent organisations.
Recover uncertain clinic saves through original-record evidence, one accountable retry and reconciled outcomes, including a timed synthetic recovery drill.
Use synthetic similar names, a shared family phone and two legacy aliases to test registration, search and duplicate review. Include simultaneous registrations and an export/import round trip that preserves leading zeros.
Request a clinic demo