US20150310007A1 - Records management system and methods - Google Patents

Records management system and methods Download PDF

Info

Publication number
US20150310007A1
US20150310007A1 US14/791,036 US201514791036A US2015310007A1 US 20150310007 A1 US20150310007 A1 US 20150310007A1 US 201514791036 A US201514791036 A US 201514791036A US 2015310007 A1 US2015310007 A1 US 2015310007A1
Authority
US
United States
Prior art keywords
page
documents
representation
document
data file
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US14/791,036
Inventor
Stephen Schneider
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
MED-LEGAL TECHNOLOGIES LLC
Original Assignee
MED-LEGAL TECHNOLOGIES LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by MED-LEGAL TECHNOLOGIES LLC filed Critical MED-LEGAL TECHNOLOGIES LLC
Priority to US14/791,036 priority Critical patent/US20150310007A1/en
Publication of US20150310007A1 publication Critical patent/US20150310007A1/en
Assigned to MVC CAPITAL, INC. AS SUCCESSOR IN INTEREST TO FIFTH THIRD BANK reassignment MVC CAPITAL, INC. AS SUCCESSOR IN INTEREST TO FIFTH THIRD BANK AMENDED AND RESTATED SENIOR SUBORDINATED PATENT SECURITY AGREEMENT Assignors: DEFENSEPRO, LLC, LEGAL SOLUTIONS HOLDINGS, INC., MED-LEGAL TECHNOLOGIES, LLC, MED-LEGAL, LLC
Priority to US15/398,439 priority patent/US20170116170A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • G06F17/30011
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00Handling natural language data
    • G06F40/10Text processing
    • G06F40/166Editing, e.g. inserting or deleting
    • G06F40/174Form filling; Merging
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10File systems; File servers
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10File systems; File servers
    • G06F16/16File or folder operations, e.g. details of user interfaces specifically adapted to file systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/93Document management systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/93Document management systems
    • G06F16/94Hypermedia
    • G06F17/30067
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00Handling natural language data
    • G06F40/10Text processing
    • G06F40/103Formatting, i.e. changing of presentation of documents
    • G06F40/114Pagination

