...
"autoCompleteFields":["familyName", "caste"]
Additional Patient Information
There are certain situations where you would need to fill in some patient attributes always, and some on a need basis. For that, the process is to add the PersonAttributes as mentioned in previous section. Then update the app.json file to include the attribute in "additionalPatientInformation" section as shown below. In this example, familyIncome was added in PatientAttributes and is configured to be shown as additional patient information.
"additionalPatientInformation" : [
{ "name":"familyIncome", "display":true }, /* display determines whether to show or hide */
{ "name":"rationCard", "display":true }
]
...
Configuring sections in Registration page
We can have patient attributes distributed into sections in the patient registration page. The configuration looks like this:
| Code Block | ||||
|---|---|---|---|---|
| ||||
"patientInformation": {
"additionalPatientInformation": {
"title": "Additional Patient Information",
"attributes": [
"distanceFromCenter",
"isUrban",
"cluster"
]
},
"patientFinancialInformation": {
"translationKey": "REGISTRATION_FINANCIAL_INFO_KEY",
"shortcutKey": "REGISTRATION_FINANCIAL_ACCESS_KEY",
"attributes": ["familyIncome", "debt"]
},
"hidden": {
"attributes": [
"RationCard","cluster"
]
}
} |
There can be multiple sections like "additionalPatientInformation", "patientFinancialInformation", etc. Each section can have the related patient attributes like - "familyIncome", "debt", etc; and title and/or translation key and a shortcut/access key. "hidden" is a special section which holds the patient attributes that should not be shown. So "Other Information" will now contain:
"Other Information" attributes = Attributes that are not present in any of the section minus attributes specified in the hidden section.