MEDICAL SOFTWARE APPLICATION AND MEDICAL COMMUNICATION SERVICES SOFTWARE APPLICATION

• US 20130110547A1
• Filed: 03/19/2012
• Published: 05/02/2013
• Est. Priority Date: 04/07/2011
• Status: Abandoned Application

• Current Assignee: Master VET Products
• Original Assignee: Master VET Products
• Inventors: Carson, Dennis, Englund, Karl
• Application Number:
  US13/423,442
• Publication Number:
  US 20130110547A1
• Time in Patent Office: Days
• US Class Current: 705/3
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 40/20 for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms

Abstract

A portable electronic device includes a memory and processor. The memory stores automatic configuration instructions, which are part of a healthcare mobile software application (MedMaster Mobility) and called upon when the device attempts connectivity. The instructions cause the device to serve as an EHR-agnostic, native mobile tablet front-end solution to virtually any existing Health Information Technology (HIT) systems, thus allowing practitioners to use MedMaster Mobility at multiple facilities that may each be running a disparate HIT system. Built entirely on independent modules, MedMaster Mobility provides a seamless way to populate the Electronic Health record (EHR). It is designed to fit in the workflow, style and work habits of users. MedMaster Mobility is not a basic cluttered view of clinical data from a PC using a Web access client such as Remote Desktop type products.

Claims

1. A computer-implemented method whether using local or cloud-based server for a portable electronic device operating in a healthcare environment, the portable electronic device including a memory and a processor, the memory storing instructions which when executed by the processor, cause the portable electronic device via Wi-Fi if Wi-Fi is not available or in the alternative on a cellular phone network but not using a Remote Desktop type connection to:

transmit a request to display the Login View of the available Electronic Health Records (EHR) or Electronic Medical Records (EMR) systems whether local or cloud-based and regardless of which legacy Health Information Technology (HIT) is in use at the facility;

request a connection to a selected EHR or EMR system server, whether local or cloud-based and regardless of which legacy Health Information Technology (HIT) is in use at the facility;

receive confirmation that the user has valid credentials to connect to the selected EHR or EMR system server;

receive connection to the selected EHR or EMR system server, whether or not the healthcare provider uses Epic, Allscripts, Cerner, GE Healthcare, Open EMR, Open Vista, World Vista, Practice Fusion, NextGen, or any of the other leading EHR or EMR solution;

provide optional seamless and effortless connections to a Health Information Exchange (HIE) platform that is specifically designed for HL7 message integration;

assure safe and secure delivery in a standardized MedMaster Mobility mobile tablet device interface of the six critical rights of information management and exchange;

getting the right information to the right person at the right time in the right place in the right format for the right value, even from different HIE systems from anywhere at anytime;

reduce overhead by optimizing the use of staff and capital resources throughout the healthcare chain;

allow access and interact with the various fully customizable core functions with the EHR or EMR; and

display the Launch View for the core functions of the medical software application such as but not limited to, My Schedule, My Patients, My Workups, Prescriptions, My Billing, SOAP, My Contacts, and My Resources.

2. The computer-implemented method of claim 1 whether using local or cloud-based server, further includes instructions, which when executed by the processor cause the portable electronic device via Wi-Fi if Wi-Fi is not available or in the alternative on a cellular phone network but not using a Remote Desktop type connection to:

transmit a request to display and interact with the user'"'"'s daily schedule using the My Schedule View;

receive connection to the selected EHR or EMR system server; and

display the My Schedule view which allows the doctor to instantly see the patients and interact with those scheduled for the day. The Status (Checked-In, Checked-Out, Examined, No Show) of each patient is color-coded. The Appointment Time, Patient Name, Location, and Room Number are also displayed.

3. The computer-implemented method of claim 1 whether using local or cloud-based server, further includes instructions, which when executed by the processor cause the portable electronic device via Wi-Fi if Wi-Fi is not available or in the alternative on a cellular phone network but not using a Remote Desktop type connection to:

transmit a request to display and interact with the doctor'"'"'s patients using the My Patients View;

receive connection to the selected EHR or EMR system server;

