Department
Medical Records (MRD)
Medical records is the department that inherits every shortcut the rest of the hospital took. An incomplete note, an unsigned form and a summary nobody wrote all become one department's problem, months after the patient went home.
A medical records department cannot fix a record after the fact. It can only find out, late, that the record was never made.
Impact and action
Deficiency is chased by hand.
- A clerk reads through files, lists what is missing, and walks the list to the consultants. The loop takes weeks and restarts every month.Atlas assembles the record and tracks deficiency on it, so an unsigned note or a missing summary is an open item against a named person from the day it appears.Atlas
- Completeness is reported as a percentage nobody can reproduce.Falcon reads completeness off the record itself, by ward, by consultant and by document type, with the source of every number visible.Falcon
Coding happens after the record closes.
- Diagnoses and procedures are coded weeks later by someone reading a discharge summary, which is the least reliable document in the file.Coding attaches at the point of entry, against a structured diagnosis and procedure list the clinician chose from rather than a phrase somebody has to interpret.AtlasForge
- A scheme or insurance claim is built from a code that disagrees with the clinical record, and the deduction arrives two months later.Vault packages the claim from the same record the code came from, so the clinical fact and the billed fact are one fact.Vault
Retrieval is a physical search.
- A court requisition, an insurer query or a patient request means finding a file, photocopying it and logging the copy in a register.The record is retrievable by patient, visit, date or document type, and every disclosure is a logged action against a named person.Atlas
- Whether a record was ever opened, and by whom, is unanswerable, which is the first question in any dispute.Cirith keeps a complete access log, and an administrator can ask it about one patient or about one staff member and get a list.
The tools this department lives in.
Read top to bottom. Each tag is a tool inside Pensieve, and the line beside it is what that tool does in a medical records department specifically.
| Tool | What it does in this department |
|---|---|
| Atlas | Record assembly, deficiency tracking, the discharge process, document attachment and the consent and access history. |
| Falcon | Completeness by ward, consultant and document type, coding coverage, and retrieval turnaround, each traceable to its source. |
| Vigil | The information management chapter of the accreditation file, internal audits, and policy acknowledgement by staff. |
| Glyph | The forms the record is made of, locked on completion, versioned, so an old filled form matches its own design. |
| Quest | Deficiency follow-up, retention review dates and periodic audit tasks as due items with a named owner. |
| Vault | The claim pack built from the same record the coding came from, including scheme and payer specific formats. |
| Westron | Files and documents moving in or out of the hospital, with a forensic trail of every exchange. |
| Raven | Requests and reminders to clinicians about outstanding documentation, on an audited channel. |
Retention and disclosure
What the department is legally holding.
Medical records is where the hospital's data obligations become concrete, and in India those obligations are moving.
- Retention periods differ by document type, by patient age and by whether the case is medico-legal. Retention is a property of the record, and a review date is a due task rather than a rule somebody remembers.
- Disclosure to a court, an insurer, a scheme or the patient themselves is a logged action with a named person, a reason and a timestamp. That log is the department's protection as much as the patient's.
- The data protection rules give a person rights over their own record, and they collide with retention duties for medical records. The resolution is policy, and policy needs a system that can state, for any record, what is held, why, and for how long.
- ABDM linkage is offered and remains voluntary. Sharing under it is consent based, and the consent artefact is part of the record rather than beside it.
Read the compliance file, how access is decided and what is logged.
Published research
What the literature already measured.
Findings about records and information transfer, each with its study and a link. None of it is a Pensieve result.
- Across 73 studies, direct communication between hospital and primary care physicians occurred in 3 to 20 percent of cases, and a discharge summary was available at the first follow-up visit 12 to 34 percent of the time.Kripalani S, LeFevre F, Phillips CO, et al. JAMA, 2007. Summaries were frequently missing results pending at discharge.
- India's national auditor found 749,820 scheme beneficiaries registered against one mobile number, and 78,396 instances of a single patient recorded as admitted to more than one hospital at the same time.Comptroller and Auditor General of India, Report No. 11 of 2023. It is a record integrity finding rather than a clinical one.
- In a 2025 study of the national and state assurance schemes in Maharashtra, settlement ran from three months to a year against a thirty day guideline.Marathe S, Hunter BM, Chakravarthi I, et al. BMC Health Services Research, 2025. Claims stalled at verification, which is a documentation stage.
Where the record can travel, and on whose authority.
Federated, rather than pooled
In a group of hospitals, each site keeps its own record and its own governance. A record is read across sites under an access rule the group has set, and it stays where it was made. Nothing is copied into a central heap that no single site is accountable for.
Under consent, out of the building
Sharing under the national digital health framework is consent based and voluntary, and the consent artefact travels with the exchange.
The quality office
Completeness, coding and retention are three chapters of the accreditation file, and all three come out of the department's own daily work.
Billing and the payer desks
A claim built from the coded record is a claim that agrees with the clinical file, which is what survives a deduction query.
A request arrives
What answering one should look like.
The request
A court, an insurer, a scheme or the patient asks for a record. The request is logged with its requester, its scope and its authority.
Authority
The department checks the basis for disclosure. Cirith decides whether the person preparing it may open what they are being asked to send.
Assembly
The record is assembled by patient, visit and document type, including the forms as they were filled, against the designs in force at the time.
Disclosure
The pack goes out with a logged action naming who prepared it, what was included and when it left, which is the entry a dispute later turns on.
This is the department's core output. Everything else it does exists so that this can be done quickly and defended afterwards.