Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The following methods will be added to the AdherenceService:

Code Block
languagejava
public class AdherenceService {
  public EventStreamAdherenceReport getEventStreamAdherenceReport(
      String appId, String studyId, String userId, DateTime now, boolean showActive) {
  }
  public WeeklyAdherenceReport getWeeklyAdherenceReport(
      String appId, String studyId, String userId, DateTime now) {
  }
  public PagedResourceList<WeeklyAdherenceReport> getPagedWeeklyAdherenceReports(
      App app, 

...

AdherenceSearch search) {
  }  
}

public class AdherenceSearch {
  int offsetBy;
  int pageSize;
  // always and only searches accounts that are enrolled in a specific study
  String studyId;
  String emailFilter;
  String phoneFilter;
  Set<String> allOfGroups;
  Set<String> noneOfGroups; 
  String language;
  DateTime startTime;
  DateTime endTime;
  String externalIdFilter;
  AccountStatus status;
  String attributeKey;
  String attributeValueFilter;
  SearchTermPredicate predicate;
  String label; // for example "Week 1" or "Study Burst 2"
  int maxWeeklyAdherencePercent
  StringSearchPosition stringSearchPosition;
}

System Messaging APIs

We have had requirements to message both participants and study administrators over the years. For example, very early on we embedded a blog in an app for this purpose. Then we implemented support for remote push notifications and topics (rarely used). Instead in recent studies we have tried using local notifications based on scheduling information. Now we are talking about showing notifications to administrators about participants being out-of-adherence in an administrative UI. Because “notifications” is heavily overloaded for Bridge, I will call these “system messages.”

...