1. Hiveware® for Patients
Patient-centric electronic health-care records
The Hiveware peer-to-peer platform presents a unique opportunity to make a significant contribution to the nation-wide effort of making our health-care records electronic. The current approach is woefully inadequate. Health-care record systems are designed and offered by each medical entity. Already there are too many systems to choose from and integration issues abound. No one provider can completely control the industry. It makes sense for each person/patient to use the computer and network to always know what one’s current prescribed medications are, to know who is in charge of prescribed procedures and treatments we are paying for, to know what the hierarchy of management and professionals who are moment-by-moment making decisions about our health care is, and to know what the running costs are. A simple approach to solving this problem is to make a health-care system that is patient-centric without the need for large server farms that are expensive to maintain.

2. Develop Hiveware connections to health care providers
Aetna
Patient
Patient
Kaiser Permanente
Patient
Patient
KP - oncology
Develop Hiveware connections to health care providers
United Health Care
(each yellow ball is a hive subscriber or contributor)
Here’s how it would work: the Hiveware® for Patients developer would secure connection rights and capabilities with as many providers as possible. This would be the Kaiser Permanentes, Aetnas, GoldenRules and the many others. Each his its own stovepipe or silo system as it is called. Their legal argument is that their patient’s data is rightfully owned by the patient who paid for it. Their financial argument would be that the providers would be compensated for their contributions. Each provider would be viewed from Hiveware as an author who outputs data each time one of their doctors, technicians or labs creates some information regarding the patient. True to Hiveware, that information would be pushed to all other participants, one of which is the patient. All see the same set of data, but only each author/provider would be able to change that data.
There are two main advantages to this kind of system:
No new servers have to be created to contain the patient’s data.
All of the patient’s care-givers all know in real-time the same up-to-date information when it changes.
Physician
Physician
Physician
NIH
Physician
Physician
NIH MRI
NIH professionals
NIH oncology

3. Hiveware® for Patients
Create a hive that creates hives for patients: Hiveware® for Patients
Hiveware® for Patients
Create a hive that creates hives for patients.

4. KP – oncology Dr. Peirera
Aetna
Linda family
Linda family
Linda family
Kaiser Permanente
Linda
KP – oncology Dr. Peirera
Develop Hiveware connections to health care providers
United Health Care
Use that hive to create a hive for a patient like Linda. Hiveware takes care of the rest by establishing real-time connections to everybody. Players may tread in and out of contributor roles over time. For example, Linda participated in two NIH Phase I and Phase II studies. Some of her attending professionals were the same and some were different. Her set of NIH professionals would contribute information while they were generating it, but move back to reader-only role for the duration.
Dr. Chand, M.D.
NIH
NIH MRI
NIH professionals
NIH oncology