API tools faq
paste
Advertisement
Guest User

Advanced Settings OM.RS

a guest
Sep 30th, 2020
65
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 50.47 KB | None | 0 0
raw download clone embed print report
  1. Currently logged in as Super User Log out My Profile HelpOpenMRS Logo
  2.  
  3.  
  4. Home Find/Create Patient Dictionary Reporting Administration
  5. Admin Set Implementation Id System Information View Quick Reports Settings Advanced Settings View Server Log View Database Changes Manage Locales And Themes View Logged In Users Search Index
  6. Advanced Settings
  7. Current properties
  8. Name Value
  9. addresshierarchy.addressToEntryMapUpdaterLastStartTime
  10. The module uses this field to store when the AddressToEntryMapUpdater task was last started; DO NOT MODIFY
  11. addresshierarchy.allowFreetext
  12. true
  13. Valid values: true/false. When overriding the address portlet, allow the entry of free text for address fields associated with the address hierarchy by providing an "Other" option
  14. addresshierarchy.database_version
  15. 2.10.0
  16. DO NOT MODIFY. Current database version number for the addresshierarchy module.
  17. addresshierarchy.enableOverrideOfAddressPortlet
  18. true
  19. Valid values: true/false. When enabled, the existing "edit" component of the address portlet is overridden by the new functionality provided by the address hierarchy module
  20. addresshierarchy.initializeAddressHierarchyCacheOnStartup
  21. true
  22. Sets whether to initialize the address hierarchy in-memory cache (which is used to speed up address hierarchy searches.
  23. Generally, you want to set this to "true", though developers may want to set it to false during development
  24. to speed module start-up.
  25. addresshierarchy.mandatory
  26. false
  27. true/false whether or not the addresshierarchy module MUST start when openmrs starts. This is used to make sure that mission critical modules are always running if openmrs is running.
  28. addresshierarchy.soundexProcessor
  29. If the Name Phonetics module is installed, this defines the name of a soundex algorithm used by the getPossibleFullAddresses service method.
  30. addresshierarchy.started
  31. true
  32. DO NOT MODIFY. true/false whether or not the addresshierarchy module has been started. This is used to make sure modules that were running prior to a restart are started again
  33. addresshierarchyrwanda.database_version
  34. 1.3.2
  35. DO NOT MODIFY. Current database version number for the addresshierarchyrwanda module.
  36. addresshierarchyrwanda.mandatory
  37. false
  38. true/false whether or not the addresshierarchyrwanda module MUST start when openmrs starts. This is used to make sure that mission critical modules are always running if openmrs is running.
  39. addresshierarchyrwanda.started
  40. false
  41. DO NOT MODIFY. true/false whether or not the addresshierarchyrwanda module has been started. This is used to make sure modules that were running prior to a restart are started again
  42. allergy.allergen.ConceptClasses
  43. Drug,MedSet
  44. A comma-separated list of the allowed concept classes for the allergen field of the allergy dialog
  45. allergy.concept.allergen.drug
  46. 162552AAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
  47. UUID for the drug allergens concept
  48. allergy.concept.allergen.environment
  49. 162554AAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
  50. UUID for the environment allergens concept
  51. allergy.concept.allergen.food
  52. 162553AAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
  53. UUID for the food allergens concept
  54. allergy.concept.otherNonCoded
  55. 5622AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
  56. UUID for the allergy other non coded concept
  57. allergy.concept.reactions
  58. 162555AAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
  59. UUID for the allergy reactions concept
  60. allergy.concept.severity.mild
  61. 1498AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
  62. UUID for the MILD severity concept
  63. allergy.concept.severity.moderate
  64. 1499AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
  65. UUID for the MODERATE severity concept
  66. allergy.concept.severity.severe
  67. 1500AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
  68. UUID for the SEVERE severity concept
  69. allergy.concept.unknown
  70. 1067AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
  71. UUID for the allergy unknown concept
  72. allergy.reaction.ConceptClasses
  73. Symptom
  74. A comma-separated list of the allowed concept classes for the reaction field of the allergy dialog
  75. appframework.mandatory
  76. false
  77. true/false whether or not the appframework module MUST start when openmrs starts. This is used to make sure that mission critical modules are always running if openmrs is running.
  78. appframework.started
  79. true
  80. DO NOT MODIFY. true/false whether or not the appframework module has been started. This is used to make sure modules that were running prior to a restart are started again
  81. application.name
  82. OpenMRS
  83. The name of this application, as presented to the user, for example on the login and welcome pages.
  84. appui.mandatory
  85. false
  86. true/false whether or not the appui module MUST start when openmrs starts. This is used to make sure that mission critical modules are always running if openmrs is running.
  87. appui.started
  88. true
  89. DO NOT MODIFY. true/false whether or not the appui module has been started. This is used to make sure modules that were running prior to a restart are started again
  90. calculation.mandatory
  91. false
  92. true/false whether or not the calculation module MUST start when openmrs starts. This is used to make sure that mission critical modules are always running if openmrs is running.
  93. calculation.started
  94. true
  95. DO NOT MODIFY. true/false whether or not the calculation module has been started. This is used to make sure modules that were running prior to a restart are started again
  96. concept.causeOfDeath
  97. 5002
  98. Concept id of the concept defining the CAUSE OF DEATH concept
  99. concept.cd4_count
  100. 5497
  101. Concept id of the concept defining the CD4 count concept
  102. concept.defaultConceptMapType
  103. NARROWER-THAN
  104. Default concept map type which is used when no other is set
  105. concept.height
  106. 5090
  107. Concept id of the concept defining the HEIGHT concept
  108. concept.medicalRecordObservations
  109. 1238
  110. The concept id of the MEDICAL_RECORD_OBSERVATIONS concept. This concept_id is presumed to be the generic grouping (obr) concept in hl7 messages. An obs_group row is not created for this concept.
  111. concept.none
  112. 1107
  113. Concept id of the concept defining the NONE concept
  114. concept.otherNonCoded
  115. 5622
  116. Concept id of the concept defining the OTHER NON-CODED concept
  117. concept.patientDied
  118. 1742
  119. Concept id of the concept defining the PATIEND DIED concept
  120. concept.problemList
  121. 1284
  122. The concept id of the PROBLEM LIST concept. This concept_id is presumed to be the generic grouping (obr) concept in hl7 messages. An obs_group row is not created for this concept.
  123. concept.reasonExitedCare
  124. 1811
  125. Concept id of the concept defining the REASON EXITED CARE concept
  126. concept.reasonOrderStopped
  127. 6098
  128. Concept id of the concept defining the REASON ORDER STOPPED concept
  129. concept.weight
  130. 5089
  131. Concept id of the concept defining the WEIGHT concept
  132. conceptDrug.dosageForm.conceptClasses
  133. A comma-separated list of the allowed concept classes for the dosage form field of the concept drug management form.
  134. conceptDrug.route.conceptClasses
  135. A comma-separated list of the allowed concept classes for the route field of the concept drug management form.
  136. concepts.locked
  137. false
  138. true/false whether or not concepts can be edited in this database.
  139. concept_map_type_management.enable
  140. false
  141. Enables or disables management of concept map types
  142. conditionList.endReasonConceptSetUuid
  143. UUID of end reason concept set
  144. conditionList.nonCodedUuid
  145. UUID of non coded concept
  146. dashboard.encounters.maximumNumberToShow
  147. 3
  148. An integer which, if specified, would determine the maximum number of encounters to display on the encounter tab of the patient dashboard.
  149. dashboard.encounters.providerDisplayRoles
  150. A comma-separated list of encounter roles (by name or id). Providers with these roles in an encounter will be displayed on the encounter tab of the patient dashboard.
  151. dashboard.encounters.showEditLink
  152. true
  153. true/false whether or not to show the 'Edit Encounter' link on the patient dashboard
  154. dashboard.encounters.showEmptyFields
  155. true
  156. true/false whether or not to show empty fields on the 'View Encounter' window
  157. dashboard.encounters.showViewLink
  158. true
  159. true/false whether or not to show the 'View Encounter' link on the patient dashboard
  160. dashboard.encounters.usePages
  161. smart
  162. true/false/smart on how to show the pages on the 'View Encounter' window. 'smart' means that if > 50% of the fields have page numbers defined, show data in pages
  163. dashboard.encounters.viewWhere
  164. newWindow
  165. Defines how the 'View Encounter' link should act. Known values: 'sameWindow', 'newWindow', 'oneNewWindow'
  166. dashboard.header.programs_to_show
  167. List of programs to show Enrollment details of in the patient header. (Should be an ordered comma-separated list of program_ids or names.)
  168. dashboard.header.showConcept
  169. 5497
  170. Comma delimited list of concepts ids to show on the patient header overview
  171. dashboard.header.workflows_to_show
  172. List of programs to show Enrollment details of in the patient header. List of workflows to show current status of in the patient header. These will only be displayed if they belong to a program listed above. (Should be a comma-separated list of program_workflow_ids.)
  173. dashboard.metadata.caseConversion
  174. Indicates which type automatic case conversion is applied to program/workflow/state in the patient dashboard. Valid values: lowercase, uppercase, capitalize. If empty no conversion is applied.
  175. dashboard.overview.showConcepts
  176. Comma delimited list of concepts ids to show on the patient dashboard overview tab
  177. dashboard.regimen.displayDrugSetIds
  178. ANTIRETROVIRAL DRUGS,TUBERCULOSIS TREATMENT DRUGS
  179. Drug sets that appear on the Patient Dashboard Regimen tab. Comma separated list of name of concepts that are defined as drug sets.
  180. dashboard.regimen.displayFrequencies
  181. 7 days/week,6 days/week,5 days/week,4 days/week,3 days/week,2 days/week,1 days/week
  182. Frequency of a drug order that appear on the Patient Dashboard. Comma separated list of name of concepts that are defined as drug frequencies.
  183. dashboard.regimen.standardRegimens
  184. <list> <regimenSuggestion> <drugComponents> <drugSuggestion> <drugId>2</drugId> <dose>1</dose> <units>tab(s)</units> <frequency>2/day x 7 days/week</frequency> <instructions></instructions> </drugSuggestion> </drugComponents> <displayName>3TC + d4T(30) + NVP (Triomune-30)</displayName> <codeName>standardTri30</codeName> <canReplace>ANTIRETROVIRAL DRUGS</canReplace> </regimenSuggestion> <regimenSuggestion> <drugComponents> <drugSuggestion> <drugId>3</drugId> <dose>1</dose> <units>tab(s)</units> <frequency>2/day x 7 days/week</frequency> <instructions></instructions> </drugSuggestion> </drugComponents> <displayName>3TC + d4T(40) + NVP (Triomune-40)</displayName> <codeName>standardTri40</codeName> <canReplace>ANTIRETROVIRAL DRUGS</canReplace> </regimenSuggestion> <regimenSuggestion> <drugComponents> <drugSuggestion> <drugId>39</drugId> <dose>1</dose> <units>tab(s)</units> <frequency>2/day x 7 days/week</frequency> <instructions></instructions> </drugSuggestion> <drugSuggestion> <drugId>22</drugId> <dose>200</dose> <units>mg</units> <frequency>2/day x 7 days/week</frequency> <instructions></instructions> </drugSuggestion> </drugComponents> <displayName>AZT + 3TC + NVP</displayName> <codeName>standardAztNvp</codeName> <canReplace>ANTIRETROVIRAL DRUGS</canReplace> </regimenSuggestion> <regimenSuggestion> <drugComponents> <drugSuggestion reference="../../../regimenSuggestion[3]/drugComponents/drugSuggestion"/> <drugSuggestion> <drugId>11</drugId> <dose>600</dose> <units>mg</units> <frequency>1/day x 7 days/week</frequency> <instructions></instructions> </drugSuggestion> </drugComponents> <displayName>AZT + 3TC + EFV(600)</displayName> <codeName>standardAztEfv</codeName> <canReplace>ANTIRETROVIRAL DRUGS</canReplace> </regimenSuggestion> <regimenSuggestion> <drugComponents> <drugSuggestion> <drugId>5</drugId> <dose>30</dose> <units>mg</units> <frequency>2/day x 7 days/week</frequency> <instructions></instructions> </drugSuggestion> <drugSuggestion> <drugId>42</drugId> <dose>150</dose> <units>mg</units> <frequency>2/day x 7 days/week</frequency> <instructions></instructions> </drugSuggestion> <drugSuggestion reference="../../../regimenSuggestion[4]/drugComponents/drugSuggestion[2]"/> </drugComponents> <displayName>d4T(30) + 3TC + EFV(600)</displayName> <codeName>standardD4t30Efv</codeName> <canReplace>ANTIRETROVIRAL DRUGS</canReplace> </regimenSuggestion> <regimenSuggestion> <drugComponents> <drugSuggestion> <drugId>6</drugId> <dose>40</dose> <units>mg</units> <frequency>2/day x 7 days/week</frequency> <instructions></instructions> </drugSuggestion> <drugSuggestion reference="../../../regimenSuggestion[5]/drugComponents/drugSuggestion[2]"/> <drugSuggestion reference="../../../regimenSuggestion[4]/drugComponents/drugSuggestion[2]"/> </drugComponents> <displayName>d4T(40) + 3TC + EFV(600)</displayName> <codeName>standardD4t40Efv</codeName> <canReplace>ANTIRETROVIRAL DRUGS</canReplace> </regimenSuggestion></list>
  185. XML description of standard drug regimens, to be shown as shortcuts on the dashboard regimen entry tab
  186. dashboard.relationships.show_types
  187. Types of relationships separated by commas. Doctor/Patient,Parent/Child
  188. dashboard.showPatientName
  189. false
  190. Whether or not to display the patient name in the patient dashboard title. Note that enabling this could be security risk if multiple users operate on the same computer.
  191. datePicker.weekStart
  192. 0
  193. First day of the week in the date picker. Domingo/Dimanche/Sunday:0 Lunes/Lundi/Monday:1
  194. default_locale
  195. en_GB
  196. Specifies the default locale. You can specify both the language code(ISO-639) and the country code(ISO-3166), e.g. 'en_GB' or just country: e.g. 'en'
  197. default_location
  198. Unknown Location
  199. The name of the location to use as a system default
  200. default_theme
  201. Default theme for users. OpenMRS ships with themes of 'green', 'orange', 'purple', and 'legacy'
  202. drugOrder.drugOther
  203. Specifies the uuid of the concept which represents drug other non coded
  204. drugOrder.requireDrug
  205. false
  206. Set to value true if you need to specify a formulation(Drug) when creating a drug order.
  207. emr.encounterMatcher
  208. Class name of a custom encounter matcher (e.g. org.openmrs.module.example.customEncounterMatcher)
  209. emrapi.conceptSourcesForDiagnosisSearch
  210. ICD-10-WHO
  211. Specifies comma separated list of reference term source names to be used for diagnosis and condition search
  212. emrapi.EmrApiVisitAssignmentHandler.adjustEncounterTimeOfDayIfNecessary
  213. false
  214. If true, and a visit is found on the same day but the encounter is not within that timeframe will adjust the encounter time as needed
  215. emrapi.EmrApiVisitAssignmentHandler.encounterTypeToNewVisitTypeMap
  216. Specifies the mapping of encounter types to new visit types for more see https://wiki.openmrs.org/x/vgF4Aw
  217. emrapi.lastViewedPatientSizeLimit
  218. 50
  219. Specifies the system wide number of patients to store as last viewed for a single user,
  220. defaults to 50 if not specified
  221. emrapi.mandatory
  222. false
  223. true/false whether or not the emrapi module MUST start when openmrs starts. This is used to make sure that mission critical modules are always running if openmrs is running.
  224. emrapi.nonDiagnosisConceptSets
  225. UUIDs or mapping of non diagnosis concept sets
  226. emrapi.started
  227. true
  228. DO NOT MODIFY. true/false whether or not the emrapi module has been started. This is used to make sure modules that were running prior to a restart are started again
  229. emrapi.suppressedDiagnosisConcepts
  230. UUIDs or mappings of suppressed diagnosis concepts
  231. emrapi.useLegacyDiagnosisService
  232. false
  233. When running Core 2.2+, use the legacy diagnosis service instead of the new one provided to work with the new diagnosis model
  234. encounterForm.obsSortOrder
  235. number
  236. The sort order for the obs listed on the encounter edit form. 'number' sorts on the associated numbering from the form schema. 'weight' sorts on the order displayed in the form schema.
  237. EncounterType.encounterTypes.locked
  238. false
  239. saving, retiring or deleting an Encounter Type is not permitted, if true
  240. event.mandatory
  241. false
  242. true/false whether or not the event module MUST start when openmrs starts. This is used to make sure that mission critical modules are always running if openmrs is running.
  243. event.started
  244. true
  245. DO NOT MODIFY. true/false whether or not the event module has been started. This is used to make sure modules that were running prior to a restart are started again
  246. FormEntry.enableDashboardTab
  247. true
  248. true/false whether or not to show a Form Entry tab on the patient dashboard
  249. FormEntry.enableOnEncounterTab
  250. false
  251. true/false whether or not to show a Enter Form button on the encounters tab of the patient dashboard
  252. forms.locked
  253. false
  254. Set to a value of true if you do not want any changes to be made on forms, else set to false.
  255. graph.color.absolute
  256. rgb(20,20,20)
  257. Color of the 'invalid' section of numeric graphs on the patient dashboard.
  258. graph.color.critical
  259. rgb(200,0,0)
  260. Color of the 'critical' section of numeric graphs on the patient dashboard.
  261. graph.color.normal
  262. rgb(255,126,0)
  263. Color of the 'normal' section of numeric graphs on the patient dashboard.
  264. gzip.enabled
  265. false
  266. Set to 'true' to turn on OpenMRS's gzip filter, and have the webapp compress data before sending it to any client that supports it. Generally use this if you are running Tomcat standalone. If you are running Tomcat behind Apache, then you'd want to use Apache to do gzip compression.
  267. hl7_archive.dir
  268. hl7_archives
  269. The default name or absolute path for the folder where to write the hl7_in_archives.
  270. hl7_processor.ignore_missing_patient_non_local
  271. false
  272. If true, hl7 messages for patients that are not found and are non-local will silently be dropped/ignored
  273. host.url
  274. The URL to redirect to after requesting for a password reset. Always provide a place holder in this url with name {activationKey}, it will get substituted by the actual activation key.
  275. htmlformentry.archiveDir
  276. htmlformentry/archive/%Y/%m
  277. Used to specify the directory used to serialize data as a blob submitted via html forms before propagation to the database.
  278. If a relative is specified then the directory is created in the default application data directory otherwise the absolute
  279. path is used.The %Y and %M are replaced with 4 digit year and 2 digit month respectively. If this property is empty nothing then nothing is saved.
  280. htmlformentry.archiveHtmlForms
  281. False
  282. Set to True if you want to archive the submitted html forms and False otherwise
  283. htmlformentry.dateFormat
  284. Always display dates in HTML Forms in this (Java) date format. E.g. "dd/MMM/yyyy" for 31/Jan/2012.
  285. htmlformentry.datePickerYearsRange
  286. 110,20
  287. datePickerYearsRange parameter can be set here Eg:'110,20' meaning that the possible years that appear in the datepicker dropdown range from 20 years past the current year, and 110 years prior to the current year.
  288. htmlformentry.mandatory
  289. false
  290. true/false whether or not the htmlformentry module MUST start when openmrs starts. This is used to make sure that mission critical modules are always running if openmrs is running.
  291. htmlformentry.showDateFormat
  292. true
  293. Set to true if you want static text for the date format to be displayed next to date widgets, else set to false.
  294. htmlformentry.started
  295. true
  296. DO NOT MODIFY. true/false whether or not the htmlformentry module has been started. This is used to make sure modules that were running prior to a restart are started again
  297. htmlformentry.timeFormat
  298. HH:mm
  299. Always display times in HTML Forms in this (Java) date format. E.g. "HH:mm" for 14:45.
  300. htmlformentryui.customPrintPageName
  301. If overriding htmlformentryui print button behavior, PageName to use in ui.pageLink() built href value
  302. htmlformentryui.customPrintProvider
  303. If overriding htmlformentryui print button behavior, artifactId or base route of provider overriding functionality
  304. htmlformentryui.customPrintTarget
  305. _self
  306. If overriding htmlformentryui print button behavior, URL target value (e.g. _self, _blank)
  307. htmlformentryui.mandatory
  308. false
  309. true/false whether or not the htmlformentryui module MUST start when openmrs starts. This is used to make sure that mission critical modules are always running if openmrs is running.
  310. htmlformentryui.started
  311. true
  312. DO NOT MODIFY. true/false whether or not the htmlformentryui module has been started. This is used to make sure modules that were running prior to a restart are started again
  313. htmlwidgets.mandatory
  314. false
  315. true/false whether or not the htmlwidgets module MUST start when openmrs starts. This is used to make sure that mission critical modules are always running if openmrs is running.
  316. htmlwidgets.started
  317. true
  318. DO NOT MODIFY. true/false whether or not the htmlwidgets module has been started. This is used to make sure modules that were running prior to a restart are started again
  319. idgen.mandatory
  320. false
  321. true/false whether or not the idgen module MUST start when openmrs starts. This is used to make sure that mission critical modules are always running if openmrs is running.
  322. idgen.prefixLocationAttributeType
  323. Name of LocationAttribute type for PatientIdentifier Prefixes.
  324. idgen.started
  325. true
  326. DO NOT MODIFY. true/false whether or not the idgen module has been started. This is used to make sure modules that were running prior to a restart are started again
  327. layout.address.format
  328. general
  329. Format in which to display the person addresses. Valid values are general, kenya, rwanda, usa, and lesotho
  330. layout.name.format
  331. short
  332. Format in which to display the person names. Valid values are short, full
  333. legacyui.mandatory
  334. false
  335. true/false whether or not the legacyui module MUST start when openmrs starts. This is used to make sure that mission critical modules are always running if openmrs is running.
  336. legacyui.started
  337. true
  338. DO NOT MODIFY. true/false whether or not the legacyui module has been started. This is used to make sure modules that were running prior to a restart are started again
  339. locale.allowed.list
  340. en,en_GB
  341. Comma delimited list of locales allowed for use on system
  342. location.field.style
  343. default
  344. Type of widget to use for location fields
  345. log.layout
  346. %p - %C{1}.%M(%L) |%d{ISO8601}| %m%n
  347. A log layout pattern which is used by the OpenMRS file appender.
  348. log.level
  349. org.openmrs.api:info
  350. Logging levels for log4j2.xml. Valid format is class:level,class:level. If class not specified, 'org.openmrs.api' presumed. Valid levels are trace, debug, info, warn, error or fatal
  351. log.level.openmrs
  352. info
  353. log level used by the logger 'org.openmrs'. This value will override the log4j.xml value. Valid values are trace, debug, info, warn, error or fatal
  354. log.location
  355. A directory where the OpenMRS log file appender is stored. The log file name is 'openmrs.log'.
  356. login.url
  357. login.htm
  358. Responsible for defining the Authentication URL
  359. mail.debug
  360. false
  361. true/false whether to print debugging information during mailing
  362. mail.default_content_type
  363. text/plain
  364. Content type to append to the mail messages
  365. mail.from
  366. info@openmrs.org
  367. Email address to use as the default from address
  368. mail.password
  369. test
  370. Password for the SMTP user (if smtp_auth is enabled)
  371. mail.smtp.starttls.enable
  372. false
  373. Set to true to enable TLS encryption, else set to false
  374. mail.smtp_auth
  375. false
  376. true/false whether the smtp host requires authentication
  377. mail.smtp_host
  378. localhost
  379. SMTP host name
  380. mail.smtp_port
  381. 25
  382. SMTP port
  383. mail.transport_protocol
  384. smtp
  385. Transport protocol for the messaging engine. Valid values: smtp
  386. mail.user
  387. test
  388. Username of the SMTP user (if smtp_auth is enabled)
  389. metadatamapping.addLocalMappings
  390. Specifies whether the concept mappings to the local dictionary should be created when exporting concepts
  391. metadatamapping.mandatory
  392. false
  393. true/false whether or not the metadatamapping module MUST start when openmrs starts. This is used to make sure that mission critical modules are always running if openmrs is running.
  394. metadatamapping.started
  395. true
  396. DO NOT MODIFY. true/false whether or not the metadatamapping module has been started. This is used to make sure modules that were running prior to a restart are started again
  397. metadatasharing.enableOnTheFlyPackages
  398. false
  399. Specifies whether metadata packages can be exported on the fly
  400. metadatasharing.mandatory
  401. false
  402. true/false whether or not the metadatasharing module MUST start when openmrs starts. This is used to make sure that mission critical modules are always running if openmrs is running.
  403. metadatasharing.persistIdsForClasses
  404. A comma separated list of class package/names that denotes classes to try and persist ids for. Common options: org.openmrs.Concept,org.openmrs.Form,org.openmrs.ConceptDatatype,org.openmrs.ConceptClass,org.openmrs.EncounterType,org.openmrs.IdentifierType,org.openmrs.RelationshipType,org.openmrs.Location
  405. metadatasharing.preferredConceptSourceIds
  406. Comma-separated list of concept source Ids for preferred sources, in case an incoming concept
  407. has duplicate mappings to any of these sources, no confirmation will be required unless its
  408. datatype or concept class differs from that of the existing concept
  409. metadatasharing.started
  410. true
  411. DO NOT MODIFY. true/false whether or not the metadatasharing module has been started. This is used to make sure modules that were running prior to a restart are started again
  412. metadatasharing.webservicesKey
  413. Key to grant access to remote systems to consume module webservices RESTfully
  414. minSearchCharacters
  415. 2
  416. Number of characters user must input before searching is started.
  417. module_repository_folder
  418. modules
  419. Name of the folder in which to store the modules
  420. newPatientForm.relationships
  421. Comma separated list of the RelationshipTypes to show on the new/short patient form. The list is defined like '3a, 4b, 7a'. The number is the RelationshipTypeId and the 'a' vs 'b' part is which side of the relationship is filled in by the user.
  422. new_patient_form.showRelationships
  423. false
  424. true/false whether or not to show the relationship editor on the addPatient.htm screen
  425. obs.complex_obs_dir
  426. complex_obs
  427. Default directory for storing complex obs.
  428. order.drugDispensingUnitsConceptUuid
  429. Specifies the uuid of the concept set where its members represent the possible drug dispensing units
  430. order.drugDosingUnitsConceptUuid
  431. Specifies the uuid of the concept set where its members represent the possible drug dosing units
  432. order.drugRoutesConceptUuid
  433. Specifies the uuid of the concept set where its members represent the possible drug routes
  434. order.durationUnitsConceptUuid
  435. Specifies the uuid of the concept set where its members represent the possible duration units
  436. order.nextOrderNumberSeed
  437. 1
  438. The next order number available for assignment
  439. order.orderNumberGeneratorBeanId
  440. Specifies spring bean id of the order generator to use when assigning order numbers
  441. order.testSpecimenSourcesConceptUuid
  442. Specifies the uuid of the concept set where its members represent the possible test specimen sources
  443. patient.defaultPatientIdentifierValidator
  444. org.openmrs.patient.impl.LuhnIdentifierValidator
  445. This property sets the default patient identifier validator. The default validator is only used in a handful of (mostly legacy) instances. For example, it's used to generate the isValidCheckDigit calculated column and to append the string "(default)" to the name of the default validator on the editPatientIdentifierType form.
  446. patient.displayAttributeTypes
  447. Birthplace
  448. patient.headerAttributeTypes
  449. A comma delimited list of PersonAttributeType names that will be shown on the patient dashboard
  450. patient.identifierPrefix
  451. This property is only used if patient.identifierRegex is empty. The string here is prepended to the sql indentifier search string. The sql becomes "... where identifier like '<PREFIX><QUERY STRING><SUFFIX>';". Typically this value is either a percent sign (%) or empty.
  452. patient.identifierRegex
  453. WARNING: Using this search property can cause a drop in mysql performance with large patient sets. A MySQL regular expression for the patient identifier search strings. The @SEARCH@ string is replaced at runtime with the user's search string. An empty regex will cause a simply 'like' sql search to be used. Example: ^0*@SEARCH@([A-Z]+-[0-9])?$
  454. patient.identifierSearchPattern
  455. If this is empty, the regex or suffix/prefix search is used. Comma separated list of identifiers to check. Allows for faster searching of multiple options rather than the slow regex. e.g. @SEARCH@,0@SEARCH@,@SEARCH-1@-@CHECKDIGIT@,0@SEARCH-1@-@CHECKDIGIT@ would turn a request for "4127" into a search for "in ('4127','04127','412-7','0412-7')"
  456. patient.identifierSuffix
  457. This property is only used if patient.identifierRegex is empty. The string here is prepended to the sql indentifier search string. The sql becomes "... where identifier like '<PREFIX><QUERY STRING><SUFFIX>';". Typically this value is either a percent sign (%) or empty.
  458. patient.listingAttributeTypes
  459. A comma delimited list of PersonAttributeType names that should be displayed for patients in _lists_
  460. patient.nameValidationRegex
  461. Names of the patients must pass this regex. Eg : ^[a-zA-Z \-]+$ contains only english alphabet letters, spaces, and hyphens. A value of .* or the empty string means no validation is done.
  462. patient.searchMaxResults
  463. 1000
  464. The maximum number of results returned by patient searches
  465. patient.viewingAttributeTypes
  466. A comma delimited list of PersonAttributeType names that should be displayed for patients when _viewing individually_
  467. patientIdentifierSearch.matchMode
  468. EXACT
  469. Specifies how patient identifiers are matched while searching for a patient. Valid values are 'EXACT, 'ANYWHERE' or 'START'. Defaults to 'EXACT' if missing or invalid value is present.
  470. patientIdentifierTypes.locked
  471. false
  472. Set to a value of true if you do not want allow editing patient identifier types, else set to false.
  473. patientSearch.matchMode
  474. START
  475. Specifies how patient names are matched while searching patient. Valid values are 'ANYWHERE' or 'START'. Defaults to start if missing or invalid value is present.
  476. patient_identifier.importantTypes
  477. A comma delimited list of PatientIdentifier names : PatientIdentifier locations that will be displayed on the patient dashboard. E.g.: TRACnet ID:Rwanda,ELDID:Kenya
  478. person.attributeSearchMatchMode
  479. EXACT
  480. Specifies how person attributes are matched while searching person. Valid values are 'ANYWHERE' or 'EXACT'. Defaults to exact if missing or invalid value is present.
  481. person.searchMaxResults
  482. 1000
  483. The maximum number of results returned by patient searches
  484. personAttributeTypes.locked
  485. false
  486. Set to a value of true if you do not want allow editing person attribute types, else set to false.
  487. provider.unknownProviderUuid
  488. Specifies the uuid of the Unknown Provider account
  489. providermanagement.addressWidget
  490. personAddress
  491. Address widget to use throughout the module
  492. providermanagement.advancedSearchPersonAttributeType
  493. Person attribute type, specified by uuid, to use as a search field on the advanced search page
  494. providermanagement.historicalPatientListDisplayFields
  495. Identifier:patient.patientIdentifier.identifier|Given Name:patient.personName.givenName|Family Name:patient.personName.familyName|Age:patient.age|Gender:patient.gender|Start Date:relationship.startDate|End Date:relationship.endDate
  496. Fields to display in the historical patient lists; specified as a pipe-delimited list of label/field pairs
  497. providermanagement.historicalProviderListDisplayFields
  498. Identifier:provider.identifier|Given Name:provider.person.personName.givenName|Family Name:provider.person.personName.familyName|Role:provider.providerRole|Gender:provider.person.gender|Start Date:relationship.startDate|End Date:relationship.endDate
  499. Fields to display in the historical provider lists; specified as a pipe-delimited list of label/field pairs
  500. providermanagement.locationTag
  501. Indicates the Health Facility location to which a provider could be assigned to.
  502. providermanagement.mandatory
  503. false
  504. true/false whether or not the providermanagement module MUST start when openmrs starts. This is used to make sure that mission critical modules are always running if openmrs is running.
  505. providermanagement.patientListDisplayFields
  506. Identifier:patient.patientIdentifier.identifier|Given Name:patient.personName.givenName|Family Name:patient.personName.familyName|Age:patient.age|Gender:patient.gender|Start Date:relationship.startDate
  507. Fields to display in the patient lists; specified as a pipe-delimited list of label/field pairs
  508. providermanagement.patientSearchDisplayFields
  509. Identifier:patient.patientIdentifier.identifier|Given Name:patient.personName.givenName|Family Name:patient.personName.familyName|Age:patient.age|Gender:patient.gender
  510. Fields to display in the patient search results; specified as a pipe-delimited list of label/field pairs
  511. providermanagement.personAttributeTypes
  512. Person attributes to display on the provider dashboard; specified as a pipe-delimited list of person attribute type uuids
  513. providermanagement.personSearchDisplayFields
  514. Given Name:person.personName.givenName|Family Name:person.personName.familyName|Age:person.age|Gender:person.gender
  515. Fields to display in the person search results; specified as a pipe-delimited list of label/field pairs
  516. providermanagement.providerListDisplayFields
  517. Identifier:provider.identifier|Given Name:provider.person.personName.givenName|Family Name:provider.person.personName.familyName|Role:provider.providerRole|Gender:provider.person.gender|Start Date:relationship.startDate
  518. Fields to display in the provider lists; specified as a pipe-delimited list of label/field pairs
  519. providermanagement.providerSearchDisplayFields
  520. Identifier:provider.identifier|Given Name:provider.person.personName.givenName|Family Name:provider.person.personName.familyName|Role:provider.providerRole|Gender:provider.person.gender
  521. Fields to display in the provider search results; specified as a pipe-delimited list of label/field pairs
  522. providermanagement.restrictedRoles
  523. Comma delimited list of UUIDs indicating the only Provider Roles to be available via the UI.
  524. providermanagement.restrictSearchToProvidersWithProviderRoles
  525. false
  526. True/false whether to restrict providers to those with roles
  527. providermanagement.started
  528. true
  529. DO NOT MODIFY. true/false whether or not the providermanagement module has been started. This is used to make sure modules that were running prior to a restart are started again
  530. providerSearch.matchMode
  531. EXACT
  532. Specifies how provider identifiers are matched while searching for providers. Valid values are START,EXACT, END or ANYWHERE
  533. referenceapplication.mandatory
  534. false
  535. true/false whether or not the referenceapplication module MUST start when openmrs starts. This is used to make sure that mission critical modules are always running if openmrs is running.
  536. referenceapplication.started
  537. true
  538. DO NOT MODIFY. true/false whether or not the referenceapplication module has been started. This is used to make sure modules that were running prior to a restart are started again
  539. registrationcore.biometrics.implementation
  540. Which Biometrics engine implementation to should we connect to?
  541. Specify a Spring bean name, or leave blank to disable
  542. registrationcore.birthdateEstimationStartMonth
  543. 0
  544. The month from which the birth date is estimated, with January having a value of 0
  545. registrationcore.familyNameAutoSuggestList
  546. A comma separated list of common names to auto suggest for the family name field, when registering patients.
  547. registrationcore.fastSimilarPatientSearchAlgorithm
  548. registrationcore.BasicSimilarPatientSearchAlgorithm
  549. Specifies a bean used for the fast similar patient search algorithm.
  550. registrationcore.givenNameAutoSuggestList
  551. A comma separated list of common names to auto suggest for the given name field, when registering patients.
  552. registrationcore.identifierSourceId
  553. Specifies the identifier source to use when generating patient identifiers
  554. registrationcore.local_mpi_identifierTypeMap.OpenEMPI ID
  555. a5d38e09-efcb-4d91-a526-50ce1ba5011a:2.16.840.1.113883.4.357:hl7
  556. Specifies the mapping from OpenEMPI Object ID (OID) to the local OpenMRS Application's identifier for OpenEMPI ID UUID.
  557. OpenEMPI ID is the default Global Identifier Domain (GID) for OpenEMPI but this can be changed.
  558. registrationcore.local_mpi_identifierTypeMap.OpenMRS ID
  559. 05a29f94-c0ed-11e2-94be-8c13b969e334:2.25.71280592878078638113873461180761116318:PI
  560. Specifies the mapping from OpenEMPI Object ID (OID) to the local OpenMRS Application's identifier for OpenMRS ID UUID.
  561. OpenMRS ID is the default generated identifier for OpenMRS but this can be changed.
  562. registrationcore.mandatory
  563. false
  564. true/false whether or not the registrationcore module MUST start when openmrs starts. This is used to make sure that mission critical modules are always running if openmrs is running.
  565. registrationcore.mpi.Hl7implementation
  566. registrationcore.mpiHl7v2HttpSender
  567. Specifies which bean should be used to send the Hl7 Message. Current options are:
  568. "registrationcore.mpiHl7v2HttpSender", "registrationcore.mpiHl7v2MllpSender".
  569. registrationcore.mpi.implementation
  570. Which MPI to should we connect to? Specify a Spring bean name, or leave blank to disable MPI integration. Options include:
  571. "registrationcore.mpi.implementation.PixPdq", "registrationcore.mpi.implementation.OpenEMPI".
  572. registrationcore.mpi.pdq.errorHandler.implementation
  573. Specify a Spring bean name of PDQ error handler service. It requires the xds-sender module and outgoing message
  574. exception module developed by SolDevelo. Set value to "outgoingmessageexceptions.PdqErrorHandlingService" and
  575. install those two modules to enable pix error handling functionality.
  576. registrationcore.mpi.pdqEndpoint
  577. http://localhost:5001/pdq
  578. Specifies endpoint for Hl7 PDQ Message
  579. registrationcore.mpi.pdqIdentifierTypeUuidList
  580. 05a29f94-c0ed-11e2-94be-8c13b969e334,a5d38e09-efcb-4d91-a526-50ce1ba5011a
  581. Specifies the list of identifiers to send in a PDQ query to get patient data from the MPI. Takes a list of UUID of patient identifier types - separate them with commas.
  582. UUIDs can be found in the patient_identifier_type database table.
  583. registrationcore.mpi.pdqPort
  584. 3600
  585. Specifies port for Hl7 PDQ Message
  586. registrationcore.mpi.personIdentifierTypeUuid
  587. a5d38e09-efcb-4d91-a526-50ce1ba5011a
  588. Specifies UUID of the identifier type that is used as the Global Identifier Domain (GID) in the MPI.
  589. It is generated by the MPI and is persisted in OpenMRS.
  590. registrationcore.mpi.pix.errorHandler.implementation
  591. Specify a Spring bean name of PIX error handler service. It requires the xds-sender module and outgoing message
  592. exception module developed by SolDevelo. Set value to "outgoingmessageexceptions.PixErrorHandlingService" and
  593. install those two modules to enable pix error handling functionality.
  594. registrationcore.mpi.pixEndpoint
  595. http://localhost:5001/pix
  596. Specifies the endpoint for the Hl7 PIX Message
  597. registrationcore.mpi.pixIdentifierTypeUuidList
  598. 05a29f94-c0ed-11e2-94be-8c13b969e334,a5d38e09-efcb-4d91-a526-50ce1ba5011a
  599. Specifies the list of identifiers to send in a PIX query to save the patient in the MPI. Takes a list of UUID of patient identifier types - separate them with commas.
  600. UUIDs can be found in the patient_identifier_type database table.
  601. registrationcore.mpi.pixPort
  602. 3700
  603. Specifies port for Hl7 PIX Message
  604. registrationcore.mpi.receivingApplication
  605. Specifies the receiving application in the MSH header section of the HL7 message
  606. registrationcore.mpi.receivingFacility
  607. Specifies sending Facility in the MSH header section of the HL7 message
  608. registrationcore.mpi.sendingApplication
  609. OpenMRS
  610. Specifies the sending application in the MSH header section of the HL7 message
  611. registrationcore.mpi.sendingFacility
  612. Specifies sending Facility in the MSH header section of the HL7 message
  613. registrationcore.mpi.url
  614. Specifies url to MPI server. (GSOC OpenEMPI Specific Implementation)
  615. registrationcore.openempi.enableProbabilisticMatching
  616. false
  617. Specifies if probability matching should be used (GSOC OpenEMPI Specific Implementation)
  618. registrationcore.openempi.globalIdentifierDomainId
  619. Specifies main identifier on MPI server (e.g. "xyz" for OpenEMPI) (GSOC OpenEMPI Specific Implementation)
  620. registrationcore.openmrsIdentifier.uuid
  621. 05a29f94-c0ed-11e2-94be-8c13b969e334
  622. UUID of the OpenMRS identifier that will be generated during MPI import unless it is present. By default set to the UUID of OpenMRS ID.
  623. Note: You have to have a Patient Identifier Source correctly configured and stored in the global property identifierSourceId
  624. registrationcore.patientNameSearch
  625. registrationcore.BasicPatientNameSearch
  626. Specifies a bean used for the auto suggest name feature.
  627. registrationcore.preciseSimilarPatientSearchAlgorithm
  628. registrationcore.BasicExactPatientSearchAlgorithm
  629. Specifies a bean used for the precise similar patient search algorithm.
  630. registrationcore.started
  631. true
  632. DO NOT MODIFY. true/false whether or not the registrationcore module has been started. This is used to make sure modules that were running prior to a restart are started again
  633. report.deleteReportsAgeInHours
  634. 72
  635. Reports that are not explicitly saved are deleted automatically when they are this many hours old. (Values less than or equal to zero means do not delete automatically)
  636. report.xmlMacros
  637. Macros that will be applied to Report Schema XMLs when they are interpreted. This should be java.util.properties format.
  638. reporting.dataEvaluationBatchSize
  639. -1
  640. This determines whether to run evaluators for Data in batches and what the size of those batches should be.
  641. A value of less than or equal to 0 indicates that no batching is desired.
  642. reporting.defaultDateFormat
  643. dd/MMM/yyyy
  644. Default date format to use when formatting report data
  645. reporting.defaultLocale
  646. en
  647. Default locale to use when formatting report data
  648. reporting.evaluationLoggerEnabled
  649. false
  650. If false, will disable the built in use of the evaluation logger to log evaluation information for performance diagnostics
  651. reporting.includeDataExportsAsDataSetDefinitions
  652. false
  653. If reportingcompatibility is installed, this indicates whether data exports should be exposed as Dataset Definitions
  654. reporting.mandatory
  655. false
  656. true/false whether or not the reporting module MUST start when openmrs starts. This is used to make sure that mission critical modules are always running if openmrs is running.
  657. reporting.maxCachedReports
  658. 10
  659. The maximum number of reports whose underlying data and output should be kept in the cache at any one time
  660. reporting.maxReportsToRun
  661. 1
  662. The maximum number of reports that should be processed at any one time
  663. reporting.preferredIdentifierTypes
  664. Pipe-separated list of patient identifier type names, which should be displayed on default patient datasets
  665. reporting.runReportCohortFilterMode
  666. showIfNull
  667. Supports the values hide,showIfNull,show which determine whether the cohort selector should be available in the run report page
  668. reporting.started
  669. true
  670. DO NOT MODIFY. true/false whether or not the reporting module has been started. This is used to make sure modules that were running prior to a restart are started again
  671. reporting.testPatientsCohortDefinition
  672. Points to a cohort definition representing all test/fake patients that you want to exclude from all queries and reports. You may set this to the UUID of a saved cohort definition, or to "library:keyInADefinitionLibrary"
  673. reportProblem.url
  674. http://errors.openmrs.org/scrap
  675. The openmrs url where to submit bug reports
  676. scheduler.password
  677. test
  678. Password for the OpenMRS user that will perform the scheduler activities
  679. scheduler.username
  680. admin
  681. Username for the OpenMRS user that will perform the scheduler activities
  682. search.caseSensitiveDatabaseStringComparison
  683. false
  684. Indicates whether database string comparison is case sensitive or not. Setting this to false for MySQL with a case insensitive collation improves search performance.
  685. search.indexVersion
  686. 7
  687. Indicates the index version. If it is blank, the index needs to be rebuilt.
  688. searchWidget.batchSize
  689. 200
  690. The maximum number of search results that are returned by an ajax call
  691. searchWidget.dateDisplayFormat
  692. Date display format to be used to display the date somewhere in the UI i.e the search widgets and autocompletes
  693. searchWidget.maximumResults
  694. 2000
  695. Specifies the maximum number of results to return from a single search in the search widgets
  696. searchWidget.runInSerialMode
  697. false
  698. Specifies whether the search widgets should make ajax requests in serial or parallel order, a value of true is appropriate for implementations running on a slow network connection and vice versa
  699. searchWidget.searchDelayInterval
  700. 300
  701. Specifies time interval in milliseconds when searching, between keyboard keyup event and triggering the search off, should be higher if most users are slow when typing so as to minimise the load on the server
  702. security.allowedFailedLoginsBeforeLockout
  703. 7
  704. Maximum number of failed logins allowed after which username is locked out
  705. security.passwordCannotMatchUsername
  706. true
  707. Configure whether passwords must not match user's username or system id
  708. security.passwordCustomRegex
  709. Configure a custom regular expression that a password must match
  710. security.passwordMinimumLength
  711. 8
  712. Configure the minimum length required of all passwords
  713. security.passwordRequiresDigit
  714. true
  715. Configure whether passwords must contain at least one digit
  716. security.passwordRequiresNonDigit
  717. true
  718. Configure whether passwords must contain at least one non-digit
  719. security.passwordRequiresUpperAndLowerCase
  720. true
  721. Configure whether passwords must contain both upper and lower case characters
  722. security.validTime
  723. 600000
  724. Specifies the duration of time in seconds for which a password reset token is valid, the default value is 10 minutes and the allowed values range from 1 minute to 12hrs
  725. serialization.xstream.mandatory
  726. false
  727. true/false whether or not the serialization.xstream module MUST start when openmrs starts. This is used to make sure that mission critical modules are always running if openmrs is running.
  728. serialization.xstream.started
  729. true
  730. DO NOT MODIFY. true/false whether or not the serialization.xstream module has been started. This is used to make sure modules that were running prior to a restart are started again
  731. uicommons.mandatory
  732. false
  733. true/false whether or not the uicommons module MUST start when openmrs starts. This is used to make sure that mission critical modules are always running if openmrs is running.
  734. uicommons.started
  735. true
  736. DO NOT MODIFY. true/false whether or not the uicommons module has been started. This is used to make sure modules that were running prior to a restart are started again
  737. uiframework.formatter.dateAndTimeFormat
  738. dd.MMM.yyyy, HH:mm:ss
  739. Format used by UiUtils.format for dates that have a time component
  740. uiframework.formatter.dateFormat
  741. dd.MMM.yyyy
  742. Format used by UiUtils.format for dates that do not have a time component
  743. uiframework.formatter.JSdateAndTimeFormat
  744. DD.MMM.YYYY, HH:mm:ss
  745. Format used by Javascript functions for dates that have a time component
  746. uiframework.formatter.JSdateFormat
  747. DD.MMM.YYYY
  748. Format used by Javascript for dates that do not have a time component
  749. uiframework.mandatory
  750. false
  751. true/false whether or not the uiframework module MUST start when openmrs starts. This is used to make sure that mission critical modules are always running if openmrs is running.
  752. uiframework.started
  753. true
  754. DO NOT MODIFY. true/false whether or not the uiframework module has been started. This is used to make sure modules that were running prior to a restart are started again
  755. uilibrary.mandatory
  756. false
  757. true/false whether or not the uilibrary module MUST start when openmrs starts. This is used to make sure that mission critical modules are always running if openmrs is running.
  758. uilibrary.started
  759. true
  760. DO NOT MODIFY. true/false whether or not the uilibrary module has been started. This is used to make sure modules that were running prior to a restart are started again
  761. user.headerAttributeTypes
  762. A comma delimited list of PersonAttributeType names that will be shown on the user dashboard. (not used in v1.5)
  763. user.listingAttributeTypes
  764. A comma delimited list of PersonAttributeType names that should be displayed for users in _lists_
  765. user.requireEmailAsUsername
  766. false
  767. Indicates whether a username must be a valid e-mail or not.
  768. user.viewingAttributeTypes
  769. A comma delimited list of PersonAttributeType names that should be displayed for users when _viewing individually_
  770. use_patient_attribute.healthCenter
  771. false
  772. Indicates whether or not the 'health center' attribute is shown when viewing/searching for patients
  773. use_patient_attribute.mothersName
  774. false
  775. Indicates whether or not mother's name is able to be added/viewed for a patient
  776. use_patient_attribute.tribe
  777. true
  778. Indicates whether or not the 'tribe' attribute is shown when viewing/searching for patients
  779. validation.disable
  780. false
  781. Disables validation of OpenMRS Objects. Only takes affect on next restart. Warning: only do this is you know what you are doing!
  782. visits.allowOverlappingVisits
  783. true
  784. true/false whether or not to allow visits of a given patient to overlap
  785. visits.assignmentHandler
  786. org.openmrs.api.handler.ExistingVisitAssignmentHandler
  787. Set to the name of the class responsible for assigning encounters to visits.
  788. visits.autoCloseVisitType
  789. comma-separated list of the visit type(s) to automatically close
  790. visits.enabled
  791. true
  792. Set to true to enable the Visits feature. This will replace the 'Encounters' tab with a 'Visits' tab on the dashboard.
  793. visits.encounterTypeToVisitTypeMapping
  794. Specifies how encounter types are mapped to visit types when automatically assigning encounters to visits. e.g 1:1, 2:1, 3:2 in the format encounterTypeId:visitTypeId or encounterTypeUuid:visitTypeUuid or a combination of encounter/visit type uuids and ids e.g 1:759799ab-c9a5-435e-b671-77773ada74e4
  795. webservices.rest.allowedips
  796. A comma-separate list of IP addresses that are allowed to access the web services. An empty string allows everyone to access all ws.
  797. IPs can be declared with bit masks e.g. 10.0.0.0/30 matches 10.0.0.0 - 10.0.0.3 and 10.0.0.0/24 matches 10.0.0.0 - 10.0.0.255.
  798. webservices.rest.mandatory
  799. false
  800. true/false whether or not the webservices.rest module MUST start when openmrs starts. This is used to make sure that mission critical modules are always running if openmrs is running.
  801. webservices.rest.maxResultsAbsolute
  802. 100
  803. The absolute max results limit. If the client requests a larger number of results, then will get an error
  804. webservices.rest.maxResultsDefault
  805. 50
  806. The default max results limit if the user does not provide a maximum when making the web service call.
  807. webservices.rest.quietDocs
  808. true
  809. If the value of this setting is "true", then nothing is logged while the Swagger specification is being generated.
  810. webservices.rest.started
  811. true
  812. DO NOT MODIFY. true/false whether or not the webservices.rest module has been started. This is used to make sure modules that were running prior to a restart are started again
  813. webservices.rest.uriPrefix
  814. The URI prefix through which clients consuming web services will connect to the web application, should be of the form http://{ipAddress}:{port}/{contextPath}
  815.  
  816.  
  817.  
  818. English (India) | English (United Kingdom) Last Build: 2020-09-30 21:06 Version: 2.5.0 SNAPSHOT Build c58512Powered by OpenMRS
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!