Secure integration of diagnostic device data into a web-based interface

1. A computer-implemented method of securely integrating diagnostic-device-generated device data in a backend through a user device the method comprising:

generating, with a diagnostic device in communication with an external device, an original instance of device data that corresponds to an analysis of a specimen performed by the diagnostic device;

receiving, with a native application of the user device, the device data through the external device;

establishing, with the native application, a secure connection with the backend;

implementing, through the native application and the secure connection, a user interface of a remote application on the user device;

implementing, through the native application, a local data call function of a remote application such that the remote application receives the device data;

determining, by the remote application, a compatibility of data elements of the device data with a first set of local fields of the remote application;

validating, by the remote application, the device data based on the compatibility determined for the data elements and the first set of local fields;

requesting, with the remote application a first authorization to integrate the device data into the first set of local fields based on a result of the validating;

populating, with the remote application, at least one of the first set of local fields with at least one corresponding data element from the device data and associating a first data control element with the data elements according to a first request result received in response to the requesting of the first authorization without permanently storing the device data on the user device;

requesting, with the remote application, a second authorization to integrate the device data, the requesting the second authorization including causing an option being displayed in an inactive state in the user interface of the remote application to be active for selection; and

populating, through the remote application, at least one storage field maintained by the backend for a first time with the at least one corresponding data element based on a selection of the option in response to the requesting of the second authorization, the at least one storage field:

being specific to the specimen and associated with the first data control element on the backend, and

corresponding to the at least one of the first set of local fields,

wherein requesting the first and second authorizations avoids cross-population of patient records associated with the device data in the backend.

2. The computer-implemented method of claim 1 , further comprising:

causing the native application to communicate with the remote application and initiate the local data call function in response to establishing the secure connection.

3. The computer-implemented method of claim 1 ,

wherein implementing the local data call function of the remote application includes the native application transferring the device data to the remote application without the device data being permanently stored by the native application or in a location on the user device.

4. The computer-implemented method of claim 1 ,

wherein the first set of local fields is expressed in a first page of the user interface of the remote application, and

wherein the remote application includes a plurality of pages and each of the plurality of pages expresses a respective set of local fields.

5. The computer-implemented method of claim 4 ,

wherein the data call function is a first data call function of the first page and each of the plurality of pages includes a respective data call function, and

wherein the first page is selected from the plurality of pages by the remote application to be loaded in the user interface based on the device data.

6. The computer-implemented method of claim 4 , further comprising:

determining, with the remote application, the data elements do not correspond to the first set of local fields based on the compatibility determined for the data elements,

wherein requesting the first authorization includes requesting a different one of the plurality of pages be selected.

7. The computer-implemented method of claim 1 , further comprising:

determining, with the remote application, the data elements do not correspond to the first set of local fields based on the compatibility determined for the data elements;

deleting the device data from the remote application based on the determination; and

setting the validation result to indicate the device data has been deleted prior to requesting the first authorization.

8. The computer-implemented method of claim 1 ,

wherein the device data includes a plurality of print commands interspersed between data elements, and

wherein the remote application extracts the data elements from the print commands as part of determining the compatibility of the data elements and validating the device data.

9. The computer-implemented method of claim 1 , further comprising, prior to receiving the device data:

pairing, with the native application, the user device to the external device; and

establishing, with the native application, a data channel between the user device and the external device.

10. The computer-implemented method of claim 1 , wherein the diagnostic device is configured to perform a lipid panel test on a blood sample provided on a test strip, and wherein the device data includes results of a lipid panel test performed for a patient identified by the first control data element.

11. A non-transitory, computer-readable medium comprising instructions that, when executed by a processor of a user device, perform stages for securely integrating diagnostic-device-generated device data in a backend through the user device, the stages comprising:

generating, with a diagnostic device in communication with an external device, an original instance of device data that corresponds to an analysis of a specimen performed by the diagnostic device;

receiving, with a native application of the user device, the device data through the external device;

establishing, with the native application, a secure connection with the backend;

implementing, through the native application and the secure connection, a user interface of a remote application on the user device;

implementing, through the native application, a local data call function of a remote application such that the remote application receives the device data;

determining, by the remote application, a compatibility of data elements of the device data with a first set of local fields of the remote application;

