Any Bahmni configuration can be overridden by creating a separate override file. That way, an implementation with multiple entities can have a standard master configuration and each entity will have the freedom to override specific parts
Let us take an example config file:
{ "id": "bahmni.clinical", "extensionPoints": [ { "id": "org.bahmni.clinical.consultation.board", "description": "Bahmni Clinical Consultation Page" }, { "id": "org.bahmni.clinical.conceptSetGroup.*", "description": "Define conceptsets part of a conceptset group" }, { "id": "org.bahmni.clinical.orders", "description": "Bahmni Orders Page" }, { "id":"org.bahmni.patient.search", "description": "Bahmni Patient search, lookups Page" } ], } |
To override this config file with another file, do the following two things
Add the flag "shouldOverRideConfig: true" as shown below
{ "id": "bahmni.clinical", "shouldOverRideConfig": true, "extensionPoints": [ { "id": "org.bahmni.clinical.consultation.board", "description": "Bahmni Clinical Consultation Page" }, { "id": "org.bahmni.clinical.conceptSetGroup.*", "description": "Define conceptsets part of a conceptset group" }, { "id": "org.bahmni.clinical.orders", "description": "Bahmni Orders Page" }, { "id":"org.bahmni.patient.search", "description": "Bahmni Patient search, lookups Page" } ], } |
Create a new file openmrs/apps/clinical/app.json in the folder /var/www/implementation_config as shown below
{ "id": "bahmni.clinical", "extensionPoints": [ { "id": "org.bahmni.clinical.consultation.board", "description": "Bahmni Clinical Consultation Page" } ], } |
The above file will override the section "extensionPoints" in the the app.json file with the contents of the app.json file.
Type | config | overridden config | Notes | ||
---|---|---|---|---|---|
override |
|
|
| ||
Remove |
|
|
|