SYSTEM, CLIENT DEVICE, SERVER AND METHOD FOR PROVIDING A CROSS-FACILITY PATIENT DATA MANAGEMENT AND REPORTING PLATFORM

• US 20150169827A1
• Filed: 02/03/2015
• Published: 06/18/2015
• Est. Priority Date: 12/23/2011
• Status: Active Grant

• Current Assignee: David Laborde
• Original Assignee: David Laborde
• Inventors: LaBorde, David
• Granted Patent: US 10,354,750 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06Q 2220/10 Usage protection of distributed data files
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04L 9/0861 Generation of secret information including derivation or calculation of cryptographic keys or passwords

Abstract

A system for providing a patient list manager includes a client device for point of care capture and access of patient data and a server for providing cloud based hosting. One or more modules can leverage the patient data to help users improve and facilitate the efficiency and safety of patient management, diagnostic imaging management, clinical work flows, charge capture, revenue cycle management, accreditation reporting, quality and outcomes monitoring and improvement, among other things.

Claims

1. A patient list manager device comprising:

a transceiver configured to receive a resource request from a remote patient list manager client device, the resource request including a verification credential issued from a certification authority and a user name;

a controller operatively coupled to the transceiver; and

one or more memory sources operatively coupled to the controller, the one or more memory sources including a patient list database and instructions for configuring the controller,

wherein the instructions configure the controller to;

verify the resource request by confirming that the certification authority is one of a number of predetermined trusted certification authorities to establish a secure communication session between the patient list manager device and the patient list manager client device; and

determine data in the patient list database that is associated with the user name,

encrypt at least a portion of the determined data in accordance with a predetermined encryption protocol to be sent to the patient list manager client device during the secure communication session by the transceiver,

wherein the patient list database includes a plurality of patient identifications and patient attributes associated with each of the patient identifications, the patient attributes include a facility, an encounter type for a care episode, a diagnosis for the care episode, and a disposition type for the care episode.

2. The patient list manager device of claim 1, wherein:

the transceiver is further configured to receive a patient data modification request from the patient list manager client device; and

the controller is further configured to modify the data in the patient list database that is associated with the user name in accordance with the patient data modification request,

modifying the data in the patient list database includes;

modifying one or more of the patient attributes associated with one or more of the patient identifications indicated in the patient data modification request;

adding a new patient identification and patient attributes associated with the new patient identification to the patient list database; and

classifying one of the patient identifications associated with the user name from the patient list database as removed.

3. The patient list manager device of claim 2,

wherein the classifying of one or more of the patient attributes associated with one of the patient identifications includes adding a tag to an episode of care to indicate a morbidity,

wherein the resource request is a hypertext transfer protocol (http) request, and

wherein the encrypting is performed in accordance with HMACsha256 secret key encryption.

4. The patient list manager device of claim 1, wherein:

the controller is further configured to determine if the user name is an administrative level user name, and

when the user name is determined to be an administrative level user name, determining the data in the patient list database further includes;

determining a plurality of user names that are associated with the administrative level user name; and

determining all data associated with each of the plurality of user names to be sent as the encrypted data to the remote patient list manager client device during the secure communication session.

5. The patient list manager device of claim 4, wherein when the controller determines the user name is the administrative level user name:

the transceiver is configured to receive one of an administrative level data modification request and an audit log request from the patient list manager client device; and

the controller is configured to modify the data in the patient list database that is associated with the administrative level user name in accordance with the administrative level data modification request and to generate encrypted historical usage information associated with the administrative level user name to be sent to the remote patient list manager client device during the secure communication session in response to the audit log request.

6. The patient list manager device of claim 4, wherein:

the transceiver is further configured to receive an encounter query request from the patient list manager client device, the encounter query request includes one or more parameters for clinical encounters; and

the controller generates historical clinical encounters associated with the administrative level user name and based upon the one or more parameters to be sent to the remote patient list manager client device during the secure communication session.

7. The patient list manager device of claim 6, wherein the one or more parameters for clinical encounters include date ranges associated with procedures and admissions, encounter types, facility names, one or more physicians, disposition types and morbidity.

8. The patient list manager device of claim 1, wherein the patient attributes associated with each of the patient identifications further includes a procedure, a physician name, and a role of the physician during the procedure.

9. The patient list manager device of claim 1, wherein:

the transceiver is further configured to receive an imaging request to access a picture archiving communication and systems (PACS) server from the remote patient list manager client device, the imaging request including the verification credential and the user name, the imaging request including one of a request to store a diagnostic image and a request to retrieve a diagnostic image, the imaging request including the diagnostic image as encrypted data when the imaging request is to store the diagnostic image,

wherein the instructions further configure the controller to;

confirm that the certificate authority which issued the verification credential is one of a number of predetermined trusted certificate authorities to establish a secure communication session between the remote patient list manager client device and the PACS server;

when the imaging request includes a request to retrieve the diagnostic image, pull the diagnostic image from the PACS server, and encrypt the diagnostic image to be sent to an originator of the imaging request; and

when the imaging request includes a request to store the diagnostic image, decrypting the data to obtain the diagnostic image from the imaging request, re-encrypt the diagnostic image, associated the re-encrypted diagnostic image with the user name and store the re-encrypted diagnostic image at the PACS server.

