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/G16H40-20 http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G16H80-00 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/G16H10-60 http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G16H20-10 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/G16H40-60 http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G16H40-63 http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G16H40-67 |
classificationIPCInventive |
http://rdf.ncbi.nlm.nih.gov/pubchem/patentipc/G16H20-17 http://rdf.ncbi.nlm.nih.gov/pubchem/patentipc/G16H20-10 http://rdf.ncbi.nlm.nih.gov/pubchem/patentipc/G16H10-60 http://rdf.ncbi.nlm.nih.gov/pubchem/patentipc/G16H40-60 http://rdf.ncbi.nlm.nih.gov/pubchem/patentipc/G16H40-67 |
filingDate |
2019-05-10-04:00^^<http://www.w3.org/2001/XMLSchema#date> |
inventor |
http://rdf.ncbi.nlm.nih.gov/pubchem/patentinventor/MD5_acde81a8aba3d0830f35f448defef813 http://rdf.ncbi.nlm.nih.gov/pubchem/patentinventor/MD5_708d0ed9aca37053c2728fa2a92b4c38 http://rdf.ncbi.nlm.nih.gov/pubchem/patentinventor/MD5_d7dd58f69a721570f68cc3111bfea2b6 |
publicationDate |
2019-11-14-04:00^^<http://www.w3.org/2001/XMLSchema#date> |
publicationNumber |
WO-2019217886-A1 |
titleOfInvention |
Medical device data back-association, system, apparatuses, and methods |
abstract |
A medical device data back-association system, apparatuses, and methods are disclosed. In an example embodiment, a server receives first medical device data from a medical device including a device identifier and stores the first medical device data to an unassociated record in a database after determining that there is no association between the device identifier and any patient identifier or medication order identifier. While the medical device is administering the medication to a patient, the server receives an identifier message including at least two of the device identifier, the patient identifier, and the medication order identifier. The server creates an identifier association between a medical record of the patient and the medical device using the identifier message. The server uses the identifier association to store subsequent medical device data from the medical device to the medical record of the patient. |
priorityDate |
2018-05-11-04:00^^<http://www.w3.org/2001/XMLSchema#date> |
type |
http://data.epo.org/linked-data/def/patent/Publication |