Location id's separated by a comma will have their remote data generated separately. Add location id's to this global property to generate remote data for those locations. This option is defined in the global property: remoteformentry.remote_locations. Optionally, remote return data can be filtered to generate data for only specific locations. The OpenMRS scheduled task "Generate Remote Return Data" should be turned on. The OpenMRS scheduled task "Process Central Server Imported Queue Items" should be turned on. Either way, the form is put in the error queue stack and must be reviewed manually by a data manager. If a different type of encounter is submitted and the patient doesn't exist yet, it is either because an identifying attribute was keyed in incorrectly at remote/central previously, or the patient never had an initial visit. 
When one of these forms are imported to central and the patient in them doesn't exist yet, they are automatically created from the data in the form.Set the Encounter Types that you assign to initial forms.Visit the "Edit Properties" page in the "Remote Form Entry" section.This setup operation simply adds a few fields to the form so that most patient data can be passed from remote to central
These forms can be used by both remote and central at the same time.
Choose the forms you want to use as remote forms. Visit the "Setup Forms" page in the "Remote Form Entry" section on the Administration screen. The runtimeproperty "rver_type" must be set to "central" (webapp restart required to read runtime properties again): rver_type=central. Formentry to google docs install#
Install the RemoteFormEntry module on both the remote server and the central server.
0 kommentar(er)
