WO2018020382A1

WO2018020382A1 - System and method for storage, management and sharing of electronic medical records

Info

Publication number: WO2018020382A1
Application number: PCT/IB2017/054440
Authority: WO
Inventors: Gulshan SALUJA
Original assignee: Saluja Gulshan
Priority date: 2016-07-23
Filing date: 2017-07-21
Publication date: 2018-02-01

Abstract

Disclosed is a system and method for storage, management and sharing of electronic medical records. The system comprises of a server, a user device 108, a plurality of healthcare provider devices and a plurality of monitoring devices. The user device and the plurality of healthcare provider devices allows user and healthcare providers, respectively to generate and transmit electronic medical records (EMRs) to the server. The server receives and stores the EMRs in the memory. The server is configured to authenticate access to the EMRs stored in the memory. The server is further configured to generate unique IDs corresponding to each of the plurality of users and the plurality of healthcare provider devices. The unique IDs and the authentication governs access to the EMRs stored in the memory.

Description

SYSTEM AND METHOD FOR STORAGE, MANAGEMENT AND SHARING OF ELECTRONIC MEDICAL RECORDS

CROSS-REFERENCE TO RELATED APPLICATIONS AND PRIORITY

[001] The present application claims priority from Indian Patent Application number 201621025262, filed on 23^rd July 2016.

TECHNICAL FIELD

[002] The present invention relates to record management systems. More particularly, the present invention relates to system and method for storage, management and sharing of electronic medical records.

BACKGROUND

[003] Maintaining medical records in an electronic format is becoming a commonplace in healthcare institutions. A vast amount of electronic medical records (EMRs) are generated for healthcare providers to assist in diagnosis corresponding to a patient's symptoms. However, the EMRs are often not available to the healthcare providers because the EMRs are stored in a non-accessible data format, stored in a personal user device or a memory, the patient visits the multiple healthcare providers, and/or the EMRs are not updated to include the most recent patient information. Additionally, when the patient visits the healthcare provider's clinic for the first time, the patient is required to fill several forms relating to personal health information and family health information prior to the patient's appointment thereby adding to inefficiency in healthcare institutions.

[004] Efficiency of treatment and care provided by the healthcare providers and the operations of healthcare management systems are affected by tasks such as time spent for diagnosing a problem, devising a treatment plan, ordering and administering necessary medications and procedures, and documenting each activity occurring within the treatment plan. Multiple EMRs are generated in the aforementioned tasks. Further, the EMRs are stored in distributed databases thereby increasing the complexities to retrieve the EMRs. Thus, the inefficiencies associated with storage and retrieval of the EMRs may impair the healthcare provider's ability to effectively and efficiently provide timely delivery of care and treatment to the patients. Further, additional time spent in performing the aforementioned tasks results in decreased productivity of the healthcare provider, which results in provision of sub optimal healthcare to the patient.

[005] Further, due to the proliferation and advancement of healthcare industry, the volume of the EMRs and their interdependencies has increased. The management of the EMRs, stored in various databases, is a serious problem to the healthcare industry and health of millions of patients. For instance, a huge investment is required to ensure efficient management of the EMRs when the EMRs are stored in distributed databases at different locations and/or healthcare institutions. The EMRs are often stored in a disjointed fashion thereby hampering daily operations of the healthcare industry and consuming precious network bandwidth. Additionally, the patients may seek multiple healthcare opinions from various healthcare providers to obtain the best course of medical treatment for a particular disease. Hence, the patient is required to manually transfer and share the EMRs, either digital or printed copies, across various healthcare clinics/hospitals. The manual transfer of the EMRs results in misplaced or lost information which leads to incorrect diagnosis and subsequently ineffective or inaccurate courses of treatment being followed.

[006] Furthermore, the complexity of modern treatment and care options increase the need for an efficient EMRs management system in order to make the treatment and the care options available to multiple patients effectively and promptly. Modern healthcare providers face a challenge to maintain complete and accurate records of all treatment and care options being provided to the patient in an "up-to-the-minute" manner. The institutions providing the healthcare facilities are faced with the challenge of maintaining complete and accurate records for all patients, which are undergoing treatment/diagnosis. Additionally, the individual healthcare provider and the healthcare institutions require access to EMR history in order to effectively treat the patient. Finally, for effective treatment of the patients it is critical that the each EMR is effectively mapped to its corresponding patient. This is particularly necessary in healthcare environments where the patient is being cared for by multiple healthcare providers or where multiple patients are being cared for by a single healthcare provider.

