Previous Page TOC Index Next Page

8.2 TRIGGER EVENTS

The Master Files Change Notification message can be used for the following message-level trigger events:

Mnn: A message containing notifications of changes to a single master file.

nn defines a particular HL7 master file. Currently defined values are (see HL7 table 0003 - Event type ): M01 - master file not otherwise specified (for backward compatibility only); M02 - staff/practitioner master file; M03 - test/observation master file; M04 - charge description master file; M05 - location master file; M06 - clinical study master file; M12 - M99 - reserved for future HL7-defined master files. Site-specific master files should use a code of the form Znn. (See also Section 8.4.1.1, "Master file identifier (CE) 00658," HL7 table 0175 - Master file identifier codes.)

An MFN message may contain the following "file-level" events, as specified in the MFI segment:

REP: Replace current version of this master file with the version contained in this message.

UPD: Change file records as defined in the record-level event codes for each record that follows.

These are the only file-level events currently defined. REP means that every MFE segment that follows will use the MAD event code.

The replace option allows the sending system to replace a file without sending delete record-level events for each record in that file. UPD means that the events are defined according to the record-level event code contained in each MFE segment in that message.

An MFN message may contain the following "record-level" events, as specified in the MFE segments.

MAD: Add record to master file.

MDL: Delete record from master file.

MUP: Update record for master file.

MDC: Deactivate: discontinue using record in master file, but do not delete from database.

MAC: Reactivate deactivated record.

The MFD transaction is used for the following trigger event:

MFA: Master Files Delayed Application Acknowledgment.

Previous Page TOC Index Next Page