Difference between revisions of "Outbound Document Interface"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
==Enable== | ==Enable== | ||
To turn on the Outbound Document Interface, you must set the [[Framework Preferences|Framework Preference]], '''DocumentWriteOutboundEvent''', to "Y". | To turn on the Outbound Document Interface, you must set the [[Framework Preferences|Framework Preference]], '''DocumentWriteOutboundEvent''', to "Y". | ||
| + | |||
| + | ==Events== | ||
| + | All actions on documents/notes create an event, with the exception of viewing, printing and faxing. These events are posted to the Event_Table for ConnectR to process. The Outbound Document Interface must be setup to receive and process the events appropriately. You would limit the events in ConnectR, based on Status, Source (the EHR, or Interface) and other appropriate criteria. | ||
| + | |||
| + | ==Inbound documents== | ||
| + | Inbound documents do process in as Events that are sent outbound. | ||
Revision as of 23:15, 22 June 2009
Enable
To turn on the Outbound Document Interface, you must set the Framework Preference, DocumentWriteOutboundEvent, to "Y".
Events
All actions on documents/notes create an event, with the exception of viewing, printing and faxing. These events are posted to the Event_Table for ConnectR to process. The Outbound Document Interface must be setup to receive and process the events appropriately. You would limit the events in ConnectR, based on Status, Source (the EHR, or Interface) and other appropriate criteria.
Inbound documents
Inbound documents do process in as Events that are sent outbound.