[007] Thus, there exists a need for a method and/or system for electronically maintaining the medical records that allows efficient storage, management, and sharing of the EMRs. Further, the system should allow communication among the healthcare providers and the patient.

SUMMARY

[008] Before the present apparatuses, methods and systems along with components related thereto are described, it is to be understood that this disclosure is not limited to the particular methods, apparatuses, systems and their arrangement as described, as there can be multiple possible embodiments which are not expressly illustrated in the present disclosure but may still be practicable within the scope of the invention. It is also to be understood that the terminology used in the description is for the purpose of describing the particular versions or embodiments only, and is not intended to limit the scope of the present application. This summary is not intended to identify essential features of the subject matter nor it is intended for use in detecting or limiting the scope of the subject matter.

[009] In one embodiment, a system for storage, management and sharing of medical records of the users is described. The system may comprise a user device, one or more healthcare provider device, a first monitoring device, a second monitoring device and a server. The first monitoring device may enable tracking of an activity of a user. The second monitoring device may measure symptoms of the user. The server may comprise a processor and a memory. The memory may be coupled with the processor. The processor may execute programmed instructions stored in the memory. The server may be configured for receiving a user data for generating a user profile. The server may be configured for assigning unique identification code and a global identification code for a generated user profile. The server may be configured for registering the user profile with the server. The server may be configured for enabling registration of the user profile with one or more healthcare provider device. The one or more healthcare provider may utilize the global identification code in order to register the user profile. The server may be configured for receiving medical records of the plurality of users from the one or more healthcare provider device and further storing the medical records of the one or more users in the respective user profile. The medical record of the user may be generated either via the one or more healthcare provider device, the first monitoring device or the second monitoring device. The server may be further configured for enabling an access of medical records of the user to other healthcare provider device via an authentication technique. The authentication technique may comprise a passcode received by respective user device, thus sharing of the medical records of the users with the healthcare providers.

[0010] In another embodiment, a method for storage, management and sharing of medical records of the users is described. The method may comprise receiving, by a processor, user data for generating a user profile. The method may comprise assigning, by the processor, unique identification code and a global identification code for a generated user profile. The method may comprise registering, by the processor, the user profile with the server. The method may comprise enabling, by the processor, registration of the user profile with one or more healthcare provider device. The one or more healthcare provider may further utilize the global identification code in order to register the user profile. The method may comprise receiving, by the processor, medical records of the plurality of users from the one or more healthcare provider device and further storing the medical records of the one or more users in the respective user profile. The medical record of the user may be generated either via the one or more healthcare provider device, the first monitoring device or the second monitoring device. The method may comprise enabling, by the processor, an access of medical records of the user to other healthcare provider device via an authentication technique. The authentication technique may comprise a passcode received by respective user device, thus sharing of the medical records of the users with the healthcare providers. BRIEF DESCRIPTION OF DRAWINGS

[0011] The invention is described in detail below with reference to the drawings and examples. Such discussion is for purposes of illustration only. Modifications within the spirit and scope of the present invention, set forth in the appended claims, will be readily apparent to one of skill in the art. Terminology used throughout the specification and claims herein is given its ordinary meaning except as more specifically defined.

[0012] Figure la and lb illustrates a system 100 for storage, management, and sharing of electronic medical records (EMRs), in accordance with an embodiment of the present invention.

[0013] Figure 2 illustrates a block diagram of the server 102, in accordance with an embodiment of the present invention. [0014] Figure 3 illustrates a method 300 for storage, management and sharing of medical records of the user, in accordance with an embodiment of the present invention.

[0015] Figure 4 illustrates a method 400 of forwarding a request for a medical test prescribed by a first healthcare provider to a second healthcare provider by a user, in accordance with an embodiment of the present invention.

DETAILED DESCRIPTION

[0016] As used in the specification and claims, the singular forms "a", "an" and "the" include plural references unless the context clearly dictates otherwise. For example, the term "an article" may include a plurality of articles unless the context clearly dictates otherwise.

[0017] Some embodiments of this disclosure, illustrating all its features, will now be discussed in detail. The words "comprising," "having," "containing," and "including," and other forms thereof, are intended to be equivalent in meaning and be open ended in that an item or items following any one of these words is not meant to be an exhaustive listing of such item or items, or meant to be limited to only the listed item or items.

[0018] Those with ordinary skill in the art will appreciate that the elements in the Figures are illustrated for simplicity and clarity and are not necessarily drawn to scale. For example, the dimensions of some of the elements in the Figures may be exaggerated, relative to other elements, in order to improve the understanding of the present invention.

[0019] There may be additional components described in the foregoing application that are not depicted on one of the described drawings. In the event such a component is described, but not depicted in a drawing, the absence of such a drawing should not be considered as an omission of such design from the specification.

[0020] Before describing the present invention in detail, it should be observed that the present invention utilizes a combination of system components which constitutes a system for storage, management, and sharing of electronic medical records (EMRs). Accordingly, the components and the method steps have been represented, showing only specific details that are pertinent for an understanding of the present invention so as not to obscure the disclosure with details that will be readily apparent to those with ordinary skill in the art having the benefit of the description herein.

[0021] As required, detailed embodiments of the present invention are disclosed herein; however, it is to be understood that the disclosed embodiments are merely exemplary of the invention, which can be embodied in various forms. Therefore, specific structural and functional details disclosed herein are not to be interpreted as limiting, but merely as a basis for the claims and as a representative basis for teaching one skilled in the art to variously employ the present invention in virtually any appropriately detailed structure. Further, the terms and phrases used herein are not intended to be limiting but rather to provide an understandable description of the invention. [0022] A "device," "application," "module" or "system" as used herein may refer to any combination of hardware, firmware, or software used to perform the specified functions. Systems, applications, modules, devices and databases may reside at different physical locations and are connected through a wired or wireless network including the Internet or Intranet.

[0023] Figs, la and lb illustrates a system 100 for storing, managing, and sharing Electronic Medical Records (EMR), in accordance with an embodiment of the present invention. The system 100 may comprise a server 102, a user device 108, one or more healthcare provider devices (110, 122, 124) and one or more monitoring devices (114, 116). Hereinafter one or more healthcare provider devices (110,122,124) may be collectively referred as healthcare provider device 110. The server 102 may store the electronic medical records and health related information of plurality of users. The server 102 may further comprise information related to the plurality of healthcare providers. The server 102 may be connected with a user device 108, a first healthcare provider device 110, a first monitoring device 114 and a second monitoring device 116 via a network 112. The user device 108 may enable a user to connect to the server 102. The user may create a user profile in the server 102 by providing user data. Hereinafter, electronic medical records may also be referred as medical records.

[0024] It should be noted that the healthcare provider may include, but not limiting to, doctors attached to hospitals, individually practicing doctors, specialists in medical clinics, nurses in the hospitals and medical laboratories and ancillary medical personnel. The healthcare provider may further include diagnostic centers, pathology laboratories, medical research laboratories, medical imaging laboratories and the like. The healthcare provider may be a person/organization that provides any kind of healthcare service and the like.

[0025] The medical record of the user may be transmitted to the server 102 via the user device 108 or the healthcare provider device 110. The medical record may comprise one or more health records of the user. The one or more medical records of the user may be present in form of prescriptions, clinical records, lab reports, personal medical history, family medical history and the like. The medical records may be important to the user as well as the healthcare provider.

[0026] In one embodiment, the server 102 may store complete medical record of the user. The medical data of the user may be stored in respective user profile. The complete medical record may also be referred as global health record. The medical record may be segregated and categorized into the global health record. The global health record of the user may be created upon creation of the user profile. The user profile may be created either by the user or by the healthcare provider. The global health record may be provided a global identification code, wherein the global identification code may comprise numeric or alphabetic or both. The global identification code may be based on, but not limiting to, mobile number of the user, country specific unique identifiers, driving license number, social security number, permanent account number, any other unique identifier and the like. Hereinafter global identification code may also be referred as global ID. The global health records may include documents such as prescriptions, clinical notes, lab reports, personal medical history, family medical history, medical reports and the like. The global health records may be stored by the user or the healthcare provider in to the server 102.

