Systems and methods for managing patient medical devices
Implementations described and claimed herein provide systems and methods for patient device management. In one implementation, interrogation data is received from a cardiac implantable electronic device corresponding to an interrogation for a patient. The interrogation data includes device data for the cardiac implantable electronic device and patient specific data for the patient. The interrogation data is normalized into manufacturer independent interrogation data. The manufacturer independent interrogation data is associated with a permitted user. A processing status is assigned to the interrogation using the manufacturer independent interrogation data. The interrogation is aggregated into a category based on the processing status, and the category is associated with an action by the permitted user.
1. A method for patient device management, the method comprising:
receiving, using a wireless transmission interface, interrogation data originating from a cardiac implantable electronic device corresponding to an interrogation for a patient, the interrogation data including device data for the cardiac implantable electronic device and patient specific data for the patient, the cardiac implantable electronic device being manufactured by one of a plurality of manufacturers;
generating, using one or more processors of a computing device, manufacturer independent interrogation data by normalizing the interrogation data of the plurality of manufacturers through a conversion of the interrogation data into a unified format;
parsing, using the one or more processors of the computing device, the manufacturer independent interrogation data to determine at least one key identifier associated with the cardiac implantable electronic device or the patient;
associating, using the one or more processors of the computing device, the manufacturer independent interrogation data with at least one permitted user;
extracting, using the one or more processors of the computing device, discrete data based on data mapping of the manufacturer independent interrogation data;
generating, using the one or more processors of the computing device and based on the extracted discrete data, provider-oriented information for the interrogation, the provider-oriented information including an association of the at least one key identifier and the manufacturer independent interrogation data;
assigning, using the one or more processors of the computing device, a processing state to the interrogation using the provider-oriented information;
aggregating, using the one or more processors of the computing device, the interrogation into a category based on the processing state, the category associated with an action by the at least one permitted user, the category being:
backlog when the processing state is passive,
compose when the processing state is saved, and
hidden when the processing state is archived; and
presenting the provider-oriented information according to the category using at least one display communicatively coupled to the computing device, wherein presenting the provider-oriented information comprises a two-click approval including:
displaying a start button corresponding to the interrogation;
upon a selection of the start button, generating a docket including an automatically generated impression and an automatically generated care plan;
displaying a save button corresponding to the docket; and
upon a selection of the save button, saving the docket,
wherein the category is cleared following the two-click approval by the at least one permitted user.
2. The method of claim 1 , wherein the processing state is docketed.
3. The method of claim 2 , wherein the category is needs approval when the processing state is docketed.
4. The method of claim 1 , wherein the at least one permitted user is at least one of: a professional associated with a clinic or a third party to which access rights were delegated.
5. The method of claim 1 , wherein the interrogation data is received from memory and obtained from the cardiac implantable electronic device using a manufacturer-specific programmer during an in-office visit.
6. The method of claim 5 , wherein a data file for the interrogation is generated by the manufacturer-specific programmer and normalizing the interrogation data includes parsing the data file into a parsed data file using a plurality of parsing stages.
7. The method of claim 1 , wherein the interrogation is a remote interrogation and the interrogation data is received over a network from a manufacturer system using a Health Level 7 (HL7) communication protocol and an Implantable Device Cardiac Observation (IDCO) data standard.
8. The method of claim 7 , wherein normalizing the interrogation data includes HL7 data extraction by mapping unidentified HL7 data to one or more interrogation fields and normalizing IDCO data.
9. The method of claim 8 , wherein normalizing the interrogation data further includes device setting calculations and normalization.
10. The method of claim 1 , wherein the interrogation is assigned a severity based on an association of the interrogation with an event type.
11. The method of claim 10 , wherein the severity is a normal device function where the event type is no event.
12. The method of claim 11 , a prompt for the two-click approval generated in response to the severity being assigned the normal device function.
13. The method of claim 12 , wherein the prompt includes the automatically generated impression and the automatically generated care plan corresponding to the normal device function.
14. The method of claim 1 , further comprising:
generating one or more billing opportunities for a clinic based on the category.
15. The method of claim 14 , wherein the one or more billing opportunities are determined based on a reimbursement rate, a frequency of available reimbursements, and a number of patients.
16. The method of claim 14 , wherein the one or more billing opportunities includes determining a billing window corresponding to the interrogation based on a number of days since the interrogation and a minimum and a maximum number of days between billable events.
17. The method of claim 1 , further comprising:
generating an audit trail for the cardiac implantable electronic device, the audit trail including at least one of past interrogations, the interrogation, or action taken with respect to the cardiac implantable electronic device.
18. The method of claim 1 , further comprising:
generating community analytics for a clinic based on the category, the community analytics including a comparison of the clinic to at least one of a second clinic or a benchmark for a plurality of clinics.
19. The method of claim 1 , wherein the computing device is configured to generate interrogation report form the manufacturer independent interrogation data, the interrogation report is included in a stack of interrogation reports for the cardiac implantable electronic device, each in the stack of interrogation reports corresponding to a disparate interrogation.
20. A method for patient device management, the method comprising:
establishing a wireless network connection between a computing device and a cardiac implantable electronic device;
receiving, using the wireless network connection, interrogation data originating from the cardiac implantable electronic device corresponding to an interrogation for a patient, the interrogation data including device data for the cardiac implantable electronic device and patient specific data for the patient, the cardiac implantable electronic device being manufactured by one of a plurality of manufacturers;
generating, using one or more processors of the computing device, manufacturer independent interrogation data by normalizing the interrogation data of the plurality of manufacturers through a conversion of the interrogation data into a unified format;
parsing, in a first stage, using the one or more processors of the computing device, the manufacturer independent interrogation data to determine at least one key identifier associated with the cardiac implantable electronic device or the patient;
associating, using the one or more processors of the computing device, the manufacturer independent interrogation data with at least one permitted user;
parsing, in a second stage, using the one or more processors of the computing device, the manufacturer independent interrogation data, to extract discrete data using data mapping;
generating, using the one or more processors of the computing device and based on the extracted discrete data, provider-oriented information for the interrogation, the provider-oriented information including an association of the at least one key identifier and the manufacturer independent interrogation data;
assigning, using the one or more processors of the computing device, a processing state to the interrogation using the provider-oriented information, the processing state being passive, saved, or archived;
aggregating, using the one or more processors of the computing device, the interrogation into a category based on the processing state, the category associated with an action by the at least one permitted user, the category being:
backlog when the processing state is passive,
compose when the processing state is saved, and
hidden when the processing state is archived; and
presenting the provider-oriented information according to the category using at least one display communicatively coupled to the computing device, wherein presenting the provider-oriented information comprises a two-click approval including:
displaying a start button corresponding to the interrogation;
upon a selection of the start button, generating a docket including an automatically generated impression and an automatically generated care plan;
displaying a save button corresponding to the docket; and
upon a selection of the save button, saving the docket,
wherein the category is cleared following the two-click approval by the at least one permitted user.