CA2895882C - Patient management of ocular health information - Google Patents
Patient management of ocular health information Download PDFInfo
- Publication number
- CA2895882C CA2895882C CA2895882A CA2895882A CA2895882C CA 2895882 C CA2895882 C CA 2895882C CA 2895882 A CA2895882 A CA 2895882A CA 2895882 A CA2895882 A CA 2895882A CA 2895882 C CA2895882 C CA 2895882C
- Authority
- CA
- Canada
- Prior art keywords
- patient
- information
- ocular health
- ocular
- clinic
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Abstract
A system a method is described that allows patient information for ocular health to be managed and provides for ordering of ocular health products through 3rd party suppliers.
Description
PATIENT MANAGMENT OF OCULAR HEALTH INFORMATION
TECHNICAL FIELD
The current disclosure relates to management of patient information and in particular to managing patient information regarding ocular health.
BACKGROUND
A patient may suffer from various eye conditions that may be treated with different medicines and/or products. For example, a patient may suffer from dry-eyes, which may be treated using eye drops.
Although ocular health conditions, such as dry-eyes, may be identified and corrected by optometrists or ophthalmologists, an improved patient experience for managing their ocular health, and in particular with regard to addressing dry-eye conditions is desirable.
SUMMARY
In accordance with the present disclosure, there is provided a system for patient management of ocular health information comprising: a network-connected server configured to provide: a database storing: patient information including contact information; and ocular condition assessment results; a mobile interface for receiving information and storing to the database, the information comprising information associated with results of a patient's ocular condition assessment; a clinic portal providing an access interface to the database to authorized users of an ocular health clinic; a user portal providing an access interface to patient information in the database;
and a product ordering interface for placing patient orders for ocular-health products; at least one portable device configured to present a patient with an ocular condition assessment and communicate the results to the mobile interface of the network-connected server.
In accordance with the present disclosure, there is further provided a method for patient management of ocular health information comprising; prompting and storing a patient for patient information including contact information; retrieving and presenting to the patient an ocular health assessment questionnaire; receiving and storing patients responses to the ocular health assessment questionnaire; presenting the ocular health questionnaire answers to a technician or an optometrist and /or ophthalmologist;
presenting the technician or the optometrist and /or ophthalmologist with one or more ocular health assessment test to perform; receiving an indication of one or more ocular health treatment products or services for the patient; and placing an order to a 3rd party provider for the indicated one or more ocular health treatment products or services.
BRIEF DESCRIPTION OF THE DRAWINGS
Further features and advantages of the present disclosure will become apparent from the following detailed description, taken in combination with the appended drawings, in which:
Figure 1 depicts components of a system for patient management of ocular health information;
Figure 2 depicts a method for managing ocular health information for patients;
Figure 3 depicts a method of using the system of Figure 1 in an optometry or ophthalmology clinic;
Figure 4 depicts a method for patient completion of ocular health assessment questionnaire; and Figure 5 depicts a method for technician or optometrist or ophthalmologist completion of ocular health assessment.
Figure 6 depicts an database structure for storing patient information.
DETAILED DESCRIPTION
The current application describes a management system for managing ocular health information for patients. As described in further detail, the management system allows clinics to effectively and efficiently manage patient's information with regard to ocular health conditions, such as dry eyes. The patient management system may allow clinics to provide ocular health assessment tests to patients and easily share and review the patient's assessment results with an optometrist and / or ophthalmologist.
Further, the patient management system may allow patients to order ocular-health products from one or more suppliers according to an ocular health plan provided by the patient's
TECHNICAL FIELD
The current disclosure relates to management of patient information and in particular to managing patient information regarding ocular health.
BACKGROUND
A patient may suffer from various eye conditions that may be treated with different medicines and/or products. For example, a patient may suffer from dry-eyes, which may be treated using eye drops.
Although ocular health conditions, such as dry-eyes, may be identified and corrected by optometrists or ophthalmologists, an improved patient experience for managing their ocular health, and in particular with regard to addressing dry-eye conditions is desirable.
SUMMARY
In accordance with the present disclosure, there is provided a system for patient management of ocular health information comprising: a network-connected server configured to provide: a database storing: patient information including contact information; and ocular condition assessment results; a mobile interface for receiving information and storing to the database, the information comprising information associated with results of a patient's ocular condition assessment; a clinic portal providing an access interface to the database to authorized users of an ocular health clinic; a user portal providing an access interface to patient information in the database;
and a product ordering interface for placing patient orders for ocular-health products; at least one portable device configured to present a patient with an ocular condition assessment and communicate the results to the mobile interface of the network-connected server.
In accordance with the present disclosure, there is further provided a method for patient management of ocular health information comprising; prompting and storing a patient for patient information including contact information; retrieving and presenting to the patient an ocular health assessment questionnaire; receiving and storing patients responses to the ocular health assessment questionnaire; presenting the ocular health questionnaire answers to a technician or an optometrist and /or ophthalmologist;
presenting the technician or the optometrist and /or ophthalmologist with one or more ocular health assessment test to perform; receiving an indication of one or more ocular health treatment products or services for the patient; and placing an order to a 3rd party provider for the indicated one or more ocular health treatment products or services.
BRIEF DESCRIPTION OF THE DRAWINGS
Further features and advantages of the present disclosure will become apparent from the following detailed description, taken in combination with the appended drawings, in which:
Figure 1 depicts components of a system for patient management of ocular health information;
Figure 2 depicts a method for managing ocular health information for patients;
Figure 3 depicts a method of using the system of Figure 1 in an optometry or ophthalmology clinic;
Figure 4 depicts a method for patient completion of ocular health assessment questionnaire; and Figure 5 depicts a method for technician or optometrist or ophthalmologist completion of ocular health assessment.
Figure 6 depicts an database structure for storing patient information.
DETAILED DESCRIPTION
The current application describes a management system for managing ocular health information for patients. As described in further detail, the management system allows clinics to effectively and efficiently manage patient's information with regard to ocular health conditions, such as dry eyes. The patient management system may allow clinics to provide ocular health assessment tests to patients and easily share and review the patient's assessment results with an optometrist and / or ophthalmologist.
Further, the patient management system may allow patients to order ocular-health products from one or more suppliers according to an ocular health plan provided by the patient's
2 optometrist and / or ophthalmologist.
The system described further below may be used to assist patients with ocular health problems, such as dry eye syndrome, as well as the patient's optometrist and /
or ophthalmologist in the tracking of symptoms, medication use and ordering, monitoring of treatment plan results and overall patient experience. Further, the system may allow automatic notifications to be sent to the patient, for example reminding the patient of an upcoming appointment, of re-ordering medication, etc.
The system may be used in various environments; however as described further below, it may be used in particular in an optometrist's and / or ophthalmologist's clinic to aid in the diagnosis and treatment of dry eye syndrome. The process begins at the optometrist and / or ophthalmologist's clinic where a patient may complete a questionnaire to determine if they are a candidate for the program for dry eye syndrome treatment. The questionnaire may be completed by a receptionist, technician, optometrist or ophthalmologist during a patient's visit. If the patient agrees to be part of the program, they may schedule a return to the clinic for a symptoms analysis, or if scheduling permits, the symptom analysis may be completed during the same visit. Using a tablet, or possibly a smart phone, the 'patient completes a survey regarding eye dryness and may watch a video describing symptoms and possible treatment options. Once completed, the patient may return the tablet to a clinic's receptionist or technician. After completing the dry-eye assessment questionnaire, the patient may be brought to a diagnostic room for further testing where a technician performs a battery of tests. The particular tests performed may depend upon the available equipment at the clinic. The technician, or other employee administering the dry eye assessment tests, records results and impressions on the tablet. The results of both the assessment questionnaire and assessment test results may be presented to a doctor or optometrist for review and discussion with the patient.
Based on the information, the ophthalmologist or optometrist may suggest one or more different treatment plans for addressing the patient's dry eye syndrome. The patient's treatment information, such as medication or other ocular health treatment products, may be entered by the patient, optometrist,
The system described further below may be used to assist patients with ocular health problems, such as dry eye syndrome, as well as the patient's optometrist and /
or ophthalmologist in the tracking of symptoms, medication use and ordering, monitoring of treatment plan results and overall patient experience. Further, the system may allow automatic notifications to be sent to the patient, for example reminding the patient of an upcoming appointment, of re-ordering medication, etc.
The system may be used in various environments; however as described further below, it may be used in particular in an optometrist's and / or ophthalmologist's clinic to aid in the diagnosis and treatment of dry eye syndrome. The process begins at the optometrist and / or ophthalmologist's clinic where a patient may complete a questionnaire to determine if they are a candidate for the program for dry eye syndrome treatment. The questionnaire may be completed by a receptionist, technician, optometrist or ophthalmologist during a patient's visit. If the patient agrees to be part of the program, they may schedule a return to the clinic for a symptoms analysis, or if scheduling permits, the symptom analysis may be completed during the same visit. Using a tablet, or possibly a smart phone, the 'patient completes a survey regarding eye dryness and may watch a video describing symptoms and possible treatment options. Once completed, the patient may return the tablet to a clinic's receptionist or technician. After completing the dry-eye assessment questionnaire, the patient may be brought to a diagnostic room for further testing where a technician performs a battery of tests. The particular tests performed may depend upon the available equipment at the clinic. The technician, or other employee administering the dry eye assessment tests, records results and impressions on the tablet. The results of both the assessment questionnaire and assessment test results may be presented to a doctor or optometrist for review and discussion with the patient.
Based on the information, the ophthalmologist or optometrist may suggest one or more different treatment plans for addressing the patient's dry eye syndrome. The patient's treatment information, such as medication or other ocular health treatment products, may be entered by the patient, optometrist,
3 ophthalmologist or other clinic staff. The system may then be used by the patient to order the medication and/or other products from the clinic. If the patient enrolls in the online ordering of the medication, the patient may receive reminders or notification via email, text messages, and/or automated phone calls to remind the patient to fill out goals and feelings as well as reminders to take their medication and order new medication as required. Reminders for medication may be based on the prescription and recommended dosages calculation prescribed. It also reminds patients to re-order medication when they run low.
Figure 1 depicts components of a system for patient management of ocular health information. The system 100 comprises a web server component 102 that may interact with a mobile application 104 running on a tablet or smart phone. Although described as a mobile application, it will be appreciated that the mobile application functionality described further below may be performed on a stationary computing device such as a personal computer. The web server component 102 may also interact with a third party ordering platform 106.
The web server 102 may comprise a processor 108 for executing instructions as well as memory 110 for storing instructions and data. The web server 102 may further comprise non-volatile (NV) storage 112 for long term storage of instructions and data as well as one or more input/output (I/O) interfaces 114 for connecting input and/or output devices to the web server 102. Although depicted as a single physical device, it is contemplated that the functionality of the web server 102 may in fact be provided by a plurality of physical and/or virtual servers. The web server 102 provides various functionality, including a clinic portal 116, a patient portal 118, an order portal 120 as well as a number of data stores such as a patient assessment questionnaire store 122, a patient assessment results store 124 and a patient information store 126.
Although described as different portals, the functionality of the clinic portal 116, patient portal 118 and order portal 120 may be provided by a single portal, or other arrangements of portals.
The clinic portal provides various functionality for the overall operation of the system for
Figure 1 depicts components of a system for patient management of ocular health information. The system 100 comprises a web server component 102 that may interact with a mobile application 104 running on a tablet or smart phone. Although described as a mobile application, it will be appreciated that the mobile application functionality described further below may be performed on a stationary computing device such as a personal computer. The web server component 102 may also interact with a third party ordering platform 106.
The web server 102 may comprise a processor 108 for executing instructions as well as memory 110 for storing instructions and data. The web server 102 may further comprise non-volatile (NV) storage 112 for long term storage of instructions and data as well as one or more input/output (I/O) interfaces 114 for connecting input and/or output devices to the web server 102. Although depicted as a single physical device, it is contemplated that the functionality of the web server 102 may in fact be provided by a plurality of physical and/or virtual servers. The web server 102 provides various functionality, including a clinic portal 116, a patient portal 118, an order portal 120 as well as a number of data stores such as a patient assessment questionnaire store 122, a patient assessment results store 124 and a patient information store 126.
Although described as different portals, the functionality of the clinic portal 116, patient portal 118 and order portal 120 may be provided by a single portal, or other arrangements of portals.
The clinic portal provides various functionality for the overall operation of the system for
4 a particular clinic or group of clinics. The clinic portal may allow clinic staff to activate patients on the tablets, download and print treatment or other information on dry eye treatment options and remove patients from the system. The portal may provide a landing page having a list of patients that may require attention in the near future, such as a follow-up call, an appointment etc.
Patient activation may allow the clinic to enter a pre-assigned patient ID.
Patient IDs may have the following format CCCDDD999999. Where CCC is a three alpha numeric code representing the clinic, DDD is a three alpha numeric code representing the doctor, 999999 is a number code to identify the patient. When entering the ID
the clinic may also enter a friendly name for the patient. The friendly name can be the patient's first name, last name, nick name, or some other name to easily identify the patient in further steps. The name is only stored for ease of use of the application and may be removed once the patient completes the overall process flow (name is encrypted, not removed as it will always be available to clinic portal but not to others outside the clinic portal). Activating the patient allows the mobile application running on, for example, a tablet to read the ID so clinic and patients do not need to enter the patient ID on the tablet.
The clinic portal may provide access to patient documents in order to download, print, save and attach to a patient's record various documents. Once a patient answers and submits the survey questions, the document will be available on the portal so it may be printed for the patient or downloaded for the EMR. The same functionality is available for the test results and Doctors recommendations. Documents may be stored as PDF's, this will allow ease of attachments or printing on unknown and numerous clinic hardware and printers.
The mobile application 104 may be provided on a tablet or other portable device. The application may provide the main interface for the patient process. Patients can use the mobile application to answer questionnaires, technicians can use the mobile application to enter test results and Doctors can use the mobile application to enter the treatment recommendations. Each of the different users, that is the patients, technicians and doctors may be provided by different interfaces.
The patient interface provides the main interaction for the patient with the application and allows the patient to fill out dry eye questionnaires, which may be a customizable feature based on the clinic and Doctor. The questionnaire may present a few questions per page to the user until the survey is complete.
The technician interface is where the technician can enter in the test results for the dry eye assessment. Tests may be ordered and performed in order as displayed on the mobile application. The tests to be performed may be customizable based on the clinic and Doctor preferences. The technician is able to go switch to whatever test they wish to perform at any time. Once all tests are preformed they can submit the test and get ready for treatment recommendations. Often the technicians have a recommended treatment prepared for the Doctor to review.
The doctor interface may be used for the doctor to review the questionnaire, assessment test results and possible technician treatment recommendations. The doctor can modify the technician's recommendations if they are entered or the doctor can enter their own recommendations. This recommendation area can be used to recommend ocular treatments such as Hyabak, Thealoz, Blephagel, Blephaclean, Punctal Plugs, Sun glasses, or other treatments. There is also a free form area for the Doctor to add qualitative information. Once the Doctor is finished with their recommendations the tablet and patient return to the clinic reception.
The tablet application may have some customization features that will not require code changes. The customizations can be stored by clinic by Doctor. The patient ID
will be used to identify which customization to run during the patient process.
Options which can be customized may include, for example, a questionnaire format such as DEQ5 or CDEA, a video displayed once patient fills out questionnaire, tests performed during assessment.
Figure 2 depicts a method for managing ocular health information for patients.
The method 200 begins with a clinic level sign on (202). The clinic sign-on may log a clinic onto a mobile application that may be used by clinic technicians, doctors and as well patients of the clinic. A patient access code may be received (204) and a patient record associated with the received access code retrieved or otherwise accessed (206). The method 200 determines if the mobile application used to access the patient record is in a patient or clinic access mode (208) and if it is in the clinic access mode (Clinic at 208), it is determined if a section of the patient record to be filled out by the section has been completed (210) and if it has been completed (Yes at 210) a clinics portal dashboard may be accessed (212) that allows patient information to be viewed and edited, as well as viewing and editing clinic information and preferences. If the clinic section is not completed (No at 210) the clinic technician, or receptionist or other employee, may use the mobile application to complete clinic section (214) and the clinic section results are submitted (216). It is determined if the patient has approved communication via email, or other methods of communication(218) and if it is approved (Yes at 218) a result email may be sent to the patient detailing the clinics completed information (220).
If the patient has not approved correspondence (No at 218), the clinic may inform the patient of the results (222).
If the patient record is accessed through the patient access interface (Patient at 208) it is determined if the patient assessment section has been completed (224). If the patient access section has been completed (Yes at 224) the patient may access a patient portal dashboard (226) that allows the patient to access and view related patient information. If the patient access section has not been completed (No at 224), ocular health assessment information may be retrieved (228) and the patient may complete the patient assessment (230). Once completed, the patient assessment questionnaire results may be submitted (232). The method may be determine if the patient has approved email correspondence, or other types of correspondence (234) and if the correspondence is approved (Yes at 234) an appointment email to the patient may be sent informing the patient of an ocular health appointment (236). If the correspondence with the patient is not approved (No at 234) the patient may be informed of the appointment (238).
Figure 3 depicts a method of using the system of Figure 1 in an optometry clinic. The method 300 begins with a patient checking in at a clinic (302). The patient's ID may be selected on a mobile application running on a tablet (304). The patient ID may be entered by a clinic employee or the patient. The patient completes an ocular health assessment questionnaire (306) presented on the tablet. After completing the ocular health assessment questionnaire, the patient may return the tablet to the clinic employee (308) and the technician or optometrist may use the table to complete an ocular health assessment (310) for the patient. The assessment may involve completing a number of health tests. Once completed, the optometrist may discuss treatment options with the patient (312) and the optometrist may prescribe ocular health treatment products or services based on the patient's answer to the questionnaire and/or results of the ocular health assessment tests performed. The clinic may enter the prescription information into the portal using the tablet or other possible interface devices (316). The patient may order the prescribed ocular health products through a patient portal (318) and the patient information may be transferred to the order supplier (320). The order supplier may use the prescription information, patient information and order information in order to provide reminders to the user such as periodically reminding the patient to refill their products, or other reminders (322).
Figure 4 depicts a method for patient completion of ocular health assessment questionnaire. The method 400 may begin when the patient receives the tablet to present the ocular health assessment questionnaire. The patient ocular health assessment questionnaire may be retrieved (402), which may comprise a number of questions for the patient to answer. A question is displayed (404) and the patient's answer to the question is received (406). It is determined if the end of questions have been reached (408) and if the end has not been reached (No at 408), the next question is retrieved and displayed (404). If the end of the questions has been reached (Yes at 408), the results may be submitted and or stored, and the patient may be presented with an ocular health video or videos to watch (410).
Figure 5 depicts a method for technician or optometrist completion of ocular health assessment. The method 500 begins with retrieving the patient's assessment questionnaire results (502) and discussing any identified ocular health problems, such as dry eye conditions with the patient (504). Test to be performed may be retrieved and displayed (506). The technician may perform the test and record the results (508). It is determined if the end of the tests has been reached (510) an if it has not been reached (No at 510) the next test is displayed (506). If there are no more tests (Yes at 510) an ocular health treatment plan may be determined and entered (512).
As described above, patient assessment questionnaires and patient assessment tests and their results may be stored and access through one or more different portals. The information may be stored in various databases, tables or other structures.
The database tables or other structures may store other information such as survey information, test information, customization information or other information.
Figure 6 depicts an database structure for storing patient information. The database structure 600 may include for example, a customization table 602 for storing information such as clinic doctor information, videos to be played, surveys to be completed, customization IDs and Custom survey IDs, which may link to other tables such as a custom Test table 604 that stores a custom test ID, customization ID, a test name and type. A custom survey table 606 may be linked to as well and store survey questions and answer types.
An active patients table 608 may be used for tracking patients and their associated information. The active patients table may be linked to patient order table 610 that stored order products and their quantity. The active patients table 608 may link to a patient survey table 612 that stores survey questions and answers as well as a patient test result table 614 that stores test questions and their answers. The active patients table may also link to a patient recommendation table 616 that stores information on patient recommendations.
The above has described various functionality provided by various systems. The functionality may be provided as a combination of hardware, firmware and software comprising instructions stored in a memory that are executed by a processor.
The executed instructions configure devices to provide at least some of the functionality described. Although specific embodiments are described herein, it will be appreciated that modifications may be made to the embodiments without departing from the scope of the current teachings. Accordingly, the scope of the appended claims should not be limited by the specific embodiments set forth, but should be given the broadest interpretation consistent with the teachings of the description as a whole.
Patient activation may allow the clinic to enter a pre-assigned patient ID.
Patient IDs may have the following format CCCDDD999999. Where CCC is a three alpha numeric code representing the clinic, DDD is a three alpha numeric code representing the doctor, 999999 is a number code to identify the patient. When entering the ID
the clinic may also enter a friendly name for the patient. The friendly name can be the patient's first name, last name, nick name, or some other name to easily identify the patient in further steps. The name is only stored for ease of use of the application and may be removed once the patient completes the overall process flow (name is encrypted, not removed as it will always be available to clinic portal but not to others outside the clinic portal). Activating the patient allows the mobile application running on, for example, a tablet to read the ID so clinic and patients do not need to enter the patient ID on the tablet.
The clinic portal may provide access to patient documents in order to download, print, save and attach to a patient's record various documents. Once a patient answers and submits the survey questions, the document will be available on the portal so it may be printed for the patient or downloaded for the EMR. The same functionality is available for the test results and Doctors recommendations. Documents may be stored as PDF's, this will allow ease of attachments or printing on unknown and numerous clinic hardware and printers.
The mobile application 104 may be provided on a tablet or other portable device. The application may provide the main interface for the patient process. Patients can use the mobile application to answer questionnaires, technicians can use the mobile application to enter test results and Doctors can use the mobile application to enter the treatment recommendations. Each of the different users, that is the patients, technicians and doctors may be provided by different interfaces.
The patient interface provides the main interaction for the patient with the application and allows the patient to fill out dry eye questionnaires, which may be a customizable feature based on the clinic and Doctor. The questionnaire may present a few questions per page to the user until the survey is complete.
The technician interface is where the technician can enter in the test results for the dry eye assessment. Tests may be ordered and performed in order as displayed on the mobile application. The tests to be performed may be customizable based on the clinic and Doctor preferences. The technician is able to go switch to whatever test they wish to perform at any time. Once all tests are preformed they can submit the test and get ready for treatment recommendations. Often the technicians have a recommended treatment prepared for the Doctor to review.
The doctor interface may be used for the doctor to review the questionnaire, assessment test results and possible technician treatment recommendations. The doctor can modify the technician's recommendations if they are entered or the doctor can enter their own recommendations. This recommendation area can be used to recommend ocular treatments such as Hyabak, Thealoz, Blephagel, Blephaclean, Punctal Plugs, Sun glasses, or other treatments. There is also a free form area for the Doctor to add qualitative information. Once the Doctor is finished with their recommendations the tablet and patient return to the clinic reception.
The tablet application may have some customization features that will not require code changes. The customizations can be stored by clinic by Doctor. The patient ID
will be used to identify which customization to run during the patient process.
Options which can be customized may include, for example, a questionnaire format such as DEQ5 or CDEA, a video displayed once patient fills out questionnaire, tests performed during assessment.
Figure 2 depicts a method for managing ocular health information for patients.
The method 200 begins with a clinic level sign on (202). The clinic sign-on may log a clinic onto a mobile application that may be used by clinic technicians, doctors and as well patients of the clinic. A patient access code may be received (204) and a patient record associated with the received access code retrieved or otherwise accessed (206). The method 200 determines if the mobile application used to access the patient record is in a patient or clinic access mode (208) and if it is in the clinic access mode (Clinic at 208), it is determined if a section of the patient record to be filled out by the section has been completed (210) and if it has been completed (Yes at 210) a clinics portal dashboard may be accessed (212) that allows patient information to be viewed and edited, as well as viewing and editing clinic information and preferences. If the clinic section is not completed (No at 210) the clinic technician, or receptionist or other employee, may use the mobile application to complete clinic section (214) and the clinic section results are submitted (216). It is determined if the patient has approved communication via email, or other methods of communication(218) and if it is approved (Yes at 218) a result email may be sent to the patient detailing the clinics completed information (220).
If the patient has not approved correspondence (No at 218), the clinic may inform the patient of the results (222).
If the patient record is accessed through the patient access interface (Patient at 208) it is determined if the patient assessment section has been completed (224). If the patient access section has been completed (Yes at 224) the patient may access a patient portal dashboard (226) that allows the patient to access and view related patient information. If the patient access section has not been completed (No at 224), ocular health assessment information may be retrieved (228) and the patient may complete the patient assessment (230). Once completed, the patient assessment questionnaire results may be submitted (232). The method may be determine if the patient has approved email correspondence, or other types of correspondence (234) and if the correspondence is approved (Yes at 234) an appointment email to the patient may be sent informing the patient of an ocular health appointment (236). If the correspondence with the patient is not approved (No at 234) the patient may be informed of the appointment (238).
Figure 3 depicts a method of using the system of Figure 1 in an optometry clinic. The method 300 begins with a patient checking in at a clinic (302). The patient's ID may be selected on a mobile application running on a tablet (304). The patient ID may be entered by a clinic employee or the patient. The patient completes an ocular health assessment questionnaire (306) presented on the tablet. After completing the ocular health assessment questionnaire, the patient may return the tablet to the clinic employee (308) and the technician or optometrist may use the table to complete an ocular health assessment (310) for the patient. The assessment may involve completing a number of health tests. Once completed, the optometrist may discuss treatment options with the patient (312) and the optometrist may prescribe ocular health treatment products or services based on the patient's answer to the questionnaire and/or results of the ocular health assessment tests performed. The clinic may enter the prescription information into the portal using the tablet or other possible interface devices (316). The patient may order the prescribed ocular health products through a patient portal (318) and the patient information may be transferred to the order supplier (320). The order supplier may use the prescription information, patient information and order information in order to provide reminders to the user such as periodically reminding the patient to refill their products, or other reminders (322).
Figure 4 depicts a method for patient completion of ocular health assessment questionnaire. The method 400 may begin when the patient receives the tablet to present the ocular health assessment questionnaire. The patient ocular health assessment questionnaire may be retrieved (402), which may comprise a number of questions for the patient to answer. A question is displayed (404) and the patient's answer to the question is received (406). It is determined if the end of questions have been reached (408) and if the end has not been reached (No at 408), the next question is retrieved and displayed (404). If the end of the questions has been reached (Yes at 408), the results may be submitted and or stored, and the patient may be presented with an ocular health video or videos to watch (410).
Figure 5 depicts a method for technician or optometrist completion of ocular health assessment. The method 500 begins with retrieving the patient's assessment questionnaire results (502) and discussing any identified ocular health problems, such as dry eye conditions with the patient (504). Test to be performed may be retrieved and displayed (506). The technician may perform the test and record the results (508). It is determined if the end of the tests has been reached (510) an if it has not been reached (No at 510) the next test is displayed (506). If there are no more tests (Yes at 510) an ocular health treatment plan may be determined and entered (512).
As described above, patient assessment questionnaires and patient assessment tests and their results may be stored and access through one or more different portals. The information may be stored in various databases, tables or other structures.
The database tables or other structures may store other information such as survey information, test information, customization information or other information.
Figure 6 depicts an database structure for storing patient information. The database structure 600 may include for example, a customization table 602 for storing information such as clinic doctor information, videos to be played, surveys to be completed, customization IDs and Custom survey IDs, which may link to other tables such as a custom Test table 604 that stores a custom test ID, customization ID, a test name and type. A custom survey table 606 may be linked to as well and store survey questions and answer types.
An active patients table 608 may be used for tracking patients and their associated information. The active patients table may be linked to patient order table 610 that stored order products and their quantity. The active patients table 608 may link to a patient survey table 612 that stores survey questions and answers as well as a patient test result table 614 that stores test questions and their answers. The active patients table may also link to a patient recommendation table 616 that stores information on patient recommendations.
The above has described various functionality provided by various systems. The functionality may be provided as a combination of hardware, firmware and software comprising instructions stored in a memory that are executed by a processor.
The executed instructions configure devices to provide at least some of the functionality described. Although specific embodiments are described herein, it will be appreciated that modifications may be made to the embodiments without departing from the scope of the current teachings. Accordingly, the scope of the appended claims should not be limited by the specific embodiments set forth, but should be given the broadest interpretation consistent with the teachings of the description as a whole.
Claims (10)
1. A system for patient management of ocular health information comprising:
a network-connected server configured to provide:
a database storing:
patient information including contact information;
ocular condition assessment results;
a mobile interface for receiving information and storing to the database, the information comprising information associated with results of a patient's ocular condition assessment;
a clinic portal providing an access interface to the database to authorized users of an ocular health clinic, the access interface of the clinic portal configured to receive an indication of one or more ocular health treatment products or services for respective patients;
a user portal providing an access interface to patient information in the database; and a product ordering interface for placing patient orders for ocular-health products and transferring patient information from the database to a product supplier for use in fulfilling a product order of the one or more ocular health treatment products or services and for use in providing reminders to a user regarding the one or more ocular health treatment products or services; and at least one portable device configured to present a patient with an ocular condition assessment and communicate the results to the mobile interface of the network-connected server.
a network-connected server configured to provide:
a database storing:
patient information including contact information;
ocular condition assessment results;
a mobile interface for receiving information and storing to the database, the information comprising information associated with results of a patient's ocular condition assessment;
a clinic portal providing an access interface to the database to authorized users of an ocular health clinic, the access interface of the clinic portal configured to receive an indication of one or more ocular health treatment products or services for respective patients;
a user portal providing an access interface to patient information in the database; and a product ordering interface for placing patient orders for ocular-health products and transferring patient information from the database to a product supplier for use in fulfilling a product order of the one or more ocular health treatment products or services and for use in providing reminders to a user regarding the one or more ocular health treatment products or services; and at least one portable device configured to present a patient with an ocular condition assessment and communicate the results to the mobile interface of the network-connected server.
2. The system of claim 1, wherein the at least one portable device is further for accessing the clinic portal.
Date Recue/Date Received 2021-10-08
Date Recue/Date Received 2021-10-08
3. The system of claim 1, wherein the at least one portable device is further for accessing the user portal.
4. The system of claim 1, wherein the database further stores questions on ocular health for presentation to the patient.
5. The system of claim 1, wherein the database further stores information on recommendations for the patient.
6. The system of claim 1, wherein the ocular health condition is dry eyes.
7. A method for patient management of ocular health information comprising:
prompting a patient for patient information including contact information, and storing the patient information;
retrieving and presenting to the patient an ocular health assessment questionnaire;
receiving and storing patients responses to the ocular health assessment questionnaire;
presenting the ocular health questionnaire answers to a technician or an optometrist;
presenting the technician or the optometrist with one or more ocular health assessment test to perform;
receiving an indication of one or more ocular health treatment products or services for the patient; and placing an order to a 3rd party provider for the indicated one or more ocular health treatment products or services including transferring patient information to the 3rd party supplier for use in fulfilling a product order and for use in providing reminders to a user regarding the one or more ocular health treatment products or services.
prompting a patient for patient information including contact information, and storing the patient information;
retrieving and presenting to the patient an ocular health assessment questionnaire;
receiving and storing patients responses to the ocular health assessment questionnaire;
presenting the ocular health questionnaire answers to a technician or an optometrist;
presenting the technician or the optometrist with one or more ocular health assessment test to perform;
receiving an indication of one or more ocular health treatment products or services for the patient; and placing an order to a 3rd party provider for the indicated one or more ocular health treatment products or services including transferring patient information to the 3rd party supplier for use in fulfilling a product order and for use in providing reminders to a user regarding the one or more ocular health treatment products or services.
8. The method of claim 7, further comprising accessing a clinic portal.
Date Recue/Date Received 2021-10-08
Date Recue/Date Received 2021-10-08
9. The method of claim 7, further comprising accessing a patient portal.
10. The method of claim 7, wherein the ocular health condition is dry eyes.
Date Recue/Date Received 2021-10-08
Date Recue/Date Received 2021-10-08
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US201462020069P | 2014-07-02 | 2014-07-02 | |
| US62/020,069 | 2014-07-02 |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CA2895882A1 CA2895882A1 (en) | 2016-01-02 |
| CA2895882C true CA2895882C (en) | 2022-12-06 |
Family
ID=54978843
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA2895882A Active CA2895882C (en) | 2014-07-02 | 2015-06-30 | Patient management of ocular health information |
Country Status (1)
| Country | Link |
|---|---|
| CA (1) | CA2895882C (en) |
-
2015
- 2015-06-30 CA CA2895882A patent/CA2895882C/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CA2895882A1 (en) | 2016-01-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20210398675A1 (en) | Method and system for medical suggestion search | |
| US20150100333A1 (en) | Systems and methods for verifying protocol compliance | |
| US20140257851A1 (en) | Automated interactive health care application for patient care | |
| US20190237203A1 (en) | Facilitating self-scheduling of medical appointments | |
| US20150286787A1 (en) | System and method for managing healthcare | |
| US11848101B2 (en) | Machine model generation systems and methods | |
| US20180277252A1 (en) | Person Engagement Index for Providing Automated Personalized Healthcare Functions | |
| US20160098542A1 (en) | Medical diagnosis and treatment support apparatus, system, and method | |
| CA2942983C (en) | System and method for managing illness outside of a hospital environment | |
| EP2973104A2 (en) | Method and apparatus for transmitting healthcare messages to an automatically identified set of patients | |
| JP2023099761A (en) | Method and system for evaluating prescribed optical device | |
| US20170103171A1 (en) | More-intelligent health care advisor | |
| de Dicastillo et al. | Development and evaluation of a telematics platform for monitoring of patients in ambulatory major surgery | |
| CA2895882C (en) | Patient management of ocular health information | |
| US11854673B2 (en) | Systems and methods for managing caregiver responsibility | |
| Bass et al. | Implementing an Application Programming Interface for PROMIS Measures at three medical centers | |
| CA3012605A1 (en) | Method and system for medical suggestion search | |
| US20140100877A1 (en) | Healthcare facility navigation method and system | |
| US20130060096A1 (en) | Integrating Wellness Care and Data into the Patient Care Cycle | |
| US20130218591A1 (en) | Method and system for delivering patient specific content at a point of care | |
| JPWO2018199850A5 (en) | ||
| US10431109B2 (en) | Systems and methods for somatization identification and treatment | |
| WO2021252126A1 (en) | Provider-curated applications for accessing patient data in an ehr system | |
| Crook et al. | Smart-phone-based Platform for Patient Medical Compliance | |
| WO2018085913A1 (en) | Method and server for maintaining medical information for establishment of clinical notes in relation to medical exams |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request |
Effective date: 20180727 |
|
| EEER | Examination request |
Effective date: 20180727 |
|
| EEER | Examination request |
Effective date: 20180727 |
|
| EEER | Examination request |
Effective date: 20180727 |
|
| EEER | Examination request |
Effective date: 20180727 |