The Miami-Dade County, Florida, court system believes that jail populations can be reduced, re-incarceration rates lowered, and court system costs lessened and most important that better outcomes can occur for people in the court system if there is a database that coordinates activities for county jails, mental health facilities, shelters, and hospitals. Based on the contents of this database, algorithms can be used to predict what kind of help a person might need to reduce his or her involvement in the justice system. Eventually, such a database could be extensive involving many agencies and lots of personal history and demographic data) once privacy issues are resolved. However, for now, the desire is to create a small, prototype database with the following data. Each participating agency is of a certain type (e. g. criminal justice, mental health) and has an agencyId, name and address. There are potentially many agencies that will participate in this database. The agency types could be standardized for consistency. Data about persons will be stored in the database, including professionals who work for the various participating agencies as well as those who have contact with an agency (e. g., someone who is a client of a mental health facility, who is incarcerated, or both). Data about people include personlD, name, birth date, gender and education level. A person could have many relationships with an agency, and an agency could have many people that have relationships with the agency. For example, a person could be an employee of an agency. If a person is an employee of an agency, we keep track of the person's job title with that agency, along with the beginning and ending date that the person worked for that agency. As another example, a person could reside in shelter. We keep track of the beginning and ending dates that a person is related to an agency as well as the role (e. g. employee, resident, incarcerated, patient) that the person has with that agency for that time period. A person in the system could potentially meet with many other people who are in the system. For example, a person who is in a mental health facility could meet with a person who works at that mental health facility. Or that same person could meet with a doctor at a local health care clinic that participates in this database as a participating agency. These meetings are referred to as "contacts" in our database. We want to have a way to record the contacts between people in the system. For each contact, the database needs to record the contact date and the reason for the contact, as well as the people who participated in the contact. A contact could have multiple people participating in the contact and the database needs to store data about each person who participates in each contact. The data that needs to be stored for a particular contact with a particular person includes an attribute for a diagnosis, an attribute for a family history code, and an attribute to store unstructured notes. Some people in the system are prescribed certain drugs while in the care of participating agencies like county hospitals, clinics and mental health facilities. A drug has an identifier (NDI or National Drug Identifier) and a name. Each prescription (Rx) is for a particular person and drug. Each prescription includes the date it was prescribed and a dosage. A prescription is due to some diagnosis, which was the result of a contact with a person. When a contact by a person results in a prescription, the system stores the diagnosis and notes about the contact. The person who makes the diagnosis is the same person who writes the prescription (Rx) during the contact with that person.