Patent Issued for Flexible Encounter Tracking Systems And Methods (USPTO 10,381,113)

2019 AUG 23 (NewsRx) -- By a News Reporter-Staff News Editor at Hospital & Nursing Home Daily -- Allscripts Software LLC (Raleigh, North Carolina, United States) has been issued patent number 10,381,113, according to news reporting originating out of Alexandria, Virginia, by NewsRx editors.

The patent’s inventors are Klocek, Stefan Mills (Berkeley, CA); Loomis, Richard (Alameda, CA); Gordinier, II, Gerald (San Francisco, CA); Board, Jonathan (San Francisco, CA).

This patent was filed on April 27, 2015 and was published online on August 26, 2019.

From the background information supplied by the inventors, news correspondents obtained the following quote: “Field

“This field is generally related to documenting a patient interaction in an electronic health record.

“Background

“Electronic Health Records

“Medical records related to a patient’s health information are essential to the practice of medical care. Traditionally, medical records were paper-based documents. The emergence of electronic medical records (EMRs), which are a digital version of the paper chart that contains all of a patient’s medical history from one medical practice, offers medical professionals and patients with new functionalities and efficiencies that paper-based medical records cannot provide. An EMR, which can be incorporated into an electronic health record (EHR), is a collection of electronically stored information about an individual patient’s medical history. EHRs may contain a broad range of data, including demographics, medical history, medication history, allergies, immunization records, laboratory test results, radiology images, vital signs, personal statistics like age and weight, and billing information. Many commercial EHR systems combine data from a number of health care services and providers, such as clinical care facilities, laboratories, radiology centers, and pharmacies.

“EHRs are a drastic improvement over paper-based medical records. Paper-based medical records require a large amount of physical storage space. Paper records are often stored in different locations, and different medical professionals may each have different and incomplete records about the same patient. Obtaining paper records from multiple locations for review by a health care provider can be time consuming, complicated, and sometimes impossible. In contrast, EHR data are stored in digital format, and thus are more secure and can be accessed from anywhere. EHR systems significantly simplify the reviewing process for health care providers. Because records in EHRs can be linked together, EHRs vastly improve the accessibility of health records and the coordination of medical care.

“EHRs also decrease the risk of misreading errors by health care professionals. Poor legibility is often associated with handwritten, paper medical records, which can lead to medical errors. EHRs, on the other hand, are inherently legible given that they are typically stored in typeface. In addition, electronic medical records enhance the standardization of forms, terminology and abbreviations, and data input, which help ensure reliability of medical records, and standardization of codesets and storage of EHR data means that data from different technical information systems can be displayed in a single, unified record. Further, EHRs can be transferred electronically, thus reducing delays and errors in recording prescriptions or communicating laboratory test results.

“The benefits of digitizing health records are substantial. Health care providers with EHR systems have reported better outcomes, fewer complications, lower costs, and fewer malpractice claim payments. But despite EHRs’ potential in drastically improving the quality of medical care, only a low percentage of health care providers use EHR systems. While the advantages of EHRs are significant, they also carry concerns, including high costs, lost productivity during EHR implementation or computer downtime, and lack of EHR usability.

“The Health Insurance Portability and Accountability Act (HIPAA), enacted in the U.S. in 1996, and as amended, established rules for use and access of protected health information (PHI). HIPAA provides restrictions on disclosure of and access to protected health information to and by third parties. HIPAA applies to information in electronic medical records, such as health information doctors and nurses input, documented conversations between a doctor and a patient, and information use to process or facilitate medical billing claims and documents. The HIPAA Security Rule, effective on Apr. 20, 2005 for most covered entities, adds additional constraints to electronic data security and the storage and transmission of PHI.

“The high cost of EHRs also significantly hinders EHR adoption. A large number of physicians without EHRs have referred to initial capital costs as a barrier to adopting EHR systems. Cost concerns are even more severe in smaller health care settings, because current EHR systems are more likely to provide cost savings for large integrated institutions than for small physician offices. During the EHR technology’s setup and implementation process, productivity loss can further offset efficiency gains. The need to increase the size of information technology staff to maintain the system adds even more costs to EHR usages.

“Usability is another major factor that holds back adoption of EHRs. It is particularly challenging to develop user-friendly EHR systems. There is a wide range of data that needs to be integrated and connected. Complex information and analysis needs vary from setting to setting, among health care provider groups, and from function to function within a health care provider group. To some providers, using electronic medical records can be tedious and time consuming, and the complexity of some EHR systems renders the EHR usage less helpful. Some doctors and nurses also complain about the difficulty and the length of time to enter patients’ health information into the system.

