The [Medical API](🔗) encompasses many datatypes that contain various forms of datetime. While it is possible to perform basic date filtering based on the standard [Patterns and Conventions](🔗), this reference should serve to provide additional precision for filtering data and their associated date fields when assigning “start_date” and “end_date” query parameters.
For additional details regarding the endpoints and examples of data, please visit our Medical API reference.
| Datatype | Endpoint | Properties that will be filtered |
| [allergies](🔗) | /v1/human/medical/allergies | dateRange.start |
| [encounters](🔗) | /v1/human/medical/encounters | date |
| [functional_statuses](🔗) | /v1/human/medical/functional_statuses | dateTime |
| [immunizations](🔗) | /v1/human/medical/immunizations | dates |
| [instructions](🔗) | /v1/human/medical/instructions | _(No date field, so filter cannot be performed)_ |
| [medications](🔗) | /v1/human/medical/medications | startDate |
| [narratives](🔗) | /v1/human/medical/narratives | dateTime |
| [organizations](🔗) | /v1/human/medical/organizations/{id} | _(No date field, so filter cannot be performed)_ |
| [plans of care](🔗) | /v1/human/medical/plans_of_care | Date (usually, this is a future date indicating the next time the patient should resume a medical encounter) |
| [problems](🔗) | /v1/human/medical/issues | date |
| [procedures](🔗) | /v1/human/medical/procedures | dateTime |
| [profile](🔗) | /v1/human/medical/profile | _(No date field, so filter cannot be performed)_ |
| [test results](🔗) | /v1/human/medical/test_results | resultDate |
| [vitals](🔗) | /v1/human/medical/vitals | dateTime |
| [ccds](🔗) | /v1/human/medical/ccds | dateTime |
| [demographics](🔗) | /v1/human/medical/demographics | _(No appropriate date field, so filter cannot be performed)_ |
| [social history](🔗) | /v1/human/medical/social_history | dateTime |