Designing a data model is always the result of a trade off. The iCure data model has been designed with several technical goals in mind:
- Ensuring the data model is extensible
- Guaranteed efficiency in resolving conflicts in the data-store
- Allowing selective encryption of the medical data
- An efficient storage strategy in document/object databases
The iCure data model is split into two categories of entities
- Actors: They provide, create, access and modify the medical data. They are either Healthcare parties (HCPs) or Patients.
- Medical data: The medical information that has been collected in iCure. This data is organized as a journal inside entities called contacts. Extra entities are used to structure the medical information.
An Actor is a patient or a healthcare party. When an actor has been given access to the EHR, a user entity is created to store Authentication/Authorization data. An actor without an associated user has no access to iCure, whereas, an actor that has been connected to a user is able to read, add or modify data in the limits of the access rights that have been assigned to it.
The patient is the recipient of care. Nearly all medical information inside iCure is linked directly or indirectly to a patient. The patient entity is usually created during the first contact of a patient with a healthcare party. The administrative information of the patient can be partially or totally encrypted before being saved inside the patient entity.
A healthcare party is someone who is recognized to provide care or services for a patient. A healthcare party is either an individual healthcare professional (a doctor, a nurse, a physiotherapist, etc.) or an organization (a clinic, a hospital, a government authority, etc.). A healthcare party includes anyone who is a stakeholder for the patient health and can access and manage the patient's file.
In the following section, the chronological entities and different structural elements of a patient's file is described in detail.
Every time a patient consults a healthcare party or every time a healthcare party accesses a patient's medical file, the actions performed are recorded and collected inside a contact. The contact is the entity that records the medical information about the patient chronologically. A visit to the patient's house, a consultation at the practice, a phone call between the patient and the HCP or integrating lab reports into the medical file are examples of when a contact can be recorded.
A contact can occur with or without direct interaction between the patient and the HCP. For example, when a healthcare party encodes data received from laboratory's test result, this is done in the absence of a patient.
A contact groups together pieces of information collected during one single event, for one single patient and for one or more healthcare parties. Patient's complaints, the diagnosis of a new problem, a surgical procedure, etc. are collected inside a contact.
The main sub-element of the contact is the service. Each atomic piece of information collected during a contact is a service and is stored inside the services list of a contact.
Services include subjective information provided by the patient, such as complaints, reason for visit, feelings, etc. or objective information like bio-metric measures (blood pressure, temperature, heart beat, etc.), or physical exam description, diagnosis, prescription, integration of lab reports from another healthcare party, action plan, etc.
Any action performed by the healthcare party which is relevant for the healthcare element of a patient is considered a service.
Because contacts are purely chronological objects, they do not convey information about the organization of the medical file. They however, do include a data structure to link services to existing structuring elements such as healthcare elements, healthcare approaches and forms. This data structure is the sub-contacts list.
A sub-contact is an object embedded inside a contact that links one or several services to one healthcare element, healthcare approach or form.
Healthcare element can be described as the reason for the patient to consult a healthcare party. The healthcare element has a starting moment and optionally an ending moment. In the case of incurable chronic diseases, the ending time is usually the time of death of the patient. The healthcare element usually represents a healthcare problem (diabetes, kidney failure, hypertension, heart attack, etc.) but this is not always the case. Pregnancy, right alignment of the heart, etc. are examples of healthcare elements which do not pose a healthcare problem.
The healthcare approach is part of a healthcare element and represents an action undertaken for the follow-up of a given healthcare element of a patient. A healthcare approach groups together the services that are meant as solution for the given healthcare element.
A form collects a series of services in one single visual entity. It is used to organize the information on screen. It is used to create input forms, dashboards, folders hierarchies or more generally any structure needed by a developer to sort or group the information for an user.
Let's look at the above mentioned elements explained with a fictional patient:
The patient observes a mild pain in the lower right side of the abdominal area on July 1. It is not consistent. On July 2, the pain becomes severe and is now covering the whole abdominal area. The pain is consistent and continuous through out the day. Towards the end of the day, the patient starts vomiting and the pain is unbearable.
The patient loses sleep and on 3 July, early morning rushes to the hospital after having vomited multiple times and the pain now being unbearable. This is the n-th contact shown above. The patient complains to the doctor about the symptoms and after thorough examination, the doctor diagnoses him with appendicitis. The doctor recommends a surgical operation of appendectomy the next day. The doctor also prescribes antibiotic cefuroxime, intravenously, to reduce spread of infection in the abdomen.
During the next contact (n+1) on July 4, the surgical operation of appendectomy, is carried out. After 3 days in observation, the patient is released from the hospital with a prescription of antibiotics for next 6 days and recommends a recovery period of 4 weeks.
Sometime later, the patient is diagnosed with diabetes. The patient develops difficulties due to this. Few consultations were made with the doctors attempting to keep these conditions under control. One of the conditions the patient develops is necrosis in a toe. The doctor recommends amputation of the toe (figure 2). On March 7, the patient is asked to get admitted for the surgical procedures of toe amputation. After proper healing of the wound, on April 7, the patient begins sessions with a physiotherapist to help with walking again.
As a result of diabetic condition, the patient later on, has an episode of heart attack. The patient is prescribed lifestyle changes, medication, cardiac rehabilitation, etc. and asked to consult again in 2 weeks for the follow up of the heart attack episode (not shown in figure 2). During this consultation, various bio-metric measures like, blood sugar level, blood pressure, etc. was recorded. The change in weight was also recorded in order to measure how much life style changes were effective.