http://rdf.ncbi.nlm.nih.gov/pubchem/patent/EP-4116985-A1
Outgoing Links
| Predicate | Object |
|---|---|
| assignee | http://rdf.ncbi.nlm.nih.gov/pubchem/patentassignee/MD5_700ff9a01db2075489cb7ed87392dc28 http://rdf.ncbi.nlm.nih.gov/pubchem/patentassignee/MD5_41a639aa11b9b2f8063a3e6b8b22b557 |
| classificationCPCAdditional | http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/A61M2205-3576 http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G16H80-00 http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G16H40-20 http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/A61M2205-6072 |
| classificationCPCInventive | http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G16H20-17 http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G16H20-40 http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G06K19-06009 http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G16H40-67 http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G16H40-20 http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G16H40-60 http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G16H40-63 http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G16H80-00 http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G16H10-60 http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G16H20-10 |
| classificationIPCAdditional | http://rdf.ncbi.nlm.nih.gov/pubchem/patentipc/G16H40-20 |
| classificationIPCInventive | http://rdf.ncbi.nlm.nih.gov/pubchem/patentipc/G16H40-67 http://rdf.ncbi.nlm.nih.gov/pubchem/patentipc/G16H40-63 http://rdf.ncbi.nlm.nih.gov/pubchem/patentipc/G16H10-60 http://rdf.ncbi.nlm.nih.gov/pubchem/patentipc/G16H20-17 |
| filingDate | 2019-05-10-04:00^^<http://www.w3.org/2001/XMLSchema#date> |
| inventor | http://rdf.ncbi.nlm.nih.gov/pubchem/patentinventor/MD5_d37d21589a087278c3ec6c09f1a79970 http://rdf.ncbi.nlm.nih.gov/pubchem/patentinventor/MD5_650d7cf1bd3af3164e5d73a87eff6f20 http://rdf.ncbi.nlm.nih.gov/pubchem/patentinventor/MD5_581e7c6227edbc260e96c5d9eaa132b5 |
| publicationDate | 2023-01-11-04:00^^<http://www.w3.org/2001/XMLSchema#date> |
| publicationNumber | EP-4116985-A1 |
| titleOfInvention | Medical device data back-association, system, apparatuses, and methods |
| abstract | An infusion pump apparatus (102) is described. The apparatus comprises: a drive mechanism that is configured to move fluid from a fluid container through intravenous tubing to a patient; a user interface (204); a display screen (202); a memory device that is configured to store (i) a device identifier (126), and (ii) prescription parameters to perform an infusion therapy on a patient; and a processor that is communicatively coupled to the drive mechanism, the user interface, the display screen, and the memory device. The processor is configured to: cause the drive mechanism to operate according to the prescription parameters to perform the infusion therapy, generate first medical device data (112) related to performing the infusion therapy, transmit the first medical device data (112) and the device identifier (126) to a server (114) via a network, where there is no association between the device identifier and any patient identifier or medication order, receive a request via the user interface (204) while performing the infusion therapy to display the device identifier (126), cause the device identifier (126) to be displayed on the device screen (202) as a machine-scannable code, where the scanning of the device identifier creates an association, via the server (114), between an electronic medical record ("EMR") (902) of the patient and the device identifier (126), generate second medical device data (112) related to performing the infusion therapy, and transmit the second medical device data (112) and the device identifier (126) to the server (114) via the network, where the association of the EMR (902) and the device identifier (126) causes the second medical device data to be stored to the EMR of the patient. Also described is a medical device data back-association method. |
| priorityDate | 2018-05-11-04:00^^<http://www.w3.org/2001/XMLSchema#date> |
| type | http://data.epo.org/linked-data/def/patent/Publication |
Incoming Links
Total number of triples: 50.