[0027] The medical/health records of the user may be stored in the server 102, via the user device 108 or the healthcare provider device 110, in various file formats including, but not limited to, scanned documents, dictation, transcribed electronic documents and through interface and other devices that capture health test results. The medical records may eliminate redundancy and illegible data in the health records of the user. The medical records may facilitate in quick and dynamic generation of accurate notes/reports that adhere to regulatory guidelines. [0028] Authorized healthcare providers may access the global health records of the user in order to review medical information of the user. The medical information of the user may comprise medical history, medical reports and vital signs/symptoms of the user. The medical information of the user may facilitate the authorized health provider to capture present illnesses of the user and further generate prescriptions for fulfillment by other healthcare providers. The medical information of the user may be displayed in various formats such as text, forms, tables, flow sheets, graphs, audio files, videos and the like. The medical information of the user may facilitate rapid chart review and meaningful data analysis to the authorized healthcare provider. Each document added to the global health records of the user may comprise date/time, stamp and may be further associated with a visit to the healthcare provider. The document may be a prescription and/or medical history. The document type may be used to sort and filter documents when viewing the list of documents in the global health records of the user. [0029] The first monitoring device 114 may be a wearable device. The first monitoring device 114 may monitor biomedical information and/or vital signs/symptoms of the user. The first monitoring device 114 may comprise one or more sensors in order to monitor vital signs and/or biomedical information of the user. The one or more sensors may include, but not limited to, a temperature sensor, a heart rate sensor, a blood pressure sensor, a pulse oximeter, a biosensor, a physiological sensor and a motion sensor. The first monitoring device 114 may communicate with the server 102 via the network 112. In one embodiment, the first monitoring device 114 may generates health related data such as calories intake, sleep hours, miles covered by walking and/or running, pulse rate and the like. The health-related data may be further transmitted, via the first monitoring device 114, to the server 102.

[0030] The second monitoring device 116 may be a device that the first healthcare provider may use in order to perform various tests on the user. In one embodiment, the second monitoring device 116 may measure health parameters of the user such as hemoglobin level in blood for the user. The measured health parameters may be further transmitted, via the second monitoring device 116, to the server 102. The server 102 may further enable sharing of the medical records, via the network 112, among the user device 108, healthcare provider device 110, the first monitoring device 114 and the second monitoring device 116. The medical records of the user may be accessed by the one or more healthcare provider via an authentication technique. The authentication technique may generate a one-time passcode and transmit to the mobile number of the user. The user may further share the one-time passcode to the respective healthcare provider in order to provide an access to the medical records present in the user profile. [0031] It may be understood that the server 102 may also be implemented in a variety of computing systems, such as a laptop computer, a desktop computer, a notebook, a workstation, a mainframe computer, a server, a network server, a cloud server and the like. It will be understood that the server 102 may be accessed by multiple users and healthcare providers through the user device 108 and healthcare provider device 110 respectively. Examples of the user device 108 and healthcare provider device 110 may include, but not limited to, a portable computer, a personal digital assistant, a handheld device, and a workstation. The server 102 is communicatively coupled user device 108 and the healthcare provider device 110 through the network 112. [0032] In one embodiment, the network 112 and may be a wireless network, a wired network or a combination thereof. The network 112 can be implemented as one of the different types of networks, such as intranet, local area network (LAN), wide area network (WAN), the internet, and the like. The first network 112 may either be a dedicated network or a shared network. The shared network represents an association of the different types of networks that use a variety of protocols, for example, Hypertext Transfer Protocol (HTTP), Transmission Control Protocol/Internet Protocol (TCP/IP), Wireless Application Protocol (WAP), and the like, to communicate with one another. Further the network 112 may include a variety of network devices, including routers, bridges, servers, computing devices, storage devices, and the like. [0033] Figure 2 illustrates a block diagram of the server 102 for, in accordance with an embodiment of the present disclosure. The server 102 may comprise a processor 201, an input/output interface 202 and a memory 203. Hereinafter input/output interface 202 may also be referred as I/O interface 202. The processor 201 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. Among other capabilities, the processor 201 is configured to fetch and execute computer-readable instructions stored in the memory 203.

