MEDICORD
Background
Looking through a patient’s eye one knows that each other doctor consultation results in 1 more document to handle. Same problem is for doctors who do not really know their patient’s medical record and has got to ask numerous inquiries to get a quick background. But all this process is not so effective together doesn’t really remember precisely about his conditions that are reported to him any time before a year approximately .
Over the years, every major industry has invested heavily in computerization. concerning a decade ago, today everyone buys airline tickets and sign up to flights online, purchase goods on the online , and even earn degrees online in such disciplines as nursing, law, and business, among others. Yet, despite all these advancements in our society, patients are still given handwritten medication prescriptions.
Electronic medical history (EMR) systems have the potential to rework the health care system from a mostly paper-based industry to at least one that utilizes clinical and other pieces of data to help providers in delivering higher quality of care to their patients.
What we propose
Made from two words medical and records, the project Medicord because the name suggests will provide a centralized database for storing patients past medical details from birth. Quite almost like EMR(Electronic Medical Records) Providing a far better location from where doctors from anywhere everywhere the India can access their patient’s medical record . All of this may be done using electronics and cloud storing.
Advantages of Medicord
• This will increase transparency and accessibility generated by the adoption of EMC which in turn will increase the convenience with which they will be accessed by healthcare professionals.
• it will include patient data sharing, better research options for pre-hospital care and elegance of future treatment options, review of clinical standards, data-based outcome improvement, and clinical decision support.
• Digital formatting will help to circulate information to be used and shared over secure networks.
• Technical and social framework that permits information to manoeuvre electronically between organizations.
• EMRs may eventually help improve care coordination. writing in a trade journal suggests that since anyone using an EMR can view the patient’s full chart, it reduces the probability of guessing histories, seeing multiple specialists, improves care settings, and should allow better care in emergency situations.
Demand of such Product
Seeing the market there is no such companies providing this type of facilities within the health care sector. The program will be in great demand. Doctors will definitely require access to patients past medical data for their better treatment.
Target costumers
Mainly targeting health institutes, the program is going to be of great help if the govt steps in to assist . All the private and government hospitals will find it helpful. The patients will not need to worry about their previous medical reports.
Expertise and knowledge required
For server development
The main requirement for the project is going to be of server management of such an outsized server because the server is going to be holding data for many people. Talking about technical requirements , we will be needing cloud storage for storing details of patients. for creating the interface, we will be needing front and backend developers. The front-end developers should be knowing languages like java script, CSS, HTML. For the database we will be needing programmers knowing the way to work with SQL, PHP, Python, MySQL, SQL Server, Postgres SQL, and Oracle. For the program to completely function we will be needing developers of python, C++, ruby, java net.
In addition to all or any this we will need doctors to understand the fundamentals of technology for editing data for respective patients.
Estimated resources
In the first phase of the project, we will be needing partnership with 6 to eight hospitals or clinics to check that the merchandise is well equipped for the market. a piece force of about 10 to 12 people 2 for handling the server , 1 full stack developer for bugs and glitches, and 1 individual in each hospital who is cognizant of the working of the program.
In the second phase we will try reaching bent more and more medical clinics hospitals for a bigger number of individuals to access our services.
In the third phase we will be having a full fledge working project that be connecting thousands of medical institutions.
We will be needing servers costing anywhere around 70 thousand to 1 lakh which will need space for setting up.
The Cost for salaries of all the working professionals should be around 15 to 25 lakhs per month.
Project pricing
Initially we will be charging a decent amount of money to cut to the requirements for running the servers. When the project will be able to stand alone selling it to government bodies should bring in decent amount of money.
Marketing plan
We will be advertising and doing conferencing, seminars to reach out everyone. Promotion on websites such as google, practo, mediplus, you practice online, health line , etc. Finding sponsor such as AIIMS, Colombia Asia, Fortis, etc. Health ministry is going to play a very important role in implementation of the project so reaching out to them for funding will be of great help for the project to succeed.
Risk analysis
· The main risk involved in the project is start up funding and gathering the work force for building/developing the program.
· Assuring the hospitals, clinics that the program is safe for use and will greatly help in there working.
· Reaching out to everyone can be a tedious and time taking task because projects like these take to make reputation in the market.
Issue that can arise in due course of time
1. Privacy issue can arise. for example
In the us , Great Britain, and Germany, the concept of a national centralized server model of healthcare data has been poorly received. problems with privacy and security in such a model are of concern. Threats to health care information are often categorized under three headings:
· Human threats, like employees or hackers
· Natural and environmental threats, like earthquakes, hurricanes and fires.
· Technology failures, like a system crashing
These threats can either be internal, external, intentional and unintentional. Therefore, one will find health information systems professionals having these threats in mind when discussing ways to guard the health information of patients. it’s been found that there’s a scarcity of security awareness among health care professionals in countries like Spain. The insurance Portability and Accountability Act (HIPAA) has developed a framework to mitigate the harm of those threats that’s comprehensive but not so specific on limit the choices of healthcare professionals who may have access to different technology.
Legal
Failure or damages caused during installation or utilization of an EMR system has been feared as a threat in lawsuits. Similarly, it’s vital to acknowledge that the implementation of Medicord carries significant legal risks. This liability concern was of special concern for small EMR system makers. Some smaller companies could even be forced to abandon markets supported the regional liability climate. Larger EMR providers (or government-sponsored providers of EHRs) are better able to withstand legal assaults. While there’s no argument that electronic documentation of patient visits and data brings improved patient care, there’s increasing concern that such documentation could open physicians to an increased incidence of malpractice suits. Disabling physician alerts, selecting from dropdown menus, and thus the utilization of templates can encourage physicians to skip a whole review of past patient history and medications, and thus miss important data. Another potential problem is electronic time stamps. Many physicians are unaware that EMR systems produce an electronic time stamp whenever the patient record is updated. If a malpractice claim goes to court, through the tactic of discovery, the prosecution can request an thorough record of all entries made during a patient’s electronic record. Waiting to chart patient notes until the highest of the day and making addendums to records well after the patient visit are often problematic, therein this practice could end in but accurate patient data or indicate possible intent to illegally alter the patient’s record. In 2006, exceptions to the Stark rule were enacted to allow hospitals to furnish software and training to community providers, mostly removing this legal obstacle.
Time line
The project should be done and be fully functional in around a Year and a half.
Web references