“Under-utilization of EHR systems, despite incentives and mandates from the government and the tremendous potential of EHRs in revolutionizing the health care system, calls for better EHR systems that are secure, cost-effective, efficient, and user-friendly.

“Comprehensive EHR systems can provide capabilities far beyond simply storing patients’ medical records. Because EHR systems offer health care providers and their workforce members the ability to securely store and utilize structured health information, EHR systems can have a profound impact on the quality of the health care system. In Framework for Strategic Action on Health Information Technology, published on Jul. 21, 2004, the Department of Health & Human Services (HHS) outlined many purposes for EHR services. The outlined purposes include, among other things, improving health care outcomes and reducing costs, reducing recordkeeping and duplication burdens, improving resource utilization, care coordination, active quality and health status monitoring, reducing treatment variability, and promoting patients’ engagement in and ownership over their own health care.

“Recent legislation has set goals and committed significant resources for health information technology (HIT). One of the many initiatives of the American Recovery and Reinvestment Act of 2009 (ARRA) was ‘to increase economic efficiency by spurring technological advances in science and health.’ The Health Information Technology for Economic and Clinical Health (HITECH) Act, passed as a part of ARRA, allocated billions of dollars for health care providers to adopt and meaningfully use EHRs in their practices. HITECH also mandates the Office of the National Coordinator for Health Information Technology (ONC) to define certification criteria for ‘Certified EHR Technology.’

“EHR systems satisfying ‘Certified EHR Technology’ criteria are capable of performing a wide range of functions, including: entry and storage, transmission and receipt of care summaries, clinical decision support, patient lists and education resources, generation of public health submission data, and patient engagement tools. Entry and storage is related to the ability to enter, access and modify patient demographic information, vital signs, smoking status, medications, clinical and radiology laboratory orders and results. Transmission and receipt of care summaries involve the ability to receive, incorporate, display and transmit transition of care/referral summaries. Clinical decision support features configurable clinical decision support tools, including evidence-based support interventions, linked referential clinical decision support, and drug-drug and drug-allergy interaction checks. Patient lists and education resources include the ability to create patient lists based on problems, medications, medication allergies, demographics and laboratory test result values, and the ability to identify patient-specific education resources based on such data elements. Generating public health submission data allows users to create electronic immunization and syndromic surveillance data files that can be submitted to public health agencies. Patient engagement tools allow medical professionals to grant patients with an online means to view, download and transmit their health information to a third party, provide patients with clinical summaries after office visits, and facilitate secure-doctor patient messaging.

“Cumbersome Data Access, Data Arrangement, and Loss of Historical Data

“The conventional access of interfaces in a patient’s electronic medical chart as well as the organization of data within an interface can sometimes make a healthcare provider’s practice difficult, because the interfaces do not align with the healthcare provider’s work flow. During an interaction with a patient, a user of an EHR system (e.g., the healthcare provider such as a physician or a nurse) typically accesses many separate interface presentations or pages of data in the patient’s EHR before making and documenting medical decisions and treatments in a separate note interface. It can be cumbersome and difficult for the user to flip back and forth to find the data they need.

“Further, only data that the user enters in the note interface is saved when the note is electronically signed. Later, when a user returns to the patient’s EHR, the user may not remember what data was present in the separate interfaces when medical decisions and treatments were documented in the note interface. Some users copy and paste data from various interfaces into the separate note interface. This can be a time-consuming and frustrating effort. In addition, some users may create shortcuts within a note interface that links to a different interface (e.g., an Allergies interface). But, after the note interface is saved, the data linked via the shortcut on the note interface (e.g., the Allergies interface) continues to change over time. Thus, a record of the data available at the time the note is signed is lost.”

Supplementing the background information on this patent, NewsRx reporters also obtained the inventors’ summary information for this patent: “Embodiments include a customizable encounter document whose contents are populated based on a template for the current patient, a template for all the user’s patients, or a combination of templates. The contents are presented in one view, a scrollable pane, to assist the user when making medical decisions. The user can make changes to the contents on the scrollable pane in real time that may affect the current patient’s template, the template for all the patients, or a combination of templates. Once the customizable encounter document is signed, the contents are captured, saved, and linked to the patient’s electronic medical chart.

