Medical registration system
Patient identification is transmitted to a health care provider prior to the patient arriving at the health care provider. The patient identification may be a driver's license, health insurance card, or other identification, and may be used to pre-register the patient. The transmission may include other information, such as health status, purpose of visit, intended procedures, symptoms, or other information. The transmission may be made via a device, such as a cellular telephone, where the information may be encrypted and transmitted using a secure mechanism. The system may be used by ambulance personnel, paramedics, or other emergency responders to notify a hospital, for example, of an inbound patient, as well as by patients prior to an appointment. The system may also be used by clinicians or other health care providers to prepare for emergent or non-emergent patients prior to arrival.
1. A system comprising:
a first device for capturing patient information, said first device comprising:
a first hardware platform comprising: a data capture mechanism, an encryption mechanism, a first communications mechanism, and a screen capture function being a built-in function, said screen capture function capturing at least a portion of information displayed on said display screen, converting said information into an image, and storing said image in said local storage;
said first hardware platform configured to:
capture said patient information from said data capture mechanism;
establish a communications pathway with a remote service using said first communications mechanism;
transmit said patient information to said remote service in a first encrypted form;
said data capture mechanism disabling said screen capture mechanism during at least said displaying said at least a portion of said patient information,
said remote service comprising:
a second hardware platform comprising: a second communications mechanism and a storage mechanism;
said second hardware platform configured to:
receive said patient information in a first encrypted form; and
transmit said encrypted patient information to a second device in a second encrypted form;
said second device comprising:
a third hardware platform comprising: a third communications mechanism, and a decryption mechanism;
said third hardware platform configured to:
receive said patient information in said second encrypted form;
decrypt said encrypted patient information to generate said patient information; and
display said patient information.
2. The system of claim 1 , said first encrypted form being the same as said second encrypted form.
3. The system of claim 2 , said remote service further configured to:
store said encrypted package.
4. The system of claim 1 , said first encrypted form being different from said second encrypted form.
5. The system of claim 4 , said communications pathway being an encrypted communications pathway.
6. The system of claim 5 , said second hardware platform further configured to:
decrypt said first encrypted form and generate said patient information; and
store said patient information in an unencrypted form.
7. The system of claim 1 , said first hardware platform being further configured to disable local storage of said patient information.
8. The system of claim 1 , said patient information comprising an image of a patient identification document.
9. The system of claim 8 , said patient identification document being at least one of a group composed of:
a driver's license;
a government issued identification;
an insurance card;
an employee identification; and
a photo identification.
10. The system of claim 8 , said third hardware platform further configured to:
perform an optical character recognition of said patient identification document.
11. The system of claim 8 , said second hardware platform further configured to:
perform an optical character recognition of said patient identification document.
12. The system of claim 1 , said first hardware platform further configured to:
authenticate with said remote service.
13. The system of claim 12 , said first hardware platform further configured to:
receive user credentials from a first user; and
authenticate with said second hardware platform using said user credentials.
14. The system of claim 12 , said first hardware platform further configured to:
determine a device identifier for said first device; and
authenticate with said third hardware platform using said user credentials.
15. The system of claim 1 , said second hardware platform further configured to:
transmit said patient information to a third device, said third device being an accounting system.