10. The patient list manager device of claim 1, wherein:

the transceiver is further configured to receive a revenue cycle management (RCM) request from an RCM device, the RCM request including another verification credential issued from a certificate authority and the user name or another user name, the revenue management request including a request to associate a RCM attribute to one or more patient identifications;

wherein the instructions further configure the controller to;

confirm that the certificate authority which issued the another verification credential is one of the number of predetermined trusted certificate authorities to establish a secure communication session between the patient list manager device and the revenue cycle management device;

store the revenue attribute in the patient list database associated with the one or more patient identifications; and

activate a revenue attribute flag associated with the one or more patient identifications.

18. The patient list manager device of claim 1,

wherein the one or more memory sources include instructions for providing a resource available to the patient list client device via a plurality of REST-like, REST-ful, and RPC based application program interfaces.

19. The patient list manager device of claim 1, wherein the verification credential includes an access token or a refresh token.

11. A patient list manager client device comprising:

a transceiver for communicating with a patient list manager device via a connection to a network;

a controller coupled to the transceiver; and

a memory coupled to the controller, the memory including instructions to configure the controller to;

generate a resource request including an authentication credential to be sent to the patient list manager device;

decrypt data received from the patient list manager device in response to the resource request; and

generate a top level display based upon the decrypted data, wherein the top level display includes a patient list graphical interface, wherein a patient list display is generated when the patient list graphical interface in the top level display is selected, wherein the patient list display includes;

one or more graphical interface filters, each of the one or more graphical interface filters including a plurality of selectable patient attributes, wherein one or more identifications of patients and patient attributes associated with the one or more identifications of patients are displayed in the patient list display in accordance with patient attributes selected;

an add patient graphical interface;

wherein an add patient display is generated when the add patient graphical interface in the top level display is selected, the add patient display subsequent in hierarchy to the patient list display, the add patient display including;

an open text filter field for receiving data attributes of a patient to be added;

one or more classifying graphical interfaces including a plurality of selectable options for classifying the patient to be added, wherein the one or more classifying graphical interfaces includes encounter type graphical interfaces including encounter types for a care episode for the patient to be added and diagnosis graphical interfaces including diagnosis types for the care episode,

a procedure graphical interface for entering data relating to a new procedure or modifying data relating to an existing procedure, wherein the procedure graphical interface includes a graphical interface for entering a physician name, a role of the physician and selecting from a list of procedure types;

a remove patient graphical interface;

wherein a remove patient display is generated when the remove patient graphical interface in the top level display is selected, the remove patient display subsequent in hierarchy to the patient list display, the remove patient display includes a disposition type graphical interface including a list of disposition types for a care episode for a patient to be removed, a tag option for indicating a particular episode of care as a morbidity, and an open text field for providing additional details, and

the controller is further configured to generate an add patient request including parameters defined by the open text filter field, the one or more classifying graphical interfaces, and the procedure graphical interface, and a remove patient request including parameters defined by the disposition type graphical interface, the tag option and the open text field,

the transceiver sends the add patient request and the remove patient request to the patient list manager device so that data in a patient list database is modified in accordance with the add patient request and the remove patient request.

12. The patient list manager client device of claim 11, wherein the one or more graphical interface filters of the patient list display include a first filter including a list of hospitals;

and a second filter including a list of physicians and groups of physicians.

13. The patient list manager client device of claim 11, wherein the patient attributes displayed in the patient list display in accordance with patient attributes selected include a hospital or care facility associated with the authentication credential, and a type of unit or physician group associated with the hospital or care facility.

14. The patient list manager client device of claim 13, wherein:

the top level display further includes an administrative level graphical interface;

an administrative level display is generated when the administrative level graphical interface is selected, the administrative level display subsequent in hierarchy to the top level display, the administrative level display including an audit log graphical interface and a list of a plurality of top level parameters which can be modified,

wherein when the audit log graphical interface is selected, historical usage information is displayed;

wherein when one of the top level parameters is selected, a modification display for the one of the top level parameters is generated in which the selected one of the top level parameter can be modified, the modification display for each of the top level parameters including a graphical interface displaying respective data and a free text input field for filtering data displayed for the respective top level parameter.

15. The patient list manager client device of claim 11, wherein:

the top level display further includes an encounter query graphical interface;

a query engine interface display including query parameters for querying historical clinical encounters is generated when the encounter query graphical user interface is selected, wherein the query parameters include date ranges associated with procedures and admissions, encounter types, facility names, one or more physicians, disposition types and morbidity; and

the query engine interface display includes a results area in which information is displayed based upon the decrypted data received and received query parameters.

16. The patient list manager client device of claim 11,

the top level display further includes an images query graphical interface, and

wherein the controller is further configured to generate an upload screen for uploading a diagnostic image associated with a patient to the patient list manager or view one or more diagnostic images associated with the patient inside an embedded Digital Imaging and Communication in Medicine (DICOM) viewer.

17. The patient list manager client device of claim 11, wherein the controller is further configured to generate a revenue cycle management (RCM) display, the RCM display including a plurality of RCM data entry graphical interfaces for entering RCM data relating to a service provided during a patient encounter, an RCM list view including one or more RCM events based upon the decrypted data.