Sign In to Follow Application
View All Documents & Correspondence

Doctor To Doctor Referral Network

Abstract: The present invention relates to the healthcare entity referral system for communicating and managing patient referral data between the target healthcare entity and the source healthcare entity. The present invention comprises a data collection module for receiving data associated with healthcare entities over a network platform, an input module for receiving query from a healthcare entity that is associated with patient, a computational module for processing the received query in accordance with one parameter and an output module for outputting information of the selected healthcare entity

Get Free WhatsApp Updates!
Notices, Deadlines & Correspondence

Patent Information

Application #
Filing Date
21 August 2018
Publication Number
09/2020
Publication Type
INA
Invention Field
COMPUTER SCIENCE
Status
Email
pujakr@gmail.com
Parent Application

Applicants

Jiyyo Innovations Pvt Ltd
House No. 329 Advocate Society Street Sector 49 A City Chandigarh State Chandigarh Pin Code 160047 Country INDIA

Inventors

1. Siddharth Angrish
House No. 329 Advocate Society Street Sector 49 A City Chandigarh State Chandigarh Pin Code 160047 Country INDIA

Specification

[0001] The present invention relates to a system for healthcare entity and more specifically to the healthcare entity referral system for communicating and managing patient referral data between the target healthcare entity and the source healthcare entity.
BACKGROUND OF THE INVENTION
[0002] Traditionally a referral is sent from a referring healthcare entity to a consulting healthcare entity in respect of a patient's medical conditions, is typically manually arranged by medical office assistant associated with the healthcare entity, who exchange telephonic calls, paper forms to arrange referral between the healthcare entities. Such an approach of referring is more time consuming and vulnerable to error.
[0003] Presently, there are several medical referral systems for electronically transmitting referral related information between referring healthcare entity to a consulting healthcare entity. But many of these systems rely on exchanging of email messaging to send referral information. Unfortunately, these systems are not secure.
[0004] Presently, there are several prior arts available which provided alternative solutions such as CN106934244 (A). The prior art discloses an intelligent terminal-based medical care cloud platform comprising a medical platform user side and a medical platform robot side. The medical platform user side comprises a system login system, an online registration unit, a disease guiding unit, an online consultation unit, an appointing and visiting unit, a user center unit and a medicine management unit and the medical platform robot side is used for processing personal information of doctors and appointed information of patients by the doctors, and comprises a doctor management unit, an appointing processing unit and a visiting record unit. Based on cloud services, a healthy medical cloud platform through an intelligent terminal provides medical services related to doctor visiting and consultation.

[0005] Another patent KR101192250B1 discloses a system for providing paramedic services. The system consists of the central server for receiving medical examination request message of a patient to be examined. The central server searches a local server which charges an area related to the patient. The central server transmits the medical examination request message to the searched local server. The local server determines a doctor who supervises the patient and a medical examiner based on the examination location and the examination time of the examination subject and transmitting the examination request message to the doctor terminal held by the doctor and also sends the doctor request sheet to the examiner terminal held by the examiner together with the examination location and the examination time information of the examinee to receive the examination result data for the examinee and sends the examination result data to the central server.
[0006] Likewise, patent WO2015142716 (Al) discloses a method of managing productivity with a peer-to-peer system. The disclosed information handling system (IHS) may receive information from a user who may be a medical professional such as a doctor or other medical practitioner. The IHS may include an information store, revenue tool, doctor referral tool, specialist referral tool, facility referral tool, consultation tool and a samples tool. The user may use the revenue tool of the IHS to view the predicted revenue of upcoming appointments in his or her schedule. The revenue tool of the IHS may predict the revenue of appointments by utilizing information from the information store of the IHS. These tools may automatically increase the revenue of the user by scheduling additional appointments and referring appointments to other medical professionals in the peer-to-peer network.
[0007] However, all these above prior art systems are complicated to use.
SUMMARY OF THE INVENTION
[0008] The main objective of the present invention is to overcome the limitations of the prior arts and addresses problems relating to patient referral management by providing healthcare referral system.