validating, by the remote application, the device data based on the compatibility determined for the data elements and the first set of local fields;

requesting, with the remote application, a first authorization to integrate the device data into the first set of local fields based on a result of the validating;

populating, with the remote application, at least one of the first set of local fields with at least one corresponding data element from the device data and associating a first data control element with the data elements according to a first request result received in response to the requesting of the first authorization without permanently storing the device data on the user device;

requesting, with the remote application, a second authorization to integrate the device data, the requesting the second authorization including causing an option being displayed in an inactive state in the user interface of the remote application to be active for selection; and

populating, through the remote application, at least one storage field maintained by the backend for a first time with the at least one corresponding data element based on a selection of the option in response to the requesting of the second authorization, the at least one storage field:

being specific to the specimen and associated with the first data control element on the backend, and

corresponding to the at least one of the first set of local fields,

wherein requesting the first and second authorizations avoids cross-population of patient records associated with the device data in the backend.

12. The non-transitory, computer-readable medium of claim 11 , the stages further comprising:

causing the native application to communicate with the remote application and initiate the local data call function in response to establishing the secure connection.

13. The non-transitory, computer-readable medium of claim 11 ,

wherein implementing the local data call function of the remote application includes the native application transferring the device data to the remote application without the device data being permanently stored by the native application or in a location on the user device.

14. The non-transitory, computer-readable medium of claim 11 ,

wherein the first set of local fields is expressed in a first page of the user interface of the remote application, and

wherein the remote application includes a plurality of pages and each of the plurality of pages expresses a respective set of local fields.

15. The non-transitory, computer-readable medium of claim 11 ,

wherein the device data includes a plurality of print commands interspersed between data elements, and

wherein the remote application extracts the data elements from the print commands as part of determining the compatibility of the data elements and validating the device data.

16. The non-transitory, computer-readable medium of claim 11 , wherein the diagnostic device is configured to perform a lipid panel test on a blood sample provided on a test strip, and wherein the device data includes results of a lipid panel test performed for a patient identified by the first control data element.

17. A system for securely integrating diagnostic-device-generated device data a backend of the system through a user device, the system comprising:

a diagnostic device;

at least one memory storage including a non-transitory, computer-readable medium comprising instructions; and

the backend,

wherein the diagnostic device and the backend include processors that execute the instructions to carry out stages comprising:

generating, with the diagnostic device in communication with an external device, an original instance of device data that corresponds to an analysis of a specimen performed by the diagnostic device;

causing a user device to receive, with a native application, the device data through the external device;

establishing, with the native application, a secure connection with the backend;

implementing, through the native application and the secure connection, a user interface of a remote application on the user device;

implementing, through the native application, a local data call function of a remote application such that the remote application receives the device data;

determining, by the remote application, a compatibility of data elements of the device data with a first set of local fields of the remote application;

validating, by the remote application, the device data based on the compatibility determined for the data elements and the first set of local fields;

requesting, with the remote application a first authorization to integrate the device data into the first set of local fields based on a result of the validating;

populating, with the remote application, at least one of the first set of local fields with at least one corresponding data element from the device data and associating a first data control element with the data elements according to a first request result received in response to the requesting of the first authorization without permanently storing the device data on the user device;

requesting, with the remote application, a second authorization to integrate the device data, the requesting the second authorization including causing an option being displayed in an inactive state in the user interface of the remote application to be active for selection; and

populating, through the remote application, at least one storage field maintained by the backend for a first time with the at least one corresponding data element based on a selection of the option in response to the requesting of the second authorization, the at least one storage field:

being specific to the specimen and associated with the first data control element on the backend, and

corresponding to the at least one of the first set of local fields,

wherein requesting the first and second authorizations avoids cross-population of patient records associated with the device data in the backend.

18. The system of claim 17 , the stages further comprising:

causing the native application to communicate with the remote application and initiate the local data call function in response to establishing the secure connection.

19. The system of claim 17 ,

wherein implementing the local data call function of the remote application includes the native application transferring the device data to the remote application without the device data being permanently stored by the native application or in a location on the user device.

20. The system of claim 17 , wherein the diagnostic device is configured to perform a lipid panel test on a blood sample provided on a test strip, and wherein the device data includes results of a lipid panel test performed for a patient identified by the first control data element.