An apparatus, computer-readable medium, and computer-implemented method for integrating and sharing patient-related information among members of a medical team in real-time via an authenticated Application Programming Interface (API), includes receiving preliminary patient data corresponding to the patient from a first member of a medical team comprising a plurality of members, the preliminary patient data being received via the authenticated API, generating a patient profile for the patient, the patient profile being accessible to each member of the medical team via the authenticated API, receiving input relating to the patient from a second member of the medical team, the input being received via the authenticated API, and updating the patient profile based at least in part on the received input, with each of the plurality of members of the medical team being able to access the updated patient profile via the authenticated API.
Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A method executed by one or more computing devices for integrating and sharing patient-related information among members of a medical team in real-time via an authenticated Application Programming Interface (API), the method comprising: receiving, by at least one of the one or more computing devices, preliminary patient data corresponding to the patient from a first member of a medical team comprising a plurality of members, wherein the preliminary patient data is received via the authenticated API from a first device; generating, by at least one of the one or more computing devices, a patient profile for the patient, wherein the patient profile is accessible to each member of the medical team via the authenticated API and wherein the authenticated API is configured to detect any changes to the patient profile; receiving, by at least one of the one or more computing devices, input relating to the patient from a second member of the medical team, wherein the input is received via the authenticated API from a second device; and updating, by at least one of the one or more computing devices, the patient profile based at least in part on the received input, wherein the updated patient profile is accessible to each of the plurality of members of the medical team via the authenticated API and wherein the authenticated API is configured to: receive a request to access data from one or more files external to the patient profile which are linked to the patient profile; retrieve the data from the one or more files external to the patient profile; and output at least a portion of the retrieved data.
A system enables real-time sharing of patient information among a medical team using a secure API. A first team member enters initial patient data (e.g., symptoms) via the API on their device. This data is used to create a patient profile accessible to all team members through the API. When a second team member adds input (e.g., diagnosis, treatment plan) via the API on their device, the patient profile is updated. All team members can then view the updated profile through the API. The API also allows access to external files linked to the profile, such as retrieving data from external files linked to the patient profile. The system retrieves requested data from these files and presents at least a portion of it to the user. The API detects any changes to the patient profile.
2. The method of claim 1 , wherein the authenticated API is a password-protected application running on a mobile device.
The system from the previous description uses a password-protected application running on a mobile device as the secure API.
3. The method of claim 1 , wherein the preliminary patient data includes patient medical history.
In the system from the first description, the initial patient data entered by the first team member includes the patient's medical history.
4. The method of claim 1 , wherein the preliminary patient data includes at least one physician associated with the patient.
In the system from the first description, the initial patient data entered by the first team member includes information on at least one physician associated with the patient.
5. The method of claim 4 , wherein the at least one physician associated with the patient comprises at least one of a referring physician and a primary care physician.
In the system where the initial patient data includes physician information, the physician information includes either the referring physician or the primary care physician, or both.
6. The method of claim 1 , wherein the one or more files external to the patient profile include one or more physician profiles, wherein the request to access data from one or more files external to the patient profile comprises a request to view contact information for a physician associated with the patient and wherein the retrieved data comprises the contact information for the physician associated with the patient.
In the system from the first description, external files linked to the patient profile include physician profiles. When a user requests a physician's contact information, the system retrieves that contact information from the corresponding physician profile and displays it.
7. The method of claim 1 , further comprising: annotating, by at least one of the one or more computing devices, the updated patient profile with an indicator designating the second member of the medical team along with the changes in the patient profile resulting from the received input.
The system from the first description annotates the updated patient profile with an indicator of which team member made the changes and what those changes were.
8. The method of claim 1 , wherein the one or more files external to the patient profile include a plurality of diagnostic test results and wherein the retrieved data comprises one or more diagnostic test results corresponding to the patient.
In the system from the first description, external files linked to the patient profile include diagnostic test results. When a user requests diagnostic results, the system retrieves and displays the patient's relevant test results.
9. The method of claim 1 , wherein the input relating to the patient comprises a recommendation regarding a surgical option.
In the system from the first description, a team member's input on a patient's profile might include a recommendation for a surgical option.
10. The method of claim 1 , wherein the input relating to the patient comprises information regarding a procedure performed on the patient or a diagnosis of the patient.
In the system from the first description, a team member's input on a patient's profile can include information about a procedure performed on the patient or a diagnosis of the patient.
11. The method of claim 1 , wherein the input relating to the patient comprises answers to a patient evaluation form.
In the system from the first description, a team member's input on a patient's profile can include answers from a patient evaluation form.
12. The method of claim 11 , wherein the patient evaluation form is integrated into the authenticated API.
In the system where a patient evaluation form is used, the form is integrated directly into the secure API application.
13. The method of claim 11 , wherein the patient evaluation form comprises at least one of a frailty test, a Kansas City Cardiomyopathy Questionnaire, a Society of Thoracic Surgeons risk evaluation, and a European System for Cardiac Operative Risk Evaluation.
In the system where a patient evaluation form is used, the form includes at least one of a frailty test, a Kansas City Cardiomyopathy Questionnaire, a Society of Thoracic Surgeons risk evaluation, or a European System for Cardiac Operative Risk Evaluation.
14. The method of claim 1 , wherein the request to access data from one or more files external to the patient profile comprises a request to generate a letter pertaining to the patient, wherein the retrieved data comprises a letter template corresponding to the requested letter including one or more blank data fields, and wherein outputting at least a portion of the retrieved data comprises outputting the letter template with the one or more blank data fields filled with information retrieved from the patient profile.
In the system from the first description, a request can be made to generate a letter pertaining to the patient. The system retrieves a letter template with blank fields. It then fills in those blank fields with information from the patient's profile before displaying or outputting the completed letter.
15. The method of claim 14 , wherein the letter comprises at least one of a referring physician letter, a consultation letter, and a procedure letter.
In the system using letter templates, the letter can be a referring physician letter, a consultation letter, or a procedure letter.
16. The method of claim 1 , wherein the request to access data from one or more files external to the patient profile comprises a request to generate a bill, wherein the retrieved data comprises one or more first billing codes corresponding to one or more procedures associated with the patient profile and one or more second billing codes corresponding to one or more diagnoses associated with the patient profile, and wherein outputting at least a portion of the retrieved data comprises outputting a billing report including the one or more first billing codes and the one or more second billing codes.
In the system from the first description, a request can be made to generate a bill. The system retrieves relevant billing codes for procedures performed and diagnoses given to the patient. It then outputs a billing report containing these codes.
17. The method of claim 1 , wherein the preliminary patient data and the input relating to the patient comprise information indicating the suitability of the patient for a surgical procedure, wherein at least one member of the medical team specializes in the surgical procedure, and wherein the authenticated API tracks one or more requirements that must be fulfilled prior to performing the surgical procedure.
In the system from the first description, the initial data and subsequent input includes information indicating whether the patient is suitable for a specific surgical procedure. The system tracks any requirements that must be met before the procedure can be performed, and at least one member of the medical team specializes in that surgical procedure.
18. An apparatus for integrating and sharing patient-related information among members of a medical team in real-time via an authenticated Application Programming Interface (API), the apparatus comprising: one or more processors; and one or more memories operatively coupled to at least one of the one or more processors and having instructions stored thereon that, when executed by at least one of the one or more processors, cause at least one of the one or more processors to: receive preliminary patient data corresponding to the patient from a first member of a medical team comprising a plurality of members, wherein the preliminary patient data is received via the authenticated API from a first device; generate a patient profile for the patient, wherein the patient profile is accessible to each member of the medical team via the authenticated API and wherein the authenticated API is configured to detect any changes to the patient profile; receive input relating to the patient from a second member of the medical team, wherein the input is received via the authenticated API from a second device; and update the patient profile based at least in part on the received input, wherein the updated patient profile is accessible to each of the plurality of members of the medical team via the authenticated API and wherein the authenticated API is configured to: receive a request to access data from one or more files external to the patient profile which are linked to the patient profile; retrieve the data from the one or more files external to the patient profile; and output at least a portion of the retrieved data.
A device for real-time sharing of patient information among a medical team using a secure API includes: a processor, memory with instructions for the processor to: receive initial patient data (e.g., symptoms) via the API from a first team member's device; create a patient profile accessible to all team members; when a second team member adds input (e.g., diagnosis, treatment plan) via the API from their device, update the patient profile; all team members can then view the updated profile through the API. The API also allows access to external files linked to the profile, such as retrieving data from external files linked to the patient profile. The device retrieves requested data from these files and presents it to the user. The API detects any changes to the patient profile.
19. The apparatus of claim 18 , wherein the one or more files external to the patient profile include one or more physician profiles, wherein the request to access data from one or more files external to the patient profile comprises a request to view contact information for a physician associated with the patient and wherein the retrieved data comprises the contact information for the physician associated with the patient.
The device from the previous description has external files linked to the patient profile including physician profiles. When a user requests a physician's contact information, the system retrieves that contact information from the corresponding physician profile and displays it.
20. The apparatus of claim 18 , wherein the one or more files external to the patient profile include a plurality of diagnostic test results and wherein the retrieved data comprises one or more diagnostic test results corresponding to the patient.
The device from the previous description has external files linked to the patient profile including diagnostic test results. When a user requests diagnostic results, the system retrieves and displays the patient's relevant test results.
21. The apparatus of claim 18 , wherein the request to access data from one or more files external to the patient profile comprises a request to generate a letter pertaining to the patient, wherein the retrieved data comprises a letter template corresponding to the requested letter including one or more blank data fields, and wherein outputting at least a portion of the retrieved data comprises outputting the letter template with the one or more blank data fields filled with information retrieved from the patient profile.
The device from the description related to patient information sharing includes a request to generate a letter pertaining to the patient. The system retrieves a letter template with blank fields. It then fills in those blank fields with information from the patient's profile before displaying or outputting the completed letter.
22. The apparatus of claim 18 , wherein the request to access data from one or more files external to the patient profile comprises a request to generate a bill, wherein the retrieved data comprises one or more first billing codes corresponding to one or more procedures associated with the patient profile and one or more second billing codes corresponding to one or more diagnoses associated with the patient profile, and wherein outputting at least a portion of the retrieved data comprises outputting a billing report including the one or more first billing codes and the one or more second billing codes.
The device from the description related to patient information sharing includes a request to generate a bill. The system retrieves relevant billing codes for procedures performed and diagnoses given to the patient. It then outputs a billing report containing these codes.
23. At least one non-transitory computer-readable medium storing computer-readable instructions that, when executed by one or more computing devices, cause at least one of the one or more computing devices to: receive preliminary patient data corresponding to the patient from a first member of a medical team comprising a plurality of members, wherein the preliminary patient data is received via the authenticated API from a first device; generate a patient profile for the patient, wherein the patient profile is accessible to each member of the medical team via the authenticated API and wherein the authenticated API is configured to detect any changes to the patient profile; receive input relating to the patient from a second member of the medical team, wherein the input is received via the authenticated API from a second device; and update the patient profile based at least in part on the received input, wherein the updated patient profile is accessible to each of the plurality of members of the medical team via the authenticated API and wherein the authenticated API is configured to: receive a request to access data from one or more files external to the patient profile which are linked to the patient profile; retrieve the data from the one or more files external to the patient profile; and output at least a portion of the retrieved data.
A non-transitory computer-readable medium stores instructions for real-time sharing of patient information among a medical team using a secure API: receive initial patient data (e.g., symptoms) via the API from a first team member's device; create a patient profile accessible to all team members; when a second team member adds input (e.g., diagnosis, treatment plan) via the API from their device, update the patient profile; all team members can then view the updated profile through the API. The API also allows access to external files linked to the profile, such as retrieving data from external files linked to the patient profile. The device retrieves requested data from these files and presents it to the user. The API detects any changes to the patient profile.
24. The at least one non-transitory computer-readable medium of claim 23 , wherein the one or more files external to the patient profile include one or more physician profiles, wherein the request to access data from one or more files external to the patient profile comprises a request to view contact information for a physician associated with the patient and wherein the retrieved data comprises the contact information for the physician associated with the patient.
The computer-readable medium from the previous description stores instructions related to patient information sharing, and has external files linked to the patient profile including physician profiles. When a user requests a physician's contact information, the system retrieves that contact information from the corresponding physician profile and displays it.
25. The at least one non-transitory computer-readable medium of claim 23 , wherein the one or more files external to the patient profile include a plurality of diagnostic test results and wherein the retrieved data comprises one or more diagnostic test results corresponding to the patient.
The computer-readable medium from the previous description stores instructions related to patient information sharing, and has external files linked to the patient profile including diagnostic test results. When a user requests diagnostic results, the system retrieves and displays the patient's relevant test results.
26. The at least one non-transitory computer-readable medium of claim 23 , wherein the request to access data from one or more files external to the patient profile comprises a request to generate a letter pertaining to the patient, wherein the retrieved data comprises a letter template corresponding to the requested letter including one or more blank data fields, and wherein outputting at least a portion of the retrieved data comprises outputting the letter template with the one or more blank data fields filled with information retrieved from the patient profile.
The computer-readable medium from the previous description stores instructions related to patient information sharing, and includes a request to generate a letter pertaining to the patient. The system retrieves a letter template with blank fields. It then fills in those blank fields with information from the patient's profile before displaying or outputting the completed letter.
27. The at least one non-transitory computer-readable medium of claim 23 , wherein the request to access data from one or more files external to the patient profile comprises a request to generate a bill, wherein the retrieved data comprises one or more first billing codes corresponding to one or more procedures associated with the patient profile and one or more second billing codes corresponding to one or more diagnoses associated with the patient profile, and wherein outputting at least a portion of the retrieved data comprises outputting a billing report including the one or more first billing codes and the one or more second billing codes.
The computer-readable medium from the previous description stores instructions related to patient information sharing, and includes a request to generate a bill. The system retrieves relevant billing codes for procedures performed and diagnoses given to the patient. It then outputs a billing report containing these codes.
Cooperative Patent Classification codes for this invention. Click any code to explore related patents in that topic.
February 3, 2015
April 11, 2017
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.