Imagine in a production box where you have lot of patients with radiology orders in OpenMRS database, and then you configure pacs and you start the pacs server. Then markers will start reading all the entires from beginning, which will take a lot of time. In that case we can add the last entry from OpenMRS event_records table to Pacs markers table as mentioned in the wiki (comparing the last_read_entry_id and feed_uri_for_last_read_entry from openelis markers table and openmrs events_tables would give you an idea of the exact values). That way we can avoid reading from the beginning.
If you don’t have too many patients with radiology orders in OpenMRS then you can ignore this step.
Thank you @binduak, that was quite helpful. The OpenELIS solution is very good. Unfortunatley, OpenELIS is not always part of the planned installation.
I still have problems finding the correct feed_uri_for_last_read_entry. Would you consider the following practice correct: