Claims:
1. A method for generating an executable file for healthcare management using a processor that executes a set of instructions that are stored in memory of a computing device, said method comprising the steps of:
receiving, from said computing device associated with a user, one or more attributes associated with said executable file;
selecting, using said processor, at least one pre-defined file from a plurality of files stored in a database based on a first set of attributes selected from said received one or more attributes;
dynamically modifying, using said processor, said selected at least one pre-defined file to generate a modified file based on a second set of attributes selected from said received one or more attributes;
generating, in reduced time period, using said processor, said executable file by processing said modified file; and
storing, using said processor, said executable file in a second database that is operatively coupled to said computing device to enable said computing device to access said executable file.
2. The method as claimed in claim 1, wherein said method comprises storing said executable file to said second database to enable accessing of said executable file with said computing device or other one or more computing devices.
3. The method as claimed in claim 1, wherein said method comprises associating a unique identifier with said generated executable file, wherein said unique identifier facilitates searching and further modification of said generated executable file.
4. The method as claimed in claim 1, wherein said method comprises automatically associating said generated executable file with a pre-existing system.
5. The method as claimed in claim 1, wherein said method comprises transmitting a signal generated by said one or more processors based on an event triggered by generation of said executable file, to said computing device.
6. The method as claimed in claim 1, wherein said method comprises registration of said user for generating said executable file, wherein an administrator enables or disables processor registration of said user.
7. A system for generating an executable file for health care management, said system comprising:
a processor coupled with a memory, the memory storing instructions executable by the one or more processors to:
receive, from said computing device associated with a user, one or more attributes associated with said executable file;
dynamically modify, using said processor, one or more pre-defined files stored in a database to generate a modified file, wherein said at least one pre-defined file is selected based on a first set of attributes selected from said received one or more attributes from said computing device; and
generate, using said processor, said executable file,
wherein said executable file is generated based on processing of said modified file using said one or more processors, in reduced time period, and
wherein said generated executable file is stored in said database operatively coupled to said computing device to enable said computing device to access said executable file.
8. The system as claimed in claim 7, wherein said system comprises a transceiver to transmit a signal generated by said one or more processors based on an event triggered by generation of said executable file, to said computing device.
9. The system as claimed in claim 7, wherein said one or more processors enables associating a unique identifier with said generated executable file, wherein further modification of said generated executable file is performed based on said unique identifier.

, Description:
TECHNICAL FIELD
[001] The present disclosure relates to the field of healthcare management system. In particular, the present disclosure provides systems and methods for generating a personalized executable file for healthcare management.

BACKGROUND
[002] Background description includes information that may be useful in understanding the present invention. It is not an admission that any of the information provided herein is prior art or relevant to the presently claimed invention, or that any publication specifically or implicitly referenced is prior art.
[003] With rapid innovation in technology, dependency of various fields on technology is inescapable. Innovation in technology as such is used for various applications and services to increase the efficiency of traditional techniques or systems. The general idea of innovation is better utilization of time and to enhance user’s overall experience.
[004] In healthcare management, present technique used by doctors and patients for interacting digitally with each one another requires doctors and/or patients to either register themselves on third party platform. Further, third party platform poses massive threat to privacy/security risk for data pertaining to patients or doctors. Since user/patient/doctor personal data is the commodity of value for the third party and can trigger various privacy threats to common user without his/her knowledge. Thus, ownership of the doctor-patient relationship often lies with the third party platforms, and the doctor-patient communication is dependent on the third party approval. The third party is incentivized to ‘cross-selling’ services/products to patients that may contradict the doctor’s advice and the like.
[005] Further, existing techniques involves investing huge amount of time and money in generating a customized solution built according to the preferences. Doctors/patients lack the resources (time and money) to invest in a customized solution. Also, the final solution, obtained after months of development efforts, may not be as per individual preference or requirements. Also, existing technique include free communication/messaging platforms being used for communication amongst patients and doctors. Such platforms are often neither secure nor trustworthy thus, can lead to privacy violations.
[006] There is, therefore need in the art to generate systems and methods for expeditiously generating an executable file for healthcare management system to enable doctor or patient to personalize the executable file per need/requirement/requirements that provides enhanced privacy and data security.

OBJECTS OF THE PRESENT DISCLOSURE
[007] Some of the objects of the present disclosure, which at least one embodiment herein satisfies are as listed herein below.
[008] It is an object of the present disclosure to provide a system and method to generate an executable file.
[009] It is another object of the present disclosure to provide a system and method to generate an executable file that can be uploaded on a secure server or database to provide enhanced data privacy and security.
[0010] It is another object of the present disclosure to provide a system and method to generate an executable file to enable user to personalize the features of the executable file being generated for enhanced user experience.
[0011] It is another object of the present disclosure to provide a system and method to generate an executable file with pre-incorporated features that can be personalized to imitate a fully functional executable file.

SUMMARY
[0012] The present disclosure relates to the field of healthcare management system. In particular, the present disclosure provides systems and methods for generating a personalized executable file for healthcare management.
[0013] According to an aspect of the present disclosure, a method for generating a personalized executable file for healthcare management is disclosed. The method for generating an executable file for healthcare management using a processor that executes a set of instructions that are stored in memory of a computing device. The method includes steps of: receiving, from the computing device associated with a user, one or more attributes associated with the executable file; selecting, using the processor, at least one pre-defined file from a plurality of files stored in a database based on a first set of attributes selected from the received one or more attributes; dynamically modifying, using the processor, the selected at least one pre-defined file to generate a modified file based on a second set of attributes selected from the received one or more attributes; generating, in reduced time period, using the processor, the executable file by processing the modified file; and storing, using the processor, the executable file in a second database that is operatively coupled to the computing device to enable the computing device to access the executable file.
[0014] In an embodiment, the method comprises storing the executable file to the second database to enable accessing of the executable file with the computing device or other one or more computing devices.
[0015] In an embodiment, the method comprises associating a unique identifier with the generated executable file, wherein the unique identifier facilitates searching and further modification of the generated executable file.
[0016] In an embodiment, the method comprises automatically associating the generated executable file with a pre-existing system.
[0017] In an embodiment, the method comprises transmitting a signal generated by the one or more processors based on an event triggered by generation of the executable file, to the computing device.
[0018] In an embodiment, the method comprises registration of the user for generating the executable file, wherein an administrator enables or disables processor registration of the user.
[0019] According to an aspect of the present disclosure, a system for generating a personalized executable file for health care management, the system comprising: a processor coupled with a memory, the memory storing instructions executable by the one or more processors to: receive, from the computing device associated with a user, one or more attributes associated with the executable file; dynamically modify, using the processor, one or more pre-defined files stored in a database to generate a modified file, wherein the at least one pre-defined file is selected based on a first set of attributes selected from the received one or more attributes from the computing device; and generate, using the processor, the executable file, wherein the executable file is generated based on processing of the modified file using the one or more processors, in reduced time period, and wherein the generated executable file is stored in the database operatively coupled to the computing device to enable the computing device to access the executable file.
[0020] In an embodiment, the system comprises a transceiver to transmit a signal generated by the one or more processors based on an event triggered by generation of the executable file, to the computing device.
[0021] In an embodiment, the one or more processors enables associating a unique identifier with the generated executable file, wherein further modification of the generated executable file is performed based on the unique identifier.
BRIEF DESCRIPTION OF DRAWINGS
[0022] The accompanying drawings are included to provide a further understanding of the present disclosure, and are incorporated in and constitute a part of this specification. The drawings illustrate exemplary embodiments of the present disclosure and, together with the description, serve to explain the principles of the present disclosure. The diagrams are for illustration only, which thus is not a limitation of the present disclosure.
[0023] FIG. 1 illustrates an exemplary network architecture in which or with which proposed system can be implemented in accordance with an embodiment of the present disclosure.
[0024] FIG. 2 illustrates an exemplary module diagram for generating a personalized executable file in accordance with an embodiment of the present disclosure.
[0025] FIG. 3 is a flow diagram illustrating a process for generating a personalized executable file in accordance with an embodiment of the present disclosure.
[0026] FIG. 4 illustrates an exemplary computer system in which or with which embodiments of the present invention can be utilized in accordance with embodiments of the present disclosure.

DETAILED DESCRIPTION
[0027] The following is a detailed description of embodiments of the disclosure depicted in the accompanying drawings. The embodiments are in such detail as to clearly communicate the disclosure. However, the amount of detail offered is not intended to limit the anticipated variations of embodiments; on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the present disclosure as defined by the appended claims.
[0028] In the following description, numerous specific details are set forth in order to provide a thorough understanding of embodiments of the present invention. It will be apparent to one skilled in the art that embodiments of the present invention may be practiced without some of these specific details.
[0029] Embodiments of the present invention include various steps, which will be described below. The steps may be performed by hardware components or may be embodied in machine-executable instructions, which may be used to cause a general-purpose or special-purpose processor programmed with the instructions to perform the steps. Alternatively, steps may be performed by a combination of hardware, software, and firmware and/or by human operators.
[0030] Various methods described herein may be practiced by combining one or more machine-readable storage media containing the code according to the present invention with appropriate standard computer hardware to execute the code contained therein. An apparatus for practicing various embodiments of the present invention may involve one or more computers (or one or more processors within a single computer) and storage systems containing or having network access to computer program(s) coded in accordance with various methods described herein, and the method steps of the invention could be accomplished by modules, routines, subroutines, or subparts of a computer program product.
[0031] If the specification states a component or feature “may”, “can”, “could”, or “might” be included or have a characteristic, that particular component or feature is not required to be included or have the characteristic.
[0032] As used in the description herein and throughout the claims that follow, the meaning of “a,” “an,” and “the” includes plural reference unless the context clearly dictates otherwise. Also, as used in the description herein, the meaning of “in” includes “in” and “on” unless the context clearly dictates otherwise.
[0033] Exemplary embodiments will now be described more fully hereinafter with reference to the accompanying drawings, in which exemplary embodiments are shown. These exemplary embodiments are provided only for illustrative purposes and so that this disclosure will be thorough and complete and will fully convey the scope of the invention to those of ordinary skill in the art. The invention disclosed may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Various modifications will be readily apparent to persons skilled in the art. The general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the invention. Moreover, all statements herein reciting embodiments of the invention, as well as specific examples thereof, are intended to encompass both structural and functional equivalents thereof. Additionally, it is intended that such equivalents include both currently known equivalents as well as equivalents developed in the future (i.e., any elements developed that perform the same function, regardless of structure). Also, the terminology and phraseology used is for the purpose of describing exemplary embodiments and should not be considered limiting. Thus, the present invention is to be accorded the widest scope encompassing numerous alternatives, modifications and equivalents consistent with the principles and features disclosed. For purpose of clarity, details relating to technical material that is known in the technical fields related to the invention have not been described in detail so as not to unnecessarily obscure the present invention.
[0034] Thus, for example, it will be appreciated by those of ordinary skill in the art that the diagrams, schematics, illustrations, and the like represent conceptual views or processes illustrating systems and methods embodying this invention. The functions of the various elements shown in the figures may be provided through the use of dedicated hardware as well as hardware capable of executing associated software. Similarly, any switches shown in the figures are conceptual only. Their function may be carried out through the operation of program logic, through dedicated logic, through the interaction of program control and dedicated logic, or even manually, the particular technique being selectable by the entity implementing this invention. Those of ordinary skill in the art further understand that the exemplary hardware, software, processes, methods, and/or operating systems described herein are for illustrative purposes and, thus, are not intended to be limited to any particular named element.
[0035] Embodiments of the present invention may be provided as a computer program product, which may include a machine-readable storage medium tangibly embodying thereon instructions, which may be used to program a computer (or other electronic devices) to perform a process. The term “machine-readable storage medium” or “computer-readable storage medium” includes, but is not limited to, fixed (hard) drives, magnetic tape, floppy diskettes, optical disks, compact disc read-only memories (CD-ROMs), and magneto-optical disks, semiconductor memories, such as ROMs, PROMs, random access memories (RAMs), programmable read-only memories (PROMs), erasable PROMs (EPROMs), electrically erasable PROMs (EEPROMs), flash memory, magnetic or optical cards, or other type of media/machine-readable medium suitable for storing electronic instructions (e.g., computer programming code, such as software or firmware).A machine-readable medium may include a non-transitory medium in which data may be stored and that does not include carrier waves and/or transitory electronic signals propagating wirelessly or over wired connections. Examples of a non-transitory medium may include, but are not limited to, a magnetic disk or tape, optical storage media such as compact disk (CD) or digital versatile disk (DVD), flash memory, memory or memory devices. A computer-program product may include code and/or machine-executable instructions that may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements. A code segment may be coupled to another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted via any suitable means including memory sharing, message passing, token passing, network transmission, etc.
[0036] Furthermore, embodiments may be implemented by hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof. When implemented in software, firmware, middleware or microcode, the program code or code segments to perform the necessary tasks (e.g., a computer-program product) may be stored in a machine-readable medium. A processor(s) may perform the necessary tasks.
[0037] Systems depicted in some of the figures may be provided in various configurations. In some embodiments, the systems may be configured as a distributed system where one or more components of the system are distributed across one or more networks in a cloud computing system.
[0038] Each of the appended claims defines a separate invention, which for infringement purposes is recognized as including equivalents to the various elements or limitations specified in the claims. Depending on the context, all references below to the "invention" may in some cases refer to certain specific embodiments only. In other cases it will be recognized that references to the "invention" will refer to subject matter recited in one or more, but not necessarily all, of the claims.
[0039] All methods described herein may be performed in any suitable order unless otherwise indicated herein or otherwise clearly contradicted by context. The use of any and all examples, or exemplary language (e.g., “such as”) provided with respect to certain embodiments herein is intended merely to better illuminate the invention and does not pose a limitation on the scope of the invention otherwise claimed. No language in the specification should be construed as indicating any non-claimed element essential to the practice of the invention.
[0040] Various terms as used herein are shown below. To the extent a term used in a claim is not defined below, it should be given the broadest definition persons in the pertinent art have given that term as reflected in printed publications and issued patents at the time of filing.
[0041] The present disclosure relates to the field of healthcare management system. In particular, the present disclosure provides systems and methods for generating a personalized executable file for healthcare management.
[0042] According to an aspect of the present disclosure, a method for generating a personalized executable file for healthcare management is disclosed. The method for generating an executable file for healthcare management using a processor that executes a set of instructions that are stored in memory of a computing device. The method includes steps of: receiving, from the computing device associated with a user, one or more attributes associated with the executable file; selecting, using the processor, at least one pre-defined file from a plurality of files stored in a database based on a first set of attributes selected from the received one or more attributes; dynamically modifying, using the processor, the selected at least one pre-defined file to generate a modified file based on a second set of attributes selected from the received one or more attributes; generating, in reduced time period, using the processor, the executable file by processing the modified file; and storing, using the processor, the executable file in a second database that is operatively coupled to the computing device to enable the computing device to access the executable file.
[0043] In an embodiment, the method comprises storing the executable file to the second database to enable accessing of the executable file with the computing device or other one or more computing devices.
[0044] In an embodiment, the method comprises associating a unique identifier with the generated executable file, wherein the unique identifier facilitates searching and further modification of the generated executable file.
[0045] In an embodiment, the method comprises automatically associating the generated executable file with a pre-existing system.
[0046] In an embodiment, the method comprises transmitting a signal generated by the one or more processors based on an event triggered by generation of the executable file, to the computing device.
[0047] In an embodiment, the method comprises registration of the user for generating the executable file, wherein an administrator enables or disables processor registration of the user.
[0048] According to an aspect of the present disclosure, a system for generating a personalized executable file for health care management, the system comprising: a processor coupled with a memory, the memory storing instructions executable by the one or more processors to: receive, from the computing device associated with a user, one or more attributes associated with the executable file; dynamically modify, using the processor, one or more pre-defined files stored in a database to generate a modified file, wherein the at least one pre-defined file is selected based on a first set of attributes selected from the received one or more attributes from the computing device; and generate, using the processor, the executable file, wherein the executable file is generated based on processing of the modified file using the one or more processors, in reduced time period, and wherein the generated executable file is stored in the database operatively coupled to the computing device to enable the computing device to access the executable file.
[0049] In an embodiment, the system comprises a transceiver to transmit a signal generated by the one or more processors based on an event triggered by generation of the executable file, to the computing device.
[0050] In an embodiment, the one or more processors enables associating a unique identifier with the generated executable file, wherein further modification of the generated executable file is performed based on the unique identifier.
[0051] FIG. 1 illustrates an exemplary network architecture in which or with which proposed system can be implemented in accordance with an embodiment of the present disclosure.
[0052] As illustrated, in a network implementation, the system 102 can be communicatively coupled with plurality of computing devices 106-1, 106-2…106-N (collectively referred to as computing devices 106 and individually referred to as computing device 106 hereinafter) through network 104. The system 102 can be implemented using any or a combination of hardware components and software components such as a server, a computing system, a computing device, a security device and the like, such that embodiments of the present disclosure can generate personalized executable file that can pertain to a healthcare management.
[0053] Further, the system 102 can interact with users 108-1, 108-2…108-N (collectively referred to as users 108, and individually referred to as user 108 hereinafter), through the computing devices 106 or through applications residing on the computing devices 106. In an implementation, the system 102 can be access by applications residing on any operating system, including but not limited to, AndroidTM, iOSTM, and the like. Examples of the computing devices 106 can include, but are not limited to, a portable computer, a personal digital assistant, a handheld device, and a workstation. In a preferred embodiment, the computing devices 106 are mobile phones of the respective users 108. Further, computing devices 106 can also be any or a combination of a hardware or a software that can require one or more attributes pertaining to executable file from the user 108 such as e-commerce websites, personal computers of users, applications residing on computing devices, computing devices of service providers or enterprises, and the like. Similarly, users 108 can also be organizations, enterprises, government bodies, etc (collectively referred as organizations, hereinafter) that can require one or more attributes pertaining to executable file from the user 108.
[0054] The network 104 can be a wireless network, a wired network or a combination thereof that can be implemented as one of the different types of networks, such as Intranet, Local Area Network (LAN), Wide Area Network (WAN), Internet, and the like. Further, the network 104 can either be a dedicated network or a shared network. The shared network can represent an association of the different types of networks that can use variety of protocols, for example, Hypertext Transfer Protocol (HTTP), Transmission Control Protocol/Internet Protocol (TCP/IP), Wireless Application Protocol (WAP), and the like.
[0055] In an embodiment, the system 102 can enable registration of the user 108. The registration can be based on details such as name, address, e-mail address, phone number, and the like. Also, the system 102 can utilize a unique identifier such as PAN card, Unique identification (UID) Card, voter ID, and the like, provided by the user 108, to verify the authenticity of the user 108. Also, in an embodiment, said unique identifier can avoid multiplicity of registration of the same user.
[0056] In an exemplary embodiment, the proposed system 102 can enable generation of the personalized healthcare management system based executable file. The executable file to be created can include patient-branded file (PBF) or healthcare-branded file (HBF) and the like. The PBF can include personalized executable file health that can be personalized for the patient’s name a. For Example, Mr. Ramesh Personal care file, Shah Family Personal care file. The HBF can include that can be personalized in the healthcare provider’s name For example, Dr. Mehta’s Health care file, Dr. Srinivas Clinic care file, Dr. Phadke Polyclinic care file.
[0057] Further, both PBF and HBF are meant for use by the user 108 (interchangeably referred as patient 108 hereinafter), but with different customizations and preferences. The medical professionals can logon healthcare management tools. The healthcare management tools can be configured such that pre-integrated with any generated personalized executable file.
[0058] In an embodiment, while registration, the system 102 can require the user 108 to enter his/her physical address/location and/or the contact details. Further, the system 102 can be configured to either allow registration of new users or disallow registration of the new users.
[0059] In an embodiment, the system 102 can receive one or more attributes associated with the executable file. The user 108 can provide the one or more attributes using his/her computing device 106 or by applications residing on any operating system residing in the computing device 106. The one or more attributes provided by the user 108 can include details about application of the generated file, type of file to be generated and the like.
[0060] In an embodiment, the system 102 can be configured to select a first set of attributes from the received one or more attributes from the computing device 106 associated with the user 108 such that at least one pre-defined file (interchangeably referred as template) can be selected from the plurality of files stored in a database. The plurality of files thus stored in the database can include files that pertain to various features or various pre-defined/pre-configured files that can be imitated for creation of the executable file.
[0061] In an embodiment, the system 102 can dynamically modify the selected pre-defined file and generate a modified file. In an embodiment, the system 102 can be further configured to select a second set of attributes from the received one or more attributes from the user 108. In an embodiment, the second set of attributes can include but not limited to details about the features of the executable file such as plurality of functions and preferences.
[0062] In an embodiment, the system 102 can enable generation of the executable file based on the processing of the generated modified file. The set of instructions and the like are processed on the generated modified file to generate the executable file. In an embodiment, the set of instructions, the algorithm and the like can be stored in the first database, a second database and the like. It must be appreciated by the person skilled in the art that the first database, the second database and the like can be present on a cloud/ server.
[0063] In an embodiment, the system 102 can be configured to store the generated personalized executable file in the second database. The second database can be cloud/server. In an embodiment, the first and the second database can be proprietor databases that can be used for securely storing the generated executable file. The file thus stored on the secure database can be accessed securely by the computing device 106 authorized to access the generated file.
[0064] In an embodiment, the generated executable file can be given associated with a unique identifier, the unique identifier associated with the executable file can be either selected from a database comprising of plurality of the unique identifiers or the unique identifier can be generated by the system 102 along with the generation of the executable file and associating with the generated executable file in real time. The unique identifier can be used for locating the generated executable file. The unique identifier can be further used for modification of the generated executable file and the like.
[0065] In an embodiment, the system 102 can generate a signal based on an event that can be triggered by either by generation of the executable file or storage of the executable file on the second database. The signal generated can be indicative of the notification or alert generated when the executable file is generated or the executable file is stored in the second database. The signal this generated can be transmitted to the computing device 106 associated with the user. In an embodiment, the signal can be either transmitted to the computing device 106 associated with the user 108 that requested to generate the executable file or can be sent to plurality of computing devices 106 associated with the respective users 108.
[0066] In an embodiment, the signal thus generated can be transmitted to the computing device 106 of the user 108 using communication mediums such as short messaging service (SMS), email and the like. In an embodiment, the executable file thus generated can be stored on a public platform for the plurality of computing devices 106 to access the file.
[0067] It must be appreciated by the person skilled in the art that the time for generating a personalized executable file is greatly reduced and also the cost for generation/development of the executable file is considerably reduced using the proposed system 102.
[0068] FIG. 2 illustrates an exemplary module diagram for generating a personalized executable file in accordance with an embodiment of the present disclosure.
[0069] In an aspect, the system 102 may comprise one or more processor(s) 202. The one or more processor(s) 202 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and/or any devices that manipulate data based on operational instructions. Among other capabilities, the one or more processor(s) 202 are configured to fetch and execute computer-readable instructions stored in a memory 206 of the system 102. The memory 206 may store one or more computer-readable instructions or routines, which may be fetched and executed to create or share the data units over a network service. The memory 206 may comprise any non-transitory storage device including, for example, volatile memory such as RAM, or non-volatile memory such as EPROM, flash memory, and the like.
[0070] The system 102 may also comprise an interface(s) 204. The interface(s) 204 may comprise a variety of interfaces, for example, interfaces for data input and output devices, referred to as I/O devices, storage devices, and the like. The interface(s) 204 may facilitate communication of the system 102 with various devices coupled to the system 102 such as the computing device 106. The interface(s) 204 may also provide a communication pathway for one or more components of the system 102. Examples of such components include, but are not limited to, processing engine(s) 208 and data 210.
[0071] The processing engine(s) 208 may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine(s) 208. In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine(s) 208 may be processor executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processing engine(s) 208 may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine(s) 208. In such examples, the system 102 may comprise the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the system 102 and the processing resource. In other examples, the processing engine(s) 208 may be implemented by electronic circuitry.
[0072] The data 210 may comprise data that is either stored or generated as a result of functionalities implemented by any of the components of the processing engine(s) 208.
[0073] In an exemplary embodiment, the processing engine(s) 208 may comprise a attributes receive module 212, modification module 214, executable file generation module 216, executable file storage module 218, signal generation module 220, and other module(s) 222.

