Patient data management platform

A patient data management system for community paramedicine, the system comprising:

• a medical database configured to store, for a patient, a patient record comprising a patient-specific program goal for the patient to reduce his/her use of emergency medical services (EMS) by a quantified amount during or within a particular time period or within a predetermined number of encounters with a healthcare provider;
• at least one mobile computing device configured to provide a portal screen to a patient data management platform;
• at least one medical device configured to communicatively couple to the at least one mobile computing device and configured to:
• couple to the patient;
• measure patient data comprising vital signs for the patient;
• and
• provide the patient data comprising the vital signs to the at least one mobile computing device;
• and
• a server hosting the patient data management platform and configured to be in communication with the at least one mobile computing device, the server comprising a processor and a memory, the memory including instructions executable to:
• provide instructions at the portal screen to prompt a user to enter information about the patient associated with the patient-specific program goal and obtained during a first encounter with the patient;
• cause the at least one mobile computing device to automatically record patient data received from the at least one medical device during the first encounter with the patient;
• provide instructions at the portal screen to prompt the user to enter information about the patient associated with the patient-specific program goal and obtained during one or more second encounters with the patient outside a health care facility, the information about the patient obtained during the one or more second encounters comprising information about travel of one or more emergency medical service professionals to a patient location;
• cause the at least one mobile computing device to automatically record patient data received from the at least one medical device during the one or more second encounters with the patient;
• receive, via the portal screen, the user entered information about the patient obtained during the first encounter and the one or more second encounters;
• determine that at least some of the user entered information about the patient is outside a predetermined range;
• in response to the determination, display, on the portal screen, (a) a warning with an alert icon indicating that the at least some of the user entered information about the patient is outside the predetermined range and (b) a data entry field;
• receive and store a user entry to the data entry field comprising information regarding the at least some of the user entered information about the patient that is outside the predetermined range;
• in response to receiving and storing the user entry to the data entry field, replace the alert icon with a selectable information icon that enables the user to view the user entry to the data entry field upon selection of the information icon;
• and
• use (a) at least some of the user entered information about the patient obtained during the first encounter and the one or more second encounters, and (b) at least some of the automatically recorded patient data received during the first encounter and the one or more second encounters to verify whether the patient reduced his/her use of the EMS by the quantified amount;
• wherein the patient-specific program goal is specific to a high frequency EMS user;
• wherein the server is communicatively coupled to an emergency dispatch service and is configured to receive an identification of the patient as the high frequency EMS user;
• and
• wherein the memory further includes instructions executable to prompt the user of the portal screen to collect information that identifies a pattern of emergency calls by the patient.