METHOD AND APPARATUS FOR MAPPING PATIENT CREATED DATA FROM EXTERNAL SYSTEMS TO ELECTRONIC HEALTH RECORDS

• US 20140136234A1
• Filed: 05/16/2013
• Published: 05/15/2014
• Est. Priority Date: 11/09/2012
• Status: Abandoned Application

• Current Assignee: David Weinstein
• Original Assignee: David Weinstein
• Inventors: WEINSTEIN, David
• Application Number:
  US13/895,909
• Publication Number:
  US 20140136234A1
• 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: G16Z 99/00 Subject matter not provided for in other main groups of this subclass

Abstract

In an embodiment of the invention, a patient'"'"'s mobile phone number and a patient matching or ID creation algorithm that requires the patient'"'"'s mobile phone number or any derivative or transformation thereof is used as a mapping method to map patient created data related to a patient'"'"'s health into the correct patient records in EHRs accurately and cost effectively.

Claims

1-21. -21. (canceled)

22. A computer implemented method for allowing information to be properly routed to and organized in an electronic health record (EHR) database for any of managing, assessing, diagnosing, and recording information relating to a patient'"'"'s health or health care, comprising:

receiving said patient'"'"'s mobile phone number;

establishing a patient identity component based on said patient'"'"'s mobile phone number, wherein said patient identity component is at least a parent ranking element in a hierarchy of personal information that is used for identifying said patient;

receiving, via a sensor or a human interface device, patient created health related data;

combining said patient identity component, patient created health related data and an authorized data user identifier to create a data origination device message; and

transmitting, within a secure wrapper, said data origination device message to at least one of a data user proxy, health related data repository, data clearinghouse, EHR and an authorized data user such that said data origination device message is available for routing to and storage in an EHR database as at least part of said patient'"'"'s record, wherein the record is accessible to one or more of said data user proxy, health related data repository, data clearinghouse, EHR and an authorized data user.

23. The method of claim 22, further comprising:

obtaining registration information that includes said patient'"'"'s mobile phone number; and

transmitting the registration information to one or more EHRs associated with said authorized data user.

24. The method of claim 22, wherein the transmitting of the registration information is conveyed in response to receiving a request for the registration information.

25. The method of claim 22, further comprising formatting said data origination device message in accordance with at least one of Continuity of Care Record (CCR), Continuity of Care Document (CCD), ELINCS, Health Level 7 (HL7), and XML standards, allowing said message to be written to a correct patient record in one or more EHRs.

26. The method of claim 22, wherein said establishing of a patient identity component further comprises using said patient'"'"'s mobile phone number or any derivative or transformation thereof.

27. The method of claim 22, further comprising:

receiving patient related data which is used for correct routing of the data origination device message to patient records in one or more EHRs.

28. The method of claim 22, wherein the authorized data user identifier comprises a National Provider Identifier (NPI) or a derivative or transformation thereof.

29. A nontransitory, computer-readable storage medium storing computer-executable instructions that allows information to be properly routed to and organized in an electronic health record (EHR) database for any of managing, assessing, diagnosing, and recording information relating to a patient'"'"'s health or health care, said instructions comprising:

an instruction to receive said patient'"'"'s mobile phone number;

instructions to establish a patient identity component based upon said patient'"'"'s mobile phone number, wherein said patient identity component is at least a parent ranking element in a hierarchy of personal information that is used for identifying said patient;

an instruction to receive, via a sensor or a human interface device, patient created health related data from said patient;

an instruction to combine said patient identity component, patient created health related data and an authorized data user identifier to create a data origination device message; and

an instruction to transmit, within a secure wrapper, said data origination device message to at least one of a data user proxy, health related data repository, data clearinghouse, EHR and an authorized data user such that said data origination device message is available for routing to and storage in an EHR database as at least part of said patient'"'"'s record, wherein the record is accessible to one or more of said data user proxy, health related data repository, data clearinghouse, EHR and an authorized data user.

30. The computer-readable storage medium of claim 29, wherein said instructions further comprise:

an instruction to receive registration information that includes said patient'"'"'s mobile phone number; and

an instruction to transmit the registration information to one or more EHRs associated with said authorized data user.

31. The computer-readable storage medium of claim 30, further comprising an instruction to transmit the registration information in response to receiving a request for the registration information.

32. The computer-readable storage medium of claim 29, wherein said instructions further comprise an instruction to format said data origination device message in accordance with either the Continuity of Care Record (CCR), the Continuity of Care Document (CCD), ELINCS, Health Level 7 (HL7), or XML standards, allowing said message to be written to a correct patient record in one or more EHRs.

33. The computer-readable storage medium of claim 29, wherein said instruction to establish a unique patient identity component further comprises an instruction to use said patient'"'"'s mobile phone number or any derivative or transformation thereof.

34. The computer-readable storage medium of claim 29, wherein the instructions further comprise an instruction to receive patient related data that aids in the correct routing of the data origination device message to patient records in one or more EHRs.

35. The computer-readable storage medium of claim 29, wherein the authorized data user identifier comprises a National Provider Identifier (NPI) or a derivative or transformation thereof.

36. A system for transmitting and routing patient created health related data to at least one of a data user proxy, health related data repository, data clearinghouse, EHR and an authorized data user, the system comprising:

a communication network;

one or more data origination devices, each data origination device having a processor, and memory coupled to the processor; and

one or more server computers communicatively coupled to the communication network and the one or more data origination devices;

one or more data origination devices having an application stored thereon, the application configured or programmed to receive inputs at the processor from a patient including said patient identity component that is established based upon said patient'"'"'s mobile phone number, wherein said patient identity component is at least a parent ranking element in a hierarchy of personal information that is used for identifying said patient, and patient created health related data and an authorized data user identifier;

wherein the application is configured or programmed to cause the processor to automatically or upon manual input, to construct a data origination device message combining said patient identity component, patient created health related data and an authorized data user identifier executing on the data origination device;

the application configured or programmed to cause the processor automatically or upon manual input to transmit the data origination device message to a communications network to at least one or more server computers such that said data origination device message is available for routing to and storage in an EHR database as at least part of said patient'"'"'s record in said EHR, wherein the record is accessible to one or more of said authorized data user, authorized data user proxy, health related data repository, data clearinghouse, and EHR.

37. The system of claim 36, further comprising:

said authorized data user using said patient'"'"'s mobile phone number to send a message to said one or more data origination devices; and

said message facilitating said patient to complete a registration procedure between one or more said data origination devices associated with said patient and one or more EHRs associated with said data user subsequent to said patient'"'"'s registration with said authorized data user.

38. The system of claim 36, wherein a patient identity component is established using a derivative or transformation of said patient'"'"'s mobile phone number.

39. The system of claim 36, wherein said one or more data origination devices receives patient related data that is used for mapping patient created health data to correct patient record(s) in one or more EHRs.

40. The system of claim 36, wherein the authorized data user identifier comprises a National Provider Identifier (NPI) or a derivative or transformation thereof.

41. The system of claim 36, wherein the application is configured to format said data origination device message in accordance with at least one of Continuity of Care Record (CCR), Continuity of Care Document (CCD), ELINCS, Health Level 7 (HL7), and XML standards, allowing said message to be written to a correct patient record in one or more EHRs.