Attributes receive module 212
[0074] In an embodiment, the attributes receive module 212 receives one or more attributes from the user 108 using the associated computing device 106. The one or more attributes can include but not limited to information about them self that can include name, email, mobile, photo and the like. In an embodiment, for HBF executable file generation the attributes can include doctors’ qualifications, experience, specialization and the like.
[0075] In an embodiment, the one or more attributes can include preferences for executable file. The one or more attributes related to preferences can include cosmetic preferences such as executable file name, visual features and the like. Further, the one or more attributes can include functional features of the executable file being generated. The functional features can include multimedia call, clinic, text messaging and/or multimedia messaging, drugs/medicine delivery, voice-activated virtual assistant, test ordering, record maintenance and the like
[0076] Further, the one or more attributes received by the attributes receive module 212 can include service configuration. Service configuration for HBF can include consultation services which when enabled can initiate video conferencing, text messaging or multimedia messaging and consultation fee payment or charges, timing for availability, location information, advanced notice, cancellation rules, consult duration and the like.
[0077] Furthermore, service configuration for PBF can include consult services which enabled can assist to choose doctors or specialist with prior knowledge specializations whom the patient would like to consult using their own personal PBF. In an embodiment, for both HBF and PBF record keeping can be enabled, categories of records to be stored. For example allergies, glucose, blood pressure, medications and the like.
[0078] In an exemplary embodiment, the proposed system 102 can require the user 108 to fill up the form or enter details using his/her computing device 106. The details entered can include the one or more attributes. Once the one or more attributes are received the system 102 proceeds to next step for generation of the executable file.
[0079] In an embodiment, the step of generation of the personalized executable file can be required to be enabled upon receipt of the payment. i.e. the services pertaining to generation of the personalized executable can be put behind pay-wall or payment wall.

