HealthcareFree
Outside Records Chronology and Gap List
Every dated event with the page it came from, an index by date and type, and a register of what could not be read.
River's outside records summary reads a stack of scans and produces two things: a chronology of every dated event with the page it came from, and an index by date and document type. Nothing gets interpreted. A discharge summary becomes a dated entry naming the discharge summary, not a judgement about what the discharge meant. Two separate registers come with it: the pages that could not be read, and the documents the stack refers to but does not contain.
What ranks for this search is record summarization sold to litigators, or advice on reading a chart faster. Both produce a narrative, and a narrative is where guessing hides. A page too dark to read becomes a smooth sentence. A procedure referenced by a discharge summary, with no operative report anywhere in the stack, disappears entirely. The two registers exist because the useful half of a received stack is often the half that is not there.
This is for whoever preps the chart before the appointment: records staff, a medical assistant, a nurse, sometimes the clinician at seven in the morning. It reads and arranges, and it never decides what the records mean. The gap register is a request list, so it goes out before the visit rather than being discovered during it. What goes back out afterwards is a referral letter or consult reply. Where the stack exists to support an authorization, a criterion by criterion map comes next.
Filing the stack changes what you owe on it
Outside records stop being someone else's problem the moment you use them. A designated record set includes anything used, in whole or in part, to make decisions about individuals, so a stack you file and rely on falls inside yours. Then the awkward part: a covered entity may deny an amendment request for a record it did not create, unless the originator is no longer available to act on it. Keeping the received pages as their own provenanced layer is what makes either answer possible.
Two more rules shape the format. Hospital record entries must be legible, complete, dated, timed and authenticated, which is why an unreadable page is a finding to record rather than an obstacle to work around. And CMS tells its reviewers that the date and author of any amendment, correction or delayed entry should be identifiable, with the addenda permanently denoted. A chronology built from someone else's records is a derived document, so every line on it names its source page.
Wrenfield Nephrology received 88 new patient stacks in a quarter, 6,410 pages, an average of 73 each. The chronology flagged 212 pages it could not read and 147 documents the stack referred to but did not contain. Sixty-one of those 147 mattered for the coming visit and were requested in advance, and 44 arrived in time. Consults rescheduled because a record was missing fell from 19 the previous quarter to 6. Not one of the 212 unreadable pages was guessed at.
How it works
Send the stack
Scanned PDFs, faxes, loose pages. Nothing needs to be searchable or in any order.
Name the purpose
A consult, a transfer, an appeal. It changes which dates the chronology puts first.
Read the chronology
Every dated event with its source page, plus the index by date and document type.
Work the registers
Unreadable pages get re-requested by page number. Missing documents get chased before the appointment.
What you get
- A dated chronology where every entry names the document and page it came from
- An index by date and document type, so retrieval takes seconds rather than minutes
- A register of every page that could not be read, with the reason why
- A list of documents the stack refers to but does not actually contain
- The gap list written as a records request, ready to send before the appointment
- Nothing interpreted: dates, providers and document types, as the received pages state them
Common questions
Does it read handwriting?
Sometimes, and it says which times. A legible handwritten note gets transcribed with its page number so you can check it. A page that is genuinely unreadable goes on the register with the reason, whether that is the handwriting, a dark scan or a fax of a fax. It never produces a best guess.
How does it know a document is missing?
Because the stack says so. A discharge summary names an operative report, a consult letter names a biopsy result, an order names a study. Each of those is a reference to a document, and the chronology checks whether the referenced document is actually in the pages you sent. What is referenced and absent goes on the second register.
Does it summarize what the records mean?
No, and that line is the whole design. It records that a discharge summary dated 6 March exists and what it states, not whether the hospitalization went well. Reading a chronology and deciding what it means are two different jobs, and only one of them belongs to software. The clinician does the second.
Can a patient ask us to change these records?
They can ask, and the answer has a specific shape. A record you did not create can be denied amendment, unless the patient gives reasonable grounds to think the originator can no longer act. Either way the request itself gets filed, alongside whatever the records request process already tracks.
What if the stack is 900 pages?
Then the index matters more than the chronology. Long stacks are mostly duplicates, billing pages and repeated flowsheets, and the index by date and document type is what makes the rest findable. The chronology stays proportionate to the events, not the page count, and the source page number sits on every line.
What goes back out to the referring office?
A reply, and it is a separate job. The chronology tells you what you received and what you are still waiting for. Turning your own findings into something the referring clinician can act on, structured around the question they asked, is what the referral letter and consult note handles.
Do the records need identifiers in them?
No. Strip names, numbers and dates of birth first if that suits your policy, because the chronology works from document types and dates rather than identity. Keeping one consistent label for the patient across the stack is the only requirement, so entries from three different offices land on the same timeline.
Outside Records Chronology and Gap List
Fill in the form and your workspace opens with the work already underway.