People & Records
Replace file rooms and scattered reports with a single, chronological, read-only record that spans OPD, IPD, OT, diagnostics, billing and insurance.
In short
Medical records (MRD) software organises a hospital's patient files into one searchable record per person. DevOrbital HMS's MRD module builds a chronological, read-only lifetime record across OPD, IPD, OT, diagnostics, billing and insurance, with completeness tracking, a duplicate UHID merge queue, a retention register and formal record-request handling.
The problem
A patient's OPD slip, lab report, discharge summary and bill sit in different places, and nobody sees the whole story in one view.
Missing discharge summaries, signatures or reports are discovered only when a record is requested months later.
The same person registered twice ends up with two partial histories, which is a clinical risk and a billing headache.
Record requests from patients, insurers or courts are handled by phone, and nobody knows what has been issued or when files may be disposed of.
How it works
OPD, IPD, OT, lab, billing and insurance entries are captured in their own modules.
Everything is tied to the patient's UHID in one chronological record.
MRD staff see which episodes have missing documents before sign-off.
Suspected duplicate patients are reviewed in a merge queue.
Record requests are logged, reviewed and fulfilled formally.
Archived records are listed in a retention register.
What's included
Use it on its own — or connected
MRD can be adopted alone by hospitals that want to organise and archive records before changing anything else. The module is strongest when the clinical modules also run on DevOrbital, because the lifetime record is then assembled automatically from OPD, IPD, OT, diagnostics and billing entries, with no scanning or re-entry.
Pairs naturally with:
Who it's for
Illustrative scenario · not a customer story
Closing a discharged file with a missing summary
MRD in-charge
The MRD in-charge reviews the list of recently discharged patients and sees one file marked incomplete: the discharge summary is missing. She sends it back to the ward, and the summary is added the same day. Meanwhile, the merge queue shows two registrations that look like the same patient. She compares them, confirms they match and merges them under one UHID. Later, an insurer's record request arrives, and she logs it and issues the record from the single timeline. (Illustrative scenario.)
MRD stands for medical records department, the unit that stores, protects and retrieves patient records. MRD software digitises that job. Instead of a room of files indexed by number, the hospital has a searchable record for every patient that shows their history in order.
In DevOrbital HMS, the MRD module is not a separate scanning exercise. It builds the lifetime record from the entries made in OPD, IPD, OT, diagnostics, billing and insurance. The result is a read-only, chronological view of what happened to each patient and when. For the definition, see the MRD entry in our glossary.
Patients return. They may come to OPD for a cough this year and be admitted for surgery next year, and the clinician needs to know about earlier allergies, investigations and procedures. When records are split by department, that history is either missed or retrieved slowly.
A single lifetime record fixes this. Every visit, admission, test and bill is tied to the same UHID and shown in order, so a doctor can read the story rather than hunt for pieces. It also supports hospitals that plan to share records under ABDM, because a clean per-patient record is the starting point for any consent-based exchange. Learn how that fits in our guide to ABDM and NABH readiness.
Hospitals usually find missing documents at the worst possible time, such as when an insurer asks for a discharge summary or a patient requests a copy. By then, the clinician has moved on and the gap is hard to fill.
Completeness tracking brings that check forward. MRD staff see which episodes are missing required documents while the case is still recent and can send them back to the right department. Only when a file passes the check is it signed off for archival.
Because the record is read-only in MRD, the archive stays faithful to what was documented. Any change in the source module is logged by the audit trail, so there is a clear history of who changed what and when, which supports internal reviews and NABH-style documentation requirements.
A UHID is the unique health ID a hospital assigns to a patient. Duplicates occur when the same person is registered twice, perhaps with a spelling variation or a new phone number. The merge queue surfaces likely duplicates so a reviewer can confirm and combine them, rather than leaving two partial histories in the system.
Retention is handled through a retention register, which lists archived records so the hospital can apply its own policy and any legal requirements to them. Specific retention periods are set by law, regulation and hospital policy, and should be confirmed with your own advisers.
Requests for records from patients, insurers and authorities are logged formally. Each request has a status, so the team can show what was asked for, what was issued and when.
FAQ
MRD means medical records department. It is responsible for storing, protecting, retrieving and, when appropriate, issuing patient records. MRD software digitises these tasks so records are searchable, complete and tied to a single patient identity instead of kept in paper files.
The lifetime record in MRD is read-only. Entries are made in the clinical and billing modules where care happens, and MRD shows them in one chronological view. This keeps the archive faithful to the original documentation, and changes in source modules are captured by the audit trail.
The system lists patients who may be registered more than once. A reviewer compares the records and, if they are the same person, merges them under one UHID. This brings scattered history together, and the merge is recorded in the audit trail.
It includes a retention register to list archived records and track them against your hospital's policy. Retention periods depend on law, regulation and your own policy, so confirm them with your advisers and configure the register accordingly. Disposal decisions remain with the hospital, supported by the register.
Record requests are logged and tracked formally in the module, so the team can record who asked for what, the status, and when it was issued. This replaces informal phone requests with a traceable process. Requests are handled by MRD staff inside the module.
Records created in DevOrbital modules appear in the lifetime record automatically. Whether and how to digitise older paper files is a project decision made with your team during onboarding, depending on the volume and the value of historical records. Many hospitals begin with new records and digitise older files in phases.
Keep exploring
HMS Basics
Hospital Management System: The Complete Guide for India
● DevOrbital HMS
HMS Basics · 9 min read
What a hospital management system is, what it covers across OPD, IPD, lab, pharmacy and billing, and how Indian hospitals can adopt one step by step.
Read this guideCompliance
NABH and Hospital Software: What an HMS Can and Cannot Do
● DevOrbital HMS
Compliance · 6 min read
How hospital software supports NABH accreditation: medical records, medication safety, access control and audit trails mapped to the 6th edition chapters.
Read this guideClinical Operations
Hospital Discharge Process Delays: Causes and Fixes
● DevOrbital HMS
Clinical Operations · 6 min read
Why hospital discharge takes so long and how to fix it: common causes in Indian hospitals, a parallel workflow, a pending-items list and metrics.
Read this guideTell us about your facility and we will walk you through the modules that fit — one department or the whole hospital.