display and interact with the Patient Chart view which is a comprehensive view of the patient'"'"'s medical record that may be conveniently appended using speech recognition. Each of the active problems, lab results, among others is selectable to see the full details and reports; and

display and interact with personal information, insurance information, and guarantor information. Using speech recognition for navigation or the tap of a finger a doctor can access the Patient'"'"'s Full Chart, Orders, Progress Notes, Allergies, and to Prescribe Medications, Admit Patient, Refer a Patient, Excuse Slips, and Advanced Directives, among other options,

4. The computer-implemented method of claim 1 whether using local or cloud-based server, further includes instructions, which when executed by the processor cause the portable electronic device via Wi-Fi if Wi-Fi is not available or in the alternative on a cellular phone network but not using a Remote Desktop type connection to:

transmit a request to display and interact with the doctor'"'"'s workups using the My Workups View;

receive connection to the selected EHR or EMR system server; and

display and interact with the My Workups View.

5. The computer-implemented method of claim 1 whether using local or cloud-based server, further includes instructions, which when executed by the processor cause the portable electronic device via Wi-Fi if Wi-Fi is not available or in the alternative on a cellular phone network but not using a Remote Desktop type connection to:

transmit a request to display and interact with the doctor'"'"'s patients'"'"' prescriptions using the Prescriptions View;

receive connection to the selected EHR or EMR system server; and

display and interact with patient Prescriptions.

6. The computer-implemented method of claim 1 whether using local or cloud-based server, further includes instructions, which when executed by the processor cause the portable electronic device via Wi-Fi if Wi-Fi is not available or in the alternative on a cellular phone network but not using a Remote Desktop type connection to:

transmit a request to display and interact with the doctor'"'"'s billing module using the My Billing View;

receive connection to the selected EHR or EMR system server; and

display and interact with the billing module for payment and payment options selected.

7. The computer-implemented method of claim 1 whether using local or cloud-based server, further includes instructions, which when executed by the processor cause the portable electronic device via Wi-Fi if Wi-Fi is not available or in the alternative on a cellular phone network but not using a Remote Desktop type connection to:

transmit a request to display and interact with the doctor'"'"'s encounter with his patients using the S.O.A.P. View;

receive connection to the selected EHR or EMR system server; and

display and interact with the S.O.A.P. View, which includes a Subjective and Objective Patient Assessment followed by Treatment Plan.

8. The computer-implemented method of claim 1 whether using local or cloud-based server, further includes instructions, which when executed cause the processor via Wi-Fi if Wi-Fi is not available or in the alternative on a cellular phone network but not using a Remote Desktop type connection to:

transmit a request to display and interact with the doctor'"'"'s professional and personal contacts using the My Contacts View;

receive connection to the selected EHR or EMR system server; and

display and interact with the My Contacts View.

9. The computer-implemented method of claim 1 whether using local or cloud-based server, further includes instructions, which when executed by the processor cause the portable electronic device via Wi-Fi if Wi-Fi is not available or in the alternative on a cellular phone network but not using a Remote Desktop type connection to:

transmit a request to display and interact with the doctor'"'"'s selected external links or native videos using the My Resources View;

receive connection to the selected EHR or EMR system server;

display and interact with the My Resources View.

10. The computer-implemented method for claims 1 though 9 whether using local or cloud-based server further includes instructions which when executed by the processor, causes the computing device deploy via Wi-Fi if Wi-Fi is not available or in the alternative on a cellular phone network but not using a Remote Desktop type connection to:

transmit a request to engage medical speech recognition for purposes of dictation and navigation;

receive connection to bi-directional audio from speech recognition software; and

transmits first to the built-in Remote Desktop receiver using MedMaster Mobility and that receiver in turn takes that audio and sends it to the host application that resides on a Remote Desktop server.

11. The computer-implemented method for claims 1 though 9 whether using local or cloud-based server further includes instructions which when executed by the processor, causes the computing device deploy via Wi-Fi if Wi-Fi is not available or in the alternative on a cellular phone network but not using a Remote Desktop type connection to:

