I have learned that while setting up a database, one should never use a key as usable data. For instance, a telephone company would not want to use a customer’s phone number nor the Social Security Administration use a members’s social security number as primary keys. If a customer changes their phone number or a member passes away, references to the previous account may be awkward. Instead, create a unique primary key that would store the phone number or social security number for the respective organization and if there is a change to this [would be] keyed data, one can still access the record with an alternate key.
With the patient portal database, there would be a great number of tables. And many people and departments would have access to the database contents. With respect to HIPPA (Health Insurance Portability and Accountability Act) only authorized parties would have access to the read the database. These would include but not be limited to the patient, provider (doctor), imaging technician, radiologist and lab technician. Only specific parties would have CRUD (create read update delete) privileges. For example, the patient would have CRUD privileges for initially entering their health history and background while only having read privileges for a provider’s diagnoses or viewing lab or imaging results. An imaging technician would only have create privileges to store an image (CT scan, MRI, Ultrasound, etc.) And the radiologist would only have read access for the image and only create access for writing the image description.
I continued work on the illustrations for the grant proposal. In addition, I worked with Drupal so there is an admin instance where a user instance, one of two where I would log in as administrator and the other as a user. Each instance would be in a separate browser so that Drupal would likely not recognize that multiple instances are not present. This way, the user log-in would appear respectively while the admin would have its respective appearance with edit tabs.
I worked on the patient portal entity relationship diagram indicating the data for patient portal and the corresponding relationships.