PHYSICIAN MOBILE COMMUNICATIONS SYSTEM AND METHOD

• US 20130103768A1
• Filed: 10/24/2011
• Published: 04/25/2013
• Est. Priority Date: 10/24/2011
• Status: Abandoned Application

• Current Assignee: Peter Freebeck
• Original Assignee: Peter Freebeck
• Inventors: Freebeck, Peter
• Application Number:
  US13/279,951
• Publication Number:
  US 20130103768A1
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: G16H 40/20 for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
• CPC Class Codes: G16H 80/00 ICT specially adapted for facilitating communication between medical practitioners or patients, e.g. for collaborative diagnosis, therapy or health monitoring
• CPC Class Codes: H04L 51/56 Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32

Abstract

The LynxIT Mobile System (LMS) provides efficient and economical communications solutions for healthcare professionals. The LMS provides physician to physician communication through mobile smartphone platforms, and rules, including role based rules that prevent unauthorized communications between users. The LMS interfaces with a paging system that provides paging services to the facilities, healthcare professionals, including physicians. The LMS and paging system may interface with staff directories and on-call schedules for hospitals and healthcare facilities accessible through a network. The LMS uses a staff directory and on-call schedule request service that communicates a request to accessible staff directories and on-call schedules for hospitals, healthcare professionals, and other healthcare facilities. The LMS and SPS ingest the directories returned from the request. In this way, physicians control communications between themselves and other healthcare professionals, and create private communications channels based on physician defined rules.

Claims

1. A method for providing physician to physician communication comprising:

registering a plurality of users, including a first user and a second user, to use an application accessible on a network;

receiving a user registration identifier for the users;

validating the user registration identifiers;

retrieving entity identifiers for entities where the users is authorized;

storing each of the entity identifiers that correspond to the validated users;

receiving a first user communication status selection for the first user;

receiving a communications request from the second user requesting to communicate with the first user;

comparing the communications request from the second user with the communication status selection of the first user; and

when the communications request satisfies the communication status selection, providing a communications method to use between the first user and the second user, according to the communication status selection of the first user.

2. The method of claim 1, wherein the registration identifier identifies a license to practice and one or more plurality of specializations for the user;

and

when the communications request of the second user does not satisfy the communication status selection of the first user, providing the second user an alternative user to select for communications, wherein the alternative user configured a communication status selection compatible with the communications request of the second user.

3. The method of claim 1, wherein validating the registration identifier comprises:

authenticating the user registration identifier by comparing the registration identifier with one of a plurality of authentication sources accessible through the network; and

communicating a validation result indicator that indicates whether the registration identifier is valid.

4. The method of claim 1, wherein the identifiers are retrieved from a plurality of accessible staff directories for hospitals and other healthcare facilities, and wherein the entities comprise hospitals and other healthcare facilities.

5. The method of claim 1, wherein storing each of the identifiers for the entities that correspond to the validated user, includes storing the identifier on a mobile device used by the user.

6. The method of claim 5, wherein the mobile device is configured to communicate audio and visual communications.

7. The method of claim 1, wherein the user communication status selection indicates the type of communication the user is willing to receive, including:

text messaging;

an email;

phone call.

8. The method of claim 1, wherein the user communication status selection indicates the type of communication the user is willing to receive based on the role of the requester requesting the communications.

9. A product for providing physician to physician communication, the product comprising:

a computer readable memory with processor executable instructions stored thereon, wherein the instructions when executed by the processor cause the processor to;

register a plurality of users, including a first user and a second user, to use an application accessible on a network;

receive a user registration identifier for the users;

validate the user registration identifiers;

retrieve entity identifiers for entities where the users are licensed to practice;

store each of the entity identifiers that correspond to the validated users;

receive a first user communication status selection for the first user;

receive a communications request from the second user requesting to communicate with the first user;

compare the communications request from the second user with the communication status selection of the first user; and

when the communications request satisfies the communication status selection, provide a communications method to use between the first user and the second user, according to the communication status selection of the first user.

10. The product of claim 9, wherein the registration identifier identifies a license to practice and one or more plurality of specializations for the user;

and

when the communications request of the second user does not satisfy the communication status selection of the first user, providing the second user an alternative user to select for communications, wherein the alternative user configured a communication status selection compatible with the communications request of the second user.

11. The product of claim 9, wherein validating the registration identifier comprises:

authenticating the user registration identifier by comparing the registration identifier with one of a plurality of authentication sources accessible through the network; and

communicating a validation result indicator that indicates whether the registration identifier is valid.

12. The product of claim 9, wherein the identifiers are retrieved from a plurality of accessible staff directories for hospitals and other healthcare facilities, and wherein the entities comprise hospitals and other healthcare facilities.

13. The product of claim 9, wherein storing each of the identifiers for the entities that correspond to the validated user, includes storing the identifier on a mobile device used by the user.

14. The product of claim 13, wherein the mobile device is configured to communicate audio and visual communications.

15. The product of claim 9, wherein the user communication status selection indicates the type of communication the user is willing to receive, including:

text messaging;

an email;

phone call.

16. The product of claim 9, wherein the user communication status selection indicates the type of communication the user is willing to receive based on the role of the requester requesting the communications.

17. A system for providing physician to physician communication, the system connected to a network comprising:

a memory coupled to a processor, the memory comprising;

registration requests for a plurality of users, including a first user and a second user, to use an application accessible on the network;

a user registration identifier for the users;

user registration identifiers validation status;

entity identifiers for entities where the users are licensed to practice;

a first user communication status selection for the first user;

a communications request from the second user requesting to communicate with the first user;

instructions executable by the processor that when executed by the processor cause the processor to;

retrieve the entity identifiers for entities;

validate the user registration identifiers;

compare the communications request from the second user with the communication status selection of the first user; and

when the communications request satisfies the communication status selection, provide a communications method to use between the first user and the second user, according to the communication status selection of the first user.

18. The system of claim 17, wherein the registration identifier identifies a license to practice and one or more plurality of specializations for the user;

and

when the communications request of the second user does not satisfy the communication status selection of the first user, providing the second user an alternative user to select for communications, wherein the alternative user configured a communication status selection compatible with the communications request of the second user.

19. The system of claim 17, wherein validating the registration identifier comprises:

authenticating the user registration identifier by comparing the registration identifier with one of a plurality of authentication sources accessible through the network; and

communicating a validation result indicator that indicates whether the registration identifier is valid.

20. The system of claim 17, wherein the identifiers are retrieved from a plurality of accessible staff directories for hospitals and other healthcare facilities, and wherein the entities comprise hospitals and other healthcare facilities.

21. The system of claim 17, wherein storing each of the identifiers for the entities that correspond to the validated user, includes storing the identifier on a mobile device used by the user.

22. The system of claim 21, wherein the mobile device is configured to communicate audio and visual communications.

23. The system of claim 17, wherein the user communication status selection indicates the type of communication the user is willing to receive, including:

text messaging;

an email;

phone call.

24. The system of claim 17, wherein the user communication status selection indicates the type of communication the user is willing to receive based on the role of the requester requesting the communications.