Skip to end of metadata
Go to start of metadata

In Attendance:

  • Martin Were
  • Paul Biondich
  • Nyoman Ribkea
  • Jeremy Keiper
  • Ada Yeung
  • Michael Downey
  • Lauren Stanisic
  • Dawn Smith
  • Burke Mamlin
  • James Kariuki
  • Frank Fries

Recordings are available at http://tiny.cc/9czjv

Agenda:

Big Question: What do we need to do from a mobile standpoint over the next 2yrs?

General Discussion:* Paul: lay out what the elements of success are for AMPATH

  • Paul: Think of things in 3 buckets: development, implementation, and maintenance** Burke: Do we have an idea of what the mobile solutions will be for AMPATH in the next year?
    • Burke: Is there a suite of tools, platforms, approaches that we can set on in how we want to get devs up to speed?
  • Martin: We can shape what AMPATH wants and gets based on what we define as what’s reasonable and what is not realistic
  • Nyoman: Further development of forms will go away from form entry** Martin: There are several questions we have to address before making that decision
    • Jer: We had a discussion at the Implementers Meeting about this*** One person installed OpenMRS server on the device to enter HTML forms this way. This is an option for us
  • Paul: the simpler we can go with some of this technology, the broader the use

What can be done on a mobile device:* Martin: data collection in remote locations on short forms** Short forms: small collection of information (not as detailed as AMPATH form)

    • HCT and revisits by home-based counseling and testing folks that require data collection
    • Patient level and household data
  • Martin: Linkage - once you find groups of interest in the community, finding a way to see who is/is not complying ** Ex: if you have patients missing appointments, create cohorts saying of these patients for a particular case (hypertension, reproductive health, diabetes, etc.) you can see who is not complying
    • End result: find a way to find these people
    • Burke: find a way for reliable mobile registration
    • Martin: if we can’t find out registration, the linkage won’t go well
    • Paul: pick apart linkage idea*** Martin: need mobile health to connect w/ people in the community. If ppl don’t come to AMPATH, we need a way to get that information
    • Paul: What do ppl need to do this?*** Martin: pregnant woman, HIV-positive,..they went to HCT and told her to come to clinic in 2wks, she doesn’t come in (she is already registered so we know she’s missing)...the community health worker will know that she has not shown
      • Burke: link persons and work flows across programs.
      • Paul: is it a checklist for what needs to be done?
      • Burke: linkages cut across programs to help HCW get things done
      • Jer: those same reminders could go to the patient too
    • Martin: We need to create some functionality to pass basic information about the individual
    • Martin: close the loop between linkage and data collection
    • Paul: This seems to be the area with the least work, so we need to improve this
  • Martin: Security Issues that come with mobile devices** Burke: A fundamental thing we want to get right is 1) if we can securely identify the user and 2) identify the patient(s) in a mobile setting
    • Martin: We should make a push to get the registration solved on their side and we can work on it from a technology side, but say we cannot quite to do this if the human side of registration is not solved *** Martin: It would be good to brainstorm on this
  • Martin: Viewing Records
  • Martin: Have patient facing
  • Paul: Alerts and Reminders
  • Martin: Tablets for all the health care workers** this would be a lower priority right now. it’s more of an implementation question than development question

What can NOT be done on a mobile device:

Paul’s Chart:

Development

  • Security layer

Implementation
Maintenance

Consumers

  • Co/Consultants
  • Community health care workers
  • Patients

Summary:* Martin: We still need a discussion of what type of technologies we need to use** Martin: Who is going to help pick what we use and what’s the framework of this conversation

    • James: Look at other models and figure out what people are already doing. We should look at the needs what we perceive the needs to be in the future
    • Martin: How do we get this started: googledoc, wiki, meeting*** Jer: Establish regular meetings and also have a space on the wiki for this. We can decide in these meetings how often we need to talk, understand the complexities and figure out who needs to be involved
    • Burke: Say what tools you have, and if someone needs a solution outside of those tools, find a way to help them customize it*** Burke: this will help us understand what we can/cannot commit to
      • Paul: same for what functionalities we will/will not commit to
    • Burke: The underpinning of linkages is that we just need to identify people
  • Martin: Who will look at the technologies to use here?** Paul: Get a list out to help us understand the amount of work involved will be useful.
    • Martin: Sounds like we’ll have a page for:*** A list of requests
      • A list of the tools
      • A list of organisations we can reach out to to see what’s out there now
  • No labels