[0034] The I/O interface 202 may include a variety of software and hardware interfaces, for example, a web interface, a graphical user interface, and the like. The I/O interface 202 may allow the server 102 to interact with a user or healthcare provider directly or through the user devices 103 and healthcare provider devices 110. Further, the I/O interface 202 may enable the server 102 to communicate with other computing devices, such as web servers and external data servers (not shown). The I/O interface 202 can facilitate multiple communications within a wide variety of networks and protocol types, including wired networks, for example, LAN, cable, etc., and wireless networks, such as WLAN, cellular, or satellite. The I/O interface 202 may include one or more ports for connecting a number of devices to one another or to another server.

[0035] The memory 203 may include any computer-readable medium known in the art including, for example, volatile memory, such as static random access memory (SRAM) and dynamic random access memory (DRAM), and/or non-volatile memory, such as read only memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes. The memory 203 may include modules 204 and data 209.

[0036] The modules 204 include routines, programs, objects, components, data structures, etc., which perform particular tasks or implement particular abstract data types. In one implementation, the modules 204 may include a receiving module 205, a generating module 206, an authentication module 207, a notification module 208 and other modules 212.

[0037] The receiving module 205 may be configured to receive the user data from the user device 103. The user data may comprise of last name, first name, address information, city, state, zip code, mobile number, email id and a combination thereof. The generation module 206 may be configured to generate a user profile based on the user data received by the server 102. The authentication module 207 may be configured to facilitate an authentication of the users and healthcare providers in the server 102 thereby enabling completion of registration process of the user profile in the server 102. The authentication module 207 may be further configured to enable access to the global. The server 102 may further provide a secure access to the medical records of the user via authentication.

[0038] The notification module 208 may be configured to transmit a notification to the user device 108 and the healthcare provider devices 110. The server 102 may provide a convenient location to collect and store the medical records of the user. The notification module 208 may send a notification to the user device 108 in order to confirm registration of the user profile. The notification module 208 may be further configured to send a notification to the user device 108 when the healthcare provider wants to access the global health records of the respective user.

[0039] The data 209, amongst other things, serves as a repository for storing data processed, received, and generated by one or more of the modules 204. The data 209 may also include a data repository 210 and other data 211. The user profiles and information of the healthcare provider may be stored in the data repository 210. The other data 211 may include data generated as a result of the execution of one or more modules in the other module 212. In an embodiment, the server 102 may enable the user to set a password for the login of user profile. When the user selects password for login, then a determination may be made as to whether the password meets security requirements of the server 102. [0040] In one embodiment, the user may access the server 102. The server 102 may initially determine whether the user is an existing user or a new user. If the user is the existing member, the user may be provided an access to the server 102 by entering login credentials. If the user is a new user to the server 102, a determination may be made whether the user agrees to certain terms and conditions of the server 102. The new user may agree the terms and conditions of the server 102 in order to access the server 102. When the new user agrees to the terms and conditions of the server 102, the server 102 may collect user data entered by the new user via the user device 108. The user data may comprise at least one of last name, first name, address information, city, state, zip code, mobile number, email id and a combination thereof. The server 102 may further create a user account for the new user. The server 102 may send a one-time password to the user device 108 having the mobile number. The server 102 may request the user to enter the one-time password, thereby enabling the server 102 to validate the mobile number of the user.

[0041] The mobile number of the user is uniquely identifiable number. The server 102 may assign a unique identification code (ID) to the user profile. The unique ID may be either numeric, alphabetic or both. Moreover, the server 102 may associate a global ID to the user based on the mobile number of the user. The server 102 may enable easy retrieval of the medical records of the user since the medical records are stored against the unique ID of the user in the server 102. Each family member of the user may be assigned a unique ID when the family member of the user registers in the server 102. The family member may be a dependent or a close relative. The user may link the family members to his/her mobile number. The server 102 may store the unique IDs of the family members against a global ID. The global ID may eliminate multiple input constraints and may provide a single point access to any healthcare provider for an entire family. It should be noted that the generation of the unique identification code and the global identification code may be based on, but not limiting to, country specific unique identifiers, driving license number, social security number, permanent account number, any other unique identifier and the like. [0042] The user may access his/her medical records and provide access of his/her medical records to any healthcare provider via authentication technique. The first healthcare provider may access the medical records of the users that are prescribed or created by him/her. The first healthcare provider may access the global health records of the user that comprise medical records of user provided by other healthcare provider only if the user enables the access to the global health records via the authentication technique.

