Abstract: A patient database system includes a patient database module and a patient database. The patient database may store longitudinal data for patients, and the patient database module may initially acquire a patient data value for a new patient, store the patient data value as part of the longitudinal data of the new patient, acquire further patient data values for the new patient, include the further patient data values as part of the longitudinal data of the new patient, retain the longitudinal data of the new patient for a time duration that extends through a plurality of medical processes having different time periods, compare the longitudinal data to a requirement of a clinical trial, and replenish the patient database with a patient data value of an additional patient. The patient database module may also perform a longitudinal data action on the longitudinal data of the new patient.

Abstract: A patient portal system may include a patient database module configured to interpret a patient profile value, a clinical database module configured to interpret a clinical study description, and a patient interface module configured to implement a patient clinical study interface in response to the patient profile value and the clinical study description.

Abstract: A system for providing a patient engagement platform for clinical protocols may include modular components that interface with each other over a network. At least some of the modular components may perform a modular component operation. The modular components may include a patient database component to establish and update longitudinal data for patients including a first patient, where the longitudinal data for the first patient includes a plurality of patient data values. The modular components may include a journey management component to curate a journey of the first patient through a first clinical protocol, the journey including a plurality of touch points. The modular components may include a patient interaction component to receive a patient data value from the first patient and provide the patient data value to the patient database component, and to interact with the first patient according to at least one of the touch points.

Abstract: A method may include building a journey of a patient through a clinical protocol, where the journey includes a plurality of touch points, and engaging the patient with the plurality of touch points via communication channels. The touch points may include a prescreening touch point, an educational touch point, a transactional touch point, and an engagement touch point. The method may also include collecting further data values of the patient including medical information patient and behavioral information, storing the data values of the patient as longitudinal data, where the longitudinal data of the patient is stored for a time duration that extends after the first clinical protocol is completed by the patient, determining a preference of the patient for a specific one of the communication channels, and engaging the patient via the specific one of the communication channels for at least one of the touch points.

Abstract: A patient portal system may include a patient database module to interpret a patient profile value and a clinical database module to interpret a clinical study description. The patient database module may also interpret patient clinical data in response to the patient profile value and the clinical study description, and include at least a portion of the patient clinical data as longitudinal data of a patient corresponding to the patient profile value. The system may also include a patient interface module to implement a patient engagement interface and to interpret a patient medical event value in response to patient interactions with the patient engagement interface. The patient database may also adjust the longitudinal data in response to the patient medical event value.