Spike: Investigate age and age range in CTS API

[sarinapadilla]

To drive our decision on type of input for the Age filter, we need to investigate the CTS API for how trials are coded for age eligibility criteria.

If trials are often more specific in age, we will use a text input. If trials are often in age ranges, we will consider using a checkbox list.

[adriancofie]

Typical trial age response data:

    "structured": {
      "max_age": "999 Years",
      "max_age_number": 999,
      "min_age_unit": "Years",
      "max_age_unit": "Years",
      "max_age_in_years": 999,
      "gender": "BOTH",
      "accepts_healthy_volunteers": false,
      "min_age": "18 Years",
      "min_age_number": 18,
      "min_age_in_years": 18
    }

"eligibility": { "structured": { "max_age": "999 Years", "max_age_number": 999, "min_age_unit": "Years", "max_age_unit": "Years", "max_age_in_years": 999, "gender": "BOTH", "min_age": "12 Years", "min_age_number": 12, "min_age_in_years": 12 } },

Full trial response age 99:

response_1710856622993.json

[sarinapadilla]

Based on the findings from @adriancofie, we're going to go ahead with the checkbox list of age ranges for the Age filter rather than a text input. The requirements on #206 have been updated!