“The scrollable pane is populated with data modules pulled from various databases and arranged according to the user’s work flow. The user further customizes the scrollable pane in real time (e.g., during a patient interaction, the user changes the sequence of the data modules, removes/adds data modules, or nests a data module within another data module). The customization affects the current encounter document of the patient, the patient’s template for the type of encounter (e.g., if the customization was for an office visit encounter, the customization affects future office visit encounter documents associated with the patient), the template for all the user’s patients (e.g., the customization affects future office visit encounter documents for all of the user’s patients), or a combination of templates.

“When a portion of the scrollable pane contents is being adjusted, the contents not being adjusted remain present in the scrollable pane. Once a user signs the encounter document of the patient interaction, a snapshot of the data in the scrollable pane is captured and saved in the patient’s EHR. Thus, the data available at the time the encounter document is signed are preserved, and viewable by the user.

“Embodiments include a method, computer-readable storage, and system for documenting an encounter including retrieving an electronic health record (EHR) of a patient, receiving a request to open an encounter document associated with the patient, and populating a scrollable pane of the encounter document based on at least one of an encounter document template of the patient, an encounter document template for all patients, or a combination of templates. The populating includes accessing one or more databases. The contents of the scrollable pane comprise at least one of a data module, a subsection, or data. Embodiments also include adjusting, in real time, at least one of the data module, the subsection, or the data, where the contents not being adjusted remain present in the scrollable pane. Embodiments further include updating, based on the real-time adjusting, at least one of the encounter document template of the patient, the encounter document template for all patients, or a selected combination of templates. After a user electronically signs the encounter document, embodiments include creating a permanent snapshot of the encounter document, where the contents of the scrollable pane are not changeable, storing the permanent snapshot, and storing a link of the permanent snapshot with the user and/or the patient’s electronic medical chart.

“Further embodiments, features, and advantages, as well as the structure and operation of the various embodiments, are described in detail below with reference to accompanying drawings.”

The claims supplied by the inventors are:

“What is claimed is:

“1. A computer-implemented method for documenting an encounter, comprising: transmitting a query comprising a patient identifier from a client electronic health record (EHR) application executing on a client computing device to a server EHR in network communication with the client EHR; receiving an EHR of a patient assigned to the patient identifier from the server EHR; receiving a request to open an encounter document associated with the patient within a graphical user interface (GUI) of the client EHR, wherein the encounter document comprises clinical data received at the client EHR during a patient encounter; populating a scrollable pane of the GUI based on at least one of an encounter document template of the patient, an encounter document template for all patients, or a combination of templates, wherein the populating comprises transmitting a query to one or more databases and populating contents of the scrollable pane of the GUI with data retrieved based upon the query to the one or more databases, wherein the contents of the scrollable pane of the GUI comprise at least one of a data module, a subsection, or data; adjusting, in real-time, at least one of the data module, the subsection, or the data, wherein contents not being adjusted remain present in the scrollable pane of the GUI; updating, based on the real-time adjusting, at least one of the encounter document template of the patient, the encounter document template for all patients, or the combination of templates; after a user electronically signs the encounter document, creating a permanent snapshot of the encounter document, wherein the contents of the scrollable pane are not changeable; transmitting a de-identified version of the permanent snapshot for storage within a database maintained by the server EHR; and transmitting a link to the de-identified version of the permanent snapshot with at least one of the user’s or the patient’s EHR for storage within the database maintained by the server EHR.

“2. The method of claim 1, wherein the real-time adjusting comprises modifying a sequence of at least one of the data module, the subsection, or the data.

“3. The method of claim 2, wherein the modifying the sequence comprises creating a hierarchically nested data module.

“4. The method of claim 1, wherein the real-time adjusting comprises adding, modifying, or removing at least one of the data module, the subsection, or the data.

“5. The method of claim 1, wherein the encounter document template of the patient is based on at least one of: an encounter type, a medical condition, or a patient age.

“6. The method of claim 5, wherein the encounter type comprises at least one of: an office visit encounter, a hospital visit encounter, a telephone encounter, or an order encounter.

