Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
MethodURIAuthBodyParametersReturnDescription
Studies
GET/studiesAdmin- PaginatedResults<Study>All studies (for creating links within any community)
POST/studiesAdminStudy Studystudy with id returned
GET/studies/{id}Admin- Study 
PUT/studies/{id}AdminStudy Study 
DELETE/studies/{id}Admin- - 
Forms / Dataset Definitions (one per research instrument participants will use in a study)
GET/studies/{id}/formsResearcher w/ edit permission- PaginatedResults<Form>Unlikely to be more than a page of these
POST/studies/{id}/formsResearcher w/ edit permissionForm Formform with id returned
GET/studies/{id}/forms/{id}Researcher w/ edit permission- Form 
PUT/studies/{id}/forms/{id}Researcher w/ edit permissionForm Form 
DELETE/studies/{id}/forms/{id}Researcher w/ edit permission- - 
Consents (a special kind of form/dataset definition, one per study, stored encrypted)
GET/studies/{id}/consentResearcher w/ edit permission -  Form 
PUT/studies/{id}/consentResearcher w/ edit permission Form  -create or update consent
DELETE/studies/{id}/consentResearcher w/ edit permission -  - 
Participants (1 + for a user; these calls are scoped to the current user). Better to have one flat list of participations, across all research studies?or more for each research project this user is involved with; I would make this a list of all participations across all projects, since we proposed initially to show it in the profile or journal section of the app)
GET/studies/{id}/participants     
POST/studies/{id}/participants     
GET/studies/{id}/participants/{id}     
PUT/studies/{id}/participants/{id}     
DELETE/studies/{id}/participants/{id}     

...