[0043] In one embodiment, the user may visit the first healthcare provider. The first healthcare provider may enter and search for the mobile number of the user on the first healthcare provider device 110. The first healthcare provider device 110 may further display a list of users registered with the server 102 against the mobile number. The first healthcare provider may select a specific user from the list of users. Once the first healthcare provider selects the user, the server 102 may enable displaying of the medical records of the user that are previously prescribed or created by the first healthcare provider. The server 102 may further allow the first healthcare provider to upload prescriptions and the medical records without any authentication. If the first healthcare provider requires an access to the global health records of the user, the server 102 may send a one-time password to the user device 108. The user may share the one-time password with the first healthcare provider, in order to permit the first healthcare provider to access the global health records of the user. [0044] In a preferred embodiment, the healthcare provider may indicate a set of health data as critical data based on the global health records of the user. The healthcare providers may mark the global health records and/or add comments in order to indicate that the global health record comprises critical data. For example, prescription for cough is not that important, but a surgery document is important. The surgery document may be indicated as a critical data in the medical records of the user. The critical data may be important global health records or medical events in the medical history of the user. The critical data is added to the user profile by multiple healthcare providers thereby creating a critical history section, including the critical data indicted by multiple healthcare providers. The critical history section may allow the future healthcare providers to get a quick view of the critical data in the medical records of the user. Further, the critical history section may facilitate in saving time of the healthcare providers by eliminating the need to go through all the health records.

[0045] The server may further assign a unique record ID for each prescription. The user may access the prescription via the user device 108. If the prescription includes a medical or diagnostic test, the user may carry the prescription to the second healthcare provider. In an embodiment, the second healthcare provider may be a diagnostic center. The second healthcare provider may perform the medical or diagnostic test and further generate a medical report. The second healthcare provider, through a second healthcare provider device 122, may upload the medical report to the server 102. The second healthcare provider may associate a unique record ID to the medical report of the user. Once the medical report is uploaded via the second health provider device 122, the server 102 may notify the user and the first healthcare provider regarding the medical report. The first healthcare provider can study the medical report and may generate a follow up meeting request to the user based on the medical report. The first healthcare provider may further upload a revised prescription in to the server 102, if required.

[0046] If the server 102 receives data from the first monitoring device 114, the server 102 may look for corrective action or advice. For example, the first monitoring device 114 detects blood pressure, the medical record of high blood pressure is stored in the server 102. The server 102, in case of high blood pressure, may send a notification to the user either to take rest, consult a doctor or not to undertake heavy exercise/work. The first healthcare provider may provide text prescription to the user. The user may call or text any healthcare provider. The user may further book an appointment with any healthcare provider. The healthcare provider may examine the user on video conference and the like. The first healthcare provider may send an advice as notifications to the user.

[0047] The user may visit a third healthcare provider for health treatment. Similar to the first healthcare provider, the third healthcare provider may enter and search for the mobile number of the user via third healthcare provider device 124. The third healthcare provider device 124 may further display a list of users registered with the mobile number. The third healthcare provider may select a specific user from the list of users. Once the third healthcare provider selects the user, the server 102 may display the medical records that are previously prescribed or created by the third healthcare provider. If the user is not associated with the third healthcare provider earlier, the user may be linked to the third healthcare provider when the third healthcare provider provides a prescription for the user. If the third healthcare provider requires an access the global health records of the user, the server 102 may send a one-time password to the user device 108. The user may further share the one-time password with the third healthcare provider in order to provide an access for the global health records of the user.

[0048] In one embodiment, when the healthcare provider selects a drug for the user, the server 102 may check the selected drug against other drugs of the current prescription, drugs in prescription history and drugs recently taken by the user. The server 102 may presents a warning to the healthcare provider when the healthcare provider selects the drug that may cause side effects. The side effects of the selected drug may be due to interaction with another drug prescribed to the user, or in the prescription history of the user and recently taken by the user. The drug interaction warning may further include an analysis of the user's family history. For example, if a certain drug is not suggested for a person with high risk of stroke, and the user has a family history of stroke, then a warning may be presented to the first healthcare provider. The server 102 may provide an alert to the healthcare provider at the time of writing prescription based on user and his family, past family history, medical records and drug interaction. When the healthcare provider selects the drug, the server 102 may check the allergies listed for the user against a stored collection of drug-allergy interactions. The server 102 may further present a warning to the healthcare provider when the prescribed drug may trigger an allergy to the user. In one embodiment, the server 102 may generate a notification in form of warning/alert to the user when food/food or drug/food interactions take place. In other words, the server 102 may provide a real-time interaction when the healthcare provider is giving the prescription.

