Description:

UCSF advertises itself as a LGBT-friendly employer and supports that claim with a diversity center, LGBT-inclusive healthcare benefits, and more. The University even has a "preferred name" column in the electronic HR files, which is great for transgender members who do not have the ability or readiness to change their first legal name, and also serves useful for when there are more than 2 University members with the same name, as well as when University members known by nicknames.

However, there are numerous University systems who map to members' legal first name instead of the preferred name, causing those transgender-identified, double names, and chosen names to get ignored and confused.

This proposal is a simple mapping project to ensure that University members are referred to and listed by their preferred name instead of their legal first name. This will ensure emails, phone calls, and auto-generated system messages are addressing the correct individuals by their correct name, as well as help others reinforce that name and eliminate confusion for finding and communicating with that individual.

Deliverables:

University systems (LMS, BearBuy, ID Badges, etc.) will automatically pull from University members' HR "Preferred Name" listing instead of their legal "First Name" listing. 

Related system administrators may receive an email, a quick reference guide, or a job aid, depending on the need for acclimating systems to this small change (team meetings will determine if there is a need for this).

Impact:

1) More inclusive space for transgender University members who may be unable or unprepared to change their first name legally.

2) Less confusion and lost communications in the case of having more than 2 University members with the same first and last name -- e.g. "Mike's not here? Oops, I must have sent the meeting invite to the wrong Michael Smith again."

3) Less confusion, time, and lost messages for staff members who are known by a nickname instead of their first legal name -- e.g. "I can't find your name in the Outlook address book, DJ, because there are 30 people with your last name," "oh, sorry, I'm the one listed under Jones, Dean."

4) Less discomfort, time, and errors spent on communications with names that University members have difficulty spelling or pronouncing, for those who opt into being referred to by a nickname toward that purpose.

5) More consistency and compatibility between University systems -- e.g. "Sorry, I cannot register you for MyAccess, CJ, because your email address does not sync up with your University Directory listing."

This affects not only those University members with preferred names that are different than their legal first name, but also those who need to communicate with them, as well as all who are affected by those members' productivity and happiness. It is a system that is easy to set in place and has no future maintenance needed to last indefinitely. In short, it is an incredibly low-involvement project with high-impact, sustainable results that have a realistically high probability of success.

Team Members & Roles:

1) Project Coordinator, Subject Matter Expert, and Test User - CJ Frosch

2) HR Administrator/Expert- ?

3) ITS Administrator/Expert- ?

Estimated time would be no more than 1 hour in weekly team meetings and 1.5 hours of implementation time spent weekly for 4-6 weeks, for a total of 10-15 hours.

Thank you for all the feedback and interest in our proposal. This version reflects updates as of 10-17-2-13. 

Description:

A student’s life is 24/7 and always on the go. Knowing where you have to be, when, and what you need to do before you get there is a key to success. Health professions students find themselves learning across five major campus sites and a multitude of smaller clinical settings, all the while still responsible for new learning.

