U.S. patent application number 14/542096 was filed with the patent office on 2015-03-12 for systems and methods for managing data.
The applicant listed for this patent is Gregory Grant, Matthew John Seidel, John Vanderhoof. Invention is credited to Gregory Grant, Matthew John Seidel, John Vanderhoof.
Application Number | 20150073826 14/542096 |
Document ID | / |
Family ID | 48903874 |
Filed Date | 2015-03-12 |
United States Patent
Application |
20150073826 |
Kind Code |
A1 |
Grant; Gregory ; et
al. |
March 12, 2015 |
SYSTEMS AND METHODS FOR MANAGING DATA
Abstract
System and methods are disclosed, one method can comprise the
steps of receiving a request for a diagnostic message, receiving a
selection of diagnostic information, retrieving at least a portion
of the selected diagnostic information, generating the requested
diagnostic message, wherein the diagnostic message comprises the
portion of the selected diagnostic information, and transmitting
the requested diagnostic message.
Inventors: |
Grant; Gregory; (Paradise
Valley, AZ) ; Vanderhoof; John; (Scottsdale, AZ)
; Seidel; Matthew John; (Scottsdale, AZ) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Grant; Gregory
Vanderhoof; John
Seidel; Matthew John |
Paradise Valley
Scottsdale
Scottsdale |
AZ
AZ
AZ |
US
US
US |
|
|
Family ID: |
48903874 |
Appl. No.: |
14/542096 |
Filed: |
November 14, 2014 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
13757382 |
Feb 1, 2013 |
|
|
|
14542096 |
|
|
|
|
61594171 |
Feb 2, 2012 |
|
|
|
Current U.S.
Class: |
705/2 |
Current CPC
Class: |
G16H 40/20 20180101;
G16H 40/63 20180101; H04L 51/08 20130101 |
Class at
Publication: |
705/2 |
International
Class: |
G06F 19/00 20060101
G06F019/00 |
Claims
1. A method comprising: receiving a request for a diagnostic
message, wherein the request for the diagnostic message comprises
information relating to an intended recipient of the requested
diagnostic message; receiving a selection of diagnostic
information; selecting a pre-defined template based upon the
information relating to the intended recipient of the requested
diagnostic or the selection of diagnostic information, or both,
wherein the pre-defined template has a plurality of data fields;
retrieving at least a portion of the selected diagnostic
information based upon one or more data fields of the plurality of
data fields of the pre-defined template; and allowing accessing to
the requested diagnostic message by a recipient device associated
with the intended recipient, based on the pre-defined template,
wherein the diagnostic message comprises the portion of the
selected diagnostic information.
2. The method of claim 1, wherein the request for the diagnostic
message comprises information relating to a requester of the
requested diagnostic message.
3. The method of claim 1, wherein the portion of the selected
diagnostic is retrieved from a remote storage device.
4. The method of claim 1, wherein the diagnostic information
comprises one or more of patient data, medical data, and a medical
image.
5. The method of claim 1, further comprising receiving a
confirmation message indicating whether the diagnostic message is
accessed by the recipient device.
6. The method of claim 1, wherein the intended recipient is a
healthcare provider having a practice specialty and the pre-defined
template is selected based on the practice specialty of the
healthcare provider.
7. A method comprising: providing availability information relating
to one or more of a plurality of on-call professionals; receiving a
selection of at least one of the plurality of on-call professionals
in response to the provided availability information; receiving a
selection of diagnostic information; retrieving information
relating to the selection of the at least one of the plurality of
on-call professionals and the selection of diagnostic information;
generating a diagnostic message comprising at least a portion of
the retrieved information; and allowing access to the diagnostic
message by a recipient device associated with the at least one of
the plurality of on-call professionals.
8. The method of claim 7, wherein the portion of the retrieved
information is retrieved based upon one or more data fields of a
pre-defined template associated with the at least one of the
plurality of on-call professionals.
9. The method of claim 7, wherein the diagnostic information
comprises one or more of patient data, medical data, and a medical
image.
10. The method of claim 7, further comprising receiving a
confirmation message indicating whether the diagnostic message is
accessed by the recipient device.
11. The method of claim 7, further comprising selecting a
pre-defined template based upon the selection of the at least one
of the plurality of users or the selection of diagnostic
information, or both, wherein the pre-defined template has a
plurality of data fields, and wherein the portion of the retrieved
information is retrieved based upon the one or more data fields of
the pre-defined template.
12. The method of claim 11, wherein the at least one of the
plurality of on-call professionals is a healthcare provider having
a practice specialty and the pre-defined template is selected based
on the practice specialty of the healthcare provider.
13. A method comprising: accessing a first diagnostic message
including diagnostic information; rendering at least a portion of
the diagnostic information; providing a plurality of first response
options, wherein at least one of the first response options is
customized based upon the rendered diagnostic information;
receiving a selection of one of the plurality of first response
options; and initiating a communication session based upon the
selection of the one of the plurality of first response
options.
14. The method of claim 13, wherein the first diagnostic message
comprises information relating to a sender of the received first
diagnostic message.
15. The method of claim 13, wherein the received first diagnostic
message comprises a pre-defined template.
16. The method of claim 15, wherein the first diagnostic message is
received by a healthcare provider having a practice specialty and
the pre-defined template is customized based on the practice
specialty of the healthcare provider.
17. The method of claim 13, wherein the diagnostic information
comprises one or more of patient data, medical data, and a medical
image.
18. The method of claim 13, wherein the plurality of response
options comprises one or more of a pre-defined diagnosis option, a
forward the first diagnostic message option, establish
communication channel, a communicate with sender option, and a
generate a custom diagnosis option.
19. The method of claim 13, further comprising authenticating a
recipient of the first diagnostic message prior to rendering the
diagnostic information.
20. The method of claim 13, further comprising: receiving a second
diagnostic message relating to the first diagnostic message;
providing a plurality of second response options, wherein at least
one of the second response options is customized based upon the
first diagnostic message, the second diagnostic message, and the
selection of the one of the plurality of first response options;
receiving a selection of one of the plurality of second response
options; and providing a response message based upon the selection
of the one of the plurality of second response options.
Description
CROSS REFERENCE TO RELATED APPLICATIONS
[0001] This application is a continuation of U.S. patent
application Ser. No. 13/757,382, filed on Feb. 1, 2013, which
claims the benefit of U.S. Provisional Patent Application No.
61/594,171 filed on Feb. 2, 2012, each of which is incorporated
herein by reference in its entirety.
BACKGROUND
[0002] Communication of diagnostic information and/or patient
information can be tedious and time consuming Currently, many
physicians and care-providers rely on paging devices and voice
calls/messages to communicate diagnostic information and
consultation information to and from hospitals, offices, and other
physicians, care providers and users of such information. For
example, in an emergency room, a physician seeing a patient with an
orthopedic problem has to page the orthopedic surgeon on call. The
physician can often wait approximately 5-10 minutes or even longer
for the orthopedic surgeon to respond. When the orthopedic surgeon
finally responds, the orthopedic surgeon is typically provided only
basic diagnostic information about the patient about which the
emergency room physician is consulting. The orthopedic surgeon then
has to find means to view certain patient diagnostic information,
most notably images, such as x-rays. Computer terminals are not
always conveniently available. Accordingly, the orthopedic surgeon
must travel to a local hospital or office or another area to access
a computer for viewing patient information and diagnostic
information. Once the orthopedic surgeon has viewed the patient and
diagnostic information, the orthopedic surgeon must communicate a
response to the consulting physician in the emergency room.
Typically, the orthopedic surgeon can rely on telephone
communication to respond to the consulting physician with
consulting information.
[0003] The current methods of consultation and remote diagnosis do
not provide an efficient means of communicating diagnostic
information and consultation responses to and from remote users.
Furthermore, the current systems and methods do not provide a means
to coordinate availability and schedules of recipients of
consultation requests. These and other shortcomings are addressed
by the present disclosure.
SUMMARY
[0004] It is to be understood that both the following general
description and the following detailed description are exemplary
and explanatory only and are not restrictive, as claimed. In an
aspect, provided are methods and systems for managing data and
transmitting information. The system and methods of the present
disclosure can be used to communication diagnostic information and
response to and from remote users, such as physicians and care
providers.
[0005] In an aspect, the systems and methods of the present
disclosure minimize the communication inefficiencies and reduce the
amount of wasted time that the emergency room physician and the
patient have to deal with during their encounter. As an example,
using the disclosed system and methods, an emergency room provider
can determine that an orthopedist is necessary for consultation.
The emergency room physician can chart like normal, but the data
that is inputted into an electronic medical record (EMR) can be
transmitted to a non-proprietary server, in which this information
can be shared with any provider whether or not they have access to
the proprietary system. The information inputted can be transmitted
to the non-proprietary system with a single click of a mouse.
[0006] In an aspect, a discrete packet of information (e.g.,
Patient History Objective findings and Test results Over Network or
PHOTON/Photon/photon) can be created once the emergency room
provider requires consultation. As an example, the Photon can be
sent to a cloud based server, which can be compatible with all or
substantially all software platforms. The server can then push the
Photon or packet of information to the remote physician or user,
and the remote user is able to review the discrete packet of
information with a user device, such as a smart device, tablet,
computing device, or the like.
[0007] In an aspect, the remote user can review the information
after logging-in in a secure manner. As an example, after reviewing
the basic information and reviewing image information such as
x-rays, the remote user can respond by transmitting a message
(e.g., in a similar manner that the message was delivered) back to
the original emergency room physician with diagnosis and
disposition information. In an aspect, the emergency room physician
can review the response provided by the remote user in a timely and
secure manner.
[0008] In an aspect, a method can comprise receiving a request for
information such as a diagnostic message. A selection of diagnostic
information can also be received. At least a portion of the
selected diagnostic information can be retrieved. The diagnostic
message can be generated, wherein the diagnostic message comprises
the portion of the selected diagnostic information. The diagnostic
message can be transmitted to a recipient such as the requestor of
information.
[0009] In an aspect, a method can comprise receiving a request for
information such as a diagnostic message. Availability information
relating to one or more of a plurality of users can be provided. A
selection of at least one of the plurality of users can be
received. A selection of diagnostic information can be received.
Information relating to the selection of the at least one of the
plurality of users and the selection of diagnostic information can
be provided. The diagnostic message can be generated, wherein the
diagnostic message comprises at least a portion of the selected
diagnostic information. The diagnostic message can be transmitted
to the at least one of the plurality of users selected.
[0010] In an aspect, a method can comprise receiving a first
diagnostic message and receiving a second diagnostic message
relating to the first diagnostic message. A plurality of response
options can be provided, wherein at least one of the response
options is customized based upon the first diagnostic message or
the second diagnostic message, or both. A selection of one of the
plurality of response options can be received. A responsive message
can be provided based upon the selection of the one of the
plurality of response options.
[0011] In an aspect, a method can comprise receiving a diagnostic
message including diagnostic information. The diagnostic
information can be rendered. A plurality of response options can be
provided, wherein at least one of the response options is
customized based upon the diagnostic information. A selection of
one of the plurality of response options can be received. A message
based upon the selection of the one of the plurality of response
options can be generated and/or transmitted.
[0012] In another aspect, a system can comprise a memory for
storing diagnostic information and a processor in communication
with the memory. The processor can be configured to: receive a
request for a diagnostic message; receive a selection of a first
portion of the diagnostic information; retrieve a sub-portion of
the selected first portion of the diagnostic information; generate
the requested diagnostic message, wherein the diagnostic message
comprises the sub-portion of the selected first portion of the
diagnostic information; and provide the requested diagnostic
message.
[0013] Additional advantages will be set forth in part in the
description which follows or may be learned by practice. The
advantages will be realized and attained by means of the elements
and combinations particularly pointed out in the appended claims.
It is to be understood that both the foregoing general description
and the following detailed description are exemplary and
explanatory only and are not restrictive, as claimed.
BRIEF DESCRIPTION OF THE DRAWINGS
[0014] The accompanying drawings, which are incorporated in and
constitute a part of this specification, illustrate embodiments and
together with the description, serve to explain the principles of
the methods and systems:
[0015] FIG. 1 is a block diagram of an exemplary network;
[0016] FIG. 2 is a block diagram of an exemplary computing
device;
[0017] FIG. 3A is a flow chart of an exemplary method;
[0018] FIG. 3B is a flow chart of an exemplary method;
[0019] FIG. 3C is a flow chart of an exemplary method;
[0020] FIG. 4 is a flow chart of an exemplary method;
[0021] FIG. 5 is a representation of a user interface;
[0022] FIG. 6 is a representation of a user interface;
[0023] FIG. 7 is a representation of a user interface;
[0024] FIG. 8 is a representation of a user interface;
[0025] FIG. 9 is a representation of a user interface;
[0026] FIG. 10 is a representation of a user interface;
[0027] FIG. 11 is a representation of a user interface;
[0028] FIG. 12 is a representation of a user interface;
[0029] FIG. 13 is a representation of a user interface;
[0030] FIG. 14 is a representation of a user interface;
[0031] FIG. 15 is a representation of a user interface;
[0032] FIG. 16 is a representation of a user interface;
[0033] FIG. 17 is a representation of a user interface;
[0034] FIG. 18 is a representation of a user interface;
[0035] FIG. 19 is a representation of a user interface;
[0036] FIG. 20 is a representation of a user interface;
[0037] FIG. 21 is a representation of a user interface;
[0038] FIG. 22 is a representation of a user interface;
[0039] FIG. 23 is a representation of a user interface;
[0040] FIG. 24 is a representation of a user interface;
[0041] FIG. 25 is a representation of a user interface;
[0042] FIG. 26 is a representation of a user interface; and
[0043] FIG. 27 is a representation of a user interface.
DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS
[0044] Before the present methods and systems are disclosed and
described, it is to be understood that the methods and systems are
not limited to specific methods, specific components, or to
particular implementations. It is also to be understood that the
terminology used herein is for the purpose of describing particular
embodiments only and is not intended to be limiting.
[0045] As used in the specification, PHOTON/Photon is an acronym
which can stand for Patient History Objective findings and Test
results Over Network. As used herein, PHOTON/Photon can comprise
patient information, diagnostic information, medical images, and
the like. In general, the Photon system provides a way to
communicate a packet of patient information in a secure manner
between healthcare professionals and, more importantly, allows
communication regarding that information. The PHOTON packet can
comprise a subset data relating to a patient, such as a small,
highly relevant, customized set of data regarding a specific
problem that a patient may be experiencing. The term PHOTON/Photon
is used for example and illustration only. PHOTON/Photon is not
intended to limit the underlying data represented thereby. Any data
can be represented and is not limited by the term PHOTON/Photon to
any particular definition or classification.
[0046] As used in the specification and the appended claims, the
singular forms "a," "an" and "the" include plural referents unless
the context clearly dictates otherwise. Ranges may be expressed
herein as from "about" one particular value, and/or to "about"
another particular value. When such a range is expressed, another
embodiment includes from the one particular value andor to the
other particular value. Similarly, when values are expressed as
approximations, by use of the antecedent "about," it will be
understood that the particular value forms another embodiment. It
will be further understood that the endpoints of each of the ranges
are significant both in relation to the other endpoint, and
independently of the other endpoint.
[0047] "Optional" or "optionally" means that the subsequently
described event or circumstance may or may not occur, and that the
description includes instances where said event or circumstance
occurs and instances where it does not.
[0048] Throughout the description and claims of this specification,
the word "comprise" and variations of the word, such as
"comprising" and "comprises," means "including but not limited to,"
and is not intended to exclude, for example, other additives,
components, integers or steps. "Exemplary" means "an example of"
and is not intended to convey an indication of a preferred or ideal
embodiment. "Such as" is not used in a restrictive sense, but for
explanatory purposes.
[0049] Disclosed are components that can be used to perform the
disclosed methods and systems. These and other components are
disclosed herein, and it is understood that when combinations,
subsets, interactions, groups, etc. of these components are
disclosed that while specific reference of each various individual
and collective combinations and permutation of these may not be
explicitly disclosed, each is specifically contemplated and
described herein, for all methods and systems. This applies to all
aspects of this application including, but not limited to, steps in
disclosed methods. Thus, if there are a variety of additional steps
that can be performed it is understood that each of these
additional steps can be performed with any specific embodiment or
combination of embodiments of the disclosed methods.
[0050] The present methods and systems may be understood more
readily by reference to the following detailed description of
preferred embodiments and the Examples included therein and to the
Figures and their previous and following description.
[0051] As will be appreciated by one skilled in the art, the
methods and systems may take the form of an entirely hardware
embodiment, an entirely software embodiment, or an embodiment
combining software and hardware aspects. Furthermore, the methods
and systems may take the form of a computer program product on a
computer-readable storage medium having computer-readable program
instructions (e.g., computer software) embodied in the storage
medium. More particularly, the present methods and systems may take
the form of web-implemented computer software. Any suitable
computer-readable storage medium may be utilized including hard
disks, CD-ROMs, optical storage devices, or magnetic storage
devices.
[0052] Embodiments of the methods and systems are described below
with reference to block diagrams and flowchart illustrations of
methods, systems, apparatuses and computer program products. It
will be understood that each block of the block diagrams and
flowchart illustrations, and combinations of blocks in the block
diagrams and flowchart illustrations, respectively, can be
implemented by computer program instructions. These computer
program instructions may be loaded onto a general purpose computer,
special purpose computer, or other programmable data processing
apparatus to produce a machine, such that the instructions which
execute on the computer or other programmable data processing
apparatus create a means for implementing the functions specified
in the flowchart block or blocks.
[0053] These computer program instructions may also be stored in a
computer-readable memory that can direct a computer or other
programmable data processing apparatus to function in a particular
manner, such that the instructions stored in the computer-readable
memory produce an article of manufacture including
computer-readable instructions for implementing the function
specified in the flowchart block or blocks. The computer program
instructions may also be loaded onto a computer or other
programmable data processing apparatus to cause a series of
operational steps to be performed on the computer or other
programmable apparatus to produce a computer-implemented process
such that the instructions that execute on the computer or other
programmable apparatus provide steps for implementing the functions
specified in the flowchart block or blocks.
[0054] Accordingly, blocks of the block diagrams and flowchart
illustrations support combinations of means for performing the
specified functions, combinations of steps for performing the
specified functions and program instruction means for performing
the specified functions. It will also be understood that each block
of the block diagrams and flowchart illustrations, and combinations
of blocks in the block diagrams and flowchart illustrations, can be
implemented by special purpose hardware-based computer systems that
perform the specified functions or steps, or combinations of
special purpose hardware and computer instructions.
[0055] FIG. 1 illustrates various aspects of an exemplary network
in which the present methods and systems can operate. The present
disclosure relates to systems and methods for managing data such as
medical related information. Those skilled in the art will
appreciate that present methods may be used in systems that employ
both digital and analog equipment. One skilled in the art will
appreciate that provided herein is a functional description and
that the respective functions can be performed by software,
hardware, or a combination of software and hardware.
[0056] The system and network 100 can comprise a client device 102
in communication (e.g., directly and/or via a network) with a
computing device 104 such as a server, for example. The computing
device 104 can be disposed locally or remotely relative to the
client device 102. As an example, the client device 102 and the
computing device 104 can be in communication via a private or
public network such as the Internet. Other forms of communications
can be used such as wired and wireless telecommunication channels,
for example.
[0057] In an aspect, the client device 102 can be an electronic
device such as a computer, a server, a smartphone, a laptop, a
tablet, or other device capable of communicating with the computing
device 104. As an example, the client device 102 can comprise a web
browser 106 for providing an interface to a user to interact with
the client device 102 and/or the computing device 104. The web
browser 106 can be any interface for presenting information to the
user and receiving a user feedback, such as Internet Explorer,
Mozilla Firefox, Google Chrome, Safari, or the like. Other
software, hardware, and/or interfaces can be used to provide
communication between the user and one or more of the client device
102 and the computing device 104. As an example, the web browser
106 can request or query various files from a local source and/or a
remote source. As a further example, the client device 102 can be
configured to transmit data to the computing device 104. Other
devices and interfaces can be used to allow a user to
intercommunicate with the computing device 104. In an aspect, the
client device 102 can be authenticated via user/device credentials
prior to communicating secure information to the computing device
104 or other device. As an example, the client device 102 can
comprise software to facilitate secure communication and/or
authentication.
[0058] In an aspect, the client device 102 can be configured to
communicate (e.g., directly and/or via a network) with an
information system 108 (e.g. emergency room information system,
hospital information system, imaging system, scheduling system,
etc.). As an example, the information system 108 can comprise a
database. As a further example, the information system 108 can
comprise hardware (e.g., terminal) and or software components for
storing and/or processing patient information such as imagining
data 110 (e.g., x-rays, CT scans, EKGs, etc.). Other information
can be stored and/or processed by the information system 108, such
as scheduling data 112 (e.g., relating to "on-call" physicians,
employee schedules, or other schedule and time related data). In an
aspect, the client device 102 can send/receive information to/from
the information system 108 for storing information in the
information system 108 and/or retrieving information from the
information system 108. As an example, the client device 102 can
comprise an instruction set or rule set to control the transmission
of data to/from the information system 108. As a further example,
the client device 102 can be configured to push data to the
information system 108 when an input data is received by the client
device 102. Any data or portion of data inputted to the client
device 102 can be selectively and/or automatically transmitted to
the information system 108 or another storage medium. In an aspect,
the client device 102 can be authenticated via user/device
credentials prior to communicating secure information to the
information system 108 or other device. As an example, the client
device 102 can comprise software to facilitate secure communication
and/or authentication.
[0059] In an aspect, the information system 108 can comprise data
relating to a hospital, clinic, medical facility, emergency room,
or other professional environment. Other data can be stored and
processed by the information system 108. As an example, the
information system 108 can be located remotely from the client
device 102. As a further example, the information system 108 can be
integrated with the client device 102 or in communication with the
client device over a local network.
[0060] In an aspect, the computing device 104 can be a server for
communicating with the client device 102. As an example, the
computing device 104 can be configured to receive message requests
(e.g. diagnostic messages) from another device, such as the client
device 102. The computing device 104 can be configured to process
the message request and generate/transmit a message in response to
the request. As a further example, the computing device 104 can
manage the intercommunication between the client device 102 and a
database 114 for sending and receiving data therebetween. In an
aspect, the database 114 can store a plurality of files (e.g. web
pages). As an example, the client device 102 can request a file
from the database 114. As a further example, the client device 102
can retrieve a file from the database 114.
[0061] In an aspect, the database 114 can store a plurality of user
records 115. As an example, one or more of the user records 115 can
comprise user information 116 relating to a client or other user.
In an aspect, the user information 116 can comprise contact
information, professional/license information, preferences, and
mailing lists, for example.
[0062] In an aspect, one or more user records 115 can comprise user
settings 118 relating to one or more users, physicians,
consultants, healthcare providers, professionals, message
recipients, and the like. As an example, the user settings 118 can
comprise demographic information, contact information, user
credentials or login credentials, a unique identifier or password,
and preferences (e.g. message preferences, including pre-defined
information fields to be populated and included in diagnostic
messages).
[0063] In an aspect, the database 114 can store a plurality of
patient records 119. As an example, one or more of the patient
records 119 can comprise patient information 120 relating to a
client or other user. In an aspect, the patient information 120 can
comprise contact information, medical information, insurance
information, preferences, and other information relating to patient
and/or treatment, for example. Other information can be stored in
the database 114 and/or associated with a particular patient record
119.
[0064] In an aspect, one or more message templates 121 can be
retrieved by the computing device 104 (e.g., stored in the database
114 or in other storage devices/media). As an example one or more
message templates 121 can comprise a pre-defined layout of a
plurality of information fields. As a further example, each of the
message templates 121 can comprise a plurality of information
fields. In an aspect, the information fields of the message
templates can be populated from data stored in the database 114.
However, the information fields of the message templates 121 can be
populated from any data source. Any number of information fields
representing any data or information can be included in the message
templates 121. Any number of message templates 121 can be stored
and/or generated. As an example, one or more message templates 121
can comprises one or more data fields relating to one or more of
the following: demographics, such as first name, middle name, last
name, date of birth, SSN, address, driver's license information,
insurance information, second insurance information, health
information; chief complaint (e.g. what is patient is primarily
complaining about?); history of present illness (e.g. what happened
to the patient? how did it happen? where did it happen? associated
symptoms, pain level, etc.); past medical history; past surgical
history; medications; allergies: social history (e.g., history of
smoking, drinking, drugs, employment, living situation); review of
systems (e.g. history of fever, headache, chest pain, shortness of
breath; physical examination information; general appearance (e.g.,
what the patient looks like--thin, obese, disheveled, clean, etc.);
mood and affect; psychiatric information; neurologic exam;
integumentary exam (skin); cardiovascular exam (blood vessels);
studies, including labs such as complete blood count, blood
electrolytes, liver function tests, urinalysis, drug screen,
alcohol level, arterial blood gas, cardiac enzymes, troponin,
erythrocyte sedimentation rate, C-reactive protein; imaging
including X-rays, MRI, CT, ultrasound, echocardiogram, bone scan,
PET scan, EKG; audio/video, clinical photographs;
impression/diagnosis, such as triage nurse impression, physician
assistant impression, ED physician impression; ED Action Plan;
and/or disposition and follow-up appointment.
[0065] In an aspect, the message can comprise complete patient
encounter information. The users that will receive the diagnostic
message can have the option of selecting a discrete amount of
highly relevant information for their particular specialty. Other
users can choose to accept all the information. Each specialty will
be different from each other with regards to what information is
most relevant.
[0066] In an aspect, the computing device 104 can comprise a rules
engine 122 for applying one or more
rules/filter/instructions/settings to the messages (e.g.,
diagnostic messages). As an example, the rules engine 122 can
retrieve preferences and instructions from the user settings 118 in
order to customize a particular message format and/or content
associated with a particular recipient. In this way, a recipient
can define a particular information and formation of the
information to be included in any messages received by the
particular recipient. As a further example, certain information is
customizable and other information and formatting is standard. In
an aspect the rules engine 122 can customize format/content based
upon any number of rules or instructions, such as information about
the sender or recipient, information specific to the client or
patient/subject of the message, specialty, time of day, means of
communication, level of urgency, and other rules.
[0067] In an aspect, a user device 124 can be in communication with
the computing device 104. The computing device 104 can be disposed
locally or remotely relative to the user device 124. As an example,
the user device 124 and the computing device 104 can be in
communication via a private or public network, such as the
Internet. Other forms of communications can be used such as wired
and wireless telecommunication channels, for example.
[0068] In an aspect, the user device 124 can be an electronic
device, such as a computer, a server, a smartphone, a laptop, a
tablet, or other device capable of communicating with the computing
device 104. As an example, the user device 124 can comprise a
communication element, such as web browser 126 for providing an
interface to a user to interact with the client device 102, the
computing device 104, the information system 108, and/or an office
system 125. The web browser 126 can be any interface for presenting
information to the user and receiving a user feedback, such as
Internet Explorer, Mozilla Firefox, Google Chrome, Safari, or the
like. Other software, hardware, and/or interfaces can be used to
provide communication between the user and one or more of the user
device 124 and the client device 102, the computing device 104, the
information system 108, and/or an office system 125. As an example,
the web browser 126 can request or query various files from a local
source and/or a remote source. As a further example, the user
device 124 can be configured to transmit data to the computing
device 104 via various protocols and over various networks. Other
devices and interfaces can be used to allow a user to
intercommunicate with the computing device 104. In an aspect, the
client device 102 can be authenticated via user/device credentials
prior to communicating secure information to the client device 102,
the computing device 104, the information system 108, and/or an
office system 125, or other device. As an example, the client
device 102 can comprise software to facilitate secure communication
and/or authentication. In an aspect, a user can use the user device
124 to communicate with client device 102 to transmit/receive data
therebetween. As an example, the client device 102 can operate as a
proxy for the user device 104 when communicating with the computing
device 104, the information system 108, and/or an office system
125. As a further example, the user device 124 may not be
authenticated with one or more of the computing device 104, the
information system 108, and/or an office system 125. Accordingly,
the user device 124 can communicate information to the client
device 102 using a unique identifier (e.g., temporary or
persistent), and the client device 102 can communication with one
or more of the computing device 104, the information system 108,
and/or an office system 125 on behalf of the user device 124.
[0069] In an aspect, the office system 125 can comprise information
relating to a particular professional office, such as a medical
office, law office, or other group of professionals. As an example,
the office system 125 can be located remote from the information
system 108 and/or the computing system 104. In an aspect, the
office system 125 can comprise a patient data 128 (e.g., EMR)
and/or a scheduling data 130. As an example, the patient data 128
can relate to a client or other user. In an aspect, patient data
128 can comprise contact information, medical information,
insurance information, preferences, and other information relating
to patient and/or treatment, for example. Other information can be
stored in office system 125 and/or associated with a particular
user/patient. As a further example, the scheduling data 130 can
comprise information relating to a schedule of one or more
physicians, healthcare providers, staff, technicians,
professionals, or other office personnel. In an aspect, the client
device 102 can be authenticated via user/device credentials prior
to communicating secure information to the office system 125 or
other device. As an example, the client device 102 can comprise
software to facilitate secure communication and/or
authentication.
[0070] In an exemplary aspect, the methods and systems can be
implemented on a computing system such as computing device 201 as
illustrated in FIG. 2 and described below. By way of example, one
or more of the client device 102, the computing device 104, and the
user device 124 of FIG. 1 can be a computer as illustrated in FIG.
2. Similarly, the methods and systems disclosed can utilize one or
more computers to perform one or more functions in one or more
locations. FIG. 2 is a block diagram illustrating an exemplary
operating environment for performing the disclosed methods. This
exemplary operating environment is only an example of an operating
environment and is not intended to suggest any limitation as to the
scope of use or functionality of operating environment
architecture. Neither should the operating environment be
interpreted as having any dependency or requirement relating to any
one or combination of components illustrated in the exemplary
operating environment.
[0071] The present methods and systems can be operational with
numerous other general purpose or special purpose computing system
environments or configurations. Examples of well known computing
systems, environments, and/or configurations that can be suitable
for use with the systems and methods comprise, but are not limited
to, personal computers, server computers, laptop devices, and
multiprocessor systems. Additional examples comprise set top boxes,
programmable consumer electronics, network PCs, minicomputers,
mainframe computers, distributed computing environments that
comprise any of the above systems or devices, and the like.
[0072] The processing of the disclosed methods and systems can be
performed by software components. The disclosed systems and methods
can be described in the general context of computer-executable
instructions, such as program modules, being executed by one or
more computers or other devices. Generally, program modules
comprise computer code, routines, programs, objects, components,
data structures, etc. that perform particular tasks or implement
particular abstract data types. The disclosed methods can also be
practiced in grid-based and distributed computing environments
where tasks are performed by remote processing devices that are
linked through a communications network. In a distributed computing
environment, program modules can be located in both local and
remote computer storage media including memory storage devices.
[0073] FIG. 2 is a block diagram illustrating an exemplary
operating environment for performing the disclosed methods. This
exemplary operating environment is only an example of an operating
environment and is not intended to suggest any limitation as to the
scope of use or functionality of operating environment
architecture. Neither should the operating environment be
interpreted as having any dependency or requirement relating to any
one or combination of components illustrated in the exemplary
operating environment.
[0074] The present methods and systems can be operational with
numerous other general purpose or special purpose computing system
environments or configurations. Examples of well known computing
systems, environments, and/or configurations that can be suitable
for use with the systems and methods comprise, but are not limited
to, personal computers, server computers, laptop devices, and
multiprocessor systems. Additional examples comprise set top boxes,
programmable consumer electronics, network PCs, minicomputers,
mainframe computers, distributed computing environments that
comprise any of the above systems or devices, and the like.
[0075] The processing of the disclosed methods and systems can be
performed by software components. The disclosed systems and methods
can be described in the general context of computer-executable
instructions, such as program modules, being executed by one or
more computers or other devices. Generally, program modules
comprise computer code, routines, programs, objects, components,
data structures, etc. that perform particular tasks or implement
particular abstract data types. The disclosed methods can also be
practiced in grid-based and distributed computing environments
where tasks are performed by remote processing devices that are
linked through a communications network. In a distributed computing
environment, program modules can be located in both local and
remote computer storage media including memory storage devices.
[0076] Further, one skilled in the art will appreciate that the
systems and methods disclosed herein can be implemented via a
general-purpose computing device in the form of a computer 201. The
components of the computer 201 can comprise, but are not limited
to, one or more processors or processing units 203, a system memory
212, and a system bus 213 that couples various system components
including the processor 203 to the system memory 212. In the case
of multiple processing units 203, the system can utilize parallel
computing.
[0077] The system bus 213 represents one or more of several
possible types of bus structures, including a memory bus or memory
controller, a peripheral bus, an accelerated graphics port, and a
processor or local bus using any of a variety of bus architectures.
By way of example, such architectures can comprise an Industry
Standard Architecture (ISA) bus, a Micro Channel Architecture (MCA)
bus, an Enhanced ISA (EISA) bus, a Video Electronics Standards
Association (VESA) local bus, an Accelerated Graphics Port (AGP)
bus, and a Peripheral Component Interconnects (PCI), a PCI-Express
bus, a Personal Computer Memory Card Industry Association (PCMCIA),
Universal Serial Bus (USB) and the like. The bus 213, and all buses
specified in this description can also be implemented over a wired
or wireless network connection and each of the subsystems,
including the processor 203, a mass storage device 204, an
operating system 205, financial software 206, financial data 207, a
network adapter 208, system memory 212, an Input/Output Interface
210, a display adapter 209, a display device 211, and a human
machine interface 202, can be contained within one or more remote
computing devices 214a,b,c at physically separate locations,
connected through buses of this form, in effect implementing a
fully distributed system.
[0078] The computer 201 typically comprises a variety of computer
readable media. Exemplary readable media can be any available media
that is accessible by the computer 201 and comprises, for example
and not meant to be limiting, both volatile and non-volatile media,
removable and non-removable media. The system memory 212 comprises
computer readable media in the form of volatile memory, such as
random access memory (RAM), and/or non-volatile memory, such as
read only memory (ROM). The system memory 212 typically contains
data such as financial data 207 and/or program modules such as
operating system 205 and financial software 206 that are
immediately accessible to and/or are presently operated on by the
processing unit 203.
[0079] In another aspect, the computer 201 can also comprise other
removable/non-removable, volatile/non-volatile computer storage
media. By way of example, FIG. 2 illustrates a mass storage device
204 which can provide non-volatile storage of computer code,
computer readable instructions, data structures, program modules,
and other data for the computer 201. For example and not meant to
be limiting, a mass storage device 204 can be a hard disk, a
removable magnetic disk, a removable optical disk, magnetic
cassettes or other magnetic storage devices, flash memory cards,
CD-ROM, digital versatile disks (DVD) or other optical storage,
random access memories (RAM), read only memories (ROM),
electrically erasable programmable read-only memory (EEPROM), and
the like.
[0080] Optionally, any number of program modules can be stored on
the mass storage device 204, including by way of example, an
operating system 205 and financial software 206. Each of the
operating system 205 and financial software 206 (or some
combination thereof) can comprise elements of the programming and
the financial software 206. Financial data 207 can also be stored
on the mass storage device 104. Financial data 207 can be stored in
any of one or more databases known in the art. Examples of such
databases comprise. DB2.RTM., Microsoft.RTM. Access, Microsoft.RTM.
SQL Server, Oracle.RTM., mySQL, PostgreSQL, and the like. The
databases can be centralized or distributed across multiple
systems.
[0081] In another aspect, the user can enter commands and
information into the computer 201 via an input device (not shown).
Examples of such input devices comprise, but are not limited to, a
keyboard, pointing device (e.g., a "mouse"), a microphone, a
joystick, a scanner, tactile input devices such as gloves, and
other body coverings, and the like. These and other input devices
can be connected to the processing unit 203 via a human machine
interface 202 that is coupled to the system bus 213, but can be
connected by other interface and bus structures, such as a parallel
port, game port, an IEEE 1394 Port (also known as a Firewire port),
a serial port, or a universal serial bus (USB).
[0082] In yet another aspect, a display device 211 can also be
connected to the system bus 213 via an interface, such as a display
adapter 209. It is contemplated that the computer 201 can have more
than one display adapter 209 and the computer 201 can have more
than one display device 211. For example, a display device can be a
monitor, an LCD (Liquid Crystal Display), or a projector. In
addition to the display device 211, other output peripheral devices
can comprise components such as speakers (not shown) and a printer
(not shown) which can be connected to the computer 201 via
Input/Output Interface 210. Any step and/or result of the methods
can be output in any form to an output device. Such output can be
any form of visual representation, including, but not limited to,
textual, graphical, animation, audio, tactile, and the like.
[0083] The computer 201 can operate in a networked environment
using logical connections to one or more remote computing devices
214a,b,c. By way of example, a remote computing device can be a
personal computer, portable computer, a server, a router, a network
computer, a peer device or other common network node, and so on.
Logical connections between the computer 201 and a remote computing
device 214a,b,c can be made via a local area network (LAN) and a
general wide area network (WAN). Such network connections can be
through a network adapter 208. A network adapter 208 can be
implemented in both wired and wireless environments. Such
networking environments are conventional and commonplace in
offices, enterprise-wide computer networks, intranets, and the
Internet 215.
[0084] For purposes of illustration, application programs and other
executable program components such as the operating system 205 are
illustrated herein as discrete blocks, although it is recognized
that such programs and components reside at various times in
different storage components of the computing device 201, and are
executed by the data processor(s) of the computer. An
implementation of financial software 206 can be stored on or
transmitted across some form of computer readable media. Any of the
disclosed methods can be performed by computer readable
instructions embodied on computer readable media. Computer readable
media can be any available media that can be accessed by a
computer. By way of example and not meant to be limiting, computer
readable media can comprise "computer storage media" and
"communications media." "Computer storage media" comprise volatile
and non-volatile, removable and non-removable media implemented in
any methods or technology for storage of information such as
computer readable instructions, data structures, program modules,
or other data. Exemplary computer storage media comprises, but is
not limited to, RAM, ROM, EEPROM, flash memory or other memory
technology, CD-ROM, digital versatile disks (DVD) or other optical
storage, magnetic cassettes, magnetic tape, magnetic disk storage
or other magnetic storage devices, or any other medium which can be
used to store the desired information and which can be accessed by
a computer.
[0085] The methods and systems can employ artificial intelligence
(AI) techniques such as machine learning and iterative learning.
Examples of such techniques include, but are not limited to expert
systems, case based reasoning. Bayesian networks, behavior based
AI, neural networks, fuzzy systems, evolutionary computation (e.g.
genetic algorithms), swarm intelligence (e.g. ant algorithms), and
hybrid intelligent systems (e.g. Expert inference rules generated
through a neural network or production rules from statistical
learning).
[0086] In an aspect, FIG. 3A illustrates an exemplary method for
generating and/or transmitting a message such as a diagnostic
message or consultation message. In an aspect, in step 302, a
request for information such as a message (e.g., diagnostic
message, PHOTON, or the like) can be received, for example, by the
computing device 104. As an example, the request can be received by
the client device 102 or the user device 124. However, other
devices and systems can be used to transmit the request. In an
aspect, an interface is provided to allow a user/client to request
a message. As an example, the client device 102 can include a user
interface with a "request message" icon or engageable button. Other
means of requesting the message can be used. As a further example,
once a user/client selects the "request message" icon, the
user/client can be prompted to provide and/or select particular
diagnostic information to be included in the message.
[0087] In an aspect, the client can select/provide a particular
information (e.g., diagnostic information, requester information,
recipient information, etc.) to be included in the message and can
submit the request for the message. In an aspect, in step 304, the
selection/provision of information can be received, for example, by
the computing device 104. As a further example, the computing
device 104 can process the request to retrieve at least a portion
of the selected information (e.g., diagnostic information), at step
306. In an aspect, the diagnostic information can comprises one or
more of patient data, medical data, and a medical image such as an
EKG, an X-ray and/or other medical images, audio or video.
[0088] In an aspect, the computing device 104 can retrieve the
selected/requested diagnostic information from any storage
medium(s). As an example, at least a portion of the
selected/requested diagnostic information can be retrieved from the
database 114. In an aspect, the user settings 118 associated with
an intended recipient of the diagnostic message can be applied to
the selected/requested diagnostic information. For example, a
particular user setting 118 may include pre-defined information
fields that should be included in the messages that are sent to the
user/recipient associated with the particular user setting 118.
Accordingly, even though the selected/requested diagnostic
information includes different information, the user setting 118
can take priority to retrieve a subset of the selected/requested
diagnostic information to be included in the message.
[0089] In an aspect, in step 308, a diagnostic message can be
generated. As an example, the diagnostic message can comprise the
portion of the selected diagnostic information. However, any
information can be included. In an aspect, the user settings 118
associated with an intended recipient of the diagnostic message are
applied to the selected/requested diagnostic information. For
example, a particular user setting 118 may include pre-defined
information fields to be included in the messages that are sent to
the user/recipient associated with the particular user setting 118.
Accordingly, even though the selected/requested diagnostic
information includes different information, the user setting 118
can take priority to retrieve a subset of the selected/requested
diagnostic information to be included in the message.
[0090] In an aspect, computing device 104 and/or database 114 can
comprise specialty templates for the messages. The specialty
templates can be specifically created for each specialty in a
particular profession, such as medicine/healthcare. For example, an
orthopedic template can consist of basic patient information as
well as x-rays. As a further example, a cardiology template can
consist of basic patient information as well as an EKG or
echocardiogram. As a further example, a gastroenterology template
will consist of basic information as well as an abdominal x-ray or
abdominal CT and perhaps lab information. The specialty templates
can be created prior to implementation of the specific specialty
message generation. Templates can be changed as needed. In an
aspect, the requester of a message can select a pre-defined
template for sending to an intended recipient.
[0091] In step 310, the message (e.g., diagnostic message) can be
transmitted. As an example, the message can be transmitted to a
recipient identified by the requester of the message. The message
can be transmitted over any communication path or network such as
the Internet and/or mobile telephone network.
[0092] In an aspect, the computing device 104 or other device can
track a status of one or more transmitted messages. As an example,
the following information can be tracked, time stamped, and or
stored: date/time the message was
generated/sent/received/forwarded/replied to; location (GPS) of
requester/recipient; recipient device: receipt confirmation: read
confirmation: no-read alert/feedback; and returned message alert.
Other information and a feedback can be tracked/stored. In an
aspect, the tracked information can be used to document the
timeline of the electronic consultation and provide some
medicolegal cushion for the emergency room providers who have to
rely strictly on a verbal order or recommendation from the
consultants. As an example, consultants who render medical
decisions verbally can now be formally documented in the medical
record when they made their diagnosis and what kind of treatment
was recommended. This provides an enormous amount of medicolegal
relief to ED providers.
[0093] FIG. 3B illustrates an exemplary method for managing a
diagnostic data based upon recipient availability. In an aspect, in
step 312, a request for information, such as a message (e.g.
diagnostic message, PHOTON, or the like), can be received, for
example, by the computing device 104. As an example, the request
can be received by the client device 102 or the user device 124.
However, other devices and systems can be used to transmit the
request. In an aspect, an interface is provided to allow a
user/client to request a message. As an example, the client device
102 can include a user interface with a "request message" icon or
engageable button. Other means of requesting the message can be
used. As a further example, once a user/client selects the "request
message" icon, the user/client can be prompted to provide and/or
select particular diagnostic information to be included in the
message.
[0094] In an aspect, in step 314, availability information relating
to one or more of a plurality of users or intended recipients can
be rendered to the client or requester. As an example, a calendar
of availability for one or more on-call professionals, such as
healthcare providers, can be rendered to the client or
requester.
[0095] In an aspect, in step 316, a selection of at least one of
the plurality of users or intended recipients can be received. In
an aspect, the client selects/provides a desired recipient of the
message based upon the availability information. As an example, the
client can select an available recipient from a list of one or more
on-call users. In an aspect, the selection/provision of
availability information is received, for example, by the computing
device 104.
[0096] In an aspect, the client selects/provides a particular
information (e.g., diagnostic information, requester information,
recipient information, etc.) to be included in the message and
submits the request for the message. In an aspect, in step 318, the
selection/provision of information is received, for example, by the
computing device 104. As a further example, the computing device
104 can process the request to retrieve at least a portion of the
selected information (e.g., diagnostic information), at step 320.
In an aspect the diagnostic information can comprises one or more
of patient data, medical data, and a medical image.
[0097] In an aspect, the computing device 104 can retrieve the
selected/requested diagnostic information from any storage
medium(s). As an example, at least a portion of the
selected/requested diagnostic information is retrieved from the
database 114. In an aspect, the user settings 118 associated with
an intended recipient of the diagnostic message are applied to the
selected/requested diagnostic information. For example, a
particular user setting 118 may include pre-defined information
fields that should be included in the messages that are sent to the
user/recipient associated with the particular user setting 118.
Accordingly, even though the selected/requested diagnostic
information includes different information, the user setting 118
can take priority to retrieve a subset of the selected/requested
diagnostic information to be included in the message.
[0098] In step 322, a diagnostic message can be generated. As an
example, the diagnostic message can comprise the portion of the
selected diagnostic information. However, any information can be
included. In an aspect, the user settings 118 associated with an
intended recipient of the diagnostic message are applied to the
selected/requested diagnostic information. For example, a
particular user setting 118 may include pre-defined information
fields to be included in the messages that are sent to the
user/recipient associated with the particular user setting 118.
Accordingly, even though the selected/requested diagnostic
information includes different information, the user setting 118
can take priority to retrieve a subset of the selected/requested
diagnostic information to be included in the message.
[0099] In an aspect, computing device 104 and/or database 114 can
comprise specialty templates for the messages. The specialty
templates can be specifically created for each specialty in a
particular profession, such as medicine/healthcare. For example, an
orthopedic template can consist of basic patient information as
well as x-rays. As a further example, a cardiology template can
consist of basic patient information as well as an EKG or
echocardiogram. As a further example, a gastroenterology template
will consist of basic information as well as an abdominal x-ray or
abdominal CT and perhaps lab information. The specialty templates
can be created prior to implementation of the specific specialty
message generation. Templates can be changed as needed. In an
aspect, the requester of a message can select a pre-defined
template for sending to an intended recipient.
[0100] In step 324, the message (e.g., diagnostic message) can be
transmitted. As an example, the message can be transmitted to a
recipient identified by the requester of the message. The message
can be transmitted over any communication path or network such as
the Internet and/or mobile telephone network.
[0101] In an aspect, the computing device 104 or other device can
track a status of one or more transmitted messages. As an example,
the following information can be tracked, time stamped, and or
stored: date/time the message was
generated/sent/received/forwarded/replied to; location (GPS) of
requester/recipient; recipient device; receipt confirmation; read
confirmation; no-read alert/feedback; and returned message alert.
Other information and a feedback can be tracked/stored.
[0102] In an aspect, the scheduling application (e.g., Photon
scheduling) can allow the client device 102 to set up appointments
at a user's/consultant's office (e.g., office system 125). As an
example, the client device 102 by accessing the scheduling data
130. As a further example, the user can reserve at least a portion
of an available schedule for a particular set of patients (e.g.,
emergency room patients). In aspect, an emergency room provider,
after requesting a diagnostic message, can use the scheduling
application to send the diagnostic message directly to the office
system 125 for direct uploading of diagnostic information into the
user's office EMR software and provide the patient the appointment
time, from the emergency room.
[0103] FIG. 3C illustrates an exemplary method for managing a
diagnostic data based upon recipient availability. In step 332, a
first message (e.g., diagnostic message) can be received by one or
more users. As an example, the first message can comprise
diagnostic information (e.g., injury description, images) to be
reviewed by the recipient. As a further example, the first message
can comprise a notification to retrieve diagnostic information from
a remote location. In an aspect, the first message can be received
by the client device 102. As an example, a confirmation message can
be transmitted to a sender indicating whether the diagnostic
message is received by a recipient device.
[0104] In another aspect, the user device 124 can be disposed in a
location that is not equipped to communicate directly with the
computing device 104. As an example, the client device 102 can
operate as a proxy for the user device 104 when communicating with
the computing device 104, the information system 108, and/or an
office system 125. As a further example, the user device 124 may
not be authenticated with one or more of the computing device 104,
the information system 108, and/or an office system 125. As such,
the user device 124 can communicate information to the client
device 102 using a unique identifier (e.g., temporary or
persistent) and the client device 102 can communication with one or
more of the computing device 104, the information system 108,
and/or an office system 125 on behalf of the user device 124. In an
aspect, a user can locate contact information for a particular
on-call physician. As an example, the user can transmit information
to the on-call physician using standard communication networks
(e.g., cellular, IP, media messaging, etc.). As a further example,
the information transmitted can be tagged with an anonymous
identifier that can later be associated with a particular medical
record or patient file in a secure environment.
[0105] In yet another aspect, the first message of step 332 can be
received by the client device 102 (e.g., a device associated
on-call physician). Accordingly, a user of the client device can
review the information comprised in the first message and can
determine if the subject patient to whom the information relates
should be transferred to a facility (e.g., emergency center,
hospital, specialists office, etc.) for treatment and/or further
analysis.
[0106] In step 334, a second message (e.g., diagnostic message,
follow-up message) can be received by one or more users. As an
example, the second message can comprise diagnostic information
(e.g., injury description, images, supplemental information) to be
reviewed by the recipient. As a further example, the second message
can comprise a notification to retrieve diagnostic information from
a remote location. In an aspect, the second message can be received
by the client device 102. As an example, the second message can
comprise supplemental information relating to the information
comprised in the first message.
[0107] In step 336, one or more response options can be provided to
the user. In an aspect, the response options can comprise one or
more of a pre-defined diagnosis option, a forwarding the diagnostic
message option, a communicating with sender option, and a
generating a custom diagnosis option. Other options can be
provided, such as an input option to allow the user to provide a
particular response. As an example, at least one of the response
options is customized based upon the diagnostic information.
[0108] In step 338, a selection of one of the plurality of response
options can be received. In an aspect, the user can provide a
particular information (e.g., consultation information, responses,
feedback) to be included in a response message. As an example, the
selection/provision of response information is received, for
example, by the computing device 104. As a further example, the
computing device 104 can process the response information to route
the response to an appropriate recipient such as the client device
102.
[0109] In step 340, information, such as a response message (e.g.,
responsive diagnostic message), can be transmitted based upon the
selection of the one of the plurality of response options. In an
aspect, the message can be transmitted to the requester of the
diagnostic information. As an example, the message can be
transmitted or forwarded to a user for further review and
consultation. As a further example, the message can be transmitted
to the office system 125, wherein, for example, the information in
the message can be used to update records stored in the office
system 125.
[0110] In an aspect, in response to receiving the first message of
step 332, the recipient can recommend that the subject patient be
admitted in an emergency center. As an example, the subject patient
can be admitted or checked-in to the emergency center. Detailed
patient information can be collected and stored. Tests and
procedures can be performed, such as X-rays and MRI's and the
collected information can be electronically stored. In another
aspect, a medical record or patient record can be created. As an
example, the information comprised in the first message can be
linked or associated with the newly created medical record, for
example, by associated the anonymous identifier with the medical
record. As a further example, information from one or more of the
first message and the second message can be merged into a single
record, such as a secure PDF. In an aspect, records can be stored
on a secure HIPPA compliant server. As an example, a location such
as a filename or URL can be used to identify and distinguish
between records. Accordingly, the record can be subsequently
accessed using the identifier.
[0111] FIG. 4 illustrates an exemplary method for managing received
diagnostic message. In an aspect, in step 402, a message (e.g.,
diagnostic message) can be received by one or more users. As an
example, the message can comprise diagnostic information to be
reviewed by the recipient. As a further example, the message can
comprise a notification to retrieve diagnostic information from a
remote location. In an aspect, the message can be received by the
user device 124. As an example, a confirmation message can be
transmitted to a sender indicating whether the diagnostic message
is received by a recipient device.
[0112] In step 404, the diagnostic information can be rendered to
the user. In an aspect, a recipient can be authenticated prior to
rendering the diagnostic information. As an example, the diagnostic
information can comprise audio, text, images, and video. As a
further example, the recipient/user can interact with the user
device 124 to review the diagnostic information. In an aspect, the
diagnostic information can be classified and/or organized by
pre-defined categories, such as objective, test results, images,
historical information, or the like. As an example, a confirmation
message can be transmitted to a sender indicating whether the
diagnostic message has been reviewed by a user.
[0113] In step 406, one or more response options can be provided to
the user. In an aspect, the response options can comprise one or
more of a pre-defined diagnosis option, a forwarding the diagnostic
message option, a communicating with sender option, and a
generating a custom diagnosis option. Other options can be
provided, such as an input option to allow the user to provide a
particular response. As an example, at least one of the response
options is customized based upon the diagnostic information.
[0114] In step 408, a selection of one of the plurality of response
options can be received. In an aspect, the user can provide a
particular information (e.g., consultation information, responses,
feedback) to be included in a response message. As an example, the
selection/provision of response information is received, for
example, by the computing device 104. As a further example, the
computing device 104 can process the response information to route
the response to an appropriate recipient such as the client device
102.
[0115] In step 410, information such as a message can be
transmitted based upon the selection of the one of the plurality of
response options. In an aspect, the message can be transmitted to
the requester of the diagnostic information. As an example, the
message can be transmitted or forwarded to a user for further
review and consultation. As a further example, the message can be
transmitted to the office system 125, wherein, for example, the
information in the message can be used to update records stored in
the office system 125.
[0116] In an aspect, FIG. 5 illustrates a user interface 500
comprising a message notification 502. As an example, a user must
be authenticated prior to viewing the message. As a further
example, the user interface 500 can comprise a password input 504
for receiving a password to authenticate the user/recipient. In an
aspect, the user interface 500 can comprise a keyboard or keypad to
receive an input from the user (e.g., to ensure HIPPA
compliance).
[0117] In an aspect, FIG. 6 illustrates a user interface 600
comprising a menu 602. As an example, the menus 602 can comprise
options for navigating and organizing one or more diagnostic
messages. In an aspect, a plurality of diagnostic messages can be
organized by most recent 602a, all active messages 602b (e.g.,
message that require action), and/or all photons 602c. As an
example, the interface 600 can comprise a homepage button 604,
wherein a user can adjust settings.
[0118] In an aspect, FIG. 7 illustrates a user interface 700
comprising a plurality of active messages icons 702 representing
messages that require action. As an example, the messages can
comprise sender information, a date, and a time. Other information
can be presented by the message icons.
[0119] In an aspect, FIG. 8 illustrates a user interface 800
comprising a plurality of setting options 802. As an example, the
settings options can be presented as part of a "My Photon" page or
homepage.
[0120] In an aspect, FIG. 9 illustrates a user interface 900
comprising an active message notification 902. As an example, the
notification 902 can comprise options, such as view now 904 and/or
a scrolling option (e.g., next 906) to facilitate the navigation
through a plurality of notifications. As a further example, the
user interface 900 can also comprise universal options 908 to
facilitate navigation between various user interface screens.
[0121] In an aspect, FIG. 10 illustrates a user interface 1000
comprising a message header 1002 identifying the particular
message. The user interface 1000 can comprise diagnostic
information, wherein the diagnostic information can be organized or
categorized. As an example, the categories can comprise history
1004, objective 1006, test/EKG/X-rays 1008 and/or other
classifications. As a further example, a plurality of response
options 1010 can be provided to the user. In an aspect, the
response options 1010 can comprise call 1012, transfer 1014, and/or
replay 1016. Other options can be provided.
[0122] In an aspect, FIG. 11 illustrates a user interface 1100
comprising a message header 1102 identifying the particular
message. In an aspect, the user interface 1100 can comprise
historical information 1104, such as a medical history, a
background to a particular incident, and/or past diagnostic
information. Other information can be provided.
[0123] In an aspect FIG. 12 illustrates a user interface 1200
comprising a message header 1202 identifying a particular message.
In an aspect, the user interface 1200 can comprise objective
information 1204, such as diagnostic information, medical
information, and/or a background to a particular incident. Other
information can be provided.
[0124] In an aspect, FIG. 13 illustrates a user interface 1300
comprising a message header 1302 identifying a particular message.
In an aspect, the user interface 1300 can comprise diagnostic
information 1304, such as lab results 1306, EKG 1308, and/or X-ray
1310. Other information can be provided.
[0125] In an aspect, FIG. 14 illustrates a user interface 1400
comprising a message header 1402 identifying a particular message.
In an aspect, the user interface 1400 can comprise detailed lab
information 1404, such as lab results or other test information.
Other information can be provided.
[0126] In an aspect, FIG. 15 illustrates a user interface 1500
comprising a message header 1502 identifying a particular message.
In an aspect, the user interface 1500 can comprise detailed
monitoring information 1504, such as EKG or other test information.
Other information can be provided. In an aspect, FIG. 16
illustrates a user interface 1600 can render an enlarged image 1602
representing a test result or medical information.
[0127] In an aspect, FIG. 17 illustrates a user interface 1700
comprising a message header 1702 identifying a particular message.
In an aspect, the user interface 1700 can comprise detailed imaging
information 1704, such as X-rays or other test information. Other
information can be provided. In an aspect, a plurality of images
1706 can be classified and rendered for a user to view.
[0128] In an aspect, FIG. 18 illustrates a user interface 1800
comprising a message header 1802 identifying a particular message.
In an aspect, the user interface 1800 can comprise a rendered image
1804, such as an X-ray or other test information. Other information
can be provided.
[0129] In an aspect, FIG. 19 illustrates a user interface 1900. In
an aspect, a user can select to transfer or forward the diagnostic
message and/or diagnostic information to another user or recipient.
As an example, the user interface 1900 can provide forwarding
options and/or selectable destinations such as an EMR 1902a, a
physician 1902b, an office 1902c (e.g., the office system 125), or
other destination. As a further example, the user interface 1900
can comprise a confirmation button 1904 for initiating the transfer
once a intended recipient has been provided.
[0130] In an aspect, FIG. 20 illustrates a user interface 2000
comprising a contact list, including a contact classification
header 2002 and an organized list 2004 of potential recipients of a
forwarded message and/or information.
[0131] In an aspect, FIG. 21 illustrates a user interface 2100
comprising a message header 2102 identifying a particular message.
In an aspect, a user can select to provide a replay to the
diagnostic message. As an example, the user interface 2100 can
comprise pre-defined response options 2104a, 2104b, 2104c, 2104d.
In an aspect, the response options 2104a, 2104b, 2104c, 2104d can
be defined based upon the diagnostic information included in the
message. As an example, the response options 2104a, 2104b, 2104c,
2104d can comprise a customizable response option 2104d to allow a
user to create a customized response message, as shown in further
detail in FIGS. 22-23. In an aspect, once a response message has
been generated (FIG. 23), the response message can be transmitted
to a recipient. As an example, a confirmation can be provided to
the user, as shown in FIG. 24, thereby completing an exemplary
cycle of consultation.
[0132] FIG. 25 illustrates a messaging screen (e.g., a Photon lite
screen). In an aspect, the messaging screen can facilitate secure
and unsecure communication of information to one or more devices
such as client devices 102 and/or user devices 124, for example. In
another aspect, the messaging screen can be rendered via user
device 124 that is disposed in a location that is not equipped to
communicate directly with the computing device 104. As an example,
the client device 102 can operate as a proxy for the user device
104 when communicating with the computing device 104, the
information system 108, and/or an office system 125. As a further
example, the user device 124 may not be authenticated with one or
more of the computing device 104, the information system 108,
and/or an office system 125. As such, the user device 124 can
communicate information to the client device 102 using a unique
identifier (e.g., temporary or persistent) and the client device
102 can communication with one or more of the computing device 104,
the information system 108, and/or an office system 125 on behalf
of the user device 124. In an aspect, a user can locate contact
information for a particular on-call physician. As an example, the
user can transmit information to the on-call physician using
standard communication networks (e.g. cellular, IP, media
messaging, etc.). As a further example, the information transmitted
can be tagged with an identifier (e.g., anonymous) that can later
be associated with a particular medical record or patient file in a
secure environment.
[0133] In an aspect, a patient code 2502 can be provided (e.g.,
manually or automatically) as an identifier for tracking
information associated with the patient code 2502. As an example, a
patient name 2504 can be provided (e.g., inputted), as opposed to
pulling patient information from the hospital EMR. As a further
example, information such as a description of the patient or
medical issue/condition can be provided. In another aspect, an
urgency option 2602 can be provided, as shown in FIG. 26. As an
example, the urgency option 2602 can be rendered to a user of the
messaging screen, whereby a selection of the urgency option
indicates a need for immediate care of the subject of the message.
As a further example, description information and/or the urgency
option 2602 can be associated with the patient code 2502 for
associating the images with a particular patient. In a further
aspect, one or more images can be provided (e.g., loaded, attached
to the message, etc.), as shown in FIG. 27. As an example, a camera
can be used to capture an image. The image can comprise video,
audio, still images, or the like. Captured images can be encrypted
and not saved to the device in a readable manner (or stored in a
secure hidden directory). Once the capture images are transmitted,
the images can be removed from the capturing device. As a further
example, one or more captured images can be associated with the
patient code 2502 for associating the images with a particular
patient.
[0134] In an aspect, the systems and methods described herein
provide a simple "click-by-click" process for both the emergency
room provider and the consultant. With regards to the emergency
room physician, once the scheduling packages open, a first click
can comprise opening an orthopedic call schedule. A second click
can comprise sending a Photon to the orthopedist that is on call,
thereby resulting in a two-click process. With regards to the
consultant physician, once the consultant has received notification
that the Photon is now on a smart device, the consultant can log
into an interface application (e.g., the Photon application),
constituting a first click. If there is only one Photon available,
it will automatically be populated. The consultant can be able to
review all the relevant information instantly. The consultant can
then click on an action button or transmit button to send the
appropriate response, thereby constituting a second click. However,
automation of certain events, such as push notifications,
populating an interface, displaying options, and the like can
facilitate a single click operation.
[0135] In an aspect, the systems and methods disclosed herein can
be integrated with one or more scheduling products to facilitate a
compliant scheduling program comprising the ability to send
compliant images and messages bidirectionally, and save such
messages into an EMR. As an example, users can use Photons to
transmit a "facesheet" for billing, wherein the can comprise a
patient's demographics, insurance information, contact
information.
[0136] Photons can be sent to virtually anyone, from a health care
provider, to industry (we can parse out non-HIPAA compliant
information). As an example, in-theatre military healthcare
applications can leverage the benefits of the systems and methods
disclosed herein.
[0137] While the methods and systems have been described in
connection with preferred embodiments and specific examples, it is
not intended that the scope be limited to the particular
embodiments set forth, as the embodiments herein are intended in
all respects to be illustrative rather than restrictive.
[0138] Unless otherwise expressly stated, it is in no way intended
that any method set forth herein be construed as requiring that its
steps be performed in a specific order. Accordingly, where a method
claim does not actually recite an order to be followed by its steps
or it is not otherwise specifically stated in the claims or
descriptions that the steps are to be limited to a specific order,
it is no way intended that an order be inferred, in any respect.
This holds for any possible non-express basis for interpretation,
including: matters of logic with respect to arrangement of steps or
operational flow; plain meaning derived from grammatical
organization or punctuation; the number or type of embodiments
described in the specification.
[0139] Throughout this application, various publications are
referenced. The disclosures of these publications in their
entireties are hereby incorporated by reference into this
application in order to more fully describe the state of the art to
which the methods and systems pertain.
[0140] It will be apparent to those skilled in the art that various
modifications and variations can be made without departing from the
scope or spirit. Other embodiments will be apparent to those
skilled in the art from consideration of the specification and
practice disclosed herein. It is intended that the specification
and examples be considered as exemplary only, with a true scope and
spirit being indicated by the following claims.
* * * * *