[0009] The present invention provides a referral system which comprises a data collection module for receiving data associated with healthcare entities over a network platform, an input module for receiving patient's query from the source healthcare entity. The system further comprises a computational module for processing the received patient query and the received data associated with healthcare entities in accordance with one parameter. The output module is configured to output information of the target healthcare entity detected by the computational module for the source healthcare entity.
[0010] In other embodiment, the output module enables the source healthcare entity to select at least one of the target healthcare entity from the output information for referral system.
[0011] In another embodiment the source healthcare entity is enabled to book an appointment with the target healthcare entity.
BRIEF DESCRIPTION OF THE DRAWINGS:
[0012] The following drawings illustrates exemplary embodiment; however, they are helpful in illustrating objects, features and advantages of the present invention because the present invention will be more apparent from the following detailed description taken in conjunction with accompanying drawings in which:
[0013] Fig.l illustrates the block diagram of the present invention.
[0014] Fig.2 illustrates the schematic view of the present invention.
[0015] Fig.3 illustrates the other schematic view of the present invention.
[0016] Fig.4 illustrates another schematic view of the present invention.
DETAILED DESCRIPTION OF THE INVENTION
[0017] Reference will now be made in detail to the exemplary embodiment (s) of the invention. References to "one embodiment," "at least one embodiment," "an embodiment," "one example," "an example," "for example," and soon indicate that the embodiment(s) or example(s) may include a particular feature, structure, characteristic, property, element, or limitation but that not every embodiment or example necessarily includes that particular feature, structure,

characteristic, property, element, or limitation. Further, repeated use of the phrase "in an embodiment" does not necessarily refer to the same embodiment.
[0018] The present invention is a healthcare entity referral system for communicating and managing patient referral data between the target healthcare entity and the source healthcare entity.
[0019] Fig.l illustrates the block diagram of the present invention. According to the present invention the referral system (100) comprises:
a. a data collection module (102) which is enabled to collect the data of the healthcare
entities over the network platform. Herein, the healthcare entities are the source
healthcare entities (202) and target healthcare entities (204) and the collected data is
enabled to create a profile of the entities in the system. The source healthcare entities
(202) are the entities referring the patients to the target healthcare entities (204) and the
target healthcare entities (204) are the entities fulfilling the requirements of accepting
the referred patient. The data collected from target healthcare entities (204) at the time
of profile creation is the static data and is one of but not limited to historical treatment
success rate, response time, location, pricing information, insurance facility, holiday
information, qualification, available resources and any combination thereof. During
patient referral, the data collection module is enabled to receive real-time data from the
healthcare entities, wherein the real-time data is at least one of but not limited to number
of resources available at source healthcare entity (202) at the time of disposal, availability
of the target healthcare entities (204), holiday information for available target healthcare
entities, number of available resources for handling the patient at target healthcare
entities, pricing information (if there are any revisions) or any combination thereof.
b. an input module (104) which is enabled to receive at least one query of the patient from
the source healthcare entity (202). The source healthcare entity (202) during raising the
referral of the patient is enabled to transmit at least one query of the patient to the
input module (104). The at least one query is at least one of but not limited to a
diagnosis information, ailment information, symptoms, patient information, the

preferred location of the healthcare entity, pricing, medical insurance facility, or any combination thereof.
c. computational module (106) enabled to process the at least one query received from
the input module (104). The computational module (106) upon receiving the at least
one query, processes the information by comparing it with the data present in the data
collection module. Thereafter, the compared data is transmitted to the database (108)
of the referral system (100) for ranking the available target healthcare entities (204).
The ranking of the target healthcare entity (204) is enabled by the pre-defined rules of
the database (108).
d. an output module (110), which is the display of the referral system (100) is enabled to
display the ranking of all available target healthcare entities (204). The user at the
source healthcare entity (202) is then connected to the user of the first ranked target
healthcare entity (204) for referring the patient.
[0020] Fig.2 illustrates the schematic view of the present invention. The first display (100a) of the referral system (100) for the target healthcare entity is shown, where the user of the target healthcare entity fill-out following static data to create a profile of the target healthcare entity on the referral system (100):
• Name
• Location
• Timings
• Services available
• Pricing information for the available services
• Response Time
• Ambulance facility
• List of available Doctors along with their background information
• Other information including: List of Holidays, Insurance facilities, Number of available resources for handling the patient at the time of emergency.

