MEDICAL DEVICE USER CACHING

• US 20170140134A1
• Filed: 11/16/2015
• Published: 05/18/2017
• Est. Priority Date: 11/16/2015
• Status: Abandoned Application

• Current Assignee: Welch Allyn Incorporated
• Original Assignee: Welch Allyn Incorporated
• Inventors: Brough, Stacie L., Nye, III, Andrew Brayton
• Application Number:
  US14/941,843
• Publication Number:
  US 20170140134A1
• Time in Patent Office: Days
• CPC Class Codes: A61B 2560/0266 for monitoring or limiting apparatus function
• CPC Class Codes: A61B 2560/0437 Trolley or cart-type apparatus
• CPC Class Codes: A61B 5/0002 Remote monitoring of patients using telemetry, e.g. transmission of vital signals via a communication network A61B5/07 takes precedence; transmission systems for measured values G08C; transmission H04B; transmission of digital information H04L; wireless communication networks H04W
• CPC Class Codes: A61B 5/002 Monitoring the patient using a local or closed circuit, e.g. in a room or building A61B5/0017 takes precedence
• CPC Class Codes: A61B 5/02055 Simultaneously evaluating both cardiovascular condition and temperature
• CPC Class Codes: G06F 12/0875 with dedicated cache, e.g. instruction or stack
• CPC Class Codes: G06F 21/31 User authentication
• CPC Class Codes: G06F 2212/1052 Security improvement
• CPC Class Codes: G06F 2212/45 Caching of specific data in cache memory
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 40/67 for remote operation

Abstract

An example medical device includes a physiological measurement device, a device management engine, a user caching engine, and a login engine. The device management engine is configured to receive data captured by the physiological measurement device. The user caching engine is configured to store cache records associated with users in a user cache. The login engine is configured to receive a user identifier associated with a user and determine whether the user identifier is associated with a cache record stored in the user cache. When determined that the user identifier is associated with a cache record stored in the user cache, the login engine is configured to log the user in. When not determined that the user identifier is associated with an unexpired cache record stored in the user cache, the login engine is configured to prompt the user for a credential.

Claims

1. A medical device, comprising:

a physiological measurement device configured to measure one or more physiological measurements from a patient;

a device management engine configured to receive data captured by the physiological measurement device;

a user caching engine configured to store cache records associated with users in a user cache; and

a login engine configured to;

receive a user identifier associated with a user;

determine whether the user identifier is associated with a cache record stored in the user cache; and

when determined that the user identifier is associated with a cache record stored in the user cache, log the user in.

2. The medical device of claim 1, wherein the medical device requires the user to login to save physiological measurements from patients.

3. The medical device of claim 2, wherein the login engine is further configured to, when determined that the user identifier is associated with a cache record stored in the user cache, update the cache record associated with the user identifier.

4. The medical device of claim 3, wherein updating the cache record comprises updating a last login time.

5. The medical device of claim 3, wherein updating the cache record comprises updating a last logout time.

6. The medical device of claim 1, wherein the login engine is further configured to when determined that the user identifier is associated with a cache record stored in the user cache:

determine whether the cache record has expired; and

when determined that the cache record has expired, prompt the user for a credential.

7. The medical device of claim 6, wherein determining whether the cache record has expired comprises comparing information stored in the cache record to a cache duration setting.

8. The medical device of claim 6, wherein determining whether the cache record has expired comprises evaluating expiration parameters associated with the cache record.

9. The medical device of claim 1, wherein the login engine is further configured to when determined that the user identifier is not cached:

prompt the user for a credential;

send an authentication request to a server device;

receive a response to the authentication request; and

when determined that the authentication request was successful, add a record associated with the user to the user cache.

10. The medical device of claim 9, wherein the credential is a password.

11. The medical device of claim 1, wherein the user caching engine is further configured to:

evaluate a cache record stored in the user cache to determine whether the cache record has expired; and

when determined that the cache record has expired, remove the cache record from the user cache.

12. The medical device of claim 1, further comprising a reader device configured to read an identification object associated with the user to receive a user identifier.

13. The medical device of claim 12, wherein the identification object is a badge comprising a barcode tag and the reader device is a barcode reader.

14. The medical device of claim 12, wherein the identification object is a badge comprising a radio frequency identifier tag and the reader device is a radio frequency identifier reader.

15. The medical device of claim 1, further comprising a user interface engine configured to:

prompt the user for a user identifier; and

when determined that the user identifier is associated with a cache record stored in the user cache, display a prompt for a credential, wherein the prompt is pre-filled; and

pause for a predetermined time period to emulates submitting an authentication request to a server.

16. A method of logging a user into a medical device, the method comprising:

receiving, by the medical device, a user identifier associated with the user;

determining whether the user identifier is associated with a valid cache record stored in the user cache;

when determined that the user identifier is associated with a valid cache record stored in the user cache, logging the user in; and

when determined that the user identifier is not associated with a valid cache record;

prompting the user for a credential;

determining if the user is authenticated based on the user identifier and credential;

when determined that the user is authenticated;

adding a record associated with the user to the user cache; and

logging the user in.

17. The method of claim 16, wherein determining whether the user identifier is associated with a valid cache record comprises evaluating information stored in the cache record to a cache duration setting.

18. The method of claim 16, further comprising when determined that the user identifier is associated with a valid cache record stored in the user cache, updating the cache record associated with the user identifier.

19. The method of claim 16, wherein determining if the user is authenticated comprises sending an authentication request to a server.

20. A medical device, comprising:

a physiological measurement device;

a device management engine configured to receive data captured by the physiological measurement device;

a user caching engine configured to store cache records associated with users in a user cache; and

a login engine configured to;

receive a user identifier associated with a user;

determine whether the user identifier is associated with an unexpired cache record stored in the user cache;

when determined that the user identifier is associated with an unexpired cache record stored in the user cache;

log the user in;

update a last login time of the cache record associated with the user identifier.

when not determined that the user identifier is associated with an unexpired cache record stored in the user cache;

prompt the user for a password;

send an authentication request to a server device;

receive a response to the authentication request; and

when determined that the authentication request was successful, add a record associated with the user to the user cache.