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.

DatatypeEndpointProperties that will be filtered
[allergies](🔗)/v1/human/medical/allergiesdateRange.start
[encounters](🔗)/v1/human/medical/encountersdate
[functional_statuses](🔗)/v1/human/medical/functional_statusesdateTime
[immunizations](🔗)/v1/human/medical/immunizationsdates
[instructions](🔗)/v1/human/medical/instructions_(No date field, so filter cannot be performed)_
[medications](🔗)/v1/human/medical/medicationsstartDate
[narratives](🔗)/v1/human/medical/narrativesdateTime
[organizations](🔗)/v1/human/medical/organizations/{id}_(No date field, so filter cannot be performed)_
[plans of care](🔗)/v1/human/medical/plans_of_careDate (usually, this is a future date indicating the next time the patient should resume a medical encounter)
[problems](🔗)/v1/human/medical/issuesdate
[procedures](🔗)/v1/human/medical/proceduresdateTime
[profile](🔗)/v1/human/medical/profile_(No date field, so filter cannot be performed)_
[test results](🔗)/v1/human/medical/test_resultsresultDate
[vitals](🔗)/v1/human/medical/vitalsdateTime
[ccds](🔗)/v1/human/medical/ccdsdateTime
[demographics](🔗)/v1/human/medical/demographics_(No appropriate date field, so filter cannot be performed)_
[social history](🔗)/v1/human/medical/social_historydateTime