The primary tool for managing a learner’s day is their course calendar. For UCSF students and thousands of others around the world the UC San Francisco Ilios Curriculum Management System delivers that calendar via an interactive webpage in their online courses. However there isn’t a flexible and reliable way to access the calendar and course materials on mobile devices or to sync a student’s schedule to their favorite calendaring application such as their iPhone calendar or Google Calendar. As a result students must manage and update their schedules in multiple places and can miss out on important scheduling changes. The ability to access scheduling data is the number one requested feature of students using Ilios. The UCSF implementation of Ilios is online at (https://curriculum.ucsf.edu/).  

We seek to develop an API (application programming interface) for calendar and curricular data in the Ilios curriculum management system in order to facilitate the creation of student and teacher tools for education. Ilios has become a powerful component of the Collaborative Learning Environment at UCSF by capturing, managing and delivering the curriculum of the schools of medicine, pharmacy and dentistry, as well as, faculty development, making it the second most accessed application at UCSF. In addition, it is in use at dozens of school around the US including UCLA, Stanford, Dartmouth, SUNY Downstate, the University of Texas Health Science campus, and most recently outside the US at the Karolinska Institute in Sweden.

Deliverables: (Revised based on feedback)

This project will develop an API for the Ilios calendar data which will:

1. Allow for the insertion and synchronization of a user’s calendar into their existing mobile device calendar (google, iPhone, etc)
2. Allow for integration into course management systems such as Moodle.
3. Provide the ability for others to build mobile tools and desktop applications that utilize calendar and curriculum data.
4. Allow for the insertion and integration of calendar and curriculum data, such as learning objectives, into enterprise tools such as Drupal and Salesforce.
5. Create efficiencies in maintaining, updating and extending the open source Ilios codebase.

Impact on UCSF's mission and/or community:

1. Will enable more flexible, real-time access to learning content for new competency-based health professions education programs.
2. Development of tool to feed data about the who, what, when, where, why and how of a course, workshops, or learning event to mobile calendars or learning interfaces is an essential need for health professions learners and teachers.
3.  Thousands of learners from more than 21 schools in the US and abroad will benefit from the development of this API.
4. Will allow for content to be embedded on sites served by another host or be dynamically posted to user interfaces.
5. Will be used to ease the work of programming graphical user interface components.

Measures of success and output:

1. Ilios Calendar API released as part of the open-source code on GitHub
2. Usage documentation for the API.

Team Members and estimated time committee: (Revised based on interest)

1. Sascha Cohen, Project Management @ 15%
2. Rich Trott, Techical Resource Coordinator @ 15%
3. Elliot Kendall, Programmer @ %70
4. Kevin H. Souza, Associate Dean, Executive Sponsor @ in-kind support

Description: Hypothesis-driven science in translational/clinical research is heavily dependent on large searchable electronic databases of clinical information.  UCSF is among the pre-eminent centers for both basic and translational research in the health sciences in part because of its foresight in implementing and maintaining such databases.   Notably, the CoPath database maintained by the department of pathology is critical to many multidisciplinary -and multi-center- translational research efforts involving the departments of pathology, surgery, radiology, transplant medicine, neurology, hematology/oncology, and many others.  At this time, however, no API exists for end-users such as faculty, staff, or residents involved in research projects to search the CoPath database themselves: rather, all searches must be performed by an IT staff member and yields only the most rudimentary information (ie, surgical case numbers only).  This approach is needlessly tedious for both IT and clinical investigators and impedes all research efforts involving the department of anatomic pathology.  We therefore propose the creation of an API accessible to suitably trained end-users for searching the CoPath database in order to harness the tremendous potential of such an interface to spur innovative clinical research.

Deliverables:

1. Database of CoPath data separately housed from the native CoPath database by the department of anatomic pathology.

2. User-friendly API for use by clinical investigators to search the database    .

3. Secure data storage of all search data.

4. Mechanism for tracking performed searches by pathology IT.

5. Secure user login requiring registration and training by pathology IT.

6. Training materials (in the form of a pdf document and an audio-visual powerpoint slide show   accessible online) to reiterate patient safety and HIPAA compliance.

Impact on UCSF’s mission and/or community:

UCSF’s mission: UCSF advances health worldwide through innovative health sciences education, discovery and patient care.

1. Completion of this project will promote innovative translational/clinical discovery by unlocking clinical data for investigators and encouraging early hypothesis-driven inquiries to spur new research directions.

2. By enabling investigative inquiry among properly trained UCSF residents and medical students, this project will also promote self-directed education/training in translational/clinical research.

3. The collaborative nature of nearly all modern translational/clinical research studies means that the impact of this project extends to all collaborators of the UCSF department of anatomic pathology, including nearly all UCSF medical center/research departments, pathology and other departments at dozens of partner universities, and industry collaborators.

4. CoPath databases are in use at hospitals throughout the U.S. and the world: distribution of this API to other CoPath users will thus promote innovative research worldwide.

Team Members:

- Ben Buelow, MD, PhD

    -Vision/Design

    -Subject matter expert (pathology resident, clinical investigator)

    -End-user

- Dianna Ng, MD:

    -Subject matter expert (pathology resident, clinical investigator)

    -End-user

- Gavin Law:

    -Programmer

- Sebastian Geiger (non-UCSF):

    -Programmer

Advisory Panel:

Enrique Terrazas, Residency director, Department of Lab Medicine

Angela See, Director of Clinical Operations, Department of Pathology

Vicky Kirby-Martin, Privacy Office

Tim Hoffman, IT, Medical Center Security

Sunny Bang, IT, Database management

Taylor Sittler: Programming consultant

This is a browser extension, a web app, also a mobile app!

-- built based on eUtils and related APIs of various web sites; Fast, Light & Mobile Friendly

#### Targeted User ####

The project targets to anyone frequently uses PubMed. It presents all the information to the users in one place, in real time, to help the users to save their valuable time.

#### Aims ####

* Direct access the PDF link of the related articles, on PubMed pages and any webpage with DOI/PMID/PMCID

* Integrate information for easy access and sharing

    ** When browsing on PubMed, display the impact factor, F1000 link, citation statistics, and any related information next to the article
    ** When browsing on PubMed, a button will be placed next to the article for copy and paste the article summary between applications
    ** When browsing on PubMed, provide links to email the PDF files or save the select articles to the Cloud services, including sharing to social networks if the user wants to

* Rich search experience when access from any mobile device, including smartphones and tablets, with single click to the PDF files, related articles, author publication statistics, etc.

* Alert service to notify users when new entry in PubMed has keyword matched their pre-entered list (alert will be delivered in real time; via email, Twitter direct message, Facebook wall post, etc.)

#### Current Progress ####

* Backends running on Google AppEngine and Amzon EC2, with >2,800,000 articles cached for quick response

* Browser extensions written by Javascript, HTML and CSS; open sourced on github

    ** Test version for Chrome, >6000 active users
    ** Test version for Firefox, >500 active users
    ** Test version for Safari, no statistics

* Testing the web app and the mobile app, please visit http://www.thepaperlink.com

* Testing the Facebook App, please visit https://apps.facebook.com/thepaperlink/

#### To-do List ####

* Decrease the server latency, aiming for 100 milliseconds response time

* Improve the user interface of the web app, using Twitter Bootstrap

* Integrate support for Google Drive, and other widely adopted cloud storage services (currently when the user click “save it”, the file can be saved to Dropbox, but not to Google Drive, etc)

* Improve keyword based text matching and alert service, including customizable alert frequency, directly store keywords for alert if the user chose to, parallel processing capability on large user population

* Build a smarter alert service using text mining and machine learning; a prototype using Google Prediction API has been tested and proven to be promising - we will modify it to decrease the cost on large user population

* Improve the integration between Google Scholar and PubMed, such as sorting by citation count, sorting by journal impact, etc.

* Improve the integration with http://www.pubmeder.com to allow full text search in a user’s own article collection

* Add support to display the Paper Link information bar into other webpages, such as F1000 comments, Cochrane summaries, etc

* If time permits, build a native iOS app to decrease the network traffic required to use the mobile app

#### Team Member ####

* Developer: liang.cai@ucsf
* Designer: hao.wu@ucsf
* Tester: xiao.peng@ucsf, and anyone interested

#### Questions Answered ####

* Why someone would be interested in using the Paper Link over PubGet?

    ** PubGet wants the users to browse the articles in their website, as a mean for revenue. The Paper Link provides many ways to access the information, without the need to change the existing reading habits.
    ** PubGet does have a mobile app, but it has much less function than the Paper Link.
    ** The Paper Link has better algorithm to extract the PDF links, which is the core of both services.
    ** The Paper Link has better integration with the social networks. Sharing the knowledge openly!
    ** There is no way to email the PDF file to yourself in PubGet.
    ** PubGet requires an institutional affiliation to check the PDF link, and requires visiting the site from a specific IP range to see the PDF file. The Paper Link does not need that. The Paper Link: displays the open access link to anyone from anywhere, allows the using of EZProxy, gives the PDF link to the user directly.
    ** The browser extension and addon of the Paper Link are open sourced. API of the Paper Link is free for personal use.
    ** The Paper Link was inspired by PubGet. It is built on the believe of Free, Open and Sharing.

* My NCBI has email alert service, why is the Paper Link trying to “reinvent the wheel”?

    ** My NCBI’s service is not in real time - an article might take days, even weeks to get to inbox
    ** My NCBI’s service is based on keyword matching, not by artificial intelligence
    ** My NCBI’s service only delivers the alert via email

Project Desription:

For UCSF there are a significant number of enterprise web applications in use; currently, 84 are listed on the MyAccess site. For many of these applications, access administrators must manually assign access to individuals. Currently, there is no automated way to request access for an application.  The objective of this project is to create a uniform and centralized process for members of the UCSF community to request and grant access to many of the systems across the enterprise.

Deliverables:

• Create a request web application with a matrix of applications to enable an application request function
• Modify the MyAccess web application with a link to the request web application
• Modify the EDS to store what applications the user has access to
• Provide Access administrator or Application Security administrator a way to update EDS with access changes.
• Email notification for the requester, approver, granter
• Create reporting from EDS.

Impact on UCSF's mission and/or community:

UCSF can move to a more uniform and centralized process to request and grant access to applications across the university.  For individuals with access to the existing MyAccess web site, they will be able to submit a request for access to an application listed in the proposed new web application, if that application owner has worked to have it setup. A process will be defined for the setup, approval, and provisioning of access that will result in the following benefits:

• A single place for 28,000+ users to not just to login into web applications but to also request access.
• A defined process that ensures a simpler access provisioning process, leading to faster turnaround times and more opportunities for automation.
• Better reporting and auditing of users and access to UCSF applications.
• A more efficient service model for groups supporting the UCSF community (ie. Service Desk, IT field service groups, administrative offices, etc.)
• Moderate to significant cost savings once all the phases are implemented derived from operational efficiencies and better security management.

Team members, roles, %:

Description of Project

We envision a smartphone app that facilitates collection of basic health data from congenital heart patients, allowing accurate monitoring and follow up and leading to reduced morbidity and mortality.

Infants with congenital heart conditions suffer from high rates of mortality after they leave the hospital. Phone-based home monitoring programs began 10 years ago and have decreased mortality.

Such programs are a great first step. Through them we have learned that systematic collection and tracking of very basic health data metrics such as weight, oxygen saturation, heart rate and caloric intake over time allows for improved follow up and significantly decreasing mortality in this population.

However, current systems of data collection are tedious, slow, and error prone. For example, Emma Olson, our team member and nurse practitioner in the Pediatric Heart Center collects, stores, and transfers data in a labor intensive and highly manual process. She sometimes must enter the same data manually 4-5 times across multiple IT platforms (Apex, Filemaker, Excel, pen/paper, etc). Just to obtain basic data, she spends significant amounts of time each week in challenging phone conversations, often requiring language translation assistance—thus increasing opportunities for miscommunication and human error.

Our BabyHeartTrak app will be the first step toward a digital, mobile-based systematic data collection and will play a leading role in establishing new mobile-based monitoring techniques for our sickest patients. We envision a simple, readily accessible, smart phone-based app that will enable simple data entry by patients' parents. The app will enable health care providers to monitor for signs of alarm. By allowing the parents to track their baby's status over time, families will be empowered to better understand the health progress of their babies.

As professionals in the UCSF Pediatric Heart Center, we have come together to improve patient care through improved data collection. Nick has experience working with this data and writing electronically secured programs to collect patient data.  Emma is ready to implement this app with her patient population. Finally, Doctors Larrazabal and Brook conceived of the idea to transfer home monitoring to a mobile platform and have prepared the clinical requirements and oversight to make the data collection of clinical importance.

Deliverable

BabyHeartTrak is a mobile app designed to assist parents in simply recording their children’s health data so that it may be easily shared with their health care providers. By using mobile data collection, the ultimate goal is to improve health outcomes for children with complex health conditions.

Our final deliverable is a mobile app that includes four simple screens:

-       Record of baby characteristics (name, DOB, diagnosis, recommended caloric intake)

-       Daily log (date, weight, heart rate, oxygen saturation)

-       Feed log (date, time, and quantity of feeds)

-       Progress report (graphs that track progress and compare against norms)

Our team lead, Dr. Larrazabal, is a native Spanish speaker who will facilitate production of our app in both English and Spanish.

Our work plan includes the following interim steps:

• As a team we have created the initial app design using software application Balsamiq (see attachment). This is already complete.
• Our team member Nick Robins, a programmer at UCSF, has built web databases with similar cardiology data and will manage the building the mobile app using our Balsamiq designs. He will also coordinate the building of a computer dashboard for medical professionals to manage and monitor patient data.
• Nick and Dr. Larrazabal are currently reviewing applications from mobile programmers.
• Christina LaMontagne (a seasoned product manager from the health IT industry) will lead a user testing process to ensure that the user interface is simple and accessible for users.
• Emma will also be responsible for the deliverable of a basic training curriculum for our users.  

Impact on UCSF’s mission and community

Mobile devices have become ubiquitous in the US and around the world. Especially in developing countries, mobile devices have become a major channel of communication and data storage. By advancing mobile data collection and analytic techniques at UCSF, we are generating new knowledge and best practices to share across departments within our hospital and at our partner sites worldwide. We aim to contribute to the setting of a new standard of data collection and patient monitoring–starting with our youngest and most fragile patients.

Eventually BabyHeartTrak will contribute to efforts to automatize collection of patient data such that the data feed directly into EMR technology like Apex. With enhanced automatization, nurses and clinicians are free to spend less time collecting data and more time diagnosing, treating, and caring for patients.

Finally, one of the primary benefits of our app is the empowerment of patients to own their health data. We believe that when patients have access to their own data they are better able to learn about and manage their own health. We believe the use of mobile apps creates a more engaged and healthy patient population.

List of team members, roles, and estimated division of responsibility & time

• Dr. Luis Alesandro Larrazabal: 15 hours
  Pediatric Cardiology Fellow @ UCSF, lead app inventor & designer, team leader

• Dr. Michael Brook: 3 hours
  Clinical expert and senior pediatric cardiology attending @ UCSF, senior clinical advisor

• Emma Olson: 20 hours
  Nurse Practitioner @ UCSF Pediatric Heart Center, lead user responsible for implementation and patient/caregiver training on app

• Nick Robins: 10 hours
  Senior Programmer @ UCSF Pediatric Heart Center, lead developer of current web-based system, responsible for managing development of app

• Mobile app programmer TBD: 20 hours

We have posted this job and already received 13 applications/bids to build this product. We are confident we can find a great programmer to collaborate on this project.

• Christina LaMontagne: 5 hours
  Experienced product manager of technology applications, health IT start-up executive, MBA (non-UCSF)

a. Description:

CareWeb is a UCSF IT innovation and the premier project for the Center for Digital Health Innovation that integrates various disparate electronic communications information systems within UCSF. This integrated solution unifies electronic messaging with a social networking/microblogging motif to provide real-time streaming as well as “push” notifications via text-page. The data stream is instantly searchable and accessible by those within the patient care workflow. The solution can be accessed via any client with a browser or via an iphone client.

The CareWeb Radiology Alert System (CARESS), the current project, aims at integrating imaging procedure status data from the Radiology Information System (RIS) into the information stream presented by CareWeb. It will allow users to designate an alert status if and as a radiograph moves from ordering to protocol to scanning to completion to having been “read” preliminarily to being finalized. This integration allows access to real-time status updates on patient imaging procedures, and delivers them to a provider if and as the provider so selects.

b. Deliverables:

A special screen/UI element in CareWeb that displays information from the Radiology feed

* Leverages existing Mule Enterprise Service Bus (ESB) software as middleware for getting this data “into” CareWeb

* Ability to select a stage in a radiology exam’s  life cycle at which a provider can be alerted when that point has been reached.

This element is enabled by server software that extracts radiology imaging study status updates in real-time and posts them to CareWeb via the middleware as noted.

An update to the mobile client that allows providers to see updates to radiograph status on their iPhone.

c. Impact on UCSF's mission:

The immediate impact would be an improvement in workflow for UCSF providers due to a reduction in the need to contact Radiology to check on imaging status and/or constantly refresh the electronic medical record to find out when a study is completed. There would also be a dramatic improvement in patient care if providers could refocus their efforts on a given task in the knowledge that once an update was available, it would be “pushed” to them rather than them having to keep checking up on the status. Additionally this project would demonstrate that the CareWeb system can serve as a platform to facilitate integration of data from other patient care systems on campus, including pathology or labs, which have equally compelling use cases in this space.

d. List of team members:

Edwin Martin - technical architect - his experience will bring the technical team together to ensure CareWeb and the RIS  can communicate.

Raman Khanna – team leader – his experience as the lead for the CareWeb project will be critical towards getting this integration completed in a fashion consumable by providers.

Rodanni Pugeda – provide the technical integration within CareWeb such that RIS updates are displayed and triggers are written for the alert feature.

Donna Cummings – updates to the CareWeb Smart Client UI to allow display of imaging status updates, in a manner that can be scaled in the future to include additional lab information.

James Hawkins  - radiology technologist – develop the server side technology to post imaging study status updates to CareWeb through the Mule ESB to leverage existing integration mechanism already in place for sources such as pager. .

Wyatt Tellis - imaging informaticist and workflow subject matter expert - coordinate the export of exam status information from the radiology department’s  RIS

Vivek Swarnakar – radiology team lead – coordinate the efforts between the radiology and CareWeb teams.

e. Estimated Effort:

It is anticipated that most of the integration work can be completed within 40 hrs using existing infrastructure on CARESS.

The mobile client updates would require 40 hrs additionally.

Non-development team members would be required to spend about 10 hrs each testing the integrated solution.

I. SUMMARY: Let’s leverage APEX and text messaging technologies to automatically reduce the anxiety and burden on patients and their caregivers currently caused by long waiting room time uncertainty!  

II. DESCRIPTION OF PROJECT:  One of the most common patient complaints in a number of clinic waiting rooms at UCSF are the long and uncertain waiting times to see their doctor. On average, wait times can be a minimum of 30 minutes up to 2 hours without any status updates to the waiting patients, causing high levels of patient frustration and anxiety to the point where patients leave unseen. Rather than discussing health issues with patients, our doctors and staff are faced with triaging anxious and angry patient complaints such as “I was afraid of missing my named being called but if I’d known how long the wait time was going to be I could have (a) used the restroom (b) gone to the cafeteria because I was starving (c) fed my meter but now I have a parking ticket”.   It has been difficult for front desk personnel or doctors to manually track and manually update patients on their wait-time statuses.  As a solution, we propose to develop “WAIT-INFO” a back-end application that utilizes APEX’s care management platform to (optionally) send automated free text message updates to patients with their estimated wait time and queue number. This will greatly reduce wait time uncertainty and provide freedom for patients to travel around.  As an example in ophthalmology, patient statuses in APEX are changed to a green circle after initial tech work-up, indicating they are now in the waiting room ready to be seen by their doctor. Wait time is often longest here. Our proposed WAIT-INFO application will utilize and track data (via color code system) from APEX to monitor patient’s wait time/queue status. Once the green circle is displayed in APEX an initial text message will be sent automatically to the patient. The first text message and subsequent messages are: "Thank you for your patience. There are currently #___ patient’s ahead (intervals >5, 5, 4, 3)".  Once the patient is #3 in the queue- the text will read: "Please return to the clinic immediately". If patients do not return to the clinic in time, they will be skipped but placed next in line.  An SMS “your patience is greatly appreciated” will then still be sent every 15 minutes, until the healthcare provider opens the chart ending all SMS alerts.  A manual override to text a patient to return to clinic can also be sent by the front desk.   

III. DELIVERABLES:  (a) Proof of value (completed!): In an already-completed pilot simulation using manually sent free SMS via txt.att.net,  “mock patients” (our team members) were followed through a real clinic schedule and responded to manually-sent SMS wait-time alerts. In this WAIT-INFO simulation, the estimated waiting room time was only 13 minutes (vs 46 minutes actual patient wait time in office).  (b)  Proof of concept:  One next step is a WAIT-INFO simulation manually monitoring and text messaging a cohort of waiting clinic patients as with the pilot study above, then surveying patients who did and did not participate in the WAIT-INFO simulation, comparing patient’s waiting-satisfaction, and gauging interest and feedback in an automated WAIT-INFO system.  From anecdotal evidence, we are confident patients will appreciate WAIT-INFO.  (c) WAIT-INFO application beta development: in parallel with step b above, the study team programmer will develop a beta version of the application that will use APEX as an automated means of gauging wait time, queueing patients, and sending text messages. (d) WAIT-INFO pilot testing and refinement: After steps b-c, we will refine in our clinic, extend and customize the application to a clinic in a second department, and then further refine for expansion at UCSF.

IV. IMPACTS: The proposed SMS WAIT app unites innovation and discovery to improve the patient and clinic staff experience and satisfaction all of which are UCSF’s foundations for quality patient care.  Just in ophthalmology alone, we estimate this would directly impact several thousand patients a month, as well as clinic staff.  Broader potential usage of this system includes wait-time alerts in other UCSF clinic and clinical lab waiting rooms with long uncertain wait times, or families waiting anxiously in surgical or maternity ward suites can be provided with SMS status updates of their loved ones. Front desk personnel could also leverage the system to manually send a text message to call patients to the front desk privately (a privacy improvement over the tradition of calling out a patient’s name in the waiting room).

V. PROJECT TEAM:   Jane Kuo, OD, FAAO (Team/clinical lead ~25 hours); Michael Deiner, PhD (Project manager ~25hours); Winnie Wat (APEX Analyst/WAIT-INFO developer ~35 hours).