Modification module 214
[0080] In an embodiment, the modification module 214 can be configured to select the at least one predefined file from the plurality of files stored in the database. Further, the modification module can be configured to dynamically modify the at least one pre-defined file to generate the modified file.
[0081] In an embodiment, the modification module 214 can be configured for conversion of the received one or more attributes. The received one or more attributed are converted in the format of the at least one pre-defined file. The one or more attributes received from the user 108 can be setup information into relevant entries of the at least one pre-defined file. The at-least one pre-defined file is selected from the first database having plurality of pre-defined files.
[0082] In an embodiment, the executable file being generated can be associated with the unique identifier and all subsequent configurations can be mapped to the associated unique identifier. The unique identifier can also be used to configure the other features or configurations related cosmetic and functional preferences into the first database, cloud/server and the like. In an embodiment, in case of PBF the patient’s information can be used to create a profile of the user 108 and login credentials for the user 108. In case of HBF, the information about the healthcare professional can be used to create a profile for the healthcare professional and login credentials for the healthcare professional to login into the healthcare management tools that are pre-integrated with the executable file being generated. The healthcare management tools can be used for the healthcare professional’s login.
[0083] In an embodiment, based on the received one or more attributes the first set of attributes selected from the one or more attributes to select the choice of the at least one pre-defined file. Depending on the first set of attributes PBF, HBF and the like can be selected from the first database and instantiated into a new unique cloud-based repository for the user 108. Further, the new repository can be modified to generate a modified file with preferences provided by the user 108. This includes name of the executable file, visual features of the executable file being generated, and the like. In an embodiment, the data pertaining to features can be downloaded from cloud/server, storage, database and the like unzipped and populated into appropriate folders of the repository, unique identifier and the like.
[0084] In an embodiment, in addition to new credentials for different third party Application programming interface (APIs)/plugins can be optionally created for features such as push notifications, video consultations, payment gateways and the like. Alternatively, predefined common credentials can be used in their place. It should be appreciated by the person skilled in the art that the system 102 processed occur in an automated mode without human intervention and would reduce the time duration for generation of said executable file which generally takes a considerable large amount of time period.