Definitions

  • the present disclosure relates to records management and, more particularly, to a records management system and method that permit a user to tag, store and/or retrieve pertinent records based on user criteria.
  • Records have long been an important part of everyday life. For example, physicians are required—under various laws—to maintain medical records for a certain period of time. These records can be quite useful in diagnosis and analysis of a patient's condition, particularly when the patient has been seen by multiple doctors.
  • doctors and other professionals may need ready access to pertinent medical records in order to make vital medical decisions regarding a course of treatment for a patient.
  • a shortened time for medical records review may be crucial.
  • doctors may be responsible for numerous patients at a single point in time. Time taken for one patient may mean time unavailable for another. This factor also highlights the need for a more streamlined medical records review.
  • a records management system comprising a location designation module configured to designate an electronic storage location for said each representation of a page; and a data module configured to create an electronic data file that corresponds to said each representation of a page, wherein the electronic data file relates said each representation of a page to a document within the project.
  • the electronic data file includes the electronic storage location for said each representation of a page.
  • the system further comprises at least one workstation configured to receive input of additional data for the electronic data file, the input additional data further including a category for said each representation of a page, a date for said each representation of a page, and a provider for each said representation of a page; and a supplementation module configured to supplement the electronic data file with said input additional data for the electronic data file.
  • the system still further includes a merging module configured to merge said each representation of a page with the corresponding electronic data file for each said representation of a page such that said each representation of a page and the corresponding electronic data file are accessible from a single electronic project file.
  • a merging module configured to merge said each representation of a page with the corresponding electronic data file for each said representation of a page such that said each representation of a page and the corresponding electronic data file are accessible from a single electronic project file.
  • the system includes output that is a summary excerpt for at least one representation of a page.
  • the excerpt includes at least one date, at least one page number and at least one provider associated with the at least one representation of a page.
  • a records management method comprises the steps of designating an electronic storage location for one or more electronic files that represent each page of each document in a project; and creating an electronic data file that corresponds to said each representation of a page, wherein the electronic data file relates said each representation of a page to a document within the project, wherein said electronic data file includes the electronic storage location for said each representation of a page.
  • the method further comprises receiving input of additional data for the electronic data file, and a category for said each representation of a page, wherein the input additional data includes a date for each said representation of a page, and at least one provider for each said representation of a page; and supplementing the electronic data file with the input additional data.
  • the method still further comprises merging said each representation of a page with the corresponding electronic data file for said each representation of a page such that said each representation of a page and the corresponding electronic data file are accessible from a single electronic project file.
  • the method comprises outputting at least one summary excerpt for at least one representation of a page, the summary excerpt including at least one date, at least one page number and at least one provider for the at least one representation of a page.
  • FIG. 1 is a records management system in accordance with one embodiment of the present disclosure.
  • FIG. 2 is a flow chart illustration of a method for records management in accordance with another embodiment of the present disclosure.
  • FIG. 3 is a screenshot illustration of records that have been sorted by date and category in accordance with one embodiment of the present disclosure.
  • FIG. 4 is a screenshot illustration that results from a user query for documents containing a particular search term in accordance with one embodiment of the present disclosure.
  • FIG. 5 is a screenshot illustration of records that have been sorted by location and category in accordance with one embodiment of the present disclosure.
  • FIG. 6 is a screenshot illustration of a viewer application as a user searches and filters selected records in accordance with one embodiment of the present disclosure.
  • FIG. 7 is a screenshot illustration of filtered records as the user prepares to create and print a new record that contains only the filtered records in accordance with one embodiment of the present disclosure.
  • FIG. 8 is an example of electronic output from the records management system and method that includes excerpts in accordance with one embodiment of the present disclosure.
  • the records management system of the present disclosure may be used to tag and store paper or electronic records so that a user can sort, filter, and edit documents that better show the information in which the user is interested.
  • a records management system 100 in accordance with one embodiment of the present disclosure. Included within the records management system 100 is a scanning module 110 that is operatively coupled to a central server 120 . Also illustrated are workstations 130 , 140 , 150 and an optical character recognition engine 160 , each of which is also operatively coupled to central server 120 .
  • connections between the various components of the system 100 may be configured in any number of ways to advance the goals of the present disclosure without departing from the inventive concept.
  • the connections between various components of system 100 may be made via wide area networks (such as the Internet) as well as local area networks (LAN's).
  • the connections may be, without limitation, wireless or wired.
  • Each one of workstations 130 , 140 , 150 may be a conventional personal computer.
  • Workstations 130 , 140 , 150 may be provided, for example, as IBM® compatible computers, APPLE® MACINTOSH® personal computers, UNIX®-based workstations, or any other equivalent computer systems, whether laptop, desktop or otherwise.
  • the workstations 130 , 140 , 150 that may be used to input and receive information from the central server 120 may be personal digital assistants (PDA's) or any other such device.
  • PDA's personal digital assistants
  • the computer system used may also be e.g., a WINDOWS® hand-held device. Some mobile phones may be used to input and receive information, where such capability is available.
  • Each of workstations 130 , 140 , 150 may include a central processing unit (not shown), a display 165 , a mouse 170 , and a keyboard 175 for receiving user input into the system. While three workstations 130 , 140 , 150 are shown in the present illustration, it should be understood that there could be only one workstation, or a large number of workstations depending on the capacity needed for a particular implementation of the system of the present disclosure. Both the mouse 170 and the keyboard 175 may be coupled to the user's workstation so that the user's computer may receive information that is input by him/her, and so that information can be routed through the network 180 to the central server.
  • the networks 180 , 185 in the current illustration are the Internet; however, the networks 180 , 185 may be any other type of wide area network, local area network, or other means by which workstations may communicate with the central server.
  • the exemplary workstations are for descriptive purposes only. Although the description may refer to terms commonly used in describing particular computer systems, the description and concepts equally apply to other processing systems, including systems having architectures dissimilar to those shown in FIG. 1 .
  • the read only memory (ROM) for each of workstations 130 , 140 , 150 may operate to effect permanent storage of information.
  • Random access memory (RAM) for each of workstations 130 , 140 , 150 may operate to effect temporary storage of information.
  • Each of the aforementioned components may be coupled to a bus. Operation of workstations 130 , 140 , 150 may be generally controlled and coordinated by operating system software. With the records system 100 of the present disclosure, the operating system that runs on workstations 130 , 140 , 150 may be, but is not limited to, MICROSOFT® WINDOWS VISTA®, MICROSOFT® WINDOWS XP®, or a version of MAC OS® or UNIX® operating system or the like. ®
  • the principles of the present application can be applied to a computer system using a version of DOS (disk operating system), or other operating system programs.
  • DOS disk operating system
  • An operating system resident in system memory and executed by the CPUs of workstations 130 , 140 , 150 may coordinate the operation of the other elements of workstations 130 , 140 , 150 .
  • Data and software may be provided to and extracted from workstations 130 , 140 , 150 via removable storage media such as, without limitation, a CD-ROM or DVD.
  • Scanner 110 may be, without limitation, an optical character recognition (OCR) scanner.
  • OCR optical character recognition
  • Workstations 130 , 140 , 150 may include a communications adapter which allows the workstation to be interconnected to a local area network (LAN), a wide area network (WAN) or a public network. Thus, records data and related computer program software can be transferred to and from workstations 130 , 140 , 150 via the adapter and network 180 .
  • LAN local area network
  • WAN wide area network
  • public network a public network
  • Portions of the filtering software used to achieve the purposes of the present disclosure can be resident on workstations 130 , 140 , 150 .
  • all of the filtering software may be resident on central server 120 such that web-based storage and filtering may occur.
  • the method 200 may begin with scanning paper documents for each page of a document in a project at step 205 using a scanner; the scanner may operate with and/or be controlled by associated software that provides for image cleanup and optimization.
  • a project as described herein may be composed of a series of related documents.
  • the documents may be deemed related by an end user, or the company/entity providing the scanning services, or a company/entity providing records maintenance services, and/or any other person/entity.
  • the end user of the system of the present disclosure may submit a series of documents for use with the system of the present disclosure.
  • the company that provides the scanning services may group all the documents for a particular end user into a group, thus identifying the documents as a project.
  • the documents in a project may consist of or include, for example, medical and other records related to a worker's compensation injury, a medical malpractice claim or any other grouping of records relevant to a particular goal.
  • Documents in a project may also consist of, or include, for example, medical records for a particular person or all persons in an organization. While the present disclosure describes the project as including medical records, it should be understood that the records could be any number of types of records including but not limited to court files, merger/acquisition documents, employment records or any other type of record whether business or personal.
  • software used in conjunction with the present disclosure may receive and/or create one or more image files for each scanned page of each document in the project.
  • the image file may be created in a tagged image file format (TIFF), a joint photographics expert group (JPEG) format, a portable network graphics (PNG) format, a graphical interchange format (GIF) or other format that is suitable for representing each page of a document in a project.
  • TIFF tagged image file format
  • JPEG joint photographics expert group
  • PNG portable network graphics
  • GIF graphical interchange format
  • Each page may be represented in one or more of these formats or any other suitable image format.
  • system and method of the present disclosure are also suitable for use with records that are not scanned, but are in another format such as a word processing application like MICROSOFT® WORD®, a chart format such as those found in MICROSOFT® EXCEL® or other type of program that can be used to create a record.
  • a word processing application like MICROSOFT® WORD®
  • a chart format such as those found in MICROSOFT® EXCEL® or other type of program that can be used to create a record.
  • the scanning of paper records and the creation of image files would not be necessary.
  • the later-described optical character recognition may not be necessary for translating text from the image files into machine-readable text since the text in electronic file may already be machine-readable.
  • each page of the scanned paper records in the project may be ordered serially and given a serial number, Bates label or other unique identification code for each page.
  • Software resident on the central server and/or workstations may be configured to provide this functionality. The software may begin the serialization process as soon as the pages are scanned or at any other suitable time.
  • software resident on the central server and/or workstations may also designate an electronic storage location for each scanned page of each document in a project. This will allow the end user to easily ascertain the storage location of a particular record.
  • the location may be, e.g., a project folder.
  • software resident on the central server and/or workstations may create a description of each scanned page of each document in a project.
  • software resident on the central server and/or workstations may build an electronic data file for each scanned page of each document in the project.
  • This electronic data file may be or include a hypertext data file. It is important to note that the data record in the hypertext data file (metadata) may be used to relate the page to the particular document within the project.
  • the hypertext data file may include the unique identification codes, image files, locations and page descriptions as well as other information related to the project.
  • the hypertext data file may also include a source indicator for the each scanned page, e.g., the author or the company from which the document originated.
  • the hypertext data file may further include a date associated with the page. The date may be, for example, the date of creation of the page or a date of delivery for the record if the record is from a third party.
  • the hypertext data file may also include a category for each page.
  • the category may be, for example, copy service paperwork in case the records relate to a legal proceeding.
  • the category may also be more generic such as “general or administrative.”
  • the categories may include, by way of example and not limitation, doctor's notes, laboratory, nursing, radiology, reports, and the like.
  • the category may be any category that is useful to the end user.
  • the hypertext data file may be uploaded to the central server so that additional identifying input may be performed by humans as described immediately below. The user may also be permitted to upload his/her own documents and add them to the document group for searching and other functions just as if the newly added documents were in the original set of documents.
  • This metadata and key text may include any pertinent information that would allow the records to be easily retrieved.
  • this metadata and key text may include an author for the pertinent record page; a date of the page, note or report; a category for each record type; and a provider for each record page.
  • This metadata and key text may be added to the hypertext data file.
  • this metadata and key text that were input by the humans at their workstations may be transmitted to, and received by, the central server.
  • tracking of the metadata to the page, document, and project may be preserved.
  • the information input by the trained readers may be included in data fields and/or data types used to sort and filter the records, respectively.
  • step 270 software resident on the central server and/or workstations may supplement the hypertext data file with the input of additional data. Once the hypertext data file is completed for the series of documents it may be merged together into one project file at step 280 .
  • the hypertext data file may be encrypted for privacy reasons, including those related to the Health Insurance Portability and Accountability Act (HIPAA).
  • HIPAA Health Insurance Portability and Accountability Act
  • Software resident on the server and/or workstations may be used to perform encryption functions. Such software is commercially available.
  • the software of the present disclosure may cause represented pages of the project to be passed through an optical character recognition (OCR) engine server at step 290 .
  • OCR engine server may be used to translate handwritten or typed text from the one or more image files into machine-readable text.
  • Software resident at the central server and/or workstations may also index the entire text of the project at step 293 and add that text to the hypertext data file at step 294 so that it may be used for filtering, sorting and editing by the end user at step 295 upon review of the records.
  • This filtering, sorting and editing of step 295 are described in further detail hereinbelow in connection with FIGS. 3-7 .
  • the end user charged with reviewing the records in a project can open the project in a viewer application provided by filtering software used in accordance with the present disclosure.
  • the end user may operate the software on a computer system similar to those of the workstations described hereinabove in connection with FIG. 1 .
  • the end user can sort the metadata by any of the fields, such as description, date of the page, record location, author of the records, etc. This sorting capability permits the end user to “shuffle” together pages from various documents in a project so that the end user may view these pages in a sequence that allows the end user to spot trends the end user may be seeking.
  • FIG. 3 illustrated is a screenshot 300 of records that have been sorted by date and category. As shown, records may be mixed from different sources altogether, and “shuffled” by date and category. A records listing may be found in the background screen 310 . A viewer window 315 is shown in the foreground.
  • the end user may obtain the viewer window that shows the record or page. On that page, the end user can see the category for the record's page as shown at column 330 , the location of the record from which the page came as shown at column 340 , and the original page number in those records (hidden). As shown at background screen 310 , the records have been sorted according to date. Also provided may be a location for the user to type and save notes. Navigation buttons may permit the user continue to page through the current sort, viewing each page in the sequence the user currently has going on the main form.
  • the software of the present disclosure may keep track of where each page being viewed belongs with respect to the original documents submitted.
  • pages may be marked as deleted or suppressed by the user according to data type so that undesired pages are filtered out while the user is viewing the project.
  • data types are the location or author of a set of pages, which can also be easily filtered out of the project using a viewer application provided by the software described in the present disclosure, adding to the efficiency of viewing the project documents.
  • Other data types include provider name and category, which may be filtered such that only records from certain categories or provider are grouped together in a listing.
  • the record pages can be filtered according to date range, and based on whether notes or edits were made to the record page. Additional data types can be identified and filtered in or out as the end user desires. Alternatively, filtering could occur such that pages are marked so that only pages related to data types are displayed.
  • Text searches can be performed within the viewer application provided by the software described in the present disclosure.
  • a search can be performed of both the scanned text of the record pages, and the metadata that was created.
  • the viewer application may build a new subset of pages where the text appeared, and display the list according to the existing sort order and filter the user had in place at the time the search was performed. This helps narrow down the pages the user must read when looking for the trends or evidence that the end user seeks.
  • Notes may be typed for any page within the provided viewer application and saved to the metadata file. This data may be included in subsequent searches.
  • the metadata for the pages that was originally created as part of the service can be edited and saved into the project by the end user.
  • the end user of the viewer application can build a custom set of pages that is sorted and filtered just the way they want to see them. They can then create a new PDF document of the results which can then be printed, saved to disk, emailed, etc.
  • the subsequent PDF can be scanned using an OCR scanner, and can include custom watermarks/stamps and page numbering schemes.
  • the filtering software described herein may be a desktop application and a web application (when the documents are stored on a web or file transfer protocol (ftp) site).
  • ftp file transfer protocol
  • FIG. 4 illustrated is a screenshot 400 .
  • the user has entered a search query for the record pages that contain the term “abdominal” as indicated at text box 410 .
  • the user has double-clicked to get the page in the records where the word “abdominal” appeared.
  • the word “abdominal” did not appear in the records.
  • a hand-written note is shown with the word abdominal abbreviated thereon as “abd.”
  • search engines might not have found this word.
  • the “Search for” textbox may be used with a search engine style of syntax for query commands Search commands can be used on the review data, OCR data from the images themselves, and/or a combination of both.
  • the viewer application may include a full search engine. Wildcards may be used, partial searches, fuzzy searches, etc. may all be included in searches performed. Search commands may be performed using a variety of query syntaxes. The query can range from single term searches to more complex search queries involving wildcards and Boolean operators. For example, where a user wishes to search for the term “knee”, the viewer application should display results of all record pages and/or the pages' metadata that contain the word “knee.” The user may also search for the phrase “left knee.” In this case, the viewer application would display all pages and/or metadata that contain the phrase “left knee.”
  • Various fields of data for the record pages can also be searched. For example, the user could perform a search of all records that contain knee in the title field using a “title:knee” query. Wildcard searches may be performed by inserting a wildcard indicator such as “?” or “*”. For example, where a user enters the query “abdom*”, the search results would include pages that contain the word “abdomen” and “abdominal.”
  • Users may also perform fuzzy searches which will include results for terms having the same or similar spelling. For example, if the user wishes to search for “abdomen,” but spells it incorrectly as “abdomen,” the search results should include pages that include the word “abdomen.”
  • the user may restrict searches to particular ranges using a range query. For example, the user may search for pages that have particular dates associated therewith. If a user only wishes to see those results that are associated with the year 2006, the user could input the search query “date: 20060101 TO 20061231.” It should be noted that other range searches may also be available to the user.
  • Boolean operators may also be used as search queries in accordance with the present disclosure. For example, if a user wishes to pull all pages that contain the terms “knee” and “abdomen” the user may input the search query “knee or abdomen.” The results should include all pages that contain the term knee, as well as all pages that contain the word “abdomen.” If the user wishes to view all pages that contain the terms “knee” and “abdomen” together, the user may input the search query “knee and abdomen.” The results should include all pages that contain the term “knee” and “abdomen” for a single page.
  • search queries may be used in accordance with the present disclosure. For example, the user may not wish to view certain pages and filter them out. If a user wishes to view all pages that contain knee, and is curious but not set on getting all the results that contain “left” as well, the user may input the search query “left+knee” to accomplish this result.
  • FIG. 5 illustrated is a screenshot 500 that shows a viewer application provided by filtering software in accordance with one embodiment of the present disclosure.
  • the “Filter” drop-down menu at text box 510 there are three sources of records.
  • the user has chosen not to view or search the personnel records as indicated by unchecked text box 520 .
  • the “Records by Location & Category” tab has been selected as indicated by user selection of tab 530 , the records are displayed in this manner using these data types.
  • FIG. 6 illustrated is a screenshot 600 that shows the viewer application as the user runs a search of selected records.
  • records are available from three sources, including Dr. Anderson's medical records, Dr. Johnson's medical records and a corporation's personnel records.
  • the user has filtered out Dr. Johnson's medical records for viewing and searching.
  • the user has also entered, a search query for records related to patient John Doe's “left knee”, as indicated by text box 620 . This allows the user to search for each page of the Dr. Anderson's records as well as Corporate Aerated's personnel records for the phrase “left knee”.
  • the “Records by Location & Category” tab has been selected at tab 630 .
  • the new set of filtered records may be created as an image file, a .pdf file or any other type of format.
  • the new file containing the filtered records may include Dr. Anderson's records and Corporate Aerated's personnel records. This new file may include data that is filtered by location, sort order and even search criteria.
  • FIG. 7 illustrated is a partial screenshot of the filtered records of FIG. 6 as the user prepares to print the new file containing the filtered records. More particularly, here, the user is preparing to print the new file containing Corporate Aerated's personnel records which have been highlighted at text box 705 as well as Dr. Anderson's medical records which has an arrow pointing to text box 715 . As shown, the user has selected the print option at text box 710 . As shown at the right at text boxes 720 , 730 , the category for these records, as filtered by the user, is “general/admin.”
  • the records management system and method of the present disclosure may be used to tag and organize paper or electronic records so that an end user can sort, filter, and edit documents that better show the information in which the user is interested. The end user can then shuffle through the documents in the order preferred by the end user, thus readily permitting a focused review of the records for purposes such as trend-spotting.
  • the output may include a bookmark section 810 that shows a user how to quickly locate the excerpt, table of contents, copy service paperwork, the start of the records compiled for the user, doctor's notes, radiology/diagnostics, laboratory, general/med (or general/medical) and general/admin (or general administrative) categories for the records. Categories were described in detail hereinabove.
  • the electronic output may be sent to the screen and/or printer. It should also be noted that when the records are output in hard copy, the records may be output from the system to a printer with physical tabs that indicate where the documents associated with the pertinent categories begin.
  • the excerpt bookmark in the bookmark section 810 of the screenshot 800 has been selected. Accordingly, an excerpt is shown in display section 820 .
  • the excerpt bookmark shown in the bookmark section 810 includes information from the hypertext data file that has been supplemented by skilled readers. Such skilled readers may be trained, for example, to summarize data from the records that may be of interest to doctors and lawyers in a medical malpractice case.
  • the summary excerpt has been presented in chronological order to give an informative portrayal of treatment history.
  • the summary excerpt is a synopsis of what is found on the page (or representation of a page).
  • the summary excerpts may be used to input handwritten notes as searchable text.
  • skilled readers have read handwritten notes and transcribed them into the records management system.
  • the transcription may be entered into the system in a number of ways, including by supplementing the hypertext data file.
  • display section 820 may display pages grouped under the selected bookmark.
  • the excerpt bookmark has been selected at section 810 ; therefore, display section 820 displays excerpts associated with the records.
  • the excerpt includes a date column 830 that shows a date that corresponds to the associated records.
  • the excerpts are displayed in chronological order.
  • the first excerpt is dated “7/26/10”.
  • the later date of “8/24/10” is shown.
  • the still later date of “10/20/10” is shown.
  • the summary excerpt may further include one or more links to the pertinent page(s) (or representations of page(s)) of the records for which the summary excerpt was written.
  • the first row shows links to pages 18-20 of the pertinent document.
  • the summary excerpt may still further include one or more providers for the associated pertinent page(s) (or representations of page(s)) of the records for which the summary excerpt was written. As shown at the first and third rows, a single provider is given. At the second row, multiple providers are given for the associated excerpt.

Abstract

A records management system and method that permits paper records to be tagged, stored and retrieved according to user criteria. The system includes a scanning module, a central server, one or more user workstations and an optical character recognition server. After scanning, the records may then be serialized and categorized by project, and then supplemented automatically by the system with a hypertext data file. The system provides for the manual input of additional hypertext data and merger of the hypertext data file with other records in the project. The end user may then search and/or filter records according to information contained in the hypertext data file. Output from the system may include summary excerpts whereby summaries for data contained in select pages of each document in a project are associated with at least dates, page numbers, and providers for the data.

Description

    CROSS-REFERENCE TO RELATED APPLICATIONS
  • This application is a continuation of pending U.S. patent application Ser. No. 13/910,035, filed Jun. 4, 2013, which is a continuation of U.S. patent application Ser. No. 13/436,637, filed Mar. 30, 2012, now U.S. Pat. No. 8,458,155, which is a continuation of U.S. patent application Ser. No. 12/853,927, filed Aug. 10, 2010, now U.S. Pat. No. 8,301,611, which is a continuation of U.S. patent application Ser. No. 12/008,139 filed Jan. 9, 2008, now U.S. Pat. No. 7,882,091, all of which are hereby incorporated by reference in their entireties.
  • BACKGROUND
  • 1. Field
  • The present disclosure relates to records management and, more particularly, to a records management system and method that permit a user to tag, store and/or retrieve pertinent records based on user criteria.
  • 2. Description of Related Art
  • Records have long been an important part of everyday life. For example, physicians are required—under various laws—to maintain medical records for a certain period of time. These records can be quite useful in diagnosis and analysis of a patient's condition, particularly when the patient has been seen by multiple doctors.
  • These medical records can also be useful to legal professionals when, for example, a patient files a worker's compensation claim or when a patient files a claim for medical malpractice.
  • In the past, medical records were largely maintained as paper records in file rooms. However, as the volume of paper records increased, so did the space required to store them. As a result, those persons responsible for maintenance of these medical records moved to electronic scanning and storage of their medical records.
  • Although advances have been made in that medical records are electronically stored, the process of reviewing the records is not necessarily as streamlined or cost effective as it could be. For example, an attorney responsible for reviewing and analyzing a worker's compensation or medical malpractice claim may charge by the hour. The longer it takes to review the medical records, the greater the amount of money expended for the records review.
  • Along the same lines, doctors and other professionals may need ready access to pertinent medical records in order to make vital medical decisions regarding a course of treatment for a patient. In this instance, a shortened time for medical records review may be crucial. In addition, doctors may be responsible for numerous patients at a single point in time. Time taken for one patient may mean time unavailable for another. This factor also highlights the need for a more streamlined medical records review.
  • Accordingly, there is a need for a records management system and method that permit rapid retrieval and filtering of pertinent electronic records.
  • When attorneys and doctors are presented with a voluminous records project, they may need not only a streamlined and cost effective way to review the records, but they may also need a streamlined and cost effective way of creating a new custom-built record that includes only the pertinent information that was reviewed.
  • Accordingly, there is a need for a record storage and retrieval system that permits the creation of a new record that includes on the pertinent information reviewed.
  • At times, when legal professionals are involved in the review of medical records for purposes of worker's compensation claims, medical malpractice claims and the like, they may need to readily cite to particular pages of those records in litigation. Accordingly, there is a need for a record storage and retrieval system and method that readily permit citation to those records if needed.
  • BRIEF SUMMARY OF DISCLOSURE
  • The present disclosure addresses the foregoing deficiencies of the prior art by providing a records management system and method that permit tagging, storage and retrieval of electronic records based on user criteria. In accordance with one embodiment of the present disclosure, a records management system is provided. The system comprises a location designation module configured to designate an electronic storage location for said each representation of a page; and a data module configured to create an electronic data file that corresponds to said each representation of a page, wherein the electronic data file relates said each representation of a page to a document within the project. The electronic data file includes the electronic storage location for said each representation of a page.
  • The system further comprises at least one workstation configured to receive input of additional data for the electronic data file, the input additional data further including a category for said each representation of a page, a date for said each representation of a page, and a provider for each said representation of a page; and a supplementation module configured to supplement the electronic data file with said input additional data for the electronic data file.
  • The system still further includes a merging module configured to merge said each representation of a page with the corresponding electronic data file for each said representation of a page such that said each representation of a page and the corresponding electronic data file are accessible from a single electronic project file.
  • Finally, the system includes output that is a summary excerpt for at least one representation of a page. The excerpt includes at least one date, at least one page number and at least one provider associated with the at least one representation of a page.
  • In accordance with another embodiment of the present disclosure, a records management method is provided. The method comprises the steps of designating an electronic storage location for one or more electronic files that represent each page of each document in a project; and creating an electronic data file that corresponds to said each representation of a page, wherein the electronic data file relates said each representation of a page to a document within the project, wherein said electronic data file includes the electronic storage location for said each representation of a page.
  • The method further comprises receiving input of additional data for the electronic data file, and a category for said each representation of a page, wherein the input additional data includes a date for each said representation of a page, and at least one provider for each said representation of a page; and supplementing the electronic data file with the input additional data.
  • The method still further comprises merging said each representation of a page with the corresponding electronic data file for said each representation of a page such that said each representation of a page and the corresponding electronic data file are accessible from a single electronic project file.
  • Finally, the method comprises outputting at least one summary excerpt for at least one representation of a page, the summary excerpt including at least one date, at least one page number and at least one provider for the at least one representation of a page.
  • These, as well as other objects, features and benefits will now become clear from a review of the following detailed description of illustrative embodiments and the accompanying drawings.
  • BRIEF DESCRIPTION OF DRAWINGS
  • FIG. 1 is a records management system in accordance with one embodiment of the present disclosure.
  • FIG. 2 is a flow chart illustration of a method for records management in accordance with another embodiment of the present disclosure.
  • FIG. 3 is a screenshot illustration of records that have been sorted by date and category in accordance with one embodiment of the present disclosure.
  • FIG. 4 is a screenshot illustration that results from a user query for documents containing a particular search term in accordance with one embodiment of the present disclosure.
  • FIG. 5 is a screenshot illustration of records that have been sorted by location and category in accordance with one embodiment of the present disclosure.
  • FIG. 6 is a screenshot illustration of a viewer application as a user searches and filters selected records in accordance with one embodiment of the present disclosure.
  • FIG. 7 is a screenshot illustration of filtered records as the user prepares to create and print a new record that contains only the filtered records in accordance with one embodiment of the present disclosure.
  • FIG. 8 is an example of electronic output from the records management system and method that includes excerpts in accordance with one embodiment of the present disclosure.
  • DETAILED DESCRIPTION OF THE DISCLOSURE
  • The records management system of the present disclosure may be used to tag and store paper or electronic records so that a user can sort, filter, and edit documents that better show the information in which the user is interested.
  • Referring now to FIG. 1, illustrated is a records management system 100 in accordance with one embodiment of the present disclosure. Included within the records management system 100 is a scanning module 110 that is operatively coupled to a central server 120. Also illustrated are workstations 130, 140, 150 and an optical character recognition engine 160, each of which is also operatively coupled to central server 120.
  • It should be understood that connections between the various components of the system 100 may be configured in any number of ways to advance the goals of the present disclosure without departing from the inventive concept. For example, the connections between various components of system 100 may be made via wide area networks (such as the Internet) as well as local area networks (LAN's). Moreover, the connections may be, without limitation, wireless or wired.
  • Each one of workstations 130, 140, 150 may be a conventional personal computer. Workstations 130, 140, 150 may be provided, for example, as IBM® compatible computers, APPLE® MACINTOSH® personal computers, UNIX®-based workstations, or any other equivalent computer systems, whether laptop, desktop or otherwise. Under some circumstances, the workstations 130, 140, 150 that may be used to input and receive information from the central server 120 may be personal digital assistants (PDA's) or any other such device. The computer system used may also be e.g., a WINDOWS® hand-held device. Some mobile phones may be used to input and receive information, where such capability is available.
  • Each of workstations 130, 140, 150 may include a central processing unit (not shown), a display 165, a mouse 170, and a keyboard 175 for receiving user input into the system. While three workstations 130, 140, 150 are shown in the present illustration, it should be understood that there could be only one workstation, or a large number of workstations depending on the capacity needed for a particular implementation of the system of the present disclosure. Both the mouse 170 and the keyboard 175 may be coupled to the user's workstation so that the user's computer may receive information that is input by him/her, and so that information can be routed through the network 180 to the central server.
  • The networks 180, 185 in the current illustration are the Internet; however, the networks 180, 185 may be any other type of wide area network, local area network, or other means by which workstations may communicate with the central server.
  • The exemplary workstations are for descriptive purposes only. Although the description may refer to terms commonly used in describing particular computer systems, the description and concepts equally apply to other processing systems, including systems having architectures dissimilar to those shown in FIG. 1.
  • The read only memory (ROM) for each of workstations 130, 140, 150 may operate to effect permanent storage of information. Random access memory (RAM) for each of workstations 130, 140, 150 may operate to effect temporary storage of information. Each of the aforementioned components may be coupled to a bus. Operation of workstations 130, 140, 150 may be generally controlled and coordinated by operating system software. With the records system 100 of the present disclosure, the operating system that runs on workstations 130, 140, 150 may be, but is not limited to, MICROSOFT® WINDOWS VISTA®, MICROSOFT® WINDOWS XP®, or a version of MAC OS® or UNIX® operating system or the like. ®
  • Alternatively, the principles of the present application can be applied to a computer system using a version of DOS (disk operating system), or other operating system programs. An operating system resident in system memory and executed by the CPUs of workstations 130, 140, 150 may coordinate the operation of the other elements of workstations 130, 140, 150.
  • Data and software, including the filtering software to be described in more detail hereinbelow, may be provided to and extracted from workstations 130, 140, 150 via removable storage media such as, without limitation, a CD-ROM or DVD.
  • Data may also be provided to workstations 130, 140, 150 via scanner 110 and software for reading information via the scanner 110. Scanner 110 may be, without limitation, an optical character recognition (OCR) scanner.
  • Workstations 130, 140, 150 may include a communications adapter which allows the workstation to be interconnected to a local area network (LAN), a wide area network (WAN) or a public network. Thus, records data and related computer program software can be transferred to and from workstations 130, 140, 150 via the adapter and network 180.
  • Portions of the filtering software used to achieve the purposes of the present disclosure can be resident on workstations 130, 140, 150. Alternatively, all of the filtering software may be resident on central server 120 such that web-based storage and filtering may occur.
  • Referring now to FIG. 2, shown is a flow chart illustration of a method 200 for records management in accordance with one embodiment of the present disclosure. As illustrated, the method 200 may begin with scanning paper documents for each page of a document in a project at step 205 using a scanner; the scanner may operate with and/or be controlled by associated software that provides for image cleanup and optimization.
  • A project as described herein may be composed of a series of related documents. The documents may be deemed related by an end user, or the company/entity providing the scanning services, or a company/entity providing records maintenance services, and/or any other person/entity. For example, the end user of the system of the present disclosure may submit a series of documents for use with the system of the present disclosure. Also by way of example, the company that provides the scanning services may group all the documents for a particular end user into a group, thus identifying the documents as a project.
  • The documents in a project may consist of or include, for example, medical and other records related to a worker's compensation injury, a medical malpractice claim or any other grouping of records relevant to a particular goal. Documents in a project may also consist of, or include, for example, medical records for a particular person or all persons in an organization. While the present disclosure describes the project as including medical records, it should be understood that the records could be any number of types of records including but not limited to court files, merger/acquisition documents, employment records or any other type of record whether business or personal.
  • At step 210, software used in conjunction with the present disclosure may receive and/or create one or more image files for each scanned page of each document in the project. The image file may be created in a tagged image file format (TIFF), a joint photographics expert group (JPEG) format, a portable network graphics (PNG) format, a graphical interchange format (GIF) or other format that is suitable for representing each page of a document in a project. Each page may be represented in one or more of these formats or any other suitable image format.
  • It should be understood that the system and method of the present disclosure are also suitable for use with records that are not scanned, but are in another format such as a word processing application like MICROSOFT® WORD®, a chart format such as those found in MICROSOFT® EXCEL® or other type of program that can be used to create a record. In this case, the scanning of paper records and the creation of image files would not be necessary. Moreover, the later-described optical character recognition may not be necessary for translating text from the image files into machine-readable text since the text in electronic file may already be machine-readable.
  • At step 220, each page of the scanned paper records in the project may be ordered serially and given a serial number, Bates label or other unique identification code for each page. Software resident on the central server and/or workstations may be configured to provide this functionality. The software may begin the serialization process as soon as the pages are scanned or at any other suitable time.
  • At step 230, software resident on the central server and/or workstations may also designate an electronic storage location for each scanned page of each document in a project. This will allow the end user to easily ascertain the storage location of a particular record. The location may be, e.g., a project folder.
  • At step 240, software resident on the central server and/or workstations may create a description of each scanned page of each document in a project.
  • At step 250, software resident on the central server and/or workstations may build an electronic data file for each scanned page of each document in the project. This electronic data file may be or include a hypertext data file. It is important to note that the data record in the hypertext data file (metadata) may be used to relate the page to the particular document within the project.
  • The hypertext data file may include the unique identification codes, image files, locations and page descriptions as well as other information related to the project. The hypertext data file may also include a source indicator for the each scanned page, e.g., the author or the company from which the document originated. The hypertext data file may further include a date associated with the page. The date may be, for example, the date of creation of the page or a date of delivery for the record if the record is from a third party.
  • The hypertext data file may also include a category for each page. The category may be, for example, copy service paperwork in case the records relate to a legal proceeding. The category may also be more generic such as “general or administrative.” In the case of medical records, the categories may include, by way of example and not limitation, doctor's notes, laboratory, nursing, radiology, reports, and the like. In brief, the category may be any category that is useful to the end user. The hypertext data file may be uploaded to the central server so that additional identifying input may be performed by humans as described immediately below. The user may also be permitted to upload his/her own documents and add them to the document group for searching and other functions just as if the newly added documents were in the original set of documents.
  • The central server now has all of the above-identified information related to the project. At this point, a manual process of identifying metadata and key text on the pages of documents may be performed by trained human readers at workstations that are operatively coupled to the central server as described in connection with FIG. 1.
  • This metadata and key text may include any pertinent information that would allow the records to be easily retrieved. For example, this metadata and key text may include an author for the pertinent record page; a date of the page, note or report; a category for each record type; and a provider for each record page. This metadata and key text may be added to the hypertext data file. At step 260, this metadata and key text that were input by the humans at their workstations may be transmitted to, and received by, the central server. Thus, tracking of the metadata to the page, document, and project may be preserved. The information input by the trained readers may be included in data fields and/or data types used to sort and filter the records, respectively.
  • At step 270, software resident on the central server and/or workstations may supplement the hypertext data file with the input of additional data. Once the hypertext data file is completed for the series of documents it may be merged together into one project file at step 280.
  • The hypertext data file may be encrypted for privacy reasons, including those related to the Health Insurance Portability and Accountability Act (HIPAA). Software resident on the server and/or workstations may be used to perform encryption functions. Such software is commercially available.
  • The software of the present disclosure may cause represented pages of the project to be passed through an optical character recognition (OCR) engine server at step 290. The OCR engine server may be used to translate handwritten or typed text from the one or more image files into machine-readable text.
  • Software resident at the central server and/or workstations may also index the entire text of the project at step 293 and add that text to the hypertext data file at step 294 so that it may be used for filtering, sorting and editing by the end user at step 295 upon review of the records. This filtering, sorting and editing of step 295 are described in further detail hereinbelow in connection with FIGS. 3-7.
  • While the steps of the method have been described hereinabove in a particular order, this order is non-limiting. It should be understood that the order could vary while still accomplishing the goals of this disclosure without departing from the inventive concept. Once the project is assembled, it may be delivered to the end-user via CD, DVD, online download, FTP, USB key, or any other type of suitable data transfer means.
  • Now, the end user charged with reviewing the records in a project can open the project in a viewer application provided by filtering software used in accordance with the present disclosure. The end user may operate the software on a computer system similar to those of the workstations described hereinabove in connection with FIG. 1. Using this viewer application, the end user can sort the metadata by any of the fields, such as description, date of the page, record location, author of the records, etc. This sorting capability permits the end user to “shuffle” together pages from various documents in a project so that the end user may view these pages in a sequence that allows the end user to spot trends the end user may be seeking.
  • Referring now to FIG. 3, illustrated is a screenshot 300 of records that have been sorted by date and category. As shown, records may be mixed from different sources altogether, and “shuffled” by date and category. A records listing may be found in the background screen 310. A viewer window 315 is shown in the foreground.
  • When an end user double-clicks on a record or page, e.g., at text box 320, the end user may obtain the viewer window that shows the record or page. On that page, the end user can see the category for the record's page as shown at column 330, the location of the record from which the page came as shown at column 340, and the original page number in those records (hidden). As shown at background screen 310, the records have been sorted according to date. Also provided may be a location for the user to type and save notes. Navigation buttons may permit the user continue to page through the current sort, viewing each page in the sequence the user currently has going on the main form. The software of the present disclosure may keep track of where each page being viewed belongs with respect to the original documents submitted.
  • Using filtering software as described in the present disclosure, pages may be marked as deleted or suppressed by the user according to data type so that undesired pages are filtered out while the user is viewing the project. Examples of data types are the location or author of a set of pages, which can also be easily filtered out of the project using a viewer application provided by the software described in the present disclosure, adding to the efficiency of viewing the project documents. Other data types include provider name and category, which may be filtered such that only records from certain categories or provider are grouped together in a listing. The record pages can be filtered according to date range, and based on whether notes or edits were made to the record page. Additional data types can be identified and filtered in or out as the end user desires. Alternatively, filtering could occur such that pages are marked so that only pages related to data types are displayed.
  • Text searches can be performed within the viewer application provided by the software described in the present disclosure. A search can be performed of both the scanned text of the record pages, and the metadata that was created. The viewer application may build a new subset of pages where the text appeared, and display the list according to the existing sort order and filter the user had in place at the time the search was performed. This helps narrow down the pages the user must read when looking for the trends or evidence that the end user seeks.
  • Notes may be typed for any page within the provided viewer application and saved to the metadata file. This data may be included in subsequent searches.
  • The metadata for the pages that was originally created as part of the service can be edited and saved into the project by the end user.
  • As described above, the end user of the viewer application can build a custom set of pages that is sorted and filtered just the way they want to see them. They can then create a new PDF document of the results which can then be printed, saved to disk, emailed, etc. The subsequent PDF can be scanned using an OCR scanner, and can include custom watermarks/stamps and page numbering schemes.
  • The filtering software described herein may be a desktop application and a web application (when the documents are stored on a web or file transfer protocol (ftp) site).
  • Referring now to FIG. 4, illustrated is a screenshot 400. Here, the user has entered a search query for the record pages that contain the term “abdominal” as indicated at text box 410. The user has double-clicked to get the page in the records where the word “abdominal” appeared. As illustrated by the text shown in text box 420, the word “abdominal” did not appear in the records. However, as shown in text box 420 a hand-written note is shown with the word abdominal abbreviated thereon as “abd.” Many of today's search engines might not have found this word. The “Search for” textbox may be used with a search engine style of syntax for query commands Search commands can be used on the review data, OCR data from the images themselves, and/or a combination of both.
  • The viewer application may include a full search engine. Wildcards may be used, partial searches, fuzzy searches, etc. may all be included in searches performed. Search commands may be performed using a variety of query syntaxes. The query can range from single term searches to more complex search queries involving wildcards and Boolean operators. For example, where a user wishes to search for the term “knee”, the viewer application should display results of all record pages and/or the pages' metadata that contain the word “knee.” The user may also search for the phrase “left knee.” In this case, the viewer application would display all pages and/or metadata that contain the phrase “left knee.”
  • Various fields of data for the record pages can also be searched. For example, the user could perform a search of all records that contain knee in the title field using a “title:knee” query. Wildcard searches may be performed by inserting a wildcard indicator such as “?” or “*”. For example, where a user enters the query “abdom*”, the search results would include pages that contain the word “abdomen” and “abdominal.”
  • Users may also perform fuzzy searches which will include results for terms having the same or similar spelling. For example, if the user wishes to search for “abdomen,” but spells it incorrectly as “abdomen,” the search results should include pages that include the word “abdomen.”
  • The user may restrict searches to particular ranges using a range query. For example, the user may search for pages that have particular dates associated therewith. If a user only wishes to see those results that are associated with the year 2006, the user could input the search query “date: 20060101 TO 20061231.” It should be noted that other range searches may also be available to the user.
  • Boolean operators may also be used as search queries in accordance with the present disclosure. For example, if a user wishes to pull all pages that contain the terms “knee” and “abdomen” the user may input the search query “knee or abdomen.” The results should include all pages that contain the term knee, as well as all pages that contain the word “abdomen.” If the user wishes to view all pages that contain the terms “knee” and “abdomen” together, the user may input the search query “knee and abdomen.” The results should include all pages that contain the term “knee” and “abdomen” for a single page.
  • Other types of search queries may be used in accordance with the present disclosure. For example, the user may not wish to view certain pages and filter them out. If a user wishes to view all pages that contain knee, and is curious but not set on getting all the results that contain “left” as well, the user may input the search query “left+knee” to accomplish this result.
  • Referring now to FIG. 5, illustrated is a screenshot 500 that shows a viewer application provided by filtering software in accordance with one embodiment of the present disclosure. As shown under the “Filter” drop-down menu at text box 510, there are three sources of records. Here, the user has chosen not to view or search the personnel records as indicated by unchecked text box 520. Because the “Records by Location & Category” tab has been selected as indicated by user selection of tab 530, the records are displayed in this manner using these data types.
  • Referring now to FIG. 6, illustrated is a screenshot 600 that shows the viewer application as the user runs a search of selected records. Here, as shown by text box 610 under the “Filter” drop-down menu, records are available from three sources, including Dr. Anderson's medical records, Dr. Johnson's medical records and a corporation's personnel records. In the screenshot of FIG. 6, the user has filtered out Dr. Johnson's medical records for viewing and searching. The user has also entered, a search query for records related to patient John Doe's “left knee”, as indicated by text box 620. This allows the user to search for each page of the Dr. Anderson's records as well as Corporate Aerated's personnel records for the phrase “left knee”. Also as shown, the “Records by Location & Category” tab has been selected at tab 630.
  • In this manner, the user can build a new set of records using the viewer application. The new set of filtered records may be created as an image file, a .pdf file or any other type of format. The new file containing the filtered records may include Dr. Anderson's records and Corporate Aerated's personnel records. This new file may include data that is filtered by location, sort order and even search criteria.
  • Referring now to FIG. 7, illustrated is a partial screenshot of the filtered records of FIG. 6 as the user prepares to print the new file containing the filtered records. More particularly, here, the user is preparing to print the new file containing Corporate Aerated's personnel records which have been highlighted at text box 705 as well as Dr. Anderson's medical records which has an arrow pointing to text box 715. As shown, the user has selected the print option at text box 710. As shown at the right at text boxes 720, 730, the category for these records, as filtered by the user, is “general/admin.”
  • It should be understood that data can be filtered based on any information in the hypertext data file. Filtering can be performed according to the data type of provider name as shown in FIG. 7 such that records from certain providers are removed from the display. Filtering could also occur by the data type of category. For example, the user could view only those records that are categorized as “doctor's notes.” Various date ranges can also be filtered as data types. For example, a user could view only those records that incorporate a certain date range. Filtering could also occur such that the user only views pages that do not have note text. The user could then type notes only for certain pages. The user could then filter the records such that only those pages with notes are displayed.
  • The records management system and method of the present disclosure may be used to tag and organize paper or electronic records so that an end user can sort, filter, and edit documents that better show the information in which the user is interested. The end user can then shuffle through the documents in the order preferred by the end user, thus readily permitting a focused review of the records for purposes such as trend-spotting.
  • The records management system and method of the present disclosure may be used to create summary excerpts which may be output from the system. The summary excerpt output from the records management system may be electronic or hard copy. In the case of electronic output, after the project has been scanned and each page categorized, a searchable electronic file may be created of the records in the project. The resulting electronic page representations may then be bookmarked. It should be noted that, in the case of hard copy output, the records may be grouped and separated with a paper tab in lieu of a bookmark.
  • Referring now to FIG. 8, illustrated is an example of electronic output from the records management system that includes summary excerpts. As shown to the left of the screen, the output may include a bookmark section 810 that shows a user how to quickly locate the excerpt, table of contents, copy service paperwork, the start of the records compiled for the user, doctor's notes, radiology/diagnostics, laboratory, general/med (or general/medical) and general/admin (or general administrative) categories for the records. Categories were described in detail hereinabove. The electronic output may be sent to the screen and/or printer. It should also be noted that when the records are output in hard copy, the records may be output from the system to a printer with physical tabs that indicate where the documents associated with the pertinent categories begin.
  • In the present illustration, the excerpt bookmark in the bookmark section 810 of the screenshot 800 has been selected. Accordingly, an excerpt is shown in display section 820. The excerpt bookmark shown in the bookmark section 810 includes information from the hypertext data file that has been supplemented by skilled readers. Such skilled readers may be trained, for example, to summarize data from the records that may be of interest to doctors and lawyers in a medical malpractice case.
  • In the present illustration, the summary excerpt has been presented in chronological order to give an informative portrayal of treatment history. The summary excerpt is a synopsis of what is found on the page (or representation of a page). The summary excerpts may be used to input handwritten notes as searchable text. Here, skilled readers have read handwritten notes and transcribed them into the records management system. The transcription may be entered into the system in a number of ways, including by supplementing the hypertext data file. When a bookmark is selected at section 810, display section 820 may display pages grouped under the selected bookmark. Here, the excerpt bookmark has been selected at section 810; therefore, display section 820 displays excerpts associated with the records.
  • Here, the excerpt includes a date column 830 that shows a date that corresponds to the associated records. The excerpts are displayed in chronological order. Here, as shown at the first row, the first excerpt is dated “7/26/10”. At the second row, the later date of “8/24/10” is shown. Meanwhile at the third row, the still later date of “10/20/10” is shown.
  • As illustrated at column 840, the summary excerpt may further include one or more links to the pertinent page(s) (or representations of page(s)) of the records for which the summary excerpt was written. Here, the first row shows links to pages 18-20 of the pertinent document.
  • As illustrated at column 850, the summary excerpt may still further include one or more providers for the associated pertinent page(s) (or representations of page(s)) of the records for which the summary excerpt was written. As shown at the first and third rows, a single provider is given. At the second row, multiple providers are given for the associated excerpt.
  • At column 860, the summaries written by the skilled readers are shown. Here, the summaries have been given the heading of progress notes. These summary excerpts may include handwritten notes that have been typed in by human readers. Using the summary excerpts described herein, the end user may get a clear picture of treatment history that may not have been previously apparent.
  • While the specification describes particular embodiments of the present disclosure, those of ordinary skill can devise variations of the present disclosure without departing from the inventive concept.

Claims (20)

1. A records management system, comprising:
a memory that stores instructions; and
a processor that executes the instructions to perform operations, the operations comprising:
creating an electronic data file for a plurality of documents, wherein the electronic data file includes an electronic storage location for a representation of a page of the plurality of documents and relates the representation of the page to a corresponding document of the plurality of documents;
receiving data for the electronic data file, the data including information that identifies the representation of the page;
correlating the representation of the page with the electronic data file such that the representation of the page and the electronic data file are accessible from an electronic project file; and
creating a summary excerpt of a plurality of pages of one document of the plurality of documents.
2. The system of claim 1, wherein the summary excerpt of the plurality of pages of one document of the plurality of documents further comprises a link to a page of the plurality of pages of the one document of the plurality of documents.
3. The system of claim 1, wherein the summary excerpt of the plurality of pages of one document of the plurality of documents further comprises an identity of the provider of the one document of the plurality of documents.
4. The system of claim 1, wherein receiving data for the electronic data file includes receiving a date for each document of the plurality of documents.
5. The system of claim 1, wherein the operations further comprise merging the representation of the page and the electronic data file to create the electronic project file.
6. The system of claim 1, wherein the operations further comprise creating a description of the representation of the page.
7. The system of claim 1, wherein the operations further comprise creating a unique identification code for the representation of the page.
8. The system of claim 1, wherein the operations further comprise creating the representation of the page of a document of a plurality of documents.
9. The system of claim 8, wherein creating the representation of the page is based on a scan of one document of the plurality of documents.
10. The system of claim 1, wherein the summary excerpt of the plurality of pages of one document of the plurality of documents includes a plurality of page numbers associated with the one document.
11. The system of claim 1, wherein the operations further comprise sorting a plurality of representations of a plurality of pages in response to a user selection.
12. The system of claim 1, wherein the operations further comprise receiving a user edit for the summary excerpt of the plurality of pages of one document of the plurality of documents.
13. The system of claim 1, wherein the operations further comprise receiving a user edit for the electronic data file.
14. The system of claim 1, wherein the operations further comprise outputting search results in response to a user search request.
15. A records management method, comprising:
creating an electronic data file for a plurality of documents, wherein the electronic data file includes an electronic storage location for a representation of a page of the plurality of documents and relates the representation of the page to a corresponding document of the plurality of documents;
receiving, by utilizing instructions stored in memory and executed by a processor, data for the electronic data file, the data including information that identifies the representation of the page;
correlating the representation of the page with the electronic data file such that the representation of the page and the electronic data file are accessible from an electronic project file; and
creating a summary excerpt of a plurality of pages of one document of the plurality of documents.
16. The method of claim 15, wherein the summary excerpt of the plurality of pages of one document of the plurality of documents further comprises a link to a page of the plurality of pages of the one document of the plurality of documents.
17. The method of claim 15, wherein the summary excerpt of the plurality of pages of one document of the plurality of documents further comprises a summary of the representation of the page.
18. The method of claim 15, further comprising creating a description of the representation of the page.
19. A computer-readable device comprising instructions, which when loaded and executed by a processor, cause the processor to perform operations comprising:
creating an electronic data file for a plurality of documents, wherein the electronic data file includes an electronic storage location for a representation of a page of the plurality of documents and relates the representation of the page to a corresponding document of the plurality of documents;
receiving data for the electronic data file, the data including information that identifies the representation of the page;
correlating the representation of the page with the electronic data file such that the representation of the page and the electronic data file are accessible from an electronic project file;
creating a summary excerpt of a plurality of pages of one document of the plurality of documents; and
creating a description of the representation of the page.
20. The computer-readable device of claim 19, wherein creating a summary excerpt of a plurality of pages of one document of the plurality of documents further comprises providing a link to a page of the plurality of pages of the one document of the plurality of documents.
US14/791,036 2008-01-09 2015-07-02 Records management system and methods Abandoned US20150310007A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US14/791,036 US20150310007A1 (en) 2008-01-09 2015-07-02 Records management system and methods
US15/398,439 US20170116170A1 (en) 2008-01-09 2017-01-04 Records management system and methods

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
US12/008,139 US7882091B2 (en) 2008-01-09 2008-01-09 Record tagging, storage and filtering system and method
US12/853,927 US8301611B2 (en) 2008-01-09 2010-08-10 Records management system and method
US13/436,637 US8458155B2 (en) 2008-01-09 2012-03-30 Records management system and method with excerpts
US13/910,035 US9305030B2 (en) 2008-01-09 2013-06-04 Records management system and methods
US14/791,036 US20150310007A1 (en) 2008-01-09 2015-07-02 Records management system and methods

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US13/910,035 Continuation US9305030B2 (en) 2008-01-09 2013-06-04 Records management system and methods

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/398,439 Continuation US20170116170A1 (en) 2008-01-09 2017-01-04 Records management system and methods

Publications (1)

Publication Number Publication Date
US20150310007A1 true US20150310007A1 (en) 2015-10-29

Family

ID=40845370

Family Applications (6)

Application Number Title Priority Date Filing Date
US12/008,139 Active 2028-11-17 US7882091B2 (en) 2008-01-09 2008-01-09 Record tagging, storage and filtering system and method
US12/853,927 Active US8301611B2 (en) 2008-01-09 2010-08-10 Records management system and method
US13/436,637 Active US8458155B2 (en) 2008-01-09 2012-03-30 Records management system and method with excerpts
US13/910,035 Active 2028-05-27 US9305030B2 (en) 2008-01-09 2013-06-04 Records management system and methods
US14/791,036 Abandoned US20150310007A1 (en) 2008-01-09 2015-07-02 Records management system and methods
US15/398,439 Abandoned US20170116170A1 (en) 2008-01-09 2017-01-04 Records management system and methods

Family Applications Before (4)

Application Number Title Priority Date Filing Date
US12/008,139 Active 2028-11-17 US7882091B2 (en) 2008-01-09 2008-01-09 Record tagging, storage and filtering system and method
US12/853,927 Active US8301611B2 (en) 2008-01-09 2010-08-10 Records management system and method
US13/436,637 Active US8458155B2 (en) 2008-01-09 2012-03-30 Records management system and method with excerpts
US13/910,035 Active 2028-05-27 US9305030B2 (en) 2008-01-09 2013-06-04 Records management system and methods

Family Applications After (1)

Application Number Title Priority Date Filing Date
US15/398,439 Abandoned US20170116170A1 (en) 2008-01-09 2017-01-04 Records management system and methods

Country Status (1)

Country Link
US (6) US7882091B2 (en)

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110145014A1 (en) * 2009-12-15 2011-06-16 Suzette Jacqueline Avneri International life-saving rapid retrieving tool
US9251295B2 (en) * 2011-08-31 2016-02-02 International Business Machines Corporation Data filtering using filter icons
US9158992B2 (en) * 2013-03-14 2015-10-13 Here Global B.V. Acceleration of linear classifiers
US9239889B2 (en) * 2013-03-15 2016-01-19 Sugarcrm Inc. Adaptive search and navigation through semantically aware searching
US8854675B1 (en) 2013-03-28 2014-10-07 Xerox Corporation Electronic document processing method and device
US9507758B2 (en) * 2013-07-03 2016-11-29 Icebox Inc. Collaborative matter management and analysis
USD789973S1 (en) 2013-12-20 2017-06-20 Roche Diagnostics Operations, Inc. Display screen or portion thereof with graphical user interface and computer icons
US11507612B2 (en) * 2017-09-15 2022-11-22 Dg Ip Llc Document elimination for compact and secure storage and management thereof
CN109710573B (en) * 2018-12-29 2021-03-30 广州易宝信息技术有限公司 Electronic archive informatization management system
US11645295B2 (en) * 2019-03-26 2023-05-09 Imagescan, Inc. Pattern search box
CN110297925B (en) * 2019-06-30 2022-05-31 联想(北京)有限公司 Data processing method and device and electronic equipment

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6263121B1 (en) * 1998-09-16 2001-07-17 Canon Kabushiki Kaisha Archival and retrieval of similar documents

Family Cites Families (39)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4553261A (en) 1983-05-31 1985-11-12 Horst Froessl Document and data handling and retrieval system
JP2695844B2 (en) 1988-06-16 1998-01-14 株式会社東芝 Document shaping device
US4970554A (en) 1988-10-24 1990-11-13 Xerox Corporation Job processing system for high speed electronic copying/printing machines
JPH03161873A (en) 1989-11-20 1991-07-11 Ricoh Co Ltd Electronic filing device having data base constructing function
US5444840A (en) 1990-06-12 1995-08-22 Froessl; Horst Multiple image font processing
US5109439A (en) 1990-06-12 1992-04-28 Horst Froessl Mass document storage and retrieval system
US5396588A (en) 1990-07-03 1995-03-07 Froessl; Horst Data processing using digitized images
JP3323535B2 (en) 1992-05-19 2002-09-09 キヤノン株式会社 Image storage device and control method of image storage device
US5991782A (en) 1994-02-18 1999-11-23 Fujitsu Limited Automated extraction and doubly linked reference marks for partialized document contents and version control
US5666490A (en) 1994-05-16 1997-09-09 Gillings; Dennis Computer network system and method for managing documents
US5926824A (en) 1994-11-16 1999-07-20 Canon Kabushiki Kaisha System and method for retrieving a document by inputting a desired attribute and the number of areas in which the attribute occurs as a retrieval condition
JP3700733B2 (en) 1995-06-12 2005-09-28 富士ゼロックス株式会社 Document management apparatus and document management method
US6427032B1 (en) 1997-12-30 2002-07-30 Imagetag, Inc. Apparatus and method for digital filing
US6744936B2 (en) 1997-12-30 2004-06-01 Imagetag, Inc. Apparatus and method for simultaneously managing paper-based documents and digital images of the same
US6192165B1 (en) 1997-12-30 2001-02-20 Imagetag, Inc. Apparatus and method for digital filing
US6661933B1 (en) 1998-01-13 2003-12-09 Matsushita Electric Industrial Co., Ltd. Apparatus and method for image data processing
US6594650B2 (en) 1998-09-04 2003-07-15 Canon Kabushiki Kaisha File management system and its method and storage medium
US6602298B1 (en) 1999-06-04 2003-08-05 Hewlett-Packard Development Company, L.P. Methods of storing and retrieving communications, information, and documents
US20020002563A1 (en) 1999-08-23 2002-01-03 Mary M. Bendik Document management systems and methods
US6466336B1 (en) 1999-08-30 2002-10-15 Compaq Computer Corporation Method and apparatus for organizing scanned images
US7215434B1 (en) 1999-10-29 2007-05-08 Oce-Technologies B.V. Automated scan processing
US6735335B1 (en) 2000-05-30 2004-05-11 Microsoft Corporation Method and apparatus for discriminating between documents in batch scanned document files
US6867765B2 (en) 2000-10-06 2005-03-15 International Business Machines Corporation Use of a paper pad with uniquely identified pages in a digitizer system
US7447713B1 (en) 2000-10-13 2008-11-04 Berkheimer Steven E System and method for archiving and outputting documents or graphical items
US6904171B2 (en) 2000-12-15 2005-06-07 Hewlett-Packard Development Company, L.P. Technique to identify interesting print articles for later retrieval and use of the electronic version of the articles
US7013029B2 (en) * 2001-06-29 2006-03-14 Intel Corporation Incorporating handwritten notations into an electronic document
SG123534A1 (en) 2001-08-08 2006-07-26 Oce Tech Bv Entry of physical documents in a digital back-end system
EP1283485A1 (en) 2001-08-08 2003-02-12 Océ-Technologies B.V. Entry of physical documents in a digital back-end system
US20030229611A1 (en) 2002-06-10 2003-12-11 Michael Hintenach Mapping, navigation, and data input for electronic documents
JP4054726B2 (en) 2003-07-09 2008-03-05 キヤノン株式会社 Information processing apparatus, control method thereof, and program
ATE492859T1 (en) 2004-04-26 2011-01-15 Adalbert Gubo DEVICE FOR ENCODING AND MARKING DOCUMENTS FOR RECOGNITION AND RECOVERY
JP4386281B2 (en) 2005-01-31 2009-12-16 キヤノン株式会社 Image processing method, image processing apparatus, and program
US7657737B2 (en) * 2005-02-28 2010-02-02 International Business Machines Corporation Method for mapping an encrypted https network packet to a specific url name and other data without decryption outside of a secure web server
US20060206498A1 (en) 2005-03-10 2006-09-14 Kabushiki Kaisha Toshiba Document information management apparatus, document information management method, and document information management program
US20060285746A1 (en) 2005-06-17 2006-12-21 Sherif Yacoub Computer assisted document analysis
US20070143141A1 (en) * 2005-12-16 2007-06-21 Siemens Medical Solutions Health Services Corporation Integrated Clinical and Medication Reconciliation System
US20070214177A1 (en) 2006-03-10 2007-09-13 Kabushiki Kaisha Toshiba Document management system, program and method
US20080005194A1 (en) * 2006-05-05 2008-01-03 Lockheed Martin Corporation System and method for immutably cataloging and storing electronic assets in a large scale computer system
JP2007334470A (en) 2006-06-13 2007-12-27 Fuji Xerox Co Ltd Information processor and program regarding electronic tag

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6263121B1 (en) * 1998-09-16 2001-07-17 Canon Kabushiki Kaisha Archival and retrieval of similar documents

Also Published As

Publication number Publication date
US20110164820A1 (en) 2011-07-07
US20120236370A1 (en) 2012-09-20
US9305030B2 (en) 2016-04-05
US20130268568A1 (en) 2013-10-10
US8458155B2 (en) 2013-06-04
US8301611B2 (en) 2012-10-30
US20090177618A1 (en) 2009-07-09
US7882091B2 (en) 2011-02-01
US20170116170A1 (en) 2017-04-27

Similar Documents

Publication Publication Date Title
US9305030B2 (en) Records management system and methods
Hart Doing a literature search: A comprehensive guide for the social sciences
Rumsey How to find information: a guide for researchers
US20040216057A1 (en) System and method for grouping and organizing pages of an electronic document into pre-defined catagories
US20070219829A1 (en) Medical record association for disability determinations
US20070005637A1 (en) System for Litigation Management
US20060282468A1 (en) System for utilizing audible, visual and textual data with alternative combinable multimedia forms of presenting information for real-time interactive use by multiple users in different remote environments
WO2010129069A1 (en) Systems and methods for interactive disambiguation of data
Carter-Templeton et al. A bibliometric analysis of review types published in the nursing scientific literature
Deshpande et al. An integrated database and smart search tool for medical knowledge extraction from radiology teaching files
Dragon Form and genre access to academic library digital collections
Juricek Access to grey literature in business: An exploration of commercial white papers
Places et al. A workflow management system to feed digital libraries: proposal and case study
JP2000020549A (en) Device for assisting input to document database system
Galloway et al. The Heinz Electronic Library Interactive On-line System (HELIOS): An Update
Urberg Digital humanities projects and standards: Let’s get this conversation started!
Derrig et al. Effective Document Review Techniques in Eclipse and Relativity
Asfoor Applying Data Science Techniques to Improve Information Discovery in Oil And Gas Unstructured Data
Craft Local name authorities and linked data: the landscape
Galloway et al. The Heinz Electronic Library Interactive Online System (HELIOS): Building a Digital Archive Using Imaging, OCR, and Natural Language Processing Technologies.
Humble Computer-Assisted Qualitative Data Analysis Software (CAQDAS) and ethnographic health research
Kumar Design and implementation of an agricultural publication information system using metadata description: A web-based documentation and performance evaluation approach
Mount Role of Technical Reports in Sci-tech Libraries
Keshavarz et al. Improvement of Image Retrieval via Site Operator: Findings at a Website Level
Rinaldo et al. Supporting Natural History Collections by Connecting Collections

Legal Events

Date Code Title Description
AS Assignment

Owner name: MVC CAPITAL, INC. AS SUCCESSOR IN INTEREST TO FIFT

Free format text: AMENDED AND RESTATED SENIOR SUBORDINATED PATENT SECURITY AGREEMENT;ASSIGNORS:LEGAL SOLUTIONS HOLDINGS, INC.;MED-LEGAL, LLC;DEFENSEPRO, LLC;AND OTHERS;REEL/FRAME:039376/0424

Effective date: 20160715

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION