[NDH-840] Centralizing API Documentation Content

[sachin-panayil]

Centralizing API Documentation Content

Jira Ticket #840

Problem

Currently, we have API documentation content defined in a number of places: views.py, each of the filter python files, etc. This makes it harder to holistically look at our documentation content and also runs the risk that documentation content could drift (e.g. if the description of a practitioner name filter is updates in practitioner_filter_set.py but not practitioner_role_filter_set.py.

Solution

Create a new python file with a dictionary to store API documentation content, which can then be imported into and referenced in the files that currently have API documentation hard-coded.

Result

All content for API documentation is now stored in documentation_content.py and centralized with tests to confirm they appear in the APIs /schema

Test Plan

• run make up
• run make test