# Contact Form Naming

**URL:** <https://forum.communityhealthtoolkit.org/t/contact-form-naming/2843>\
**Category:** Technical Support\
**Created:** [June 16, 2023, 4:59am UTC](https://forum.communityhealthtoolkit.org/t/contact-form-naming/2843 "2023-06-16T04:59:53Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Japheth\_Kiprotich](https://communityhealthtoolkit.b-cdn.net/user_avatar/forum.communityhealthtoolkit.org/japheth_kiprotich/32/2438_2.png) [@Japheth\_Kiprotich](https://forum.communityhealthtoolkit.org/u/Japheth_Kiprotich)\
**Post date:** [June 16, 2023, 4:59am UTC](https://forum.communityhealthtoolkit.org/t/contact-form-naming/2843/1 "2023-06-16T04:59:53Z")

</div>

Hi team, I upgraded to version 4.2 and noticed a change in the contact form naming. Below are the new names for each of the forms:

- New District → New Health Facility
- New Health Center → New Area
- New Area → New Household

The behavior is not stable since in one of the installations we’re getting the expected names. Attached are sample screenshots from the instances

 ![aw](https://communityhealthtoolkit.b-cdn.net/uploads/default/original/2X/1/1f21e2f822a862d9b8a24b3f511d95d5d0914776.png)  
 ![ac](https://communityhealthtoolkit.b-cdn.net/uploads/default/original/2X/4/4e976b0efe84b46e1cf66b3908d89b5b9b51c735.jpeg)

---

<div class="post-metadata">

**Author:** ![Japheth\_Kiprotich](https://communityhealthtoolkit.b-cdn.net/user_avatar/forum.communityhealthtoolkit.org/japheth_kiprotich/32/2438_2.png) [@Japheth\_Kiprotich](https://forum.communityhealthtoolkit.org/u/Japheth_Kiprotich)\
**Post date:** [June 16, 2023, 5:30am UTC](https://forum.communityhealthtoolkit.org/t/contact-form-naming/2843/2 "2023-06-16T05:30:06Z")

</div>

@Esther_Moturi @michael @antony I would like to request your assistance in reviewing this issue.

Thank you in advance for your time and contributions

---

<div class="post-metadata">

**Author:** ![Jennifer\_Quesada](https://communityhealthtoolkit.b-cdn.net/user_avatar/forum.communityhealthtoolkit.org/jennifer_quesada/32/553_2.png) [@Jennifer\_Quesada](https://forum.communityhealthtoolkit.org/u/Jennifer_Quesada)\
**Post date:** [June 16, 2023, 6:36am UTC](https://forum.communityhealthtoolkit.org/t/contact-form-naming/2843/3 "2023-06-16T06:36:41Z")

</div>

Hi @Japheth_Kiprotich

Thank you for your questions in the forum!

I think migrating to 4.2.0 shouldn’t affect the contact form labels. We have a simple app configuration that you can use as a reference [here](https://github.com/medic/cht-core/tree/master/config/covid-19).

Your app must configure the [hierarchy](https://docs.communityhealthtoolkit.org/apps/concepts/hierarchy/) by defining the [contact\_types](https://docs.communityhealthtoolkit.org/apps/reference/app-settings/hierarchy/) in your [app\_settings](https://docs.communityhealthtoolkit.org/apps/reference/app-settings/) file. As a sample of our app configuration, we define a [translation key](https://github.com/medic/cht-core/blob/3c1bb5e402700128d1713b6ff1c439a2d56176ca/config/covid-19/app_settings/base_settings.json#L173) in the `create_key` property; this is done according to each level of your hierarchy. In this sample, the translation key for district hospital is `contact.type.district_hospital.new`.

Then, the label (`New health facility` or any other text) for that translation key can be defined in the [translation file](https://github.com/medic/cht-core/blob/master/config/covid-19/translations/messages-en.properties#L32). I’m sharing more about translations [here](https://docs.communityhealthtoolkit.org/apps/reference/translations).

---

<div class="post-metadata">

**Author:** ![Japheth\_Kiprotich](https://communityhealthtoolkit.b-cdn.net/user_avatar/forum.communityhealthtoolkit.org/japheth_kiprotich/32/2438_2.png) [@Japheth\_Kiprotich](https://forum.communityhealthtoolkit.org/u/Japheth_Kiprotich)\
**Post date:** [June 16, 2023, 7:02am UTC](https://forum.communityhealthtoolkit.org/t/contact-form-naming/2843/4 "2023-06-16T07:02:13Z")

</div>

Hello @Jennifer_Quesada

Works perfectly! thank you for the pointers.