[0021] Fig.3 illustrates the other schematic view of the present invention. The first display (100b) of the referral system (100) for the source healthcare entity is shown where the user of the source healthcare entity fill out following real-time data at the time of referring the patient:
• Name
• Location
• Patient's Personal details- Name, Age, Gender
• Patient's Health Condition
• Preferred location of the target healthcare entity
• Important Medical History associated with the patient
• Time to transfer the patient
• Other Information such as- Pricing, medical insurance facility and ambulance facility (If the source healthcare entity is looking for ambulance facility).
[0022] Fig.4 illustrates another schematic view of the present invention. The second display (100c) of the referral system (100) for the source healthcare entity is shown having the list of ranked target healthcare entities available for transfer of the patient.
[0023] In the preferred embodiment, the user from the target healthcare entity (204) creates a profile on the first display (100a) referral system (100). The profile of the target healthcare entity (204) has static data such as but not limited to name of the target healthcare entity, location, timings, services available, pricing information for the available services, response time, ambulance facility, list of available doctors along with their background information and other information such as list of holidays, insurance facilities, number of available resources for handling the patient at the time of emergency. At the time of patient transfer or patient referral the user from source healthcare entity (202) input real-time data in the form of a query in the first display (100b) of their referral system (100). Herein, the real-time data includes following but not limited to:
• Name and location of the source healthcare entity (202),
• Patient's personal details such as name, age, gender, address, patient's health condition,

08682278
• Patient's health condition including diagnosis information, ailment information, symptoms
• Important medical history of the patient such as if the patient is diabetic, or have an allergy to certain medicines
• Preferred location of the healthcare entity
• Time to transfer the patient- The user here defines the time within which the patient needs to be referred. If the case is critical and need immediate help or define the number of hours/days patient is enabled to visit the target healthcare entity (204).
• Other information: Pricing, medical insurance facility and ambulance facility. In case of emergency, the source healthcare entity (202) notifies the requirement of the ambulance. For example, if all the ambulances of the source healthcare entity (202) are busy and the patient needs an immediate transfer, the source healthcare entity (202) is enabled to ask for ambulance facility from the target healthcare facility (204).
Herein, the source healthcare entity (202) is also a target healthcare entity (204) and vice-versa. The static data incorporated in the first display (100a) of the target healthcare entity's referral system (100) is collected by the data collection module (102) and the real-time data incorporated in the first display (100b) of the source healthcare entity's referral system (100) is collected by the input module (104) of the referral system (100). The input module (104) of the referral system (100) transmits the received information to the computational module (106) for processing. The computational module (106) process the received information and process it by matching it with the information of target healthcare entities (204) available in the data collection module (102). Also, the information is matched with the predefined rules available in the database (108) of the referral system (100) which enable the computational module (106) to rank the available target healthcare entities (204) according to the need of the source healthcare entity (202). The processed data from the computational module is then transmitted to the output module (110) of the referral system (100). The output module (110) is enabled to display the available ranked target healthcare entities (204) at the second display (100c) of the source healthcare entity's referral system (100). The user at the source healthcare entity (202) is enabled to connect to the user of the first ranked target healthcare entity (204) through the

