METHOD AND SYSTEM FOR HEALTHCARE PROVIDER TRACKING

• US 20140330575A1
• Filed: 05/01/2014
• Published: 11/06/2014
• Est. Priority Date: 05/02/2013
• Status: Abandoned Application

• Current Assignee: Eloquence Communications, Inc.
• Original Assignee: Eloquence Communications, Inc.
• Inventors: Traughber, Bryan J., Patak, Lance S., Dugan, Brendon, Teegarden, Vaughn
• Application Number:
  US14/267,239
• Publication Number:
  US 20140330575A1
• Time in Patent Office: Days
• US Class Current: 705/2
• CPC Class Codes: A61B 5/0015 characterised by features of the telemetry system
• CPC Class Codes: A61B 5/0022 Monitoring a patient using a global network, e.g. telephone networks, internet
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 40/63 for local operation
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04W 4/80 Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication

Abstract

A health care provider tracking system and method are disclosed. Such a method may include customizing a healthcare device user interface by presenting a first user interface on the healthcare device; receiving tag data having a healthcare provider identifier; sending the tag data to an authentication server; receiving an access token; and presenting a second user interface on the healthcare device different from the first user interface. The second user interface is configured based on the access token and the healthcare provider identifier. A healthcare tracking system may include a plurality of user tags and a plurality of healthcare devices configured to present a first user interface; obtain the tag data from user tags; communicate tag data; receive an access token; and present a second user interface on the healthcare device different from the first user interface.

Claims

1. A method of customizing a healthcare device user interface, the method comprising:

presenting a first user interface on the healthcare device;

receiving tag data comprising a healthcare provider identifier;

sending a portion of the tag data to an authentication server;

receiving an access token from the authentication server; and

presenting a second user interface on the healthcare device different from the first user interface, the second user interface configured based on the access token and the healthcare provider identifier.

2. The method of claim 1, wherein the tag data is received from a user tag via near field communication.

3. The method of claim 1, further comprising:

receiving a logout via the second user interface; and

presenting the first user interface in place of the second user interface.

4. The method of claim 1, wherein the first user interface has functionalities for patient use, wherein the second user interface has functionalities for healthcare provider use, and wherein the second user interface and the healthcare provider functionalities are not accessible via the first user interface.

5. The method of claim 1, wherein receiving tag data occurs automatically without user interaction when a tag is present within operable range of a tag reader.

6. The method of claim 1, wherein receiving tag data generates a message to the server, which can then send a message or plurality of messages to one or more than one other devices

7. A healthcare tracking system comprising:

a first user tag storing first tag data and operable to communicate the first tag data via near field communication, the first tag data comprising a healthcare provider identifier;

a first healthcare device configured to;

present a first user interface;

obtain the first tag data from the first user tag via near field communication;

communicate a portion of the first tag data;

receive an access token; and

present a second user interface on the healthcare device different from the first user interface, the second user interface configured based on the access token and the healthcare provider identifier; and

a healthcare provider server configured to;

receive a portion of the first tag data from the first healthcare device;

generate an authentication token based on the first tag data; and

communicate the authentication token to the first healthcare device.

8. The system of claim 7, wherein the first user interface has functionalities for patient use, wherein the second user interface has functionalities for healthcare provider use, and wherein the second user interface and the healthcare provider functionalities are not accessible via the first user interface.

9. The system of claim 7, wherein the tag data further comprises a first tag identifier, and wherein the healthcare provider server generates the authentication token based on a comparison of the first tag identifier and the first healthcare provider identifier to authentication data stored on the healthcare provider server.

10. The system of claim 7, wherein the first healthcare device is further operable to:

generate session data corresponding to receiving tag data and actions performed via the second user interface; and

communicate the session data to the healthcare provider server.

11. The system of claim 7, wherein obtaining the first tag data from the first user tag via near field communication occurs automatically without user interaction when the first user tag is present within operable range of a tag reader associated with the first healthcare device.

12. The system of claim 7, wherein receiving tag data generates a message to the server, which can then send a message or plurality of messages to one or more than one other devices

13. The system of claim 7 further comprising:

a second healthcare device configured to;

present the first user interface;

obtain the first tag data from the first user tag via near field communication;

communicate a portion of the first tag data;

receive a second access token; and

present the second user interface on the healthcare device different from the first user interface, the second user interface configured based on the access token and the healthcare provider identifier.

14. A healthcare tracking system comprising:

a plurality of user tags, each storing tag data and operable to communicate the tag data via near field communication, the tag data each comprising a healthcare provider identifier;

a plurality of healthcare devices configured to;

present a first user interface;

obtain the tag data from a user tag via near field communication;

communicate a portion of the tag data;

receive an access token; and

present a second user interface on the healthcare device different from the first user interface, the second user interface configured based on the access token and the healthcare provider identifier; and

a healthcare provider server configured to;

receive a portion of tag data from the healthcare devices;

generate an authentication token based on the tag data; and

communicate the authentication token to the healthcare device that sent the tag data.

15. The system of claim 14, wherein the first user interface has functionalities for patient use, wherein the second user interface has functionalities for healthcare provider use, and wherein the second user interface and the healthcare provider functionalities are not accessible via the first user interface.

16. The system of claim 15, wherein, for a second healthcare device, the first user interface is a locked interface, wherein the second user interface has functionalities healthcare provider use, and wherein the second user interface and the healthcare provider functionalities are not accessible via the first user interface.

17. The system of claim 14, wherein each of the plurality of user tags is carried by a respective healthcare provider user that is associated with the health care provider identifier stored on the respective tag.

18. The system of claim 14, wherein each of the plurality of healthcare devices are located in a plurality of separate health care providing locations.

19. The system of claim 18, wherein the health care providing locations include at least one of a hospital room, exam room and nurses station.

20. The system of claim 14, wherein obtaining the first tag data from the first user tag via near field communication occurs automatically without user interaction when the first user tag is present within operable range of a tag reader associated with the first healthcare device.

21. The system of claim 14, wherein receiving tag data generates a message to the server, which can then send a message or plurality of messages to one or more than one other devices.