Executable file generation module 216
[0085] In an embodiment, the executable file generation module 216 can be configured to generate the personalized executable file based on the processing of the generated modified file. Once the repository is auto-customized, a request can be initiated pertaining to processing of the modified file. In an embodiment, a build server can comprise pre-stored instructions. The build server can be configured receive the modified file and further can be configured to trigger generate the executable file.
[0086] It would be appreciated by the person skilled in the art that executable file generation/build function can be completed by using the cloud-based processing of the generated modified based on the instructions stored in the build server.
Executable file storage module 218
[0087] In an embodiment, executable file storage module 218 can be configured to generate the executable file, the generated executable file can be stored at a specific folder on the build server, cloud/server and the like. In an exemplary embodiment, a custom job can run at a predetermined time interval to sweep up all newly built executable files generated, by the users 108, on the build server and store them at a second database, cloud/server specifically for storage and the like. This cloud storage location may be provided by the user 108 or can be pre-defined by the system 102.
[0088] In an embodiment, after the generated executable file(s) are stored to the cloud storage, the link/path to storage location of the generated executable file is updated into the database. In an embodiment, associated unique identifier can be stored along with the respective generated executable file.

Signal generation module 220
[0089] In an embodiment, the system signal generation module 220 can generate a signal based on an event. The event can be triggered by either by generation of the executable file or storage of the executable file on the second database. The signal generated can be indicative of the notification or alert generated when the executable file is generated or the executable file is stored in the second database. The signal this generated can be transmitted to the computing device 106 associated with the user. In an embodiment, the signal can be either transmitted to the computing device 106 associated with the user 108 that requested to generate the executable file or can be sent to plurality of computing devices 106 associated with the respective users 108.
[0090] In an embodiment, the signal thus generated can be transmitted to the computing device 106 of the user 108 using communication mediums such as short messaging service (SMS), email and the like. In an embodiment, the executable file thus generated can be stored on a public platform for the plurality of computing devices 106 to access the file.
[0091] FIG. 3 is a flow diagram illustrating a process for generating a personalized executable file in accordance with an embodiment of the present disclosure.
[0092] In an embodiment, the process for generating a personalized executable file can be initiated at step 302, which pertains to receiving one or more attributes associated with the executable file. In an embodiment, at step 304, at least one pre-defined file is selected from a plurality of files stored in a database based on a first set of attributes selected from the received one or more attributes. Further at step 306, the selected pre-defined file is dynamically modified to generate a modified file based on a second set of attributes selected from the received one or more attributes. Furthermore at step 308, the executable file is generated by processing the modified file. Also, at step 320 the executable file is stored in a second database that is operatively coupled to the computing device 106 to enable the computing device 106 to access the executable file.
[0093] FIG. 4 illustrates an exemplary computer system in which or with which embodiments of the present invention can be utilized in accordance with embodiments of the present disclosure.
[0094] Computer system 400 includes a bus 420 or other communication mechanism for communicating information, and a processor 470 coupled with bus 420 for processing information. Computer system 400 can also include a main memory 430 or other non-transitory computer-readable medium, such as a random-access memory (RAM) or other dynamic storage device, which can then be coupled to bus 420 for storing information and instructions to be executed by processor 470. Main memory 430 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processor 470. Computer system 400 may further include a read only memory (ROM) 440 or other static storage device coupled to bus 420 for storing static information and instructions for processor 470. A data/external storage device 410, such as a magnetic disk or optical disk, is provided and coupled to bus 420 for storing information and instructions.
[0095] Computer system 400 may be coupled via bus 420 to a display (not shown), such as a cathode ray tube (CRT), for displaying information to a user. An input device (not shown), including alphanumeric and other keys, can be coupled to bus 420 for communicating information and command selections to processor 470. Another type of user input device can be cursor control, such as a mouse, a trackball, or cursor direction keys for communicating direction information and command selections to processor 470 and for controlling cursor movement on display. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allows the device to specify positions in a plane.
[0096] The invention is related to the use of computer system 400 for creation and management of BOMs as elaborated above. According to some embodiments of the invention, such use may be provided by computer system 400 in response to processor 470 executing one or more sequences of one or more instructions contained in the main memory 430. Such instructions may be read into main memory 430 from another computer-readable medium, such as storage device 450. Execution of the sequences of instructions contained in main memory 430 causes processor 470 to perform the process steps described herein. One or more processors in a multi-processing arrangement may also be employed to execute the sequences of instructions contained in main memory 430. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions to implement the invention. Thus, embodiments of the invention are not limited to any specific combination of hardware circuitry and software.
[0097] The term “computer-readable medium” as used herein refers to any medium that participates in providing instructions to processor 470 for execution. Such a medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media. Non-volatile media includes, for example, optical or magnetic disks, such as storage device 450. Volatile media includes dynamic memory, such as main memory 430. Transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise bus 420. Transmission media can also take the form of acoustic or light waves, such as those generated during radio wave and infrared data communications.
[0098] Common forms of computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, or any other magnetic medium, a CD-ROM, any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, any other memory chip or cartridge, a carrier wave as described hereinafter, or any other medium from which a computer can read.
[0099] Various forms of computer-readable media may be involved in carrying one or more sequences of one or more instructions to processor 470 for execution. For example, the instructions may initially be carried on a magnetic disk of a remote computer. The remote computer can load the instructions into its dynamic memory and send the instructions over a telephone line using a modem. A modem local to computer system 400 can receive the data on the telephone line and use an infrared transmitter to convert the data to an infrared signal. An infrared detector coupled to bus 420 can receive the data carried in the infrared signal and place the data on bus 420. Bus 420 carries the data to main memory 430, from which processor 470 retrieves and executes the instructions. The instructions received by main memory 430 may optionally be stored on storage device 450 either before or after execution by processor 470.
[00100] Computer system 400 also includes a communication interface 460 coupled to bus 420. Communication interface 460 can provide a two-way data communication coupling to a network link (not shown) that can be connected to a local network (not shown). For example, communication interface 460 may be an integrated services digital network (ISDN) card or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, communication interface 460 may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, communication interface 460 sends and receives electrical, electromagnetic or optical signals that carry data streams representing various types of information.
[00101] Although the proposed system has been elaborated as above to include all the main parts, it is completely possible that actual implementations may include only a part of the proposed modules/engines or a combination of those or a division of those in various combinations across multiple devices that can be operatively coupled with each other, including in the cloud. Further the modules/engines can be configured in any sequence to achieve objectives elaborated. Also, it can be appreciated that proposed system can be configured in a computing device or across a plurality of computing devices operatively connected with each other, wherein the computing devices can be any of a computer, a laptop, a smart phone, an Internet enabled mobile device and the like. All such modifications and embodiments are completely within the scope of the present disclosure.
[00102] Embodiments of the present disclosure may be implemented entirely hardware, entirely software (including firmware, resident software, micro-code, etc.) or combining software and hardware implementation that may all generally be referred to herein as a “circuit,” “module,” “component,” or “system.” Furthermore, aspects of the present disclosure may take the form of a computer program product comprising one or more computer readable media having computer readable program code embodied thereon.
[00103] Thus, it will be appreciated by those of ordinary skill in the art that the diagrams, schematics, illustrations, and the like represent conceptual views or processes illustrating systems and methods embodying this invention. The functions of the various elements shown in the figures may be provided through the use of dedicated hardware as well as hardware capable of executing associated software. Similarly, any switches shown in the figures are conceptual only. Their function may be carried out through the operation of program logic, through dedicated logic, through the interaction of program control and dedicated logic, or even manually, the particular technique being selectable by the entity implementing this invention. Those of ordinary skill in the art further understand that the exemplary hardware, software, processes, methods, and/or operating systems described herein are for illustrative purposes and, thus, are not intended to be limited to any particular named.
[00104] As used herein, and unless the context dictates otherwise, the term "coupled to" is intended to include both direct coupling (in which two elements that are coupled to each other contact each other) and indirect coupling (in which at least one additional element is located between the two elements). Therefore, the terms "coupled to" and "coupled with" are used synonymously. Within the context of this document terms "coupled to" and "coupled with" are also used euphemistically to mean “communicatively coupled with” over a network, where two or more devices are able to exchange data with each other over the network, possibly via one or more intermediary device.
[00105] It should be apparent to those skilled in the art that many more modifications besides those already described are possible without departing from the inventive concepts herein. The inventive subject matter, therefore, is not to be restricted except in the spirit of the appended claims. Moreover, in interpreting both the specification and the claims, all terms should be interpreted in the broadest possible manner consistent with the context. In particular, the terms “comprises” and “comprising” should be interpreted as referring to elements, components, or steps in a non-exclusive manner, indicating that the referenced elements, components, or steps may be present, or utilized, or combined with other elements, components, or steps that are not expressly referenced. Where the specification claims refers to at least one of something selected from the group consisting of A, B, C …. and N, the text should be interpreted as requiring only one element from the group, not A plus N, or B plus N, etc.
[00106] While the foregoing describes various embodiments of the invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof. The scope of the invention is determined by the claims that follow. The invention is not limited to the described embodiments, versions or examples, which are included to enable people having ordinary skill in the art to make and use the invention when combined with information and knowledge available to the person having ordinary skill in the art.

ADVANTAGES OF THE PRESENT DISCLOSURE
[00107] The present disclosure provides a system and method to generate an executable file.
[00108] The present disclosure provides a system and method to generate an executable file that can be uploaded on a secure server or database to provide enhanced data privacy and security.
[00109] The present disclosure provides a system and method to generate an executable file to enable user to personalize the features of the executable file being generated for enhanced user experience.
[00110] The present disclosure provides a system and method to generate an executable file with pre-incorporated features that can be personalized to imitate a fully functional executable file.