At Saama we work with pharmaceutical compaines to speed up their clinical Trials. Clinical Trials - For a drug/medicine to get to the market it has to go through certain phases of testing on humans. These trials are done in hospitals(sites) and medicines are administered to selected patients(subjects) by the doctors.
During the trial there can be Adverse events (a situation when the subject has side effects because of the drug under investigation).
Concomitant medications (CM) are other prescription medications study participant takes because of an Adverse Event.
For Example: Loperamide (Medication) taken for Diarrhea (Adverse event). As it happens usually, The Medication is typically taken only during the Adverse event
Data from Clinical Trials are collected by the means of various Forms. For example, in this Hackathon, we have the Adverse Event (AE) and Concomitant Medication (CM) Forms and their respective information collected. The Adverse Event (AE) Form captures all the adverse side effects the Patient or Subject may face during a Clinical Trial after enrollment. These effects can then be treated by a medication, called Concomitant Medication and the related data is again captured as a Concomitant Medication (CM) Form. Hence we can see that both Adverse Events (AE) and Concomitant Medications (CM) are interrelated. Here, we will provide two datasets, each of AE and CM Forms samples as CSV files, to access full dataset use the APIs. APIs must be called after referring to the API guide and the goal of this Hackathon is to find specific issues with this data.
Below you can take a look at how the data looks like in the backend. This is the data that we will be serving you on the api requests.
| Domain | Link |
|---|---|
| AE | Sample |
| CM | Sample |
You can check what each column means in the data dictionary.
Common Problems(discrepancies) seen in this dataset are
Patients and rows for which Medication are given prior to the Adverse Events.
Eg: 
Patients and rows for which days Medications are given and Adverse Event occur don't match.
Eg: 
Duplicate Adverse events are entered or Adverse Events overlap.

Patients and rows which have overlapping of Concomitant medications.

Patients for which the duration of Adverse Events is not adding up to corresponding concomitant medication.

...
-
API Host: https://pharmanlp-177020.uc.r.appspot.com
This is where we have hosted the api, play around with a temporary email address initially if you want to test out the api before actual submission. -
API Docs: https://pharmanlp-177020.uc.r.appspot.com/apidocs
This will contain the docs to the endpoints that you will have to connect to to get the data and subimt the result at the end.
Look in the api docuemntation to see how you can communicate with the api and perform these tasks.
- Get a list subjects for the given study id + domain id
- Get subject data for study id + domain id + subject id
- Process data and find discrepancy (diffent type of discrepancies are defined above)
- Submit discrepancy data to the API (use your email address to submit the discrepancies)
- Well written Test Harness for testing your code