Vous êtes sur la page 1sur 14
as) United States US 20030120516A1 «2 Patent Application Publication co) Pub. No.: US 2003/0120516 Al Perednia 43) Pub. Date: Jun. 26, 2003 Ga) (7) (oo) INTERACTIVE RECORD-KEEPING AND METHOD TEM Inventor: Douglas A. Perednia, Portland, OR (us) Correspondence Address MARGER JOHNSON & MCCOLLOM PC 1030 SW MORRISON STREET PORTLAND, OR 97205 (US) Appl. No 10/300,672 Filed: Nov. 19, 2002 Related U.S. Application Data Provisional application No. 60/339,845, filed on Nov. (~~ / [—wermore \ ww ELECTRONIC PROCESSING DEVICE 10 ») a Publication Classification 1) In. cw GO6E 17/00; GO6F 17/60; GO6F 7/00 (2) US.CL 705)3; 707/104.1 6 ‘A medical record system has an electronic processing device ‘coupled to a network, a database stored on the electronic processing device, and a form generator for creation of encounter form corresponding 10 a set of data ficlds. A. ‘communicator transmits the encounter form via the network ABSTRACT to a remote location, the encounter form being siruetured to receive patient encounter information of a patient encounter atthe remote location. A data capture device can clectroni~ cally capture patient encounter information from. the ‘encounter form. The system can schedule events and moni- tor compliance therewith, As well, aa interactive medical ‘consent curator can create a consent form corresponding to ‘8 medical procedure, User inputs can be received and a session recorder employed! to record a consent session, o DATA CAPTURE DEVICE 50 ry DATA CAPTURE DEVICE 60 JRE DEVICE 50 | _.g DATA CAPTURE DEVICE 50 — cL TABASE 20 ences Patent Application Publication Jun. 26, 2003 Sheet 1 of 5 US 2003/0120516 Al — DATA CAPTURE DEVICE 50 FIG. 1 NETWORK DATA CAPTURE DEVICE 50 (ml DATA CAPTURE DEVICE 50 DATA CAPTURE DEVICE 50 COMMUNICATOR 40 DATABASE 20 ELECTRONIC PROCESSING DEVICE 10 FORM GENERATOR 30 _| Patent Application Publication FIG. 2 NETWORK COMMUNICATOR 40 —— en ELECTRONIC PROCESSING DEVICE 10 Jun. 26, 2003 Sheet 2 of 5 LI US 2003/0120516 AL —o DATA CAPTURE DEVICE 50 DATA CAPTURE DEVICE 50 DATA CAPTURE DEVICE 50 + ai DATA CAPTURE DEVICE 50 DATABASE 20 CALENDAR ELEMENT 60 Patent Application Publication Jun. 26, 2003 Sheet 3 of 5 US 2003/0120516 AL —2 DATA CAPTURE DEVICE 50 FIG. 3 NETWORK DATA CAPTURE DEVICE 50 CI DATA CAPTURE DEVICE 50 DATA CAPTURE DEVICE 50 COMMUNICATOR 40 PERFORMANCE TRACKER 70 A ELECTRONIC PROCESSING \* DEVICE 10 DATABASE 20 NN CALENDAR ELEMENT 60 , 2003 Sheet 4 of 5 US 2003/0120516 AL Patent Application Publication Jun. 2 FIG. 4 O DATA CAPTURE DEVICE 50 th DATA CAPTURE DEVICE 50 FAC | DATA CAPTURE DEVICE 50 DATA CAPTURE DEVICE 50 COMMUNICATOR 40 [— FORM GENERATOR 30 PERFORMANCE TRACKER 70 A ELECTRONIC PROCESSING }¢«———+—} DEVICE 10 DATABASE 20 CALENDAR ELEMENT 60 Patent Application Publication Jun. 26, 2003 Sheet 5 of 5 US 2003/0120516 Al FIG. 5 PATIENT CONSENT SESSION NETWORK —— | DIRECTORY | 92 Ly r—| SESSION RECORDER 90 ELECTRONIC PROCESSING }*+——~ DEVICE 10 CONSENT FORM GENERATOR 80 US 2003/0120516 AL INTERACTIVE RECORD-KEEPING SYSTEM AND, METHOD CROSS REFERENCE TO RELATED ‘APPLICATIONS [0001] ‘This application claims priority to U.S. Provisional Application Serial No. 60/339,845, filed on Nov. 19, 2001 and incorporated herein by reference. BACKGROUND OF THE INVENTION [0002] Patient medical information traditionally has been kept in paper-based medical records at a medical practice. Efforts have been made recently to digitalize medical records into what is commonly known as electronic medical record (EMR) systems. [0003] However, EMR systems lamely have been spurned by the medical community as difficult to use, physically ‘cumbersome, time-consuming, and costly. Physicians gen- erally have litle time to learn how to use EMR systems ‘compared (0 the simple pen-and-paper format. [0004] Storage of patient information in electronie form facilitates data searching, trending, and other related ben- ‘fits. However, EMR systems have provided no assistance to medical professionals in avoiding many common medical ‘errors that can be detected by data monitoring and trending. [0005] Traditional EMR systems, like the paper-based medical records that preceded them, generally have been stand-alone systems, A lack of integration has prevented use of patient data for epidemiological or other purposes. [0006] Further, most EMR systems are intended for use by ‘a physician or by medical ollice staff. Atypical EMR system therefore fails to satisfy a patient’s need for access fo health information, be it historical or specific to a current medical condition, BRIEF DESCRIPTION OF THE DRAWINGS [0007] The interactive record-keeping system and method disclosed herein will become more readily apparent from the following detailed description, which proceeds with refer- ‘ence to the drawings, in which: [0008] FIG. 1 is a block diagram ofa first embodiment of the present interactive record-keeping system; [0009] FIG. 2 is a block diagram of a second! embodiment ‘of the present system having a calendar element; [0010] | FIG.3 isa block diagram ofan alternative embodi- ‘ment ofthe system of FIG. 2, further having a performance tracker, [0011] _ FIG. 4s block diagram of an alternative embodi- iment of the system of FIG. 1, further having a calendar ‘element and a performance tracker; and [0012] FIG. $i block diagram of an interactive medical ‘consent curator. DETAILED DESCRIPTION OF PREFERRED EMBODIMENT(S) [0013] A interactive record-keeping system as deseribed herein serves as a repository for medical information about patients, Similar in a basic way to conventional electronic Jun. 26, 2003 medical record (EMR) systems, information generated dur- ing a healthcare provider visit can be inputted into such a system and stored in electronic form. [0014] The present system is adapted to provide patients ‘with health information specific to their current medical condition, The system also assists medical professionals in avoiding many common medical errors [0015] The system further is operative to produce encoun- ter forms specific to each patient that can be customized for ceach clinician, practice, or specialty. Encounter forms allow clinicians to record information manually, from which data ‘and images can be scanned into the system, Alternatively, information can be entered into the system manually or via anelectronic device such as an electronic tablet, and the data then can be uploaded to the system, [0016] Finally the system provides monitoring and statis- tical mechanisms to assist in the identification of various events and trends associated with bealth care. [0017] The below description of preferred embodiments focuses on a system adapted! for use in medical information management. It is readily understood that the present system efficaciously can be utilized in other arts An exemplary system provides a way to capture and store medical infor- mation ofa patient, such as medical information entered into a patient record, Patient information typicaly is entered into ‘a patient record by a health care provider, or agent thereof, during a patient encounter, ie. a medical oflice ot clinic vis ‘a hospital admission, an emergency room treatment or other such patient-care provider interaction, [0018] ‘The system includes an electronic processing device 10, such as a computer, coupled to @ network, The network can be, among others, a local-area, wide-area or slobal network, or a wireless’ network such as a radio- frequeney-based network: [0019] The electronic processing device 10 can be of a type well-known in the art (¢.2 desktop personal computer, laptop or notebook computer, personal digital assistant, cellular telephone or other electronic device) having a network interface [0020] A database 20 is coupled to the electronic process- ing device 10 and configured to contain a patient profile. The patient profile contains data of a type found in a patient medical record, but ean include additional information, [0021] A form generator 30 is operative to create an ‘encounter form. The encounter form includes fields corre- sponding fo set of data fields. The encounter form is, inthe present medical context, structured to be used by a care provider contemporaneous with a patient encounter. [0022] The form generator 30 is operative to generate an ‘encounter form that can present information and provide ‘prompts or opportunities for data input by the care provider, [0023] The form generator 30 is operative to present the fields of the encounter form in a variety of ways. For example, a data field can provide for a data input. The encounter form in a clinical setting typically is used to record patient information pertinent to the encounter. The encounter form therefore can be structured to receive an input coresponding to, for example, a measured physiologi- cal (€, weigh, temperature, a ab test resul), a patict

Vous aimerez peut-être aussi