transmit a request to engage medical speech recognition for purposes of dictation and navigation;

receive connection to bi-directional audio from speech recognition software;

capture the uniqueness of each patient encounter and document the clinical decision-making process without the limitations of rigid documentation templates;

help physicians capture all the information needed for coding in ICD-10, in real time, at the point of documentation without manual data entry;

create ICD-9-compliant clinical documentation and streamlines the transition from ICD-9 to ICD-10;

identify key patient data and automatically saves it as structured data in the EHR'"'"'s database, where information can be analyzed, reported and used for better patient care;

analyze free text dictation, and then tags the most important clinical data elements such as medications, problems, social history, allergies, and procedures;

streamline EHR population from the narrative by automatically extracting clinical facts from dictation and then placing that data into the appropriate fields in each respective form facilitate more accurate coding;

finish notes more quickly, thus enabling more one-on-one time with patients, which enhances patient satisfaction and outcomes;

ensure that the spelling of some inanely spelled medication will be correct;

preserve the patient'"'"'s unique clinical story by eliminating point-and-click and reliance on keyboard and mouse;

enable physicians to document their clinical decision making processes;

integrate into physician and enterprise workflows;

support compliance with CCHIT EHR certification criteria; and

dictate the chart note in the room with the patient sitting there, print it out, and then hand the patient a copy right then and there.

12. A computer-implemented method for claims 1 though 9 whether using local or cloud-based server for a portable electronic device operating in a healthcare environment, the portable electronic device including a memory and a processor, the memory storing instructions which when executed by the processor, cause the portable electronic device via Wi-Fi if Wi-Fi is not available or in the alternative on a cellular phone network but not using a Remote Desktop type connection for interoperability to:

facilitate Computerized Physician Order Entry (CPOE);

facilitate Clinical Decision Support (CDS);

facilitate Picture Archiving along with Communications Systems (PACS);

facilitate E-prescribing

13. A computer-implemented method for claims 1 though 9 whether using local or cloud-based server for a portable electronic device operating in a healthcare environment, the portable electronic device including a memory and a processor, the memory storing instructions which when executed by the processor, cause the portable electronic device via Wi-Fi if Wi-Fi is not available or in the alternative on a cellular phone network but not using a Remote Desktop type connection to:

allow patients to interact with their practitioner by email or video chat, and to view test results and upcoming &

past appointments, schedule appointments, pay bills securely and saving phone calls and mailing expenses, get automated health maintenance reminders, request refills, manage the care of elderly parents, and access benefit and eligibility information, referral authorizations and account balances;

allow healthcare entities to implement as well as execute cost-containment strategies such as cost-effective revenue cycle processes, more efficient management of patients within systems, reduction of the accreditation and credentialing steps;

provide a wealth of information at the time and place of care; and

provide reliable and accurate patient history, enables providers to perform a more accurate, focused patient evaluations, reduced costs to patients and healthcare system, and improved overall patient care.

14. A computer-implemented method for claims 1 though 9 whether using local or cloud-based server for a portable electronic device operating in a healthcare environment, the portable electronic device including a memory and a processor, the memory storing instructions which when executed by the processor, cause the portable electronic device via Wi-Fi if Wi-Fi is not available or in the alternative on a cellular phone network but not using a Remote Desktop type connection to facilitate connectivity by using existing API'"'"'s. This would be a SOAP or REST solution that would:

create a connection to API server;

send request to API; and

receive and parse the results.

15. A computer-implemented method for claims 1 though 9 whether using local or cloud-based server for a portable electronic device operating in a healthcare environment, the portable electronic device including a memory and a processor, the memory storing instructions which when executed by the processor, cause the portable electronic device via Wi-Fi if Wi-Fi is not available or in the alternative on a cellular phone network but not using a Remote Desktop type connection to facilitate connectivity by creating an extremely thin middleware service to reside on a server. This thin client would be a REST solution, its functions are:

create/maintain a connection to the appropriate database

receive requests (via PHP or otherwise)

pass SQL/Query statement directly to the database receive the results

return XML or JSON response