second display (100c) of the referral system (100). The selected target healthcare entity (204) is enabled to get a notification and details about the source healthcare entity (202).
[0024] In other embodiment, upon receiving the list of the ranked target healthcare entities the user is enabled to view the details of each target healthcare entity and is further enabled to select one out of all target healthcare entities.
[0025] In another embodiment, upon receiving the list of the ranked target healthcare entities the user is enabled to view the details of each target healthcare entity and is further enabled to book an appointment at the target healthcare entity of his/her choice.
[0026] In yet another embodiment, the at least one user from each source and target healthcare entities are enabled to connect over the call. The details for the call are transmitted over the network platform once the source healthcare entity has selected target healthcare entity. The data such as but not limited to patient's condition, patient referral details/timing, ambulance information or appointment with the doctor of the target healthcare entity is transmitted over the call.
[0027] In yet another embodiment, the at least one user from each source and target healthcare entities are enabled to connect over the email. The details for the emails are transmitted over the network platform once the source healthcare entity has selected target healthcare entity. The user from the source healthcare entity is enabled to email the patient's medical history details and reports over an email.
[0028] In yet another embodiment, the at least one user from each source healthcare entity is enabled to transmit the current location of the patient transferred over the network platform. The current location of the patient is also enabled to be transmitted over the network platform so that the target healthcare entity is enabled to track the arrival of the patient.
[0029] While the invention has been described in detail with specific reference to preferred embodiments thereof, it is understood that variations and modifications thereof may be made without departing from the true spirit and scope of the invention.

WE CLAIM