[0049] In another embodiment, the user may request the server 102 in order to permit a healthcare provider to view a set of medical records. The server 102 may permit the healthcare provider to view such records on uploading, writing of medical record by another healthcare provider to which user has granted permission. The server 102 may further allow the first healthcare provider to refer the user/patient to another healthcare provider, say a doctor, such as a specialist. The server 102 may send a referral notice to the specialist, informing the specialist that the user has been referred. The server 102 may allow the user to view summary information (a summary report), that may include, but not limiting to, a listing of allergies, medications, family history, genetic screening, past medical history, past surgical history and any other user-defined information. In yet another embodiment, the user may provide access of the medical records to the healthcare providers on a need-to-know basis or for a temporary period. [0050] In yet another embodiment, when the healthcare provider uploads the medical records in the server 102, the healthcare provider may choose to restrict the access to a specific set of medical records to the user. The healthcare provider may choose to restrict the access to the users based on the nature of the medical condition. For instance, if the nature of the medical condition of the user is critical, the healthcare providers may choose to share the set of medical records, pertaining to the critical medical condition, with the guardians or relatives of the user.

[0051] In yet another embodiment, the medical records uploaded by the users may be classified into either verified medical records or unverified medical records. The verified medical records may be the medical records verified and authenticated by the healthcare provider selected by the users. The unverified medical records are the medical records that are not verified by the healthcare provider. The verification of the medical records may ensure the authenticity of the medical records stored in the server 102.

[0052] Figure 3 illustrates a method 300 for storage, management and sharing of medical records of the user, in accordance with an embodiment of the present invention. At step 302, the user may register with the server 102. The user may provide the user data to the server 102 in order to create a user profile. The user data may comprise at least one of last name, first name, address information, city, state, zip code, mobile number, email id and a combination thereof. At step 304, the server 102 may assign a unique ID to the user profile and further assign a global ID to the user. The global ID may comprise numerals, alphabets or both. The global ID may be based on mobile number of the user, country specific unique identifiers, driving license number, social security number, permanent account number, any other unique identifier and the like.

[0053] At step 306, the server 102 may register the user with a healthcare provider, wherein the healthcare provider may utilize mobile number of the user. At step 308, the healthcare provider, via the healthcare provider device 110, may upload the medical record in the user profile. The server 102 may receive the medical record of the user generated via the healthcare provider device 110, the first monitoring device 114 or the second monitoring device 116. At step 310, the healthcare provider may request for an access to global health records of the user. The server 102 may generate one-time password that can be used for authentication to provide the access to the global health records of the user. The server 102 may further transmit the one-time password to the mobile number of the user. At step 312, the user may share the one-time password with the healthcare provider in order to enable the access of the global health records of the user to the healthcare provider. [0054] Figure 4 illustrates a method 400 of forwarding a request for a medical test prescribed by a first healthcare provider to a second healthcare provider by the user, in accordance with an embodiment of the present invention. At step 402, user may register with the first healthcare provider. The server 102 may further assign a unique ID to the user. At step 404, the first healthcare provider may prescribe a medical test to the user. At step 406, the server 102 may generate a medical record ID for the medical test prescribed by the first healthcare provider. At step 408, the user may request the second healthcare provider to conduct the test and upload medical record to the server 102. At step 410, the server 102 may further notify the user and the first healthcare provider regarding the medical record. At step 412, the first healthcare provider may generate a follow-up meeting request with the user based on the medical record if required or notify the user to continue with the medical advice and/or prescription already provided.

[0055] Moreover, the present invention ensures user's confidentiality through the use of a tiered password/permission server. The healthcare providers may have restricted access to the user's medical record. The invention likewise may provide instant access to a patient's electronic medical record by authorized healthcare providers from any geographical location. Thus, the EMR management system may enable authorized healthcare providers to access and update user's medical records/files. In addition, the authorized healthcare providers can access a record while the other healthcare providers may use the same record. By providing simultaneous access to the user data, the present invention may enable real-time collaboration of the medical records of the users among multiple healthcare providers.

