Protected health information image capture, processing and submission from a mobile device

• US 10,492,062 B2
• Filed: 03/28/2014
• Issued: 11/26/2019
• Est. Priority Date: 03/28/2013
• Status: Active Grant

• Current Assignee: Iconic Data, Inc.
• Original Assignee: Iconic Data, Inc.
• Inventors: LaBorde, David
• Primary Examiner(s): Pauls, John A
• Application Number:
  US14/228,723
• Publication Number:
  US 20150281949A1
• Time in Patent Office: 2,069 Days
• Field of Search: 705 2, 705 3, 358 12, 380 25, 715741
• CPC Class Codes: G06F 21/6245 Protecting personal data, e.g. for financial or medical purposes
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G16H 10/65 stored on portable record carriers, e.g. on smartcards, RFID tags or CD
• CPC Class Codes: G16H 30/20 for handling medical images, e.g. DICOM, HL7 or PACS
• CPC Class Codes: G16H 40/20 for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
• CPC Class Codes: G16H 50/20 for computer-aided diagnosis, e.g. based on medical expert systems
• CPC Class Codes: H04W 12/02 Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
• CPC Class Codes: H04W 12/06 Authentication
• CPC Class Codes: H04W 88/02 Terminal devices

Abstract

A system and method that permits a user to utilize a means of capturing and managing one or more images containing protected health information (PHI) on a mobile device, as disclosed herein. The user of the system and method may be required to undergo authentication and authorization to access the system and use the method.

Claims

1. A charge capture client device comprising:

a transceiver for communicating with a charge capture manager device via a connection to a network;

a controller coupled to the transceiver;

an imaging device coupled to the controller, the imaging device configured to capture an image including protected health information (PHI); and

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

generate a new bill graphical display for facilitating user entry of a new patient data set, the new bill graphical display including;

an image graphical interface, wherein an image input interface is generated when the image graphical interface is selected for selecting an image captured by the imaging device so that the PHI information can be parsed from the image, the image graphical interface including a thumbnail image of the image after the image is selected;

a diagnosis selection graphical interface, wherein a diagnosis selection display is generated when the diagnosis selection graphical interface is selected, the diagnosis selection display subsequent in hierarchy to the new bill graphical display, the diagnosis selection display including;

an open text field for receiving diagnosis related information; and

a results display for displaying a plurality of diagnosis codes returned as results based upon the diagnosis related information;

an evaluation and management (E/M) code selection graphical interface; and

a procedure code selection graphical interface, wherein a procedure code selection display is generated when the procedure code selection graphical interface is selected, the procedure code selection display subsequent in hierarchy to the new bill graphical display, the procedure code selection display including;

an open text field for receiving procedure code related information; and

a results display for displaying a plurality of procedure codes returned as results based upon the procedure code related information, wherein;

the imaging device is a camera or video sensor;

the image graphical interface includes a patient sticker image graphical interface and a patient facesheet graphical interface;

a patient sticker image input interface for inputting a patient sticker image is generated when the patient sticker image graphical interface is selected, the controller configured to parse the PHI information from the patient sticker image and change the patient sticker image graphical interface to include a thumbnail image of the patient sticker image; and

a patient facesheet image input interface for inputting a patient facesheet image is generated when the patient facesheet graphical is selected, the controller configured to parse the PHI information from the patient facesheet image and change the patient facesheet graphical interface to include a thumbnail image of the facesheet.

2. The charge capture client device of claim 1, wherein:

an E/M code selection display is generated when the E/M code selection graphical interface is selected, the E/M code selection display subsequent in hierarchy to the new bill graphical display, the E/M code selection display including a plurality of selectable Current Procedural Terminology (CPT) codes or Systematized Nomenclature of Medicine (SNOMED) descriptors that map to the CPT codes;

the plurality of procedure codes of the procedure code selection display are CPT codes and descriptors or SNOMED descriptors that map to the CPT codes; and

the plurality of diagnosis codes are International Classification of Diseases (ICD) codes and descriptors or SNOMED descriptors that map to the ICD codes.

3. The charge capture client device of claim 1, wherein the controller is further configured to generate:

a voice input graphical interface, wherein a voice input display subsequent in hierarchy to the new bill graphical display is generated when the voice input graphical interface is selected, the voice input display including a record control graphical interface for indicating recording or streaming over the network data representing voice utterances including PHI information when selected.

4. The charge capture client device of claim 3, further comprising:

a microphone device for capturing the voice utterances,

wherein the controller is further configured to initiate the microphone device to capture the voice utterance when the record control graphical interface is selected, and to generate one or more voice files including the voice utterances and temporarily store the one or more voice files in the memory.

5. The charge capture client device of claim 1, wherein:

the open text field for receiving diagnosis related information receives transcribed voice utterance as the diagnosis related information;

the open text field for receiving procedure code related information receives transcribed voice utterance as the procedure code related information;