1. A source healthcare entity to target healthcare entities referral system comprising: a. a data collection module configured to receive data, at least partially, associated
with the source healthcare entity and target healthcare entities connected over a
network platform; b. an input module configured to receive at least one query, associated with at least
one patient, from the source healthcare entity associated with the patient; c. a computational module configured to process the at least one query and to
derive the context of the query based on predefined rules located in a database,
wherein the computational module is further enabled to rank the target health
care entities with respect to the context of the query; and d. an output module configured to output the first ranked target healthcare entity
amongst the target healthcare entities. 2. The source healthcare entity to target healthcare entities referral system of claim 1,
wherein the data is the real-time data associated with the healthcare entity. 3. The source healthcare entity to target healthcare entities referral system of claim 1 or 2,
wherein the data associated with the healthcare entity is at least one of availability of the
healthcare entity, number of resources available at the disposal of the healthcare entity
or any combination thereof. 4. The source healthcare entity to target healthcare entities referral system of claim 1,
wherein the data is the static data associated with the target healthcare entities. 5. The source healthcare entity to target healthcare entities referral system of claim 1 or 4,
wherein the data is the historical treatment success rate, response time, location, pricing
information, insurance facility, holiday information, qualification, available resources and
any combination thereof. 6. The source healthcare entity to target healthcare entities referral system of claim 1,
wherein the query comprises at least one of a diagnosis information, ailment information,
symptoms, patient information, preferred location of the healthcare entity, pricing,
medical insurance facility, or any combination thereof.
7. The source healthcare entity to target healthcare entities referral system of claim 1,
wherein the source healthcare entity associated with the patient is enabled to book an
appointment with the selected target healthcare entity over the network platform. 8. The source healthcare entity to target healthcare entities referral system of claim 8,
wherein an information related to the patient referral is shared with the selected target
healthcare entity over the network platform. 9. The source healthcare entity to target healthcare entities referral system of claim 9,
wherein an information related to the patient arrival is shared with the source healthcare
entity associated with the patient over the network platform.
, Description:DETAILED DESCRIPTION OF THE INVENTION
[0017] Reference will now be made in detail to the exemplary embodiment (s) of the invention.
References to “one embodiment,” “at least one embodiment,” “an embodiment,” “one
example,” “an example,” “for example,” and so on indicate that the embodiment(s) or example(s)
may include a particular feature, structure, characteristic, property, element, or limitation but
that not every embodiment or example necessarily includes that particular feature, structure,
characteristic, property, element, or limitation. Further, repeated use of the phrase “in an
embodiment” does not necessarily refer to the same embodiment.
[0018] The present invention is a healthcare entity referral system for communicating and
managing patient referral data between the target healthcare entity and the source healthcare
entity.
[0019] Fig.1 illustrates the block diagram of the present invention. According to the present
invention the referral system (100) comprises:
a. a data collection module (102) which is enabled to collect the data of the healthcare
entities over the network platform. Herein, the healthcare entities are the source
healthcare entities (202) and target healthcare entities (204) and the collected data is
enabled to create a profile of the entities in the system. The source healthcare entities
(202) are the entities referring the patients to the target healthcare entities (204) and the
target healthcare entities (204) are the entities fulfilling the requirements of accepting
the referred patient. The data collected from target healthcare entities (204) at the time
of profile creation is the static data and is one of but not limited to historical treatment
success rate, response time, location, pricing information, insurance facility, holiday
information, qualification, available resources and any combination thereof. During
patient referral, the data collection module is enabled to receive real-time data from the
healthcare entities, wherein the real-time data is at least one of but not limited to number
of resources available at source healthcare entity (202) at the time of disposal, availability
of the target healthcare entities (204), holiday information for available target healthcare
entities, number of available resources for handling the patient at target healthcare
entities, pricing information (if there are any revisions) or any combination thereof. b. an input module (104) which is enabled to receive at least one query of the patient from
the source healthcare entity (202). The source healthcare entity (202) during raising the
referral of the patient is enabled to transmit at least one query of the patient to the
input module (104). The at least one query is at least one of but not limited to a
diagnosis information, ailment information, symptoms, patient information, the
preferred location of the healthcare entity, pricing, medical insurance facility, or any
combination thereof. c. computational module (106) enabled to process the at least one query received from
the input module (104). The computational module (106) upon receiving the at least
one query, processes the information by comparing it with the data present in the data
collection module. Thereafter, the compared data is transmitted to the database (108)
of the referral system (100) for ranking the available target healthcare entities (204).
The ranking of the target healthcare entity (204) is enabled by the pre-defined rules of
the database (108). d. an output module (110), which is the display of the referral system (100) is enabled to
display the ranking of all available target healthcare entities (204). The user at the
source healthcare entity (202) is then connected to the user of the first ranked target
healthcare entity (204) for referring the patient.
[0020] Fig.2 illustrates the schematic view of the present invention. The first display (100a) of
the referral system (100) for the target healthcare entity is shown, where the user of the target
healthcare entity fill-out following static data to create a profile of the target healthcare entity
on the referral system (100):
• Name • Location • Timings • Services available • Pricing information for the available services • Response Time • Ambulance facility • List of available Doctors along with their background information • Other information including: List of Holidays, Insurance facilities, Number of available
resources for handling the patient at the time of emergency.
[0021] Fig.3 illustrates the other schematic view of the present invention. The first display
(100b) of the referral system (100) for the source healthcare entity is shown where the user of
the source healthcare entity fill out following real-time data at the time of referring the patient:
• Name • Location • Patient’s Personal details- Name, Age, Gender • Patient’s Health Condition • Preferred location of the target healthcare entity • Important Medical History associated with the patient • Time to transfer the patient • Other Information such as- Pricing, medical insurance facility and ambulance facility (If
the source healthcare entity is looking for ambulance facility).
[0022] Fig.4 illustrates another schematic view of the present invention. The second display
(100c) of the referral system (100) for the source healthcare entity is shown having the list of
ranked target healthcare entities available for transfer of the patient.
[0023] In the preferred embodiment, the user from the target healthcare entity (204) creates a
profile on the first display (100a) referral system (100). The profile of the target healthcare
entity (204) has static data such as but not limited to name of the target healthcare entity,
location, timings, services available, pricing information for the available services, response
time, ambulance facility, list of available doctors along with their background information and
other information such as list of holidays, insurance facilities, number of available resources for
handling the patient at the time of emergency. At the time of patient transfer or patient
referral the user from source healthcare entity (202) input real-time data in the form of a query
in the first display (100b) of their referral system (100). Herein, the real-time data includes
following but not limited to:
• Name and location of the source healthcare entity (202), • Patient’s personal details such as name, age, gender, address, patient’s health
condition,
• Patient’s health condition including diagnosis information, ailment information,
symptoms • Important medical history of the patient such as if the patient is diabetic, or have an
allergy to certain medicines • Preferred location of the healthcare entity • Time to transfer the patient- The user here defines the time within which the patient
needs to be referred. If the case is critical and need immediate help or define the
number of hours/days patient is enabled to visit the target healthcare entity (204). • Other information: Pricing, medical insurance facility and ambulance facility. In case of
emergency, the source healthcare entity (202) notifies the requirement of the
ambulance. For example, if all the ambulances of the source healthcare entity (202) are
busy and the patient needs an immediate transfer, the source healthcare entity (202) is
enabled to ask for ambulance facility from the target healthcare facility (204).
Herein, the source healthcare entity (202) is also a target healthcare entity (204) and vice-versa.
The static data incorporated in the first display (100a) of the target healthcare entity’s referral
system (100) is collected by the data collection module (102) and the real-time data
incorporated in the first display (100b) of the source healthcare entity’s referral system (100) is
collected by the input module (104) of the referral system (100). The input module (104) of the
referral system (100) transmits the received information to the computational module (106) for
processing. The computational module (106) process the received information and process it by
matching it with the information of target healthcare entities (204) available in the data
collection module (102). Also, the information is matched with the predefined rules available in
the database (108) of the referral system (100) which enable the computational module (106)
to rank the available target healthcare entities (204) according to the need of the source
healthcare entity (202). The processed data from the computational module is then transmitted
to the output module (110) of the referral system (100). The output module (110) is enabled to
display the available ranked target healthcare entities (204) at the second display (100c) of the
source healthcare entity’s referral system (100). The user at the source healthcare entity (202)
is enabled to connect to the user of the first ranked target healthcare entity (204) through the
second display (100c) of the referral system (100). The selected target healthcare entity (204) is
enabled to get a notification and details about the source healthcare entity (202).
[0024] In other embodiment, upon receiving the list of the ranked target healthcare entities the
user is enabled to view the details of each target healthcare entity and is further enabled to
select one out of all target healthcare entities.
[0025] In another embodiment, upon receiving the list of the ranked target healthcare entities
the user is enabled to view the details of each target healthcare entity and is further enabled to
book an appointment at the target healthcare entity of his/her choice.
[0026] In yet another embodiment, the at least one user from each source and target
healthcare entities are enabled to connect over the call. The details for the call are transmitted
over the network platform once the source healthcare entity has selected target healthcare
entity. The data such as but not limited to patient’s condition, patient referral details/timing,
ambulance information or appointment with the doctor of the target healthcare entity is
transmitted over the call.
[0027] In yet another embodiment, the at least one user from each source and target
healthcare entities are enabled to connect over the email. The details for the emails are
transmitted over the network platform once the source healthcare entity has selected target
healthcare entity. The user from the source healthcare entity is enabled to email the patient’s
medical history details and reports over an email.
[0028] In yet another embodiment, the at least one user from each source healthcare entity is
enabled to transmit the current location of the patient transferred over the network platform.
The current location of the patient is also enabled to be transmitted over the network platform
so that the target healthcare entity is enabled to track the arrival of the patient.
[0029] While the invention has been described in detail with specific reference to preferred
embodiments thereof, it is understood that variations and modifications thereof may be made
without departing from the true spirit and scope of the invention.

Documents

Application Documents

# Name Date
1 201811031220-STATEMENT OF UNDERTAKING (FORM 3) [21-08-2018(online)].pdf 2018-08-21
2 201811031220-POWER OF AUTHORITY [21-08-2018(online)].pdf 2018-08-21
3 201811031220-FORM FOR STARTUP [21-08-2018(online)].pdf 2018-08-21
4 201811031220-FORM FOR SMALL ENTITY(FORM-28) [21-08-2018(online)].pdf 2018-08-21
5 201811031220-FORM 1 [21-08-2018(online)].pdf 2018-08-21
6 201811031220-EVIDENCE FOR REGISTRATION UNDER SSI(FORM-28) [21-08-2018(online)].pdf 2018-08-21
7 201811031220-DECLARATION OF INVENTORSHIP (FORM 5) [21-08-2018(online)].pdf 2018-08-21
8 201811031220-COMPLETE SPECIFICATION [21-08-2018(online)].pdf 2018-08-21