User visits the "Import Forms" page (linked from the central server's Administration screen).User walks/jogs/drives/flies to central with the usb key to the central server. The xml forms are moved from the formentry queue to the remoteformentry pending queue.Behind the scenes: The xml forms are zipped and timestamped.Using that page, the user downloads a zip file to a usb key, cdr, or cdrw.The user transporting data from remote to central visits the "Export Forms" page (linked from the Administration screen).Behind the scenes: The xml forms that infopath submits back to OpenMRS are stored in the formentry queue table.Infopath forms are filled out in the remote site (is ongoing throughout this workflow).The values in the drop down are taken from the locations table Set the location of this remote server.The OpenMRS scheduled task "Generate Remote Return Data" should always be turned off.The OpenMRS scheduled task "Process Central Server Imported Queue Items" should always be turned off.The OpenMRS scheduled task "Process HL7 Task" should always be turned off.Set both the "Start on Startup" to false and select "Stop" for the task.If this task is turned on, forms submitted by infopath will be parsed and placed into the remote server database and never transferred back to central.VERY IMPORTANT The OpenMRS scheduled task "Process Form Entry Queue" should always always always be turned off.Now set the global properties for the remote server.The runtimeproperty "rver_type" must be set to "remote": rver_type=remote.(Be sure to copy the database after setting up your forms for remote entry.) RemoteFormEntry will copy just the right encounters/obs the first time data is taken out the site. Note: If you have a large database, you might want to skip exporting the (large) number of rows in the "obs" and "encounter" tables to save time. Copy the central server database to the remote server's database.Remote data will be generated into six groups:.Locations id's separated by a space will generate remote data for those locations all together.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.Install the RemoteFormEntry module on both the remote server and the central server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |