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 | + | To turn on the Outbound Document Interface, you must set the update a table in the database called Preference. The preference is: DocumentWriteOutboundEvent and must be set to Y in the Works database: |
| + | <source lang=tsql> | ||
| + | UPDATE Preference SET Setting = 'Y' | ||
| + | WHERE Name = 'DocumentWriteOutboundEvent' | ||
| + | </source> | ||
==Events== | ==Events== | ||
Revision as of 22:31, 30 June 2009
Enable
To turn on the Outbound Document Interface, you must set the update a table in the database called Preference. The preference is: DocumentWriteOutboundEvent and must be set to Y in the Works database:
UPDATE Preference SET Setting = 'Y'
WHERE Name = 'DocumentWriteOutboundEvent'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.