Skip to content

Latest commit

 

History

History

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 

readme.md

Symptom Reporter

The Symptom Reporter helps a patient distill and clarify subjective symptoms and experiences into structured data that can be conveniently and consistently shared with clinicians in person, via email/text, or the Electronic Medical Record. Foreign language support will help patients prepare a report in English before an appointment so they can be more comfortable and confident in communicating their experiences and needs.

Similar products exist, but there are important differences. There are many online symptom checking tools (WebMD.com, Isabel symptomchecker.isabelhealthcare.com) that focus on providing a home diagnosis. Symptom trackers are popular mobile apps that allow a patient to keep tabs on a chronic or recurring symptom over time. Neither of these types of application focuses on aiding communication or creating a detailed and medically relevant report at the point of pain. The most similar app available is AHRQuestionBuilder, developed by U.S. Department of Health and Human Services. Some patient portals integrate a symptom checker (Epic - Mayo Clinic’s MyChart), but again, it does not provide any way to begin a conversation with a clinician regarding those symptoms. Hopefully, an open source tool such as openPRO - Symptom Reporter would help encourage such integration.

Purpose/Goals

  • Improve communication between patient and care team
  • Improve fidelity of information from patient, by recording events and pains closer to relevant time and place (point of pain)
  • Lower stress on patient and improve fidelity of data during transfers of care

Components

  • Design & Develop: Web Interface to identify symptom and collect relevant info (onset, intensity, location, etc.)
  • Design & Develop: Receipt for patient in both plain English and medical language for sharing, cutting & pasting, printing, etc.
  • Develop: script to prepare FHIR Condition resource, ready for integration

Additional features

  • Language support
  • Accessibility support

###Estimated Level of Effort### Design: 4 weeks, 1.0FTE Development v1.0: 6 weeks, 1.0FTE

Contents