| http-equiv="Content-Type" content="text/html; | | | | that exist between the entities, the diagram is as |
| charset=utf-8"> | | | | follows: |
| The proposed electronic medical record design will | | | | The above diagram represents the entry |
| contain patient demography which will record | | | | relationship diagram, from the above it is clear |
| patient information; it will also contain the medial | | | | that the health representative will serve many |
| history of the patient. Another important part in | | | | patients, the patient will have different complaints |
| the EHR is the presence of laboratory test | | | | and therefore different encounter types. The |
| information, images such as x ray images, | | | | encounter type will have different diagnosis or |
| payment records, physician information and the | | | | health disorder, finally the health disorders must |
| encounter type. | | | | be referred to a specialized physician and |
| The first step in constructing an entry relationship | | | | therefore one physician will serve on health |
| diagram is to identify all the parts in our electronic | | | | disorder. |
| system, in our case the parts we will consider | | | | The system will assist in recording and ease |
| include the health representative, the patients, the | | | | diagnosis of health disorders presented by |
| encounter type, diagnosis and health disorders | | | | consumers, when the patient visits the health |
| then we will consider the physicians. | | | | center the health representative will first record |
| The second step is to determine the relationships | | | | the complaint and also names and other important |
| between the entities we are to consider in our | | | | information., the health representative will also try |
| electronic system, in this case we will consider the | | | | to find out whether this is the first time the |
| first place where the information is first collected, | | | | patient is visiting or whether a regular patient, |
| we consider this as the entity health | | | | after this is established depending on the |
| representative which will serve many patients, the | | | | encounter type and previous health history the |
| patients will have many different complaints, | | | | health representative will refer the patient to a |
| these complaints will be referred to different | | | | specialized physician. |
| physicians and therefore after the patient’s | | | | The existence of a complex communication |
| complaint we consider the relationship between | | | | system the physician will also be in a position to |
| the complaints and the encounter type and | | | | refer to the stored complaint, also the health |
| diagnosis. The encounter type will then determine | | | | history of patient, allergies and other information. |
| the physician type. | | | | This access to information will make diagnosis |
| The final step before drawing our ERD is to | | | | easy and therefore improved services in a health |
| analyze the relationship between the entities, | | | | care. |
| when the relationships are determined we can | | | | Therefore we can conclude that this system will |
| now draw the diagram, we have to consider all | | | | add value to the health center due to enhanced |
| the entities, the crow foot symbol will signify one | | | | communication systems and also ease update and |
| entity serving too many of another entity. | | | | retrieval of information. The time taken to serve |
| The following is the entry relationship diagram, the | | | | a patient will also be reduced due to increased |
| diagram contains all the entities we will consider | | | | efficiency in the health center. |
| and the joining lines show the type of relationship | | | | |