VA Online Memorial - API design update challenge

The U.S. Dept. of Veterans Affairs (The VA), are developing an application that will allow registered family members and the general public to find deceased veterans that buried at national cemeteries around the United States, and leave stories, photos, comments, memories, etc. to that person's profile. Approved family members or Next of Kins (NOKs) will be allowed to edit and update the person's profile information, included profile image, live events, and additional details about the person. The NOK will act as the "moderator" for the profile.

In a previous challenge we have designed the backend API based on the wireframes. In a parallel challenge we have finalized the application designs and that introduced a few changes that we need to reflect to the API and database models as well. Most of the changes are around the veteran details page (stories, testimonials, badges). 

No coding is required. Challenge output is:

• Swagger API definition (updated)

• Database model (diagram and sql script), updated

• Design screens to API and API to DB mapping document (new)

Please note that during data import, we are importing NOK data (relationship, name), but those are just data about the next of kin - not actual application user. Only after a registered user applies to be a next of kin should his data be used
���Latest wireframes are available at https://marvelapp.com/4b3g03j. Latest UI designs are available at http://memorial-app-final.herokuapp.com/249765. See the wireframe design challenge details for description of application features (this should be obvious from the wireframes as well, but if anything is not clear, please do ask questions in the forums).
We already have some parts of the backend implemented, and you should take the existing endpoints and database structure into consideration. If some of the data models or API endpoints don't match with the wireframes, please raise the issue in the forums. If your API design requires modifications to the existing code, please mark those changes clearly in your submission.
API should use consistent naming conventions (camelCase) and don't introduce multiple names for the same entities. Response types and error handling should be covered in swagger document. API will later be implemented with NodeJS, using Postgres as the backend.
Project repository is available here. Previous API design is available in the forums.

Final Submission Guidelines