[0056] In accordance with embodiments of the present disclosure, the system and method for storing, management and sharing the electronic medical records described above may have following advantages including but not limited to:

• Maintaining medical records of family members under single account.

• Eliminating redundancy and illegible data in the health records of the user. • Facilitate in quick and dynamic generation of accurate notes/reports, adhering to regulatory guidelines, etc.

[0057] The embodiments, examples and alternatives of the preceding paragraphs or the description and drawings, including any of their various aspects or respective individual features, may be taken independently or in any combination. Features described in connection with one embodiment are applicable to all embodiments, unless such features are incompatible.

Claims

I Claim:

1. A system 100 for storage, management and sharing of medical records of the users, the system 100 comprising:

a user device 108;

one or more healthcare provider device (110,122, 124);

a first monitoring device 114, wherein the first monitoring device 114 enables tracking of an activity of a user;

a second monitoring device 116, wherein the second monitoring device 116 measures symptoms of the user; and

a server 102;

a processor 201; and

a memory 203 coupled with the processor 201, wherein the processor 201 executes programmed instructions stored in the memory 203 for:

receiving a user data for generating a user profile;

assigning unique identification code and a global identification code for a generated user profile;

registering the user profile with the server 102;

enabling registration of the user profile with one or more healthcare provider device (110,122,124), wherein the one or more healthcare provider device (110,122,124) utilizes the global identification code in order to register the user profile;

receiving medical records of the plurality of users from the one or more healthcare provider device (110,122,124) and further storing the medical records of the one or more users in the respective user profile, wherein the medical record of the user is generated either via the one or more healthcare provider device (110, 122, 124), the first monitoring device 114 or the second monitoring device 116;

enabling an access of medical records of the user to other healthcare provider device via an authentication technique, wherein the authentication technique comprises a passcode received by respective user device 108, thus sharing of the medical records of the users with the healthcare providers.

2. The system of claim 1, wherein the first monitoring device 114 is wearable by the user.

3. The system of claim 1, wherein the generated user profile is registered with the server 102 via an authentication technique, wherein the authentication technique comprises receiving of a one-time passcode on mobile number of the user, wherein the one-time passcode comprises either numerals, alphabets or both.

4. The system of claim 1, wherein the server 102 further enables grouping a set of user profiles based on a global identification code.

5. The system of claim 1, wherein the unique identification code and the global identification code comprises either numerals, alphabets or both.

6. The system of claim 1, wherein global identification code comprises at least one of mobile number of the user, country specific unique identifiers, driving license number, social security number, permanent account number and a combination thereof.

7. The system of claim 1, wherein the passcode received by the user device 108 is a onetime passcode, wherein the one-time passcode comprises either numeral or alphabets or both.

8. The system of claim 1, wherein the server 102 further sends a notification to the user device 108 when the healthcare provider device (110 or 122 or 124) requires an access to the medical records of the respective user.

9. The system of claim 1, wherein server 102 further sends a notification to the either user device 108 or healthcare provider device (110 or 122 or 124) or both, when the healthcare provider device (110 or 122 or 124) is writing a prescription/health record for the user indicating either a drug-drug, a drug-food or a food-food interaction.

10. The system of claim 1, wherein one or more medical record of the user is marked in a predefined category via the healthcare provider device (110 or 122 or 124).

11. A method for storage, management and sharing of medical records of the users, the method comprising:

receiving, by a processor 201, user data for generating a user profile; assigning, by the processor 201, unique identification code and a global identification code for a generated user profile;

registering the user profile with the server 102;

receiving medical records of the plurality of users from the one or more healthcare provider device (110,122,124) and further storing the medical records of the one or more users in the respective user profile, wherein the medical record of the user is generated either via the one or more healthcare provider device (110,122,124), the first monitoring device 114 or the second monitoring device 116;

enabling an access of medical records of the user to other healthcare provider device via an authentication technique, wherein the authentication technique comprises a passcode received by respective user device, thus sharing of the medical records of the users with the healthcare providers.

Dated this 21^st Day of July, 2017