WO2024076669A1 - Identification des services fournis à un patient par un fournisseur de soins médicaux sur la base des interactions du fournisseur de soins médicaux avec un dispositif de surveillance de patient - Google Patents
Identification des services fournis à un patient par un fournisseur de soins médicaux sur la base des interactions du fournisseur de soins médicaux avec un dispositif de surveillance de patient Download PDFInfo
- Publication number
- WO2024076669A1 WO2024076669A1 PCT/US2023/034532 US2023034532W WO2024076669A1 WO 2024076669 A1 WO2024076669 A1 WO 2024076669A1 US 2023034532 W US2023034532 W US 2023034532W WO 2024076669 A1 WO2024076669 A1 WO 2024076669A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- medical
- medical providers
- services provided
- patient
- providers
- Prior art date
Links
- 230000003993 interaction Effects 0.000 title claims abstract description 80
- 238000012806 monitoring device Methods 0.000 title description 4
- 238000012544 monitoring process Methods 0.000 claims abstract description 117
- 238000000034 method Methods 0.000 claims abstract description 113
- 230000002452 interceptive effect Effects 0.000 claims abstract description 75
- 239000003814 drug Substances 0.000 claims description 154
- 229940079593 drug Drugs 0.000 claims description 152
- 238000002483 medication Methods 0.000 claims description 79
- 230000015654 memory Effects 0.000 claims description 32
- 235000015097 nutrients Nutrition 0.000 description 28
- 230000036541 health Effects 0.000 description 27
- 230000003862 health status Effects 0.000 description 22
- 238000012549 training Methods 0.000 description 21
- 238000005399 mechanical ventilation Methods 0.000 description 16
- 238000004458 analytical method Methods 0.000 description 15
- 230000008569 process Effects 0.000 description 14
- 238000009423 ventilation Methods 0.000 description 14
- 238000013459 approach Methods 0.000 description 13
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 description 13
- 238000012384 transportation and delivery Methods 0.000 description 11
- 238000012360 testing method Methods 0.000 description 10
- MYPYJXKWCTUITO-UHFFFAOYSA-N vancomycin Natural products O1C(C(=C2)Cl)=CC=C2C(O)C(C(NC(C2=CC(O)=CC(O)=C2C=2C(O)=CC=C3C=2)C(O)=O)=O)NC(=O)C3NC(=O)C2NC(=O)C(CC(N)=O)NC(=O)C(NC(=O)C(CC(C)C)NC)C(O)C(C=C3Cl)=CC=C3OC3=CC2=CC1=C3OC1OC(CO)C(O)C(O)C1OC1CC(C)(N)C(O)C(C)O1 MYPYJXKWCTUITO-UHFFFAOYSA-N 0.000 description 10
- 108010059993 Vancomycin Proteins 0.000 description 9
- 230000001276 controlling effect Effects 0.000 description 9
- 238000010586 diagram Methods 0.000 description 9
- 230000036387 respiratory rate Effects 0.000 description 9
- MYPYJXKWCTUITO-LYRMYLQWSA-N vancomycin Chemical compound O([C@@H]1[C@@H](O)[C@H](O)[C@@H](CO)O[C@H]1OC1=C2C=C3C=C1OC1=CC=C(C=C1Cl)[C@@H](O)[C@H](C(N[C@@H](CC(N)=O)C(=O)N[C@H]3C(=O)N[C@H]1C(=O)N[C@H](C(N[C@@H](C3=CC(O)=CC(O)=C3C=3C(O)=CC=C1C=3)C(O)=O)=O)[C@H](O)C1=CC=C(C(=C1)Cl)O2)=O)NC(=O)[C@@H](CC(C)C)NC)[C@H]1C[C@](C)(N)[C@H](O)[C@H](C)O1 MYPYJXKWCTUITO-LYRMYLQWSA-N 0.000 description 9
- 229960003165 vancomycin Drugs 0.000 description 9
- 230000029058 respiratory gaseous exchange Effects 0.000 description 8
- 208000025721 COVID-19 Diseases 0.000 description 7
- 230000033228 biological regulation Effects 0.000 description 7
- 206010035664 Pneumonia Diseases 0.000 description 6
- 206010069351 acute lung injury Diseases 0.000 description 6
- 239000003708 ampul Substances 0.000 description 6
- 230000004872 arterial blood pressure Effects 0.000 description 6
- 201000010099 disease Diseases 0.000 description 6
- 208000037265 diseases, disorders, signs and symptoms Diseases 0.000 description 6
- 238000010801 machine learning Methods 0.000 description 6
- 210000000056 organ Anatomy 0.000 description 6
- 239000006187 pill Substances 0.000 description 6
- 230000002269 spontaneous effect Effects 0.000 description 6
- QVGXLLKOCUKJST-UHFFFAOYSA-N atomic oxygen Chemical compound [O] QVGXLLKOCUKJST-UHFFFAOYSA-N 0.000 description 5
- 238000007726 management method Methods 0.000 description 5
- 239000001301 oxygen Substances 0.000 description 5
- 229910052760 oxygen Inorganic materials 0.000 description 5
- 230000000241 respiratory effect Effects 0.000 description 5
- 230000008901 benefit Effects 0.000 description 4
- 230000003205 diastolic effect Effects 0.000 description 4
- 230000000694 effects Effects 0.000 description 4
- 238000013507 mapping Methods 0.000 description 4
- 208000009470 Ventilator-Associated Pneumonia Diseases 0.000 description 3
- 230000036449 good health Effects 0.000 description 3
- 210000001147 pulmonary artery Anatomy 0.000 description 3
- 230000004044 response Effects 0.000 description 3
- 206010040047 Sepsis Diseases 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 238000002591 computed tomography Methods 0.000 description 2
- DDRJAANPRJIHGJ-UHFFFAOYSA-N creatinine Chemical compound CN1CC(=O)NC1=N DDRJAANPRJIHGJ-UHFFFAOYSA-N 0.000 description 2
- 238000013481 data capture Methods 0.000 description 2
- 230000034994 death Effects 0.000 description 2
- 231100000517 death Toxicity 0.000 description 2
- 238000001914 filtration Methods 0.000 description 2
- IRSCQMHQWWYFCW-UHFFFAOYSA-N ganciclovir Chemical compound O=C1NC(N)=NC2=C1N=CN2COC(CO)CO IRSCQMHQWWYFCW-UHFFFAOYSA-N 0.000 description 2
- 229960002963 ganciclovir Drugs 0.000 description 2
- 229920000669 heparin Polymers 0.000 description 2
- ZFGMDIBRIDKWMY-PASTXAENSA-N heparin Chemical compound CC(O)=N[C@@H]1[C@@H](O)[C@H](O)[C@@H](COS(O)(=O)=O)O[C@@H]1O[C@@H]1[C@@H](C(O)=O)O[C@@H](O[C@H]2[C@@H]([C@@H](OS(O)(=O)=O)[C@@H](O[C@@H]3[C@@H](OC(O)[C@H](OS(O)(=O)=O)[C@H]3O)C(O)=O)O[C@@H]2O)CS(O)(=O)=O)[C@H](O)[C@H]1O ZFGMDIBRIDKWMY-PASTXAENSA-N 0.000 description 2
- 229960001008 heparin sodium Drugs 0.000 description 2
- 238000003384 imaging method Methods 0.000 description 2
- 208000015181 infectious disease Diseases 0.000 description 2
- 230000003434 inspiratory effect Effects 0.000 description 2
- 238000007477 logistic regression Methods 0.000 description 2
- 210000004072 lung Anatomy 0.000 description 2
- 238000006213 oxygenation reaction Methods 0.000 description 2
- 230000001681 protective effect Effects 0.000 description 2
- 238000011160 research Methods 0.000 description 2
- 238000012552 review Methods 0.000 description 2
- 238000007619 statistical method Methods 0.000 description 2
- 238000012706 support-vector machine Methods 0.000 description 2
- 238000001356 surgical procedure Methods 0.000 description 2
- 238000002560 therapeutic procedure Methods 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 230000000007 visual effect Effects 0.000 description 2
- 235000013343 vitamin Nutrition 0.000 description 2
- 229940088594 vitamin Drugs 0.000 description 2
- 229930003231 vitamin Natural products 0.000 description 2
- 239000011782 vitamin Substances 0.000 description 2
- 101100407030 Arabidopsis thaliana PAO2 gene Proteins 0.000 description 1
- 206010010071 Coma Diseases 0.000 description 1
- 208000035473 Communicable disease Diseases 0.000 description 1
- 208000028399 Critical Illness Diseases 0.000 description 1
- 101001001645 Homo sapiens Serine/threonine-protein kinase pim-3 Proteins 0.000 description 1
- 206010021079 Hypopnoea Diseases 0.000 description 1
- DGAQECJNVWCQMB-PUAWFVPOSA-M Ilexoside XXIX Chemical compound C[C@@H]1CC[C@@]2(CC[C@@]3(C(=CC[C@H]4[C@]3(CC[C@@H]5[C@@]4(CC[C@@H](C5(C)C)OS(=O)(=O)[O-])C)C)[C@@H]2[C@]1(C)O)C)C(=O)O[C@H]6[C@@H]([C@H]([C@@H]([C@H](O6)CO)O)O)O.[Na+] DGAQECJNVWCQMB-PUAWFVPOSA-M 0.000 description 1
- ZLMJMSJWJFRBEC-UHFFFAOYSA-N Potassium Chemical compound [K] ZLMJMSJWJFRBEC-UHFFFAOYSA-N 0.000 description 1
- 206010039897 Sedation Diseases 0.000 description 1
- 102100036119 Serine/threonine-protein kinase pim-3 Human genes 0.000 description 1
- 208000027418 Wounds and injury Diseases 0.000 description 1
- 239000008186 active pharmaceutical agent Substances 0.000 description 1
- 230000002411 adverse Effects 0.000 description 1
- 230000003466 anti-cipated effect Effects 0.000 description 1
- 238000007486 appendectomy Methods 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000001746 atrial effect Effects 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 238000003339 best practice Methods 0.000 description 1
- 230000003115 biocidal effect Effects 0.000 description 1
- 230000000740 bleeding effect Effects 0.000 description 1
- 210000004369 blood Anatomy 0.000 description 1
- 239000008280 blood Substances 0.000 description 1
- 238000004820 blood count Methods 0.000 description 1
- 230000036772 blood pressure Effects 0.000 description 1
- 210000000746 body region Anatomy 0.000 description 1
- 210000000988 bone and bone Anatomy 0.000 description 1
- 230000006931 brain damage Effects 0.000 description 1
- 231100000874 brain damage Toxicity 0.000 description 1
- 208000029028 brain injury Diseases 0.000 description 1
- 230000035565 breathing frequency Effects 0.000 description 1
- 230000000747 cardiac effect Effects 0.000 description 1
- 238000012656 cationic ring opening polymerization Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000001684 chronic effect Effects 0.000 description 1
- 239000003086 colorant Substances 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000002596 correlated effect Effects 0.000 description 1
- 229940109239 creatinine Drugs 0.000 description 1
- 229940124446 critical care medicine Drugs 0.000 description 1
- 230000006378 damage Effects 0.000 description 1
- 238000007405 data analysis Methods 0.000 description 1
- 238000013480 data collection Methods 0.000 description 1
- 238000013479 data entry Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000001934 delay Effects 0.000 description 1
- 230000003111 delayed effect Effects 0.000 description 1
- 206010012601 diabetes mellitus Diseases 0.000 description 1
- 230000008030 elimination Effects 0.000 description 1
- 238000003379 elimination reaction Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000000605 extraction Methods 0.000 description 1
- 230000002349 favourable effect Effects 0.000 description 1
- PJMPHNIQZUBGLI-UHFFFAOYSA-N fentanyl Chemical compound C=1C=CC=CC=1N(C(=O)CC)C(CC1)CCN1CCC1=CC=CC=C1 PJMPHNIQZUBGLI-UHFFFAOYSA-N 0.000 description 1
- 239000007789 gas Substances 0.000 description 1
- 238000005534 hematocrit Methods 0.000 description 1
- 230000000004 hemodynamic effect Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 208000014674 injury Diseases 0.000 description 1
- 238000003780 insertion Methods 0.000 description 1
- 230000037431 insertion Effects 0.000 description 1
- MJIHNNLFOKEZEW-UHFFFAOYSA-N lansoprazole Chemical compound CC1=C(OCC(F)(F)F)C=CN=C1CS(=O)C1=NC2=CC=CC=C2N1 MJIHNNLFOKEZEW-UHFFFAOYSA-N 0.000 description 1
- 229960003174 lansoprazole Drugs 0.000 description 1
- 210000000265 leukocyte Anatomy 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000005065 mining Methods 0.000 description 1
- 239000000203 mixture Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 239000004050 mood stabilizer Substances 0.000 description 1
- 229940127237 mood stabilizer Drugs 0.000 description 1
- 210000003205 muscle Anatomy 0.000 description 1
- 230000003387 muscular Effects 0.000 description 1
- 230000008518 non respiratory effect Effects 0.000 description 1
- 230000000474 nursing effect Effects 0.000 description 1
- 230000004768 organ dysfunction Effects 0.000 description 1
- 229940124641 pain reliever Drugs 0.000 description 1
- 229910052700 potassium Inorganic materials 0.000 description 1
- 239000011591 potassium Substances 0.000 description 1
- 230000002028 premature Effects 0.000 description 1
- 238000011321 prophylaxis Methods 0.000 description 1
- 238000010223 real-time analysis Methods 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 230000036280 sedation Effects 0.000 description 1
- 201000009890 sinusitis Diseases 0.000 description 1
- 229910052708 sodium Inorganic materials 0.000 description 1
- 239000011734 sodium Substances 0.000 description 1
- 238000001228 spectrum Methods 0.000 description 1
- 238000013125 spirometry Methods 0.000 description 1
- 238000011272 standard treatment Methods 0.000 description 1
- 238000007627 surgical diagnostic procedure Methods 0.000 description 1
- 230000001225 therapeutic effect Effects 0.000 description 1
- 210000000115 thoracic cavity Anatomy 0.000 description 1
- 238000011282 treatment Methods 0.000 description 1
- 210000002700 urine Anatomy 0.000 description 1
- 150000003722 vitamin derivatives Chemical class 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/14—Payment architectures specially adapted for billing systems
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
- A61B5/00—Measuring for diagnostic purposes; Identification of persons
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/14—Payment architectures specially adapted for billing systems
- G06Q20/145—Payments according to the detected use or quantity
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/04—Billing or invoicing
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H20/00—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance
- G16H20/40—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance relating to mechanical, radiation or invasive therapies, e.g. surgery, laser therapy, dialysis or acupuncture
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
- G16H40/20—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
- G16H40/60—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices
- G16H40/63—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices for local operation
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
- G16H40/60—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices
- G16H40/67—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices for remote operation
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H50/00—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics
- G16H50/20—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics for computer-aided diagnosis, e.g. based on medical expert systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/08—Insurance
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H10/00—ICT specially adapted for the handling or processing of patient-related medical or healthcare data
- G16H10/60—ICT specially adapted for the handling or processing of patient-related medical or healthcare data for patient-specific data, e.g. for electronic patient records
Definitions
- the present disclosure generally relates to systems and methods for identifying services provided by one or more medical providers based on medical provider interactions with a patient monitoring interface.
- VAEs are Ventilator Associated Events that negatively impact patient outcomes - the most common of which are pneumonia and sepsis.
- VAP Ventilator-Associated Pneumonias
- Other common ventilator risks are air leaks, brain damage and sinus infection.
- ALI acute lung injury
- ventilator induced injuries with an associated mortality rate of 40%.
- Typical causes of ALI are pneumonia, massive bleeding, a serious car accident or a life-threatening infection.
- the annual cost associated with ALI patients alone is $5.58B per year.
- Patients in urban areas experienced additional challenges including a higher number of organ dysfunctions, tracheostomies and higher mortality when compared to their non-urban counterparts.
- requirements for weaning from ventilation consist of both respiratory and non-respiratory parameters, all of which may play a critical role in weaning success and all of which the experienced intensivist considers at the time of weaning.
- requirements for weaning from ventilation include: adequate oxygen, adequate CO2 elimination, adequate respiratory muscular strength and ability to protect the airway are all examples of requirements for weaning from ventilation.
- Indicators of successful withdrawal of ventilation include a successful spontaneous breathing trial, minute ventilation, spirometry, PAO2/FIO2 ratio and rapid shallow breathing index.
- Telemedicine in the ICU provides remote monitoring of vital signs; for more detailed information, physicians typically consult the EMR remotely away from the ICU.
- ICU e.g., eICU, tele-ICU, virtual ICU
- EMR electronic medical record
- patients were 26% more likely to survive the ICU, discharged from the ICU 20% faster, 16% more likely to survive hospitalization and be discharged as well as be discharged from the hospital 15% faster.
- most tele-ICU vendors do not provide ventilator settings to hospitals (owing to a myriad of equipment in use in any ICU).
- a method for identifying services provided by one or more medical providers based on medical provider interactions with a patient monitoring interface may include receiving, by one or more processors, biometric data captured by one or more medical devices associated with one or more patients; providing, by the one or more processors, via a patient monitoring interface, one or more interactive displays including indications of the biometric data captured by the one or more medical devices associated with the one or more patients; receiving, by the one or more processors, an indication of one or more interactions, of one or more medical providers, with the one or more interactive displays provided by the patient monitoring interface; and analyzing, by the one or more processors, the one or more interactions, of the one or more medical providers, with the one or more interactive displays provided by the patient monitoring interface, in order to identify one or more services provided by the one or more medical providers.
- a system for identifying services provided by one or more medical providers based on medical provider interactions with a patient monitoring interface may include a patient monitoring interface; one or more processors; and a non-transitory computer-readable memory storing one or more instructions that, when executed by the one or more processors, cause the one or more processors to: receive biometric data captured by one or more medical devices associated with one or more patients; provide, via the patient monitoring interface, one or more interactive displays including indications of the biometric data captured by the one or more medical devices associated with the one or more patients; receive an indication of one or more interactions, of one or more medical providers, with the one or more interactive displays provided by the patient monitoring interface; and analyze the one or more interactions, of the one or more medical providers, with the one or more interactive displays provided by the patient monitoring interface, in order to identify one or more services provided by the one or more medical providers.
- a non-transitory, computer-readable memory storing one or more instructions for identifying services provided by one or more medical providers based on medical provider interactions with a patient monitoring interface.
- the instructions when executed by the one or more processors, may cause the one or more processors to: receive biometric data captured by one or more medical devices associated with one or more patients; provide, via the patient monitoring interface, one or more interactive displays including indications of the biometric data captured by the one or more medical devices associated with the one or more patients; receive an indication of one or more interactions, of one or more medical providers, with the one or more interactive displays provided by the patient monitoring interface; and analyze the one or more interactions, of the one or more medical providers, with the one or more interactive displays provided by the patient monitoring interface, in order to identify one or more services provided by the one or more medical providers.
- One or more medical devices configured to capture one or more types of biometric data associated with a patient may be positioned in an intensive care unit (ICU) environment with the patient, and a remote display device positioned external to the ICU environment may be configured to display, via a user interface, an indication of the health of the patient based on the captured biometric data.
- the indication of the health of the patient may include a graph mapping one or more normalized health statuses associated with the patient over time.
- Each normalized health status may be based on normalizing a particular type of the captured biometric data based on a medical protocol, such that each data point of the graph includes an indication of a normalized health status associated with the patient at a given time.
- the indication of the health of the patient may further include an animated three-dimensional model associated with the body of the patient, the animated three-dimensional model being dynamically updated to reflect biometric data associated with the patient captured at a time selected by a user.
- a remote display device positioned external to an intensive care unit (ICU) environment.
- the remote display device may be configured to display, via a user interface, an indication of the health of a patient positioned in the ICU environment based on biometric data captured by one or more medical devices positioned in the ICU environment.
- the indication may include a graph mapping one or more normalized health statuses associated with the patient over a period of time.
- Each normalized health status may be based on normalizing a particular type of the captured biometric data based on a medical protocol, such that each data point of the graph includes an indication of a normalized health status associated with the patient at a given time.
- a method for displaying an indication of health of a patient over time may include normalizing, by one or more processors, one or more types of biometric data associated with a patient based on a medical protocol to produce a normalized health status for each type of biometric data and generating, by the one or more processors, an indication of the health of the patient based on the biometric data.
- the indication may include a graph mapping one or more normalized health statuses associated with the patient over a period of time, such that each data point of the graph includes an indication of a normalized health status associated with the patient at a given time.
- the method may further include displaying, by the one or more processors, the generated indication of the health of the patient via a user interface display.
- a method for displaying an indication of health of a patient over time may include receiving, by one or more processors, one or more types of biometric data associated with a patient captured over a period of time and generating, by the one or more processors, an animated three- dimensional model associated with the body of the patient.
- One or more features of the animated three-dimensional model associated with the body of the patient may be dynamically updated as the one or more types of biometric data associated with the patient are change over the period of time.
- the method may further include displaying, by the one or more processors, the generated animated three-dimensional model associated with the body of the patient via a user interface display.
- a method for displaying an indication of health of a patient over time may include receiving, by one or more processors, one or more types of biometric data associated with a patient captured over a period of time; receiving, by the one or more processors, one or more text notes associated with the patient entered by a user over the period of time; storing, by the one or more processors, indications of times at which each of the one or more text notes were recorded; receiving, by the one or more processors, an indication of a term to be searched within the one or more text notes associated with the patient entered by the user; searching, by the one or more processors, the one or more text notes associated with the patient entered by the user for instances of the indicated term within the one or more text notes; displaying, by the one or more processors, an instance of the indicated term within the text notes via a user interface display; and displaying, by the one or more processors, a graphic based on the one or more types of biometric data associated with the patient captured
- a system for managing and controlling the process of weaning a patient from a ventilator may include ventilators positioned inside ventilator patient rooms, remote display devices associated with each ventilator positioned outside each ventilator patient room, and a computing device configured to analyze current patient information and current ventilator settings to determine metrics such as the current status of the ventilator patient, clinical recommendations regarding whether the ventilator patient is ready for weaning, clinical recommendations regarding timing and methodology of weaning steps likely to be successful for the ventilator patient, etc.
- the analysis may involve comparison to a ventilator weaning protocol and/or may involve the use of a predictive model.
- the computing device may provide the metrics (in some examples including graphics associated with the metrics) for display via the remote display devices positioned outside of the ventilator patient rooms.
- systems and methods for remotely monitoring medications administered to hospital patients are provided.
- Healthcare providers such as doctors and nurses, attending to various hospital patients in an intensive care unit (ICU) environment may log instances at which various medications or nutrients are administered to each patient, including indications of types of medications or nutrients, methods of delivery of medications or nutrients, dosages of medications or nutrients, etc.
- One or more medical devices configured to capture one or more types of biometric data associated with a patient may be positioned in an ICU environment with the patient, and a remote display device positioned external to the ICU environment may be configured to display, via a user interface, an indication of the health of the patient based on the logged medication or nutrient administration data and the captured biometric data.
- the indication of the health of the patient may include a graph mapping one or more indicators of biometric data associated with the patient over time, with instances of medication administration represented as icons on the graph at times of medication administration.
- an a medication administration icon may include an indication of the type of medication administered, and/or the method of delivery for the medication. When a user selects a given icon, additional information associated with the administration of medication represented by the icon may be displayed.
- One or more processors may receive one or more text notes associated with the patient entered by a user over the period of time, including indications of instances at which various medications or nutrients were administered to each patient, including indications of types of medications or nutrients, methods of delivery of medications or nutrients, dosages of medications or nutrients, etc., as well as indications of observations, diagnoses, etc., associated with the patient.
- the one or more processors may store indications of times at which each of the one or more text notes were recorded.
- the one or more processors may receive an indication of the name of a medication, to be searched within the one or more text notes associated with the patient entered by the user, and may search the one or more text notes associated with the patient entered by the user for instances of the indicated medication within the one or more text notes.
- the one or more processors may display an instance of the indicated medication within the text notes via a user interface display and may display a graphic based on the one or more types of biometric data associated with the patient captured at the time at which the text note containing the instance of the indicated medication was entered.
- the graphic may further include one or more icons associated with instances of administration of the indicated medication, i.e., overlaid upon the graphic based on the one or more types of biometric data associated with the patient captured at the time at which the text note containing the instance of the indicated medication was entered.
- One or more processors may access a database storing indications of instances (e.g., dates and/or times) at which various medications or nutrients were administered to each patient, including indications of types of medications or nutrients, methods of delivery of medications or nutrients, dosages of medications or nutrients, etc.
- the database may further store biometric data captured by medical devices positioned in the ICU environment with each patient.
- the one or more processors may receive indications of search criteria from a user, and may provide data from the database in response to the search criteria.
- a user may search by any criteria, such as a particular medication or nutrient, particular doses of a given medication, combinations of medications, combinations of medications and certain ranges of biometric data, etc., and the one or more processors may provide this data to the user to perform further analysis, in a manner consistent with privacy regulations in countries where patients are located.
- the one or more processors may perform statistical analysis of this data, again, in a manner consistent with privacy regulations in countries where patients are located.
- the one or more processors may access data from multiple patients in a manner consistent with privacy regulations in countries where patients are located and analyze the data in order to determine, e.g., the effectiveness of various medications, the effects various medications have on various biometric data, side effects associated with various medications, etc., for a large pool of patients.
- One or more medical devices configured to capture one or more types of biometric data associated with various patients may be positioned in an intensive care unit (ICU) environment with the patient and may store indications of the captured biometric data in a database.
- ICU intensive care unit
- a remote display device positioned external to the ICU environment may be configured to access the biometric data from the database.
- the remote display device may be further configured to access a database storing indications of instances of medications or nutrients administered to various patients.
- the remote display device may be configured to display, via a user interface, an indication of the health of a given patient based on the captured biometric data and the medication administration data.
- One or more processors of the remote display device may receive an indication, from a user, of a newly selected patient from a listing of possible patients, and may switch to display an indication of the biometric and medication administration data for the newly selected patient based on captured biometric data and accessed medication administration data associated with the newly selected patient. Prior to switching the display, the one or more processors may locally cache the biometric data, medication data, etc., associated with the original patient, as well as a display state for the particular biometric data associated with the original patient being viewed by a user.
- the indication of the display state may include an indication of biometric data of interest being viewed by the user, medication data of interest being viewed by the user, time ranges being viewed by the user, etc., for the biometric and medication administration data associated with the original patient.
- the one or more processors of the remote display device may subsequently receive an indication, from the user, of the original patient, and may accessed the cached data and cached display state in order to again generate and display an indication of the biometric and medication administration data for the original patient.
- FIG. 1 illustrates a block diagram of an example system for remotely monitoring patients in an intensive care unit (ICU) environment, including managing and controlling the process of weaning a patient from a ventilator.
- ICU intensive care unit
- FIGS. 1A-1 H, 1J-1 N, and 1 P-1 Z, and FIGS. 2A-2N illustrate example user interface display screens that may be displayed via a remote display device used for remotely monitoring patients in an intensive care unit (ICU) environment, in accordance with some examples.
- ICU intensive care unit
- FIG. 2P illustrates a schematic diagram of variables that may be used in developing a predictive model for ventilator weaning.
- FIG. 3 illustrates a flow diagram of an example method of managing and controlling the process of weaning a patient from a ventilator based on a ventilator weaning protocol.
- FIG. 4 illustrates a flow diagram of an example method of managing and controlling the process of weaning a patient from a ventilator using a predictive model for ventilator weaning.
- FIG. 5 illustrates a flow diagram of an example method for identifying services provided by one or more medical providers based on medical provider interactions with a patient monitoring interface.
- the present disclosure provides a software and hardware platform that allows healthcare providers to easily access and interact with biometric data from multiple medical devices attached to a patient in the intensive care unit (ICU), and subsequently identifies services provided by one or more medical providers based on medical provider interactions with the platform.
- ICU intensive care unit
- the platform aggregates readings and settings across a wide array of equipment such as ventilators, pulse oximeters, and other bedside monitors, and displays them on a single screen in real time through an application.
- These screens can be implemented via remote display devices, including tablets or other mobile computing devices that can be mounted outside of each patient’s room in the ICU or at other appropriately secure locations (such as a nurses’ station), or almost anywhere, subject to security protocols - or personal computers or smart phones.
- this platform provides a window into the ICU from a safe distance outside - thus minimizing the need for health care personnel to physically enter the ICU for monitoring and recording data from the bedside monitors and ventilators.
- this platform allows providers to send customized instructions to ICU teams for display on the aforementioned tablets via a secure messaging channel.
- the mobile access feature is compatible with PCs, tablets and all smart devices.
- this platform may be implemented via these existing bedside monitors and ventilators that have either been integrated with EMR systems or have published APIs which allow for real-time data capture, storage and display.
- this platform may be integrated into older generations of bedside monitors and ventilators, i.e. , makes and models that do not readily support real-time data transmission.
- the data from such machines will be captured through a combination of methods including screen capture and available interfaces such as Recommended Standard 232 (RS-232).
- RS-232 Recommended Standard 232
- These devices will also need to be connectivity enabled, e.g., via an Ethernet cable or via Wi-Fi.
- MFA multi-factor authentication
- the present disclosure provides a ventilator weaning platform that aids in clinical decision support through remote monitoring of ventilator settings and real time analysis of patient data with a focus on weaning from ventilation.
- the key thrust is reducing ventilator associated events (VAE) by weaning patients from mechanical ventilation in the most efficient and optimized manner.
- VAE ventilator associated events
- a ventilator weaning platform accomplishes remote monitoring of ventilator settings via a screen that displays real time ventilator settings outside of each patient’s room.
- EMR electronic medical record
- EMR electronic medical record
- PEEP Positive End Respiratory Pressure
- Tidal Volume Respiratory Rate
- Respiratory Rate Peak Inspiratory Flow
- Pressure Support Peak Inspiratory Flor Rate
- Low Minute Ventilation Alarm Limit High Pressure Alarm Limit
- High Respiratory Rate Alarm Limit High Respiratory Rate Alarm Limit
- Low Tidal Volume Alarm Limit Analysis of this data can be used to update and customize automated ventilator protocols and thereby reduce the duration of mechanical ventilation.
- patient data (physical, medications, radiology, underlying disease conditions, etc.) along with ventilator settings may stream to the cloud, analysis may be performed, and data may streamed back to the displays outside of each patient’s room and/or made available remotely to the clinical team.
- the power of this analysis is that the ventilator weaning platform will have access to data from many patients and will compare similar patients in its database to the exact patient in each room.
- the ventilator platform aggregates data, performs a unique analysis/prediction and places that information in the hands of the care team, who will then make actual decisions regarding the ventilator (e.g., changing ventilator settings, initiating a spontaneous breathing trial, extubating, etc.).
- a monitor outside of each patient room may display ventilator settings as well as a visual system (red/yellow/green background) highlighting each patient’s trajectory on the ventilator as they progress in the ventilator weaning process.
- the ventilator weaning platform may include a clinical guidance tool rooted in this analysis and driven by protocol.
- the remote display device may also recommend/remind the treating healthcare professional (or team of healthcare professionals) of the need (when appropriate) for a spontaneous breathing trial (SBT).
- SBT spontaneous breathing trial
- the ventilator weaning platform makes ventilator information (including, e.g., ventilator settings information, recommendations, etc.) displayed on the screens of remote display device easily available to the clinical team on their phones and computers at any time and in any location.
- ventilator information including, e.g., ventilator settings information, recommendations, etc.
- the ventilator weaning platform uses this ventilator weaning platform, senior intensivists will minimize their chances of contracting COVID-19, efficiently guiding junior physicians and other members of the clinical team through ventilator management. Perhaps more importantly, one skilled intensivist will be able to monitor many ventilated patients simultaneously.
- the remote display device will act not only as a guidance tool for mechanical ventilation, but will serve as an easy to interpret communications tool for patient status (e.g., preparing to wean, weaning, ready to extubate).
- senior critical care physicians are not required to enter each patient’s room to evaluate ventilator settings as they can simply walk through the ICU hallways and view settings outside of each patient’s room.
- the use of PPE is minimized as each member of the clinical team is not required to don protective equipment to perform ventilator setting checks.
- the ventilator weaning platform may be agnostic to the EMR system (e.g., Epic, Cerner) as well as the equipment being used in the ICU.
- EMR system e.g., Epic, Cerner
- ventilator weaning platform all hospital systems may benefit from the analysis provided by the ventilator weaning platform, not just hospitals contracted to a particular vendor. For instance, eICU software that is only able to communicate with other certain vendors can underserve both patients and critical care teams. Moreover, the ventilator weaning platform will reinforce best practices/outcomes in one ICU and share with others; conversely, practices with less favorable outcomes will be highlighted for physician review.
- the analysis performed by the ventilator weaning platform involves accessing protected health information (PHI) from patients’ EMR.
- PHI protected health information
- the ventilator weaning platform employs best-in-class methods to ensure that that patient information, privacy, integrity and confidentiality data remain secure at all times.
- accessing PHI must incorporate the following security policies and procedures: authorization, authentication, availability, confidentiality, data integrity, and nonrepudiation (transaction records).
- physical safeguards may include: use of encrypted storage or devices, restricting access to authorized personnel only, reserving copies and conducting data backups, maintaining emergency contingency protocols, and disposing outdated devices and data sources properly.
- each remote display device may require an authentication process that links it with a given patient in a given room.
- disposable smart card that is unique to each patient may be inserted in each remote display device.
- the smart card may be programmed by hospital IT for each unique patient and, after insertion in each remote display device, the ventilator weaning platform will automatically authenticate the card with the patient’s EMR and synchronize with the cloud.
- FIG. 1 illustrates a block diagram of an example system 100 for remotely monitoring patients in an intensive care unit (ICU) environment, including managing and controlling the process of weaning patients from ventilators.
- the system 100 includes one or more medical devices 102 positioned within an ICU environment 103 and configured to capture biometric data associated with patients in the ICU environment.
- the medical devices 102 may include ventilators, arterial catheters, external pressure cuffs, pulse oximeters, electrocardiograms, pulmonary artery (PA) catheters, other bedside monitors, and any other suitable devices configured to capture biometric data associated with patients.
- PA pulmonary artery
- one or more of the medical devices 102 may be configured to capture data related to identifying services provided to patients by medical providers.
- one or more of the medical devices 102 may capture data indicating amounts of time medical providers spend setting up the one or more medical devices 102, training patients or other medical providers to use the one or more medical devices 102, using the one or more medical devices 102 to monitor patients and/or provide services to patients, etc. Furthermore, in some examples, one or more medical devices 102 may store an indication of one or more particular medical billing codes associated with the use of the medical devices 102.
- a heart monitor medical device may store an indication of a single medical billing code associated with the use of the heart monitor generally, or a first medical billing code associated with setting up the heart monitor, a second medical billing code associated with training patients or other medical providers to use the heart monitor, a third medical billing code associated with using the heart rate monitor to monitor patients and/or provide services to patients, etc., and may associate the captured data with a respective medical billing code accordingly.
- Other types of medical devices may store indications of different medical billing codes associated with the use of those devices, that may be different than the heart monitor medical billing codes, and may associate their captured data with those medical billing codes.
- one or more of the medical devices 102 may further analyze this data to identify services provided to patients by the medical providers that should be billed using a given medical billing code and/or to determine amounts of time associated with the services provided to the patients by the medical providers.
- biometric data associated with patients may include one or more of: admission weight, admit type, age, blood pressure (e.g., arterial diastolic, arterial mean, arterial systolic), arterial CO2 pressure, arterial 02 pressure, creatinine, ethnicity, gender, Glasgow coma scale, height, hematocrit, inspired 02 fraction, mean airway pressure, 02 flow, oxygen saturation of blood, oxygen saturation pulseoxymetry, peak inspiration pressure, PEEP set, PH (arterial), plateau pressure, potassium, sodium, tidal volume, urine output, ventilator mode, white blood cell count, heart rate, respiratory rate, central venous pressure, right atrial pressure, PA pressure, cardiac output, and any other captured or recorded biometric data associated with patients in the ICU environment.
- the system 100 may store current and/or historical biometric data and/or data related to identifying services provided to patients by medical providers captured by the medical devices 102, as well as data associated with patients associated with
- the system 100 may further include one or more remote display devices 104 configured to graphically display indications of the health of the patients based on data associated with the patients captured by the medical devices 102.
- the example system 100 may include a computing device 106.
- the medical devices 102 and/or the remote display devices 104 may communicate with the computing device 106 via a network 108. Additionally, the medical devices 102, remote display devices 104, and/or the computing device 106 may further communicate with one or more healthcare computing devices 110 via the network 108.
- Each of the remote display devices 104 may include a user interface 111 (also referred to as a “patient monitoring interface” herein) configured to present information to users and/or receive various inputs from users.
- the user interface 111 may provide information related to patient to users, who may be medical providers (also referred to as “healthcare providers” herein), and may capture indications of the medical providers’ interactions with the patient monitoring interface, such as indications of which medical provider is accessing the patient monitoring interface, which display screens are accessed or viewed by the medical provider, and the patients associated with each display screen, as well as input provided by the medical provider, including cursor clicks or cursor hovering events, or typing/keystrokes that occur while the medical provider is accessing the patient monitoring interface.
- medical providers also referred to as “healthcare providers” herein
- the user interfaces 111 of the remote display devices 104 may be configured to receive input from users, including healthcare providers, which may include, for instance, input indicating which medications (or food or water or other nutrients) are administered to patients, a manner in which the medications are administered to patients (e.g., via a pill, IV drip, ampoule, etc.) and dates and times at which these medications (or food or water or other nutrients) are administered.
- This data may be stored in the database 123.
- each remote display device 104 may be configured to graphically display indications of the health of the patients based on the biometric data associated with the patients captured by the medical devices 102 via a respective user interface 111.
- displaying the indications of the health of patients via the respective user interfaces 111 may include displaying indications of dates and times at which various medications (or food or water or other nutrients) were administered to patients, and indications of a manner in which the medications are administered to patients (e.g., via a pill, IV drip, ampoule, etc.), e.g., alongside or overlaid upon displayed indications of biometric data associated with patients captured by the medical devices 102.
- each remote display device 104 may be configured to graphically display indications of the health of a particular patient (i.e. , based on data captured by a particular medical device 102 or particular set of medical devices 102, and/or based on data from the database 123 provided by a particular healthcare professional associated with the particular patient, e.g., including indications of which medications (or food or water or other nutrients) were administered to the patient, a manner in which the medications were administered to the patient (e.g., via a pill, IV drip, ampoule, etc.), and dates and/or times at which medications (or food or water or other nutrients) were administered to the patient, while in other examples, each remote display device 104 may be configured to graphically display indications of the health of multiple patients, based on data captured by multiple medical devices 102 associated with various patients and/or based on data from the database 123 provided by healthcare professionals associated with the various patients, e.g., including indications of medications (or food or water or other nutrients) administered to
- one or more remote display devices 104 may be positioned directly outside of rooms associated with particular patients, and each remote display device may be configured to display data associated with each respective patient. Additionally, in some examples, the remote display devices 104 may be positioned together in a room designed for patient monitoring by healthcare professionals. Moreover, in some examples, the remote display devices 104 may include mobile devices, such as laptops, smart watches, smart phones, tablets, etc., i.e. , so that healthcare professionals may monitor patients from any location. In any case, each remote display device 104 may be positioned outside of the ICU environment 103 so that healthcare professionals can monitor patients without being exposed to diseases that may be present in the ICU environment 103.
- the remote display devices 104 may be password protected, or may be authenticated by registered users using a security card 112. For instance, a remote display device 104 for a particular patient may be configured to remain in a locked mode unless a security card 112 associated with a healthcare professional for the patient is used to access the remote display device 104.
- the computing device 106 may include a processor 114, such as one or more microprocessors, controllers, and/or any other suitable type of processor, and a memory 116 (e.g., volatile memory or non-volatile memory) accessible by the one or more processors 114 (e.g., via a memory controller).
- the one or more processors 114 may interact with the memory 116 to obtain, for example, computer-readable instructions stored in the memory 114 for executing a graphical display application 117, a control application 118, a medical provider service identification application 119, a ventilator weaning predictive model 120 and/or a ventilator weaning predictive model training application 122.
- the computer-readable instructions stored on the memory 114 may include instructions for carrying out any of the steps of the method 300 described in greater detail below with respect to FIG. 3, the method 400 described in greater detail below with respect to FIG. 4, and/or the method 500 described in greater detail below with respect to FIG. 5.
- Executing the graphical display application 117 and the control application 118 may include receiving various data, including patient biometric data, indications of medicine or other nutrients provided to the patient, which data may be provided from an administration device automatically or manually by healthcare professionals, e.g., including via notes related to various patient conditions, and/or manually entered indications of medications (or food or water or other nutrients) administered to the patient and dates and/or times at which medications were administered to the patient, other patient data (e.g., EMR data) and medical device settings data, including ventilator settings data, directly from the medical devices 102 or from the database 123 storing current and/or historical data captured by the medical devices 102 and/or current and/or historical data provided by healthcare professionals associated with the various patients, remote display devices 104, and/or healthcare computing device 110, and may analyze this data to generate graphics and/or information to be displayed via the remote display devices 104, i.e., via the user interfaces 111 of the remote display devices 104.
- patient data e.g., EMR data
- executing the medical provider service identification application 119 may include identifying services provided to patients by medical providers.
- the medical provider service identification application 119 may identify services provided to patients by medical providers based at least in part on data captured by one or more of the medical devices 102. For instance, one or more of the medical devices 102 may capture data indicating amounts of time medical providers spend setting up the one or more medical devices 102, training patients or other medical providers to use the one or more medical devices 102, using the one or more medical devices 102 to monitor patients and/or provide services to patients, etc., and the medical provider service identification application 119 may identify services provided to patients by medical providers based on this data received from the medical devices 102. Additionally, in some examples, the medical provider service identification application 119 may receive indications of medical billing codes associated with this captured data from one or more of the medical devices 102.
- These medical billing codes may be associated with each respective type of medical device 102 generally (e.g., one billing code for the use of a heart monitor, another billing code for the use of a ventilator, etc.), or may be associated with specific services associated with the one or more medical devices 102. Moreover, in some examples, one or more of the medical devices 102 may further analyze this data to identify services provided to patients by the medical providers and/or to determine amounts of time associated with the services provided to the patients by the medical providers, and the medical provider service identification application 119 may receive indications of particular services identified by the medical devices 102.
- the medical provider service identification application 119 may identify services provided to patients by medical providers based on the medical providers’ interactions with the user interface 111 (i.e., the patient monitoring interface). For instance, the medical provider service identification application 119 may generate and store (e.g., in a database) user logs including, e.g., particular user interface display screens (discussed further below at FIGS. 1 A-1 H, 1 J-1 N, and 1 P-1 Z, and FIGS. 2A- 2N) accessed by medical providers via the patient monitoring interface, the medical providers’ interactions with and input provided to the patient monitoring interface, the amount of time the medical providers spend providing input to and/or otherwise interacting with various screens of the patient monitoring interface, etc.
- user logs including, e.g., particular user interface display screens (discussed further below at FIGS. 1 A-1 H, 1 J-1 N, and 1 P-1 Z, and FIGS. 2A- 2N) accessed by medical providers via the patient monitoring interface, the medical providers’ interactions with and input provided to the patient monitoring interface,
- the medical provider service identification application 119 may identify services that various medical providers provide to various patients (e.g., including services that multiple medical providers provide to the same patient).
- the services provided may include medical procedures, the administration of medications, the analysis of diagnostic results, etc.
- the medical provider service identification application 119 may also identify services that various medical providers provide to various patients based on input from the medical providers indicating specific services provided to the various patients. For instance, in some examples, as shown at FIGS. 2J, 2K, and 2L, the medical provider service identification application 119 may detect inactivity with respect to the user interface 111 and may prompt the medical provider, via the user interface 111 , to provide indications of services provided while the medical provider was not interacting with the user interface 111 , and amounts of time associated with those services (e.g., manually or via a drop-down menu).
- the medical provider service identification application 119 may further identify patients associated with the services provided, as well as medical providers associated with the services provided. In some examples, the medical provider service identification application 119 may determine a particular medical provider, or multiple medical providers, associated with the service provided to a given patient. For instance, the medical provider service identification application 119 may prompt a medical provider accessing the patient monitoring interface to log in or otherwise provide identification or credentials.
- the medical provider service identification application may determine a category, level, or rank associated with the medical service provider (e.g., a job title indicating seniority, a type of medical service provider such as a doctor, nurse, or physician assistant, a specialty of the medical service provider such as surgery, internal medicine, gynecology, oncology, dermatology, radiology, cardiology, etc.).
- a category, level, or rank associated with the medical service provider e.g., a job title indicating seniority, a type of medical service provider such as a doctor, nurse, or physician assistant, a specialty of the medical service provider such as surgery, internal medicine, gynecology, oncology, dermatology, radiology, cardiology, etc.
- the medical provider service identification application 119 may in turn generate a medical bill based on the service provided, the medical provider(s) that provided the service (i.e. , a particular medical service provider, or a particular category/level/rank of medical provider, or a particular specialty of medical provider, etc.), the patient to whom the service was provided, an amount of time associated with the service provided, an amount of time during which multiple providers provided one or more services to the patient, a billing code associated with the use of a particular medical device 102, etc.
- the medical provider(s) that provided the service i.e. , a particular medical service provider, or a particular category/level/rank of medical provider, or a particular specialty of medical provider, etc.
- the medical provider service identification application 119 may prompt the medical provider to confirm any identified services provided and amounts of time associated with those services, prior to generating a medical bill based on the services provided, e.g., as shown with respect to FIGS. 2M and 2N. Moreover, in some embodiments, the medical provider service identification application 119 may provide indications of amounts of time associated with each of the services provided to other internal or external applications. For example, the amounts of time associated with each of the services provided may be provided to an auditing service, an insurance provider, centers for Medicare & Medicaid services (CMS), etc.
- CMS Medicare & Medicaid services
- FIGS. 1A-1 H, 1J-1 N, and 1 P-1Z, and FIGS. 2A-2N illustrate example user interface display screens that may be displayed via user interfaces 111 of remote display devices 104 used for remotely monitoring patients in an intensive care unit (ICU) environment, in accordance with some examples.
- the user interface 111 may receive selections from a user of one or more types of biometric data to be displayed, and may accordingly display the selected types of biometric data over time in one or more graphs presented within a single screen by a user interface 111. For instance, as shown in FIGS.
- the user interface 111 may receive selections from users regarding which types of biometric data are displayed in each graph, and may modify the display based on the selections.
- the medical provider service identification application 119 may identify the medical service provided based on the medical provider’s selection of particular types of biometric data, including past biometric data and current biometric data for various patients. For instance, particular types of biometric data may be associated with particular medical services provided to patients.
- FIGS. 1 E-1 M illustrate various example graphs reflecting various types of biometric data over time within a single display screen.
- executing the medical provider service identification application 119 may include receiving, from authorized users (such as hospital administrators, supervisors, etc.), inputs including indications of medical providers to be added or removed from the system, or indications of medical provider information (such as, e.g., license information) to be updated within the system 100, and subsequently adding, removing, and/or updating the medical provider information within the system 100.
- authorized users such as hospital administrators, supervisors, etc.
- inputs including indications of medical providers to be added or removed from the system, or indications of medical provider information (such as, e.g., license information) to be updated within the system 100, and subsequently adding, removing, and/or updating the medical provider information within the system 100.
- executing the medical provider service identification application 119 may include receiving, from authorized users (such as hospital administrators, supervisors, etc.), inputs including indications of devices (such as, e.g., devices 102, 104, 110, etc.) to be added or removed from the system, or indications of information (e.g., status information) associated with devices (such as, e.g., devices 102, 104, 110, etc.) to be updated within the system 100, and subsequently adding, removing, and/or updating the devices within the system 100.
- authorized users such as hospital administrators, supervisors, etc.
- inputs including indications of devices (such as, e.g., devices 102, 104, 110, etc.) to be added or removed from the system, or indications of information (e.g., status information) associated with devices (such as, e.g., devices 102, 104, 110, etc.) to be updated within the system 100, and subsequently adding, removing, and/or updating the devices within the system 100.
- executing the medical provider service identification application 119 may include receiving, from authorized users (such as hospital administrators, supervisors, etc.), inputs including indications of drugs or medications to be added or removed from the system, or indications of information associated with drugs or medications to be updated within the system 100, and subsequently adding, removing, and/or updating the drug or medication information within the system 100.
- executing the medical provider service identification application 119 may include providing, to authorized users (such as hospital administrators, supervisors, etc.), reports including, e.g., identified services provided to patients by the medical providers, patients associated with the services provided, and/or medical providers associated with the services provided, as well as any generated medical bills.
- the graphical display application 117 may generate display items (e.g., graphs, three-dimensional animations, scalars, etc.) to be displayed by the user interfaces 111 of the remote display devices 104 that are color coded, generally on a two- sided spectrum - meaning that the “good” range will be in the middle as shown by green, and as the values go either above or below the normal range, the displays will move from green to yellow to orange to red.
- the graphical display application 117 may color code the display items according to a pre-defined protocol.
- the graphical display application 117 may be configured to operate using various pre-defined protocols, and may receive a selection of one of the pre-defined protocols from a particular hospital or healthcare professional. Additionally, in some examples, the graphical display application 117 may define a new protocol based on selections from a user.
- the graphical display application 117 may normalize the biometric data such that each data point for each type of biometric data is sorted into one of several health status categories (e.g., a “normal” or “good” health status, several intermediate health statuses, a “bad” or “alarm” health status, etc.) based on a medical protocol. For instance, biometric heart rate data within a certain range of heart rates may be associated with a normal or good health status, while biometric heart rate data outside of that range may associated with an intermediate health status, and biometric heart rate data above or below certain threshold values may be associated with a bad or alarm health status.
- a “normal” or “good” health status e.g., a “normal” or “good” health status, several intermediate health statuses, a “bad” or “alarm” health status, etc.
- biometric heart rate data within a certain range of heart rates may be associated with a normal or good health status
- biometric heart rate data outside of that range may associated with an intermediate health status
- the graphical display application 117 may generate a single graph to display the various different types of normalized biometric data over time. For instance, the graphical display application 117 may generate a graph that includes a time axis and another axis that utilizes “lanes” for various health statuses (e.g., normal or good health status in a center lane, intermediate health statuses in bordering lanes above and below the center lane, and bad or alarm health statuses in highest and lowest lanes).
- various health statuses e.g., normal or good health status in a center lane, intermediate health statuses in bordering lanes above and below the center lane, and bad or alarm health statuses in highest and lowest lanes.
- the graphical display application 117 may color-code the graphs based on the health status associated with each data point (e.g., with normal or good health status data points being shown in green, intermediate health status data points being shown in yellow or orange, bad or alarm health status data points being shown in red, etc.).
- the user interface 111 may receive a selection by a user of a specific date and/or time, and may accordingly display graphs reflecting biometric data captured at the selected date or time (or within a certain range of the selected date or time). That is, in a “normal” mode of operation, the user interface 111 may be configured to display moving wave forms of selected streaming biometrics at a current time. For instance, the user interface 111 may display current values of the selected biometrics and wave forms for a period of time in the past. The user interface 111 may receive user selections of a time, as shown in FIG. 1 N, and may modify the displayed time span accordingly.
- the user interface 111 may receive haptic user input, such as “pinching in” and “pinching out,” i.e. , similar to a GPS or map screen, and may modify the displayed time span based on this user input, e.g., by zooming out or zooming in.
- haptic user input such as “pinching in” and “pinching out,” i.e. , similar to a GPS or map screen
- the user interface 111 may be configured to do an “instant replay,” in response to a user selection or command, by moving the vertical time line to any time slice in the past, and allowing it to go forward - either real time or a time-compressed fast-forward mode.
- the user interface 111 may be configured to receive user input in the form of “swipe-left” or “swipe-right” input, and may modify the display to show different data.
- the medical provider service identification application 119 may identify the medical service provided based on these various user inputs with the user interface 111. For instance, the medical provider interacting with a particular display screen containing certain types of medical data associated with a particular patient for a period of time may indicate that the medical provider is providing a service to that patient related to the medical data being accessed, and may indicate an amount of time that the medical provider has spent providing the service to the patient.
- the user interface 111 may display searchable nurse’s notes that allow custom search input and word-based analysis and textmining beyond simple word look-ups. Moreover, in some examples, the user interface 111 may be configured to display a side toolbar displaying specific scalar values and indexes (e.g. BMI, diabetes indicators, etc.) to ensure that all co-morbidities are displayed. That is, as shown in FIG.
- the graphical display application 117 may receive text notes as user input (e.g., from an attending healthcare professional, such as a doctor or a nurse, via the user interface 111) regarding the patient’s health status at various times, and may store these notes including an indication of the time at which they are recorded.
- the graphical display application 117 may then subsequently receive user input including search terms, and may locate instances of the term in historical notes and times at which the historical notes were recorded.
- the graphical display application 117 may then cause the user interface 111 to display indications of times at which notes related to a given term were recorded, so that other users (or the same user) can easily search for terms within the notes and see an indication of a time at which notes related to a certain term were recorded.
- the graphical display application 117 may store these notes in the database 123 along with the medical device data.
- the graphical display application 117 may cause these notes to be displayed simultaneously with the graphs discussed above on a single screen via the user interface 111 so that a user can see biometric data recorded at the time of any given note.
- the graphical display application 117 may locate instances in which the term appears within the text notes, along with times associated with each instance, and may cause the user interface 111 to display the instances and associated times. For instance, the user interface 111 may display the text notes in which the term appears and may highlight the term within notes in which it appears, e.g., as shown at FIGS. 1 P-1 U.
- the user interface 111 may receive a selection, from a user, of a particular instance where the term appears within the text notes, and the graphical display application 117 may cause the user interface 111 to display graphs of biometric data as recorded at the time (or within a range of times) associated with the selected instance of the term based on the selection, e.g., as shown at FIG. 1 V. For instance, as shown in FIG.
- the graphical display application 117 may cause the user interface 111 to display one or more graphs of biometric data recorded at 6:57 AM on 8/23 (or from a range of times around 6:57 AM on 8/23, etc.) For example, as shown in FIG. 1 V, the graphical display application 117 may cause the user interface to display a graph of the patient’s respiratory rate, 02 saturation pulseoxymetry, pH (arterial), and heart rate at 6:57 AM on 8/23, when the selected term was noted.
- the graphical display application 117 may cause the user interface to highlight or otherwise identify the exact time and date associated with the selected term within the graphs of the biometric data (e.g., using a vertical line as shown in FIG. 1 V).
- these features help users to visually connect various noted conditions or observations to graphs displaying biometric data from times at which the conditions were noted. Additionally, these features allow for a smoother transfer of knowledge/information across healthcare professionals’ shift changes, because a healthcare professional in a later shift can easily identify which patient conditions were noted by healthcare professionals in earlier shifts, and can the patient’s biometric data from past times when these conditions were noted. Furthermore, these features allow healthcare professionals to easily identify patterns, trends, or anomalies in patient conditions and biometric data across multiple shift changes.
- the medical provider service identification application 119 may identify the medical service provided based on notes entered by the medical provider related to a particular patient, or based on notes searched by the medical provider, or an amount of time the medical provider spends entering or searching the notes.
- the textual content of the notes may indicate a particular service provided (e.g., “appendectomy”), or may be associated with a particular medical service provided (e.g., a mention of “x-rays” may indicate that the medical provider is providing a diagnostic service).
- the graphical display application 117 may cause the user interface 111 to display three-dimensional models of a patient’s organs, e.g., including the heart and lungs of the patient, alongside the one or more graphs as discussed above with respect to FIGS. 1 A-1 H and 1 J-1 N.
- the graphical display application 117 may generate the three-dimensional models of the patient’s organs such that the models, as displayed by the user interface 111 , are dynamically animated to reflect biometric data associated with the patient.
- the graphical display application 117 may generate a three-dimensional model of the patient’s heart that is animated to reflect the patient’s actual heart rate based on biometric data captured by ICU medical devices (i.e. , at a current time or at a past time selected by a user of the remote display device).
- the graphical display application 117 may generate a three- dimensional model of the patient’s lungs that are animated to reflect the patient’s actual respiratory rate based on biometric data captured by ICU medical devices (i.e., at a current time or at a past time selected by a user of the remote display device).
- the user interface 111 may display these three-dimensional models simultaneously with graphs reflecting the biometric data associated with the patient over time.
- the graphical display application 117 may generate three-dimensional models that are animated to reflect a patient’s breathing rate and heart rate relative to the actual biometric values present on the graphs. Additionally, the graphical display application 117 may color-code the three-dimensional models of the patient’s body areas to match the normalized values of the raw biometric readings shown in the graphs.
- the graphical display application 117 may generate a three-dimensional animation of the patient’s heart (or a relevant portion of the patient’s heart) that is shown in green when normalized biometric data associated with the patient’s heart (or associated with the relevant portion of the patient’s heart) is in a “good” range, and shown in red when normalized biometric data associated with the patient’s heart (or associated with the relevant portion of the patient’s heart) is in a “bad” or “alarm” range. Accordingly, as displayed by the user interface 111 , as the data shown in the graphs changes, the model animations and colors will continuously match the changing biometric values.
- the graphical display application 117 may animate the three-dimensional models of the user’s body areas displayed by the user interface 111 to reflect the patient’s biometric data as captured at the selected time or over the selected time period.
- the medical provider service identification application 119 may identify the medical service provided based on the medical provider viewing or otherwise interacting with the three-dimensional models of a patient’s organs. As an example, the medical provider service identification application 119 may identify that the medical provider is performing a medical procedure related to a particular organ based on the medical provider’s input related to the three- dimensional model of that organ.
- the user interface 111 may display a three-dimensional model note-taking view for use by healthcare professionals. That is, based on input from the user, the user interface 111 may dynamically update the three-dimensional display to move around a three-dimensional model of the patient’s body. The user interface 111 may further receive user input indicating specific bones, muscles and organs, from the displayed three-dimensional model associated with issues related to the patient.
- the user interface 111 may receive “tags” or otherwise notes (written and/or voice) associated with specific points within the three-dimensional model of the patient’s body, and the graphical display application 117 may store the tags or notes in a database (e.g., database 123) so that other healthcare professionals associated with the patient can easily review all notes (written or voiced) associated with the patient's body in a three- dimensional view.
- the graphical display application 117 may cause the user interface 111 to rotate the three-dimensional model of the patient’s body along any axis and any angle based on input from the user, and may receive notes from the user based on user input selecting different body regions within the three-dimensional model of the patient’s body.
- the graphical display application 117 may add these text-based notes to the database, including an indication of the tagged point on the patient’s body, along with the perceived three-dimensional view of the creator of the note. Accordingly, the graphical display application 117 may cause the user interface 111 to display the tagged three- dimensional location in a three-dimensional immersive view when the user interface 111 receives a subsequent user’s selection of the same note. Furthermore, as discussed above, in some examples, the medical provider service identification application 119 may identify the medical service provided based on notes entered by the medical provider related to a particular patient, or based on notes searched by the medical provider, or an amount of time the medical provider spends entering or searching the notes.
- the user interface 111 may display radiology imaging (i.e. , in addition to graphs and/or three-dimensional models of the patient’s body).
- Various images may be captured from various radiology imaging devices (e.g., X-Ray, sonogram, CT scan, etc.).
- a hospital’s radiology department may send these radiology images to an online database (e.g., database 123) accessible by the remote display device, which can show multiple radiology images simultaneously, including in a grid, for maximum understanding of the radiology results.
- the graphical display application 117 may cause the user interface 111 to display a three- dimensional animated “tour” of image-series data (e.g.
- the user interface 111 may receive “tags” or other to tag written or voiced notes for specific regions within the image-series data (i.e., in a similar manner as discussed above with respect to the three-dimensional model of the patient’s body).
- the graphical display application 117 may cause the user interface 111 to display a specific region within the image-series data associated with a particular tag or note when the user interface 111 receives a selection of the particular tag or note from a subsequent user.
- the medical provider service identification application 119 may identify the medical service provided based on the medical provider’s interaction with the radiology images via the user interface 111.
- the user interface may display indications of medications (or food or water or other nutrients) administered to the patient, and dates/times at which medications (or food or water or other nutrients) are administered to the patient.
- the graphical display application 117 may receive data indicating input from healthcare professionals, e.g., by accessing such data in the database 123, indicating which medications, food, water, vitamins, etc. (collectively referred to as “medications” herein) are administered to each patient, the dosages of the medications, the manner in which the medications are delivered or administered to each patient, and dates/times at which these medications are administered to the patient.
- the data indicating the input from healthcare professionals may further include additional information such as dates/times at which the input from the healthcare professionals is logged by the healthcare professional, as well as indications of which medications, dosages, methods of delivery and dates and times of administrations are ordered (i.e., as opposed to which medications, dosages, methods of delivery, and dates and times of administrations are actually implemented).
- the medical provider service identification application 119 may identify the medical service provided based on input provided by the medical provider regarding the administration of various medications. For instance, the medical provider service identification application 119 may identify that a particular medical provider has administered a particular medication to a patient based on the medical provider’s input of a particular medication via the user interface 111.
- the graphical display application 117 may generate an icon 201 indicating the method of delivery (e.g., an ampoule, a bolus, a shot, a pill, an IV drip, etc.) of the medication and the date and/or time of administration. That is, a pill icon may be different from an ampoule icon, which may be different from an IV icon, which may be different from a syringe icon, which may be different from a food icon, which may be different from a water icon, which may be different from a vitamin icon, etc.
- the icon 201 may further include an indication of a generalized type of medication (e.g., antibiotic, pain reliever, mood stabilizer, etc.).
- the graphical display application 117 may cause the user interface
- I I I to display the icon 201 (or set of icons 201) indicating the method of delivery and/or generalized type of medication at a location in a graph that indicates the date or time at which the medication was administered.
- the icon 201 may be depicted in a single instance at the time of delivery or administration, while for medications delivered or administered over a period of time, such as
- the graphical display application 117 may generate two icons 201 (i.e., an icon 201 associated with the start time for the medication and an icon 201 associated with the end time for the medication) connected, e.g., by a line.
- the graphical display application 117 may cause the user interface 111 to display the icon 201 (or set of icons 201) indicating the method of delivery of a medication overlaid upon a graph displaying biometric data associated with the patient, i.e., such that it is possible for users to easily see biometric data associated with the patient at the time that the medication is administered, and how the biometric data associated with the patient changes over time after the medication is administered.
- the graphical display application 117 may cause the user interface 111 to display detailed information associated with the administration of a medication based on a user selection or hover over an icon 201 (or set of icons 201 ) on one of the biometric graphs. That is, the graphical display application 117 access data related to medications administered for each patient stored in the database 123, and may may cause the user interface 111 to display detailed information associated with an administration of medication represented by a selected icon 201 , For instance, as shown at FIG. 2A, the detailed information associated with a selected icon 201 indicates that the selected icon 201 corresponds to the administration of a med bolus of Fentanyl 25 mcg.
- the graphical display application 117 may cause the user interface 111 to display detailed information associated with a selected icon 201 , indicating that the selected icon 201 corresponds to the administration of a non-IV prophylaxis of one dose of Lansoprazole.
- the graphical display application 117 may access, from the database 123, data indicating one or more of the following: a date and/or time at which the medication was ordered for the patient, a date and/or time at which the medication was administered (i.e. , as indicated by the administering healthcare professional), and a date and/or time at which the data was entered (i.e., by the administering healthcare professional), and display indications of this data with the detailed information via the user interface 111. That is, the date and/or time at which the medication was administered and the date and/or time at which the data was entered will generally be different unless the administration is via a machine that communicates with the database 123.
- other users who view the detailed information displayed via the user interface 111 may compare the date and/or time of administration to the date and/or time of data entry to determine how quickly administration data is being entered, i.e., in order to determine the likelihood of errors, as there could be more errors if the date/time of administering the medication is long before the date/time of logging the data.
- the graphical display application 117 may access, from the database 123, data indicating one or more of the following: a type of medication, method of administration of medication, and/or dosage of medication as ordered for the patient, and the actual type of medication, method of administration of medication and/or dosage of medication as administered by the healthcare professional (i.e., as indicated by the administering healthcare professional), and display indications of this data with the detailed information via the user interface 111. Consequently, other users who view the detailed information may compare the medication as ordered to the medication as administered to determine whether there are discrepancies in medications as ordered compared to medications as administered to the patient. [0077] Additionally, in some examples, e.g., as shown at FIG.
- the graphical display application 117 may cause the user interface 111 to display or highlight icons 201 associated with the administration of a particular medication (e.g., “Heparin Sodium”) in graphs displaying biometric data associated with the patient. That is, as shown at FIG. 2C- 2D, the graphs associated with the patient HenriettaQ may include icons 201 indicating dates and times associated with administration of Heparin Sodium alongside, e.g., biometric data, such as respiratory rate, arterial blood pressure diastolic, arterial blood pressure systolic, 02 saturation pulseoxymetry, arterial PH, heart rate, etc., at the same times. Furthermore, as shown at FIG.
- the graphical display application 117 may cause the user interface 111 to display or highlight icons 201 associated with the administration of multiple selected medications (e.g., “Gancyclovir”, “Vancomycin”) in graphs displaying biometric data associated with the patient. That is, as shown at FIG. 2E, the graphs associated with the patient HenriettaQ may include icons 201 indicating dates and times associated with administration of Gancyclovir and Vancomycin alongside, e.g., biometric data, such as respiratory rate, arterial blood pressure diastolic, arterial blood pressure systolic, 02 saturation pulseoxymetry, arterial PH, heart rate, etc., at the same dates/times. Similarly, as shown at FIG.
- the graphical display application 117 may cause the user interface 111 to display or highlight icons 201 associated with the administration of a selected medication, e.g., “Vancomycin” in graphs displaying a selected type of biometric data associated with the patient, e.g., “Respiratory Rate.”
- the user interface 111 may display searchable nurse’s notes that allow custom search input and word-based analysis and text-mining in text notes from an attending healthcare professional, such as a doctor or nurse.
- these text notes may include indications of which medications are administered to patients at which dates/times.
- the graphical display application 117 may then subsequently receive user input including search terms indicating a particular medication, and may locate instances of the term in historical notes and times at which the historical notes were recorded.
- the graphical display application 117 may then cause the user interface 111 to display indications of times at which notes related to a given medication were recorded, so that other users (or the same user) can easily search for specific medications within the notes and see an indication of a time at which notes related to a certain term were recorded. For instance, in some examples, the graphical display application 117 may store these indications of administered medications in the database 123 along with the medical device data. The graphical display application 117 may cause these notes to be displayed simultaneously with the graphs discussed above on a single screen via the user interface 111 so that a user can see biometric data recorded at the time of any administered medication.
- the graphical display application 117 may locate instances in which the medication Vancomycin appears within the text notes, along with times associated with each instance, and may cause the user interface 111 to display the instances and associated times. For instance, the user interface 111 may display the text notes in which the medication Vancomycin appears and may highlight the term within notes in which it appears, e.g., as shown at FIGS. 2G-2H.
- the user interface 111 may receive a selection, from a user, of a particular instance where the medication Vancomycin appears within the text notes, and the graphical display application 117 may cause the user interface 111 to display graphs of biometric data as recorded at the time (or within a range of times) associated with the selected instance of the term based on the selection, e.g., as shown at FIGS. 2G-2H.
- the graphical display application 117 may cause the user interface 111 to display one or more graphs of biometric data recorded at 11 :16 AM on 8/30 (or from a range of times around 11 :16 AM on 8/30, etc.) For example, as shown in FIG. 2G, when the user interface 111 receives a selection, from a user, of a particular instance of the medication Vancomycin in a healthcare professional’s text note from 11 :16 AM on 8/30, the graphical display application 117 may cause the user interface 111 to display one or more graphs of biometric data recorded at 11 :16 AM on 8/30 (or from a range of times around 11 :16 AM on 8/30, etc.) For example, as shown in FIG.
- the graphical display application 117 may cause the user interface to display a graph of the patient’s respiratory rate, arterial blood pressure diastolic, arterial blood pressure systolic, 02 saturation pulseoxymetry, arterial PH, heart rate, etc., at 11 :16 AM on 8/30, when the administration of Vancomycin was noted. Moreover, the graphical display application 117 may cause the user interface to highlight or otherwise identify the exact time and date associated with the selected term within the graphs of the biometric data (e.g., using a vertical line as shown in FIG. 2G).
- these features help users to visually connect various noted conditions or observations to graphs displaying biometric data from times at which the conditions were noted.
- these features allow for a smoother transfer of knowledge/information across healthcare professionals’ shift changes, because a healthcare professional in a later shift can easily identify which medications were administered by healthcare professionals in earlier shifts, and can view the patient’s biometric data from past times when these medications were administered. Furthermore, these features allow healthcare professionals to easily identify patterns, trends, or anomalies in patient conditions and biometric data as medications are administered across multiple shift changes.
- the user interface 111 may display a listing of possible patients (e.g., JoselynQ, LyndaQ, RebeccaQ, SallyQ, SassyQ, as shown at FIG. 2I). The patients may be listed based on patient identification numbers or room numbers in some examples.
- the graphical display application 117 may cause the user interface 111 to display various possible patients, and receive input from a user regarding a particular patient of interest of the various possible patients.
- the graphical display application 117 may access biometric data (and/or other kinds of data including medication data, as discussed above) associated with a selected patient in the database 123, generate one or more graphs showing the biometric data and/or medication data associated with a selected patient, and cause the user interface 111 to display the generated one or more graphs. Furthermore, before switching displays from one patient to another via the user interface 111 , the graphical display application 117 may cache the biometric data, medication data, etc., associated with the original patient, as well as a display state for the particular biometric data associated with the original patient, being viewed by a user.
- the indication of the display state may include an indication of biometric data of interest being viewed by the user, medication data of interest being viewed by the user, time ranges being viewed by the user, etc., in each of various graphs being viewed by the user for a particular patient.
- the graphical display application 117 may cache the biometric data, medication data, etc., for the patient, as well as the nurse’s display state for the particular patient, e.g., locally via the memory 116, prior to switching to viewing a different patient based on a selection from the nurse.
- the graphical display application 117 may access the biometric data and medication data associated with the original patient, so that the graphical display application 117 does not need to reload all of the biometric data and medication data associated with the original patient from the database 123. Accordingly, the graphical display application 117 can pull any new biometric and medication data from the database 123 and otherwise use the biometric and medication data that are locally cached data from the memory 116.
- the graphical display application 117 may access the cached display state stored in the memory 116 so that the graphical display application 117 can display the biometric data of interest being viewed by the nurse, medication data of interest being viewed by the nurse, time ranges being viewed by the nurse, etc., in each of various graphs that the nurse was previously viewing for the original patient, i.e. , such that the user can pick up where he or she left off with respect to the initial patient.
- control application 118 may receive indications of search criteria from a user, e.g., via a user interface 111 , and may provide data from the database 123, including biometric data from the medical devices 102 and data provided by healthcare professionals, including indications of which medications (or food or water or other nutrients) were administered to the patient, methods of delivery of the medications, dosages of the medications, and dates and/or times at which medications were administered to the patient, etc., in response to the search criteria.
- data from the database 123 including biometric data from the medical devices 102 and data provided by healthcare professionals, including indications of which medications (or food or water or other nutrients) were administered to the patient, methods of delivery of the medications, dosages of the medications, and dates and/or times at which medications were administered to the patient, etc.
- a user may search by any criteria, such as a particular medication, particular doses of a given medication, combinations of medications, combinations of medications and certain ranges of biometric data, etc., and the control application 118 may provide this data to the user to perform further analysis, in a manner consistent with privacy regulations in countries where patients are located.
- this data searching can span across multiple patients to provide enough data for the control application 118 (or for the user, independently of the control application 118) to perform statistical analysis of the data, again, in a manner consistent with privacy regulations in countries where patients are located.
- control application 118 may access data from multiple patients in a manner consistent with privacy regulations in countries where patients are located and analyze the data in order to determine, e.g., the effectiveness of various medications, the effects various medications have on various biometric data, side effects associated with various medications, etc., for a large pool of patients.
- the medical provider service identification application 119 may identify the medical service provided based on the medical provider’s searches, including the content of the searches and the amount of time spent searching.
- control application 118 may generate the graphics and/or information based on comparing the data to a ventilator weaning protocol (e.g., a ventilator weaning protocol retrieved from a ventilator weaning protocol database 124).
- the control application 118 may transmit the generated graphics and/or information to the remote display devices 104 (or to healthcare computing devices 110) via the network 108.
- the control application 118 may generate indications of each patient’s ventilator settings as well as a visual system (red/yellow/green background) highlighting each patient’s trajectory on the ventilator as they progress in the ventilator weaning process for display via remote display devices 104 positioned outside of each ventilator patient’s room. That is, generally speaking, ventilator weaning may be dived into three phases: (1) preparing to wean, (2) weaning and (3) extubation, and the remote display device may display a patient’s current phase, as well as a status associated with that phase. For example, if a patient is weaning and their SpO2 is declining, the screen may display a ‘W’ with a red background.
- the screen may display a ‘P’ with a yellow background. Additionally, as another example, if a patient is ready to extubate, the screen may display an ‘E’ with a green background. Similarly, as another example, if a patient is successfully weaning, the screen may display a ‘W’ with a green background. Furthermore, as another example, if a patient is fully prepared to begin weaning, the screen may display a ‘P’ with a green background.
- the control application 118 may generate indications of clinical guidance, e.g., to recommend/remind a treating healthcare professional (or team of healthcare professionals) of the need (when appropriate) for a spontaneous breathing trial (SBT) for a particular ventilator patient or other recommendations (e.g., a recommendation for extubation, a recommendation to modify ventilator settings, or various other recommendations related to ventilator weaning) and may transmit this generated indication to a remote display device 104 positioned outside of the room of the ventilator patient (or to a healthcare computing device 110 associated with the patient’s healthcare provider). The remote display device 104 or the healthcare computing device may then display the generated indication. Furthermore, in some examples, the control application 118 may generate the graphics and/or information and
- the predictive model 120 may be trained using a predictive model training application 122.
- the predictive model training application 122 may train a machine learning model (e.g., using Kalman filtering, support vector machine, logistic regression and boosting, etc.) to identify metrics such as readiness to wean, weaning parameters, time of extubation, factors associated with successful extubation, etc., e.g., using information stored in a historical ventilator patient database 126 and/or information stored in a historical ventilator operational database 128 as training data.
- the historical ventilator patient database 126 and historical ventilator operational database 128 may store clinical data associated with mechanically ventilated ICU patients.
- the predictive model training application 122 may train the predictive model 120 using machine learning techniques, while in other examples the predictive model training application 122 may train the predictive model 120 using a multiple hypothesis testing approach, or a mix of machine leaning approaches and multiple hypothesis approaches. That is, some variables associated with ventilator weaning are correlated and some of them are uncorrelated.
- multiple hypothesis testing approaches may be used to determine the most accurate predictor for those variables and to evaluate the significance level of each.
- multiple hypothesis testing approaches treat type-l and type-ll error separately, while most other approaches fail to make a difference when dealing with both.
- the predictive model 120 may be trained (using the predictive model training application 122) to select the best indicators for weaning and to predict those weaning indices.
- the predictive model 120 may use real time forecasting approaches to predict the parameters during the day, providing an advantage over current methods in which the evaluating the readiness of patients is performed only once a day.
- the predictive model training application 122 may train the predictive model 120to identify the best time for weaning from a ventilator during the day when dealing with the multi-scale time-series of different parameters. Additionally, the predictive model training application 122 may train the predictive model 120 by testing the optimal time to wean as well as the rate of chronic weaning can also be tested using multiple hypothesis testing approaches.
- the predictive model training application 122 may use multiple hypothesis testing approaches to select the top significant variables may be selected while controlling the type-l error at 5%, with a confidence level for each variable. Additionally, the predictive model training application 122 may use machine learning approaches to select variables that are most important for prediction accuracy. Additionally, the predictive model training application 122 may use feature engineering in artificial intelligence to create the significant variables based on the given information. Accordingly, after this selection process, there will be some number (n) of selected variables (e.g., Vi , V 2 , V 3 , ..., V n ).
- the predictive model training application 122 may apply several different data balancing processes, followed by machine learning and real time forecasting approaches (e.g., Kalman filtering, support vector machine, logistic regression and boosting). Furthermore, the predictive model training application 122 may train and test the predictive model 120 on different balanced datasets. Reduction of Type I & II errors may be accomplished via multivariate hypothesis techniques. Additionally, the predictive model training application 122 may refine the predictive model 120 as new data is collected by ventilators (i.e., by ventilators that are part of the medical devices 102), remote display devices 104, and/or healthcare computing device 110 and added to databases 126 and 128.
- ventilators i.e., by ventilators that are part of the medical devices 102
- the success criteria for prediction is the ability of the predictive model 120 to predict the weaning outcomes based on the EMR and ventilator settings (i.e., delta in inspired fraction of Oxygen (AFiO2), delta in tidal volume, pressure support or pressure controlled (AVt, APS or APC) or delta in positive end expiratory pressure set (APEEP)).
- EMR and ventilator settings i.e., delta in inspired fraction of Oxygen (AFiO2), delta in tidal volume, pressure support or pressure controlled (AVt, APS or APC) or delta in positive end expiratory pressure set (APEEP)
- Example variables used in the model are detailed in FIG. 2P within their sources, means of extraction and a schematic of the main components of the study.
- the predictive model training application 122 transforms data from the linear format into a table, where the clinical variables are the column labels and the patient codes are stored as the row labels. Since the readings for the various variables involved are not all set at the same frequency, the data for the different variables will require alignment along the rows time-steps. Then, only the rows at which at least one of the setting variables is modified will be preserved in the data file. Binning of the target variable data into several classes (e.g., scoring for readiness to wean) allows for better classification performance. For all time-steps, key values will be validated and kept in the database if other metrics from monitors in each row are within 10% of other sensors measuring the same data points. In some cases, rows containing readings which do not fit this condition will be removed. The number of rows will be randomly distributed between the training and test databases, without considering the number of patients in each dataset.
- control application 118 may apply the trained predictive model 120 to a particular patient’s current patient data and/or current ventilator settings (e.g., obtained from ventilators that are part of the medical devices 102,, remote display devices 104, healthcare computing device 106, etc.) in order to identify parameters with a high likelihood of leading to successful extubation for that particular patient.
- the control application 118 may then use the identified parameters to generate graphics and/or information, including indications of the patient’s trajectory on the ventilator and/or indications of clinical guidance or other recommendations for the patient, and transmit the generated graphics and/or information to the remote display device 104 associated with that patient (or to a healthcare computing device 110 associated with the patient’s healthcare provider).
- FIG. 3 illustrates a flow diagram of an exemplary method 300 for managing and controlling the process of weaning a patient from a ventilator based on a ventilator weaning protocol (e.g., the ventilator weaning protocol from the database 124 described above), in accordance with some embodiments.
- a ventilator weaning protocol e.g., the ventilator weaning protocol from the database 124 described above
- One or more steps of the method 300 may be implemented as a set of instructions stored on a computer-readable memory 116 and executable on one or more processors 114.
- current ventilator operational data and current health data associated with a ventilator patient may be received or accessed (block 302).
- the current ventilator operational data and current health data associated with the ventilator patient may be compared (block 304) to a ventilator weaning protocol.
- the patient’s current ventilator weaning status, a recommended timeline for ventilator weaning for the patient, and/or a recommended methodology for ventilator weaning for the patient may be determined (block 306) based on the comparison.
- An indication of the patient’s current ventilator weaning status, a recommended timeline for ventilator weaning for the patient, and/or a recommended methodology for ventilator weaning for the patient may be transmitted (block 308) to a remote display device associated with the ventilator patient.
- FIG. 4 illustrates a flow diagram of an exemplary method 400 for managing and controlling the process of weaning a patient from a ventilator based on a predictive model for ventilator weaning (e.g., the predictive model 120 described above), in accordance with some embodiments.
- One or more steps of the method 400 may be implemented as a set of instructions stored on a computer-readable memory 116 and executable on one or more processors 114.
- historical ventilator operational data and historical health data associated with a plurality of historical ventilator patients may be received or accessed (block 402).
- a ventilator weaning predictive model may be trained (block 404) to identify recommended timing and methodology for ventilator weaning associated with successful outcomes for ventilator patients using the historical ventilator operational data and historical health data.
- Current ventilator operational data and current health data associated with a ventilator patient may be received or accessed (block 406).
- the trained predictive model may be applied (block 408) to the current ventilator operational data and current health data associated with the ventilator patient.
- a recommending timing and/or methodology for ventilator weaning for the patient may be identified (block 410).
- An indication of a recommended timeline for ventilator weaning for the patient, and/or a recommended methodology for ventilator weaning for the patient may be transmitted (block 412) to a remote display device associated with the ventilator patient.
- FIG. 5 illustrates a flow diagram of an example method 500 for identifying services provided to patients by medical providers based on the medical providers’ interactions with a patient monitoring interface.
- Instructions for performing the method 500 may be stored on one or more memories, such as the memory 116 as shown in FIG. 1 , and may be executed by one or more processors, such as the processor 114 as shown at FIG. 1 .
- biometric data captured by one or more medical devices may be received (block 502), e.g., by the graphical display application 117 and/or the medical provider service identification application 119.
- One or more interactive displays e.g., the displays shown at FIGS. 1A-1 H, 1J-1 N, and 1 P-1Z, and FIGS. 2A-2N
- One or more interactive displays including indications of the biometric data captured by the one or more medical devices associated with the one or more patients
- a patient monitoring interface e.g., user interface 111 as shown at FIG. 1
- An indication of one or more interactions, of one or more medical providers, with the one or more interactive displays provided by the patient monitoring interface may be received (block 506), e.g., by the medical provider service identification application 119.
- the one or more interactions, of the one or more medical providers, with the one or more interactive displays provided by the patient monitoring interface may be analyzed (block 508), e.g., by the medical provider service identification application 119, in order to identify one or more services provided by the one or more medical providers.
- the analysis may include identifying services provided by the one or more medical providers based on which interactive displays are viewed by or interacted with by the one or more medical providers.
- the services provided by the one or more medical providers may be identified based on cursor clicks or hovering associated with interactive displays that are viewed by or interacted with by the one or more medical providers, and/or based on active time associated with interactive displays that are viewed by or interacted with by the one or more medical providers.
- the one or more services provided by the one or more medical providers may include one or more medical procedures performed by the one or more medical providers, such as surgical procedures, diagnostic procedures or scans, therapeutic procedures, etc.
- the one or more services provided by the one or more medical providers may include one or more medications administered by the one or more medical providers.
- Identifying the one or more services provided by the one or more medical providers may also include, for instance, identifying a particular patient associated with a particular service provided by the one or more medical providers. Additionally, identifying the one or more services provided by the one or more medical providers may include identifying a category, ranking, or level associated with medical providers who performed a particular service (e.g., identifying whether the medical provider is a doctor, nurse, physician assistant, etc., identifying a specialty of the medical provider, identifying a seniority level or job title of the medical provider, etc.). Furthermore, identifying the one or more services provided by the one or more medical providers may include identifying a particular medical provider associated with a particular service provided to a patient. For instance, a medical provider may be identified by name, or by an identification number such as a badge number or other employee identification.
- a particular medical provider who is interacting with the patient monitoring interface may be prompted (e.g., by the patient monitoring interface) to provide identifying information.
- the medical provider may be prompted to log in or otherwise provide identifying information or credentials to the patient monitoring interface, and services provided by the particular medical provider may be identified based on the identifying information or credentials that the particular medical provider provided to the patient monitoring interface.
- identifying the one or more services provided by the one or more medical providers may also include determining amounts of time associated with the one or more services provided by the one or more medical providers, e.g., based on amounts of time associated with the one or more interactions of the one or more medical providers with the patient monitoring interface.
- the method 500 may further include generating a medical bill based on the identified one or more services provided by the one or more medical providers.
- the medical bill may be generated based on one or more of: one or more medical procedures performed by the one or more medical providers; one or more medications administered by the one or more medical providers; a category, ranking, or level associated with the one or more medical providers; particular medical providers associated with the identified one or more services; and/or a particular patient associated with the identified one or more services; or amounts of time associated with the identified one or more services.
- a method for identifying services provided by one or more medical providers based on medical provider interactions with a patient monitoring interface comprising: receiving, by one or more processors, biometric data captured by one or more medical devices associated with one or more patients; providing, by the one or more processors, via a patient monitoring interface, one or more interactive displays including indications of the biometric data captured by the one or more medical devices associated with the one or more patients; receiving, by the one or more processors, an indication of one or more interactions, of one or more medical providers, with the one or more interactive displays provided by the patient monitoring interface; and analyzing, by the one or more processors, the one or more interactions, of the one or more medical providers, with the one or more interactive displays provided by the patient monitoring interface, in order to identify one or more services provided by the one or more medical providers.
- analyzing the one or more interactions, of the one or more medical providers, with the one or more interactive displays provided by the patient monitoring interface, in order to identify one or more services provided by the one or more medical providers includes determining amounts of time associated with the one or more services provided by the one or more medical providers based on amounts of time associated with the one or more interactions, of the one or more medical providers with the patient monitoring interface.
- analyzing the one or more interactions, of the one or more medical providers, with the one or more interactive displays provided by the patient monitoring interface, in order to identify one or more services provided by the one or more medical providers includes identifying the one or more services provided by the one or more medical providers based on active time associated with interactive displays that are viewed by or interacted with by the one or more medical providers.
- the medical bill is generated based on one or more of: one or more medical procedures performed by the one or more medical providers; one or more medications administered by the one or more medical providers; a category, ranking, or level associated with the one or more medical providers; particular medical providers associated with the identified one or more services; a particular patient associated with the identified one or more services; or amounts of time associated with the identified one or more services.
- a system for identifying services provided by one or more medical providers based on medical provider interactions with a patient monitoring interface comprising: a patient monitoring interface; one or more processors; and a non-transitory computer-readable memory storing one or more instructions that, when executed by the one or more processors, cause the one or more processors to: receive biometric data captured by one or more medical devices associated with one or more patients; provide, via the patient monitoring interface, one or more interactive displays including indications of the biometric data captured by the one or more medical devices associated with the one or more patients; receive an indication of one or more interactions, of one or more medical providers, with the one or more interactive displays provided by the patient monitoring interface; and analyze the one or more interactions, of the one or more medical providers, with the one or more interactive displays provided by the patient monitoring interface, in order to identify one or more services provided by the one or more medical providers.
- a non-transitory, computer-readable memory storing one or more instructions for identifying services provided by one or more medical providers based on medical provider interactions with a patient monitoring interface that, when executed by the one or more processors, cause the one or more processors to: receive biometric data captured by one or more medical devices associated with one or more patients; provide, via the patient monitoring interface, one or more interactive displays including indications of the biometric data captured by the one or more medical devices associated with the one or more patients; receive an indication of one or more interactions, of one or more medical providers, with the one or more interactive displays provided by the patient monitoring interface; and analyze the one or more interactions, of the one or more medical providers, with the one or more interactive displays provided by the patient monitoring interface, in order to identify one or more services provided by the one or more medical providers.
Landscapes
- Engineering & Computer Science (AREA)
- Health & Medical Sciences (AREA)
- Business, Economics & Management (AREA)
- Biomedical Technology (AREA)
- Public Health (AREA)
- General Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Medical Informatics (AREA)
- General Health & Medical Sciences (AREA)
- Primary Health Care (AREA)
- Finance (AREA)
- Epidemiology (AREA)
- Physics & Mathematics (AREA)
- Development Economics (AREA)
- Life Sciences & Earth Sciences (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Strategic Management (AREA)
- Economics (AREA)
- Pathology (AREA)
- Surgery (AREA)
- Nuclear Medicine, Radiotherapy & Molecular Imaging (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Urology & Nephrology (AREA)
- Biophysics (AREA)
- Heart & Thoracic Surgery (AREA)
- Molecular Biology (AREA)
- Animal Behavior & Ethology (AREA)
- Veterinary Medicine (AREA)
- Marketing (AREA)
- Measuring And Recording Apparatus For Diagnosis (AREA)
Abstract
La présente invention concerne des systèmes et des procédés pour identifier les services fournis par un ou plusieurs fournisseurs de soins médicaux sur la base des interactions du fournisseur de soins médicaux avec une interface de surveillance de patient. Des données biométriques peuvent être capturées par un ou plusieurs dispositifs médicaux associés à un ou plusieurs patients. Une interface de surveillance de patient peut fournir un ou plusieurs affichages interactifs comprenant des indications des données biométriques capturées par le ou les dispositifs médicaux associés au ou aux patients. Une ou plusieurs interactions d'un ou plusieurs fournisseurs de soins médicaux avec le ou les affichages interactifs fournis par les interfaces de surveillance de patient peuvent être analysées afin d'identifier un ou plusieurs services fournis par le ou les fournisseurs de soins médicaux.
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US202263413547P | 2022-10-05 | 2022-10-05 | |
US63/413,547 | 2022-10-05 | ||
US202263385624P | 2022-11-30 | 2022-11-30 | |
US63/385,624 | 2022-11-30 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2024076669A1 true WO2024076669A1 (fr) | 2024-04-11 |
Family
ID=90608909
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2023/034532 WO2024076669A1 (fr) | 2022-10-05 | 2023-10-05 | Identification des services fournis à un patient par un fournisseur de soins médicaux sur la base des interactions du fournisseur de soins médicaux avec un dispositif de surveillance de patient |
Country Status (1)
Country | Link |
---|---|
WO (1) | WO2024076669A1 (fr) |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7467094B2 (en) * | 1999-06-23 | 2008-12-16 | Visicu, Inc. | System and method for accounting and billing patients in a hospital environment |
US8600769B2 (en) * | 2004-05-19 | 2013-12-03 | Fairpay Solutions, Inc. | Medical bill analysis and review |
US20130325508A1 (en) * | 2012-05-30 | 2013-12-05 | Covidien Lp | Systems and methods for providing transparent medical treatment |
US20160239617A1 (en) * | 2015-02-13 | 2016-08-18 | Cerner Innovation, Inc. | Systems and methods for capturing data, creating billable information and outputting billable information |
EP3236408A1 (fr) * | 2007-08-16 | 2017-10-25 | Earl Edward Breazeale, Jr. | Suivi de soins de santé |
-
2023
- 2023-10-05 WO PCT/US2023/034532 patent/WO2024076669A1/fr unknown
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7467094B2 (en) * | 1999-06-23 | 2008-12-16 | Visicu, Inc. | System and method for accounting and billing patients in a hospital environment |
US8600769B2 (en) * | 2004-05-19 | 2013-12-03 | Fairpay Solutions, Inc. | Medical bill analysis and review |
EP3236408A1 (fr) * | 2007-08-16 | 2017-10-25 | Earl Edward Breazeale, Jr. | Suivi de soins de santé |
US20130325508A1 (en) * | 2012-05-30 | 2013-12-05 | Covidien Lp | Systems and methods for providing transparent medical treatment |
US20160239617A1 (en) * | 2015-02-13 | 2016-08-18 | Cerner Innovation, Inc. | Systems and methods for capturing data, creating billable information and outputting billable information |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20220037038A1 (en) | Operating room checklist system | |
Jabre et al. | Effect of bag-mask ventilation vs endotracheal intubation during cardiopulmonary resuscitation on neurological outcome after out-of-hospital cardiorespiratory arrest: a randomized clinical trial | |
US20210308006A1 (en) | Tools for case review performance analysis and trending of treatment metrics | |
JP2019071084A (ja) | 輸液計画システム | |
AU2004312890B2 (en) | Centralized medication management system | |
US20060111933A1 (en) | Adaptive medical decision support system | |
US20150025329A1 (en) | Patient care surveillance system and method | |
US20090094063A1 (en) | Display and method for medical procedure selection | |
US20070033073A1 (en) | System and user interface for monitoring patient treatment orders | |
JP2002312472A (ja) | 医療情報システム及び医療情報システムによって使用される方法 | |
US20100063845A1 (en) | Systems and Methods for Allowing Patient Access to a Patient Electronic Health Records | |
JP2023519672A (ja) | 患者エンカウンタ記録を生成するシステム及び方法 | |
US20140278492A1 (en) | System and methods for proving medical care algorithms to a user | |
US8438043B2 (en) | Nursing information management method and nursing information management apparatus for managing nursing actions | |
Angus | Whether to intubate during cardiopulmonary resuscitation: conventional wisdom vs big data | |
US20230157544A1 (en) | System and Methods for Remotely Monitoring an ICU Environment | |
US8538771B2 (en) | Medical treatment supporting method and medical treatment supporting apparatus for managing nursing care actions | |
US20230041220A1 (en) | ICU Monitor With Medication Data | |
Rasubala et al. | Digital twin roles in public healthcare | |
WO2024076669A1 (fr) | Identification des services fournis à un patient par un fournisseur de soins médicaux sur la base des interactions du fournisseur de soins médicaux avec un dispositif de surveillance de patient | |
Ratnakar et al. | Smart Innovative Medical Devices Based on Artificial Intelligence | |
Manukova et al. | Innovative Concept of Application of Electronic Modeling in Building e-Health Systems | |
Samal et al. | Impact of electronic health records on racial and ethnic disparities in blood pressure control at US primary care visits | |
US20140310012A1 (en) | Centralizing protocol guidance and documentation for a healthcare event | |
WO2024086646A1 (fr) | Systèmes et procédés de génération de protocole de guidage clinique |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 23875506 Country of ref document: EP Kind code of ref document: A1 |