the controller is further configured to initiate a query based upon the diagnosis related information and the procedure code related information to be sent to the charge capture manager device, and to return billing codes based upon a response from the charge capture manager device.

6. The charge capture client device of claim 1,

wherein the controller is further configured to:

generate a resource request including an authentication credential associated with a user to be sent to the charge capture manager device;

generate a data set including the PHI parsed from the image;

store one or more diagnoses in the data set;

store one or more evaluation and management codes in the data set;

store information about a procedure performed on the patient and a procedure billing code associated with the procedure in the data set;

encrypt the data set and store the encrypted data set in the memory to be transmitted to the charge capture manager device; and

delete the encrypted data set from the memory after receiving an acknowledgment message indicating successful transmission from the charge capture manager device.

7. The charge capture client device of claim 6, wherein the storing of the one or more diagnoses further comprises:

receiving voice data including diagnosis related information and returning a plurality of diagnosis codes based upon the diagnosis related information; and

receiving an indication of a selection of one or more of the plurality of diagnosis codes as the one or more diagnoses, wherein the plurality of diagnosis codes are International Classification of Diseases (ICD) codes or SNOMED codes and descriptors that map to a ICD codes.

8. The charge capture client device of claim 6, wherein the storing of the one or more evaluation and management codes includes:

receiving voice data including evaluation and management related information and returning a plurality of evaluation and management codes based upon the evaluation and management related information; and

receiving an indication of a selection of one or more of the evaluation and management codes as the one or more evaluation and management codes,

wherein the evaluation and management codes are Current Procedural Terminology (CPT) codes or SNOMED codes and descriptors that map to CPT codes.

9. The charge capture client device of claim 6, wherein the storing of the procedure includes:

receiving voice data including procedure related information and returning a plurality of procedure billing codes based upon the procedure related information; and

receiving an indication of a selection of one of the plurality of procedure billing codes as the procedure billing code,

wherein the procedure billing code is a CPT code or a SNOMED code that maps to a CPT code.

10. The charge capture client device of claim 6, wherein the controller is further configured to generate a bill history display based upon data received from the charge capture manager device in response to the resource request, wherein the bill history display includes one or more patient identifications for patients which bills have been created associated with the user or a group of which the user is a member, a medical record number and facility for each of the one or more patient identifications, diagnosis, evaluation and management and procedure billing code information, date information regarding when a charge was submitted, and a current status of the charge.

11. The charge capture client device of claim 6,

wherein the controller is further configured to encrypt the image and send the encrypted image to the charge capture manager device where the encrypted image is decrypted and PHI is parsed from the image, and the controller is further configured to decrypt encrypted PHI received from the charge capture manager device.

12. The charge capture client device of claim 1, wherein the charge capture manager device comprising:

a transceiver configured to receive a resource request from a client device remote from the charge capture manager device, the resource request including authentication credentials associated with 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 charge database, billing code database and instructions for configuring the controller, wherein the instructions configure the controller to;

add a new bill data set in response to a request received from the client device to a bill history and set a status flag associated with the new bill data set to indicate new charge, the new bill data set including patient identification information, one or more diagnoses, one or more evaluation and management codes, one or more procedure billing codes, date information and user information in the data set;

generate an acknowledgment message indicating successful transmission of the new bill data set to be sent to the client device;

delete a data set indicated in a request from the client device; and

execute a billing code query in response to an authenticated and authorized user request from a charge capture client device.

13. The charge capture client device of claim 12, wherein the controller of the charge capture manager device is further configured to:

generate a notification message to be sent to an authorized and authenticated third party user indicating that the new bill data set has been stored;

modify the status flag associated with the data set in response to a resource request received from the another remote client device including a request to change the status flag; and

maintain an activity log of all access to resources on the charge capture manager device.

14. The charge capture client device of claim 12, wherein the controller of the charge capture manager device is further configured to determine the bill history in the charge database that is associated with the user name to be sent to the client device during the secure communication session by the transceiver, the bill history including one or more data sets, each of the one or more data sets including a patient identification of a patient for which a bill has been created, a medical record number and facility, date information regarding when a charge was submitted and medical service was provided, diagnosis, evaluation and management and procedure billing code information and a current status of the charge.

15. The charge capture client device of claim 12, wherein the controller of the charge capture manager device is further configured to decrypt an encrypted image received from the client device, parse protected health information (PHI) from the decrypted image and encrypt and send the parsed PHI to the client device.

16. The charge capture client device of claim 12, wherein the controller of the charge capture manager device is further configured to decrypt voice data received from the client device, generate a transcript from the decrypted voice data and send the transcript to the remote client device as encrypted data.

17. The charge capture client device of claim 12, wherein the controller of the charge capture manager device is further configured to search for and obtain billing codes for each of the one or more diagnoses, the one or more evaluation and management codes, and the one or more procedure billing codes in the billing code database based upon information included in the request from the client device, and return the obtained billing codes to the client device.

18. The charge capture client device of claim 12, wherein the bill history includes PHI information parsed from an image.