User objective assistance technologies
US-11361266-B2 · Jun 14, 2022 · US
US12159130B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12159130-B2 |
| Application number | US-202117383524-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jul 23, 2021 |
| Priority date | Jul 23, 2021 |
| Publication date | Dec 3, 2024 |
| Grant date | Dec 3, 2024 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A computer-implemented method, a medical device, and a system for acquiring user-specific customization data, i.e. user-specific language packages, are provided. The computer-implemented method comprises: determining a first set of user-specific customization data stored on the medical device; comparing the first set of user-specific customization data with a second set of user-specific customization data that is required by a user; and upon determining that the second set of user-specific customization data is different from the first set of user-specific customization data, acquiring, from a data storage external to the medical device, the second set of user-specific customization data or a delta between the first set and the second set of user-specific customization data.
Opening claim text (preview).
The invention claimed is: 1. A computer-implemented method for resource-efficient customization of an operating system of a medical device, the method comprising: identifying, by the medical device, a first set of user-specific customization data stored on the medical device; determining, by the medical device, a second set of user-specific customization data that is required by a user; comparing, by the medical device, the first set of user-specific customization data with the second set of user-specific customization data; in response to determining that the second set of user-specific customization data is different from the first set of user-specific customization data stored on the medical device: determining, by the medical device, a delta consisting of one or more items of data present in the second set of user-specific customization data and absent from the first set of user-specific customization data stored on the medical device; acquiring a first subset of the second set of user-specific customization data from the first set of user-specific customization data stored on the medical device; and acquiring a second subset of the second set of user-customization data from a data storage external to the medical device, the second subset consisting of the delta between the first set of user-specific customization data and the second set of user-specific customization data; customizing, based on the acquired delta, an output generated by the operating system of the medical device during treatment of the user, wherein customizing the output comprises changing a graphical layout of one or more graphical user interface (GUI) elements during the treatment of the user based on the second subset of the second set of user-customization data acquired from the external data storage; and causing the medical device to provide the customized output to the user. 2. The computer-implemented method of claim 1 , further comprising storing the acquired delta on a data storage of the medical device. 3. The computer-implemented method of claim 1 , further comprising reading the acquired delta and customizing the operating system of the medical device based at least on the acquired delta. 4. The computer-implemented method of claim 1 , wherein the data storage external to the medical device comprises a remote server, a data cloud, and/or a token, wherein the token is or comprises a USB drive, a smart card, a hard-disk drive, and/or a solid-state disk. 5. The computer-implemented method of claim 1 , wherein at least a part of the user-specific customization data is stored on a token, and wherein the step of determining, by the medical device, the second set of user-specific customization data comprises reading the token. 6. The computer-implemented method of claim 1 , wherein the user-specific customization data comprises language data, the GUI elements, user-specific functions, and/or any combination thereof. 7. The computer-implemented method of claim 6 , wherein the language data comprises text and sound. 8. The computer-implemented method of claim 1 , wherein the GUI elements comprise user-specific text, buttons, sounds, and/or colors. 9. The computer-implemented method of claim 1 , wherein the user-specific customization data further comprises user-specific system rights for controlling the medical device. 10. The computer-implemented method of claim 1 , wherein the medical device is configured to provide a renal replacement therapy to a patient, including one or more of Peritoneal Dialysis, Hemodialysis, Hemofiltration, and/or Hemodiafiltration. 11. The computer-implemented method of claim 1 , further comprising reading log-in information from the user, wherein the method of claim 1 is triggered at least partly in response to the user having logged in for a first time at the medical device. 12. The computer-implemented method of claim 11 , wherein reading the log-in information comprises reading the log-in information via a log-in screen provided by a display of the medical device, and wherein the log-in screen is displayed when the medical device is started and/or woken up from hibernation. 13. The computer-implemented method of claim 1 , further comprising providing, by a display of the medical device, different sets of user-specific customization data for the user to select from, wherein the second set of user-specific customization data is the set of user-specific customization data selected by the user. 14. A computer-implemented method for resource-efficient customization of an operating system of a medical device, the method comprising: (1) identifying, by the medical device, a first set of user-specific customization data stored on the medical device; (2) determining, by the medical device, a second set of user-specific customization data that is required by a user; (3) comparing, by the medical device, the first set of user-specific customization data with the second set of user-specific customization data; (4) in response to determining that the second set of user-specific customization data is different from the first set of user-specific customization data stored on the medical device: determining, by the medical device, a delta consisting of one or more items of data present in the second set of user-specific customization data and absent from the first set of user-specific customization data stored on the medical device; acquiring a first subset of the second set of user-specific customization data from the first set of user-specific customization data stored on the medical device; and acquiring a second subset of the second set of user-customization data from a data storage external to the medical device, the second subset consisting of the delta between the first set of user-specific customization data and the second set of user-specific customization data; (5) customizing, based on the acquired delta, an output generated by the operating system of the medical device during treatment of the user, wherein customizing the output comprises changing a graphical layout of one or more graphical user interface (GUI) elements during the treatment of the user based on the second subset of the second set of user-customization data acquired from the external data storage; and (6) causing the medical device to provide the customized output to the user; and (7) verifying an identity of the user, before, during, and/or after steps (1) through (6). 15. The computer-implemented method of claim 14 , wherein verifying the identity of the user occurs before the steps (1), (2), (3), (4), (5), and (6), and wherein the steps (2), (3), (4), (5), and (6) are automatically triggered in response to verifying the identity of the user. 16. The computer-implemented method of claim 14 , wherein verifying the identity of the user is performed via an authentication device of the medical device, the authentication device being or comprising a smartcard reader, an RFID/NFC reader, a QR code reader, a barcode reader, a USB port, a fingerprint sensor, a retina scanner, a microphone and/or a camera. 17. The computer-implemented method of claim 14 , wherein verifying the identity of the user is based on multi-factor authentication. 18. The computer-implemented method of claim 14 , further comprising reading a user profile after verifying the identity of the user, wherein the user profile comprises information of the second set of user-specific customization data that is required by the user; and wherein, the steps (1), (2), (3), (4), (5), and (6) are automatically triggered
Execution arrangements for user interfaces · CPC title
based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance · CPC title
for the management of medical equipment or devices, e.g. scheduling maintenance or upgrades · CPC title
stored on portable record carriers, e.g. on smartcards, RFID tags or CD · CPC title
Dialysis systems; Artificial kidneys; Blood oxygenators (semi-permeable membranes characterised by the material, manufacturing processes therefor B01D71/00){; Reciprocating systems for treatment of body fluids, e.g. single needle systems for hemofiltration or pheresis} · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.