| Predicate |
Object |
| assignee |
http://rdf.ncbi.nlm.nih.gov/pubchem/patentassignee/MD5_41a639aa11b9b2f8063a3e6b8b22b557
http://rdf.ncbi.nlm.nih.gov/pubchem/patentassignee/MD5_700ff9a01db2075489cb7ed87392dc28 |
| classificationCPCAdditional |
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/A61M2205-18
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/A61M2205-3303
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/A61M2205-3331
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/A61M2205-3327
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/A61M2205-3553
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/A61M2205-3592
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/A61M2205-3576
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/A61M2230-005
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/A61M2205-502
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/A61M1-1522
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/A61M2230-30 |
| classificationCPCInventive |
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/A61M1-287
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/A61M1-28
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/A61M1-341
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/A61M1-282
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/A61M1-1603
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G16H20-40
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/A61M1-16
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/B01D61-32
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/B01D61-30
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/A61M1-159
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/A61M1-155
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/A61M1-281 |
| classificationIPCInventive |
http://rdf.ncbi.nlm.nih.gov/pubchem/patentipc/B01D61-32
http://rdf.ncbi.nlm.nih.gov/pubchem/patentipc/B01D61-30
http://rdf.ncbi.nlm.nih.gov/pubchem/patentipc/A61M1-16
http://rdf.ncbi.nlm.nih.gov/pubchem/patentipc/A61M1-34
http://rdf.ncbi.nlm.nih.gov/pubchem/patentipc/A61M1-28
http://rdf.ncbi.nlm.nih.gov/pubchem/patentipc/G16H20-40 |
| filingDate |
2017-08-02-04:00^^<http://www.w3.org/2001/XMLSchema#date> |
| grantDate |
2019-04-30-04:00^^<http://www.w3.org/2001/XMLSchema#date> |
| inventor |
http://rdf.ncbi.nlm.nih.gov/pubchem/patentinventor/MD5_ecd9072ba71ac96f08cceffb5c4f2fbd
http://rdf.ncbi.nlm.nih.gov/pubchem/patentinventor/MD5_4634ef4fbb7ec0ef7348688767733d47
http://rdf.ncbi.nlm.nih.gov/pubchem/patentinventor/MD5_f9f5fbd8229fa3f3ee65b7b6ad50592c |
| publicationDate |
2019-04-30-04:00^^<http://www.w3.org/2001/XMLSchema#date> |
| publicationNumber |
US-10272190-B2 |
| titleOfInvention |
Renal therapy system including a blood pressure monitor |
| abstract |
An example renal therapy system includes a blood pressure monitor configured to output blood pressure data concerning a patient and a renal therapy machine communicatively coupled to the blood pressure monitor. The renal therapy machine is configured to generate ultrafiltration (“UF”) removed data from a prescribed renal therapy treatment performed by the renal therapy machine on the patient, and transmit the UF removed data and the blood pressure data via a network. At least one of a UF trend or a blood pressure trend from the UF removed data or the blood pressure data is determined, enabling a further determination as to at least one of (a) whether a prescribed renal therapy treatment adjustment or a new prescribed renal therapy treatment needs to be made, (b) whether the patient is complying with the prescribed renal therapy treatment, or (c) whether a condition related to an alarm or an alert exists. |
| isCitedBy |
http://rdf.ncbi.nlm.nih.gov/pubchem/patent/US-11278653-B2 |
| priorityDate |
2008-07-09-04:00^^<http://www.w3.org/2001/XMLSchema#date> |
| type |
http://data.epo.org/linked-data/def/patent/Publication |