“7. A program storage device tangibly embodying a program of instructions executable by at least one processor to perform operations for documenting an encounter, comprising: transmitting a query comprising a patient identifier from a client electronic health record (EHR) application executing on a client computing device to a server EHR in network communication with the client EHR application; receiving an electronic health record (EHR) of a patient assigned to the patient identifier from the server EHR; receiving a request to open an encounter document associated with the patient within a graphical user interface (GUI) of the client EHR, wherein the encounter document comprises clinical data received at the client EHR during a patient encounter; populating a scrollable pane of the encounter document based on at least one of an encounter document template of the patient, an encounter document template for all patients, or a combination of templates, wherein the populating comprises transmitting a query for clinical data in the at least one of the encounter document template of the patient, an encounter document template for all patients, or a combination of templates to one or more databases and populating contents of the scrollable pane of the GUI with the clinical data assigned to the patient identified retrieved from the query to the one or more databases wherein the contents of the scrollable pane of the GUI comprise at least one of a data module, a subsection, or data; adjusting, in real-time, at least one of the data module, the subsection, or the data, wherein contents not being adjusted remain present in the scrollable pane; updating based on the real-time adjusting, at least one of the encounter document template of the patient, the encounter document template for all patients, or the combination of templates; after a user electronically signs the encounter document, creating a permanent snapshot of the encounter document, wherein the contents of the scrollable pane are not changeable; storing a de-identified version of the permanent snapshot; and transmitting a link to the de-identified version of the permanent snapshot with at least one of the user’s or the patient’s EHR for storage within the database maintained by the server EHR.

“8. The program storage device of claim 7, wherein the real-time adjusting comprises modifying a sequence of at least one of the data module, the subsection, or the data.

“9. The program storage device of claim 8, wherein the modifying the sequence comprises creating a hierarchically nested data module.

“10. The program storage device of claim 7, wherein the real-time adjusting comprises adding, modifying, or removing at least one of the data module, the subsection, or the data.

“11. The method of claim 7, wherein the encounter document template of the patient is based on at least one of: an encounter type, a medical condition, or a patient age.

“12. The method of claim 11, wherein the encounter type comprises at least one of: an office visit encounter, a hospital visit encounter, a telephone encounter, or an order encounter.

“13. A system for documenting an encounter, comprising: one or more processors; a memory storing instructions that, when executed by the one or more processors, cause the one or more processors to: transmit a query comprising a patient identifier from a client electronic health record (EHR) application executing on a client computing device to a server EHR in network communication with the client EHR; receive an EHR of a patient assigned to the patient identifier from the server EHR; receive a request to open an encounter document associated with the patient within a graphical user interface (GUI) of the client EHR, wherein the encounter document comprises clinical data received at the client EHR during a patient encounter; populate a scrollable pane of the encounter document based on at least one of an encounter document template of the patient, an encounter document template for all patients, or a combination of templates, wherein populating the scrollable pane comprises transmitting a query for clinical data in the at least one of the encounter document template of the patient, an encounter document template for all patients, or a combination of templates to one or more databases and wherein the contents of the scrollable pane of the GUI comprise at least one of a data module, a subsection, or data; adjust, in real-time, at least one of the data module, the subsection, or the data, wherein contents not being adjusted remain present in the scrollable pane; update, based on the real-time adjustment, at least one of the encounter document template of the patient, the encounter document for all patients, or the combination of templates; after a user electronically signs the encounter document, create a permanent snapshot of the encounter document, wherein the contents of the scrollable pane are not changeable; transmit a de-identified version of the permanent snapshot for storage within the database maintained by the server EHR; and transmit a link to the de-identified version of the permanent snapshot with at least one of the user’s or the patient’s EHR for storage within the database maintained by the server EHR.

“14. The system of claim 13, wherein the real-time adjustment comprises a modification to a sequence of at least one of the data module, the subsection, or the data.

“15. The system of claim 14, wherein modifying the sequence of at least one of the data module, the subsection, or the data comprises creating a hierarchically nested data module.

“16. The system of claim 13, wherein the real-time adjustment comprises: an addition to at least one of the data module, the subsection, or the data; a modification to at least one of the data module, the subsection, or the data; or a removal of at least one of the data module, the subsection, or the data.

“17. The system of claim 13, wherein the encounter document template of the patient is based on at least one of: an encounter type, a medical condition, or a patient age.

“18. The system of claim 17, wherein the encounter type comprises at least one of: an office visit encounter, a hospital visit encounter, a telephone encounter, or an order encounter.”

For the URL and additional information on this patent, see: Klocek, Stefan Mills; Loomis, Richard; Gordinier, II, Gerald; Board, Jonathan. Flexible Encounter Tracking Systems And Methods. U.S. Patent Number 10,381,113, filed April 27, 2015, and published online on August 26, 2019. Patent URL: http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO1&Sect2=HITOFF&d=PALL&p=1&u=%2Fnetahtml%2FPTO%2Fsrchnum.htm&r=1&f=G&l=50&s1=10,381,113.PN.&OS=PN/10,381,113RS=PN/10,381,113

(Our reports deliver fact-based news of research and discoveries from around the world.)