The fields in the MFI segment are defined in Figure 8-1. MFI attributes.
Figure 8-1. MFI attributes
SEQ |
LEN |
DT |
OPT |
RP/# |
TBL# |
ITEM# |
ELEMENT NAME |
1 |
60 |
CE |
R |
0175 |
00658 |
Master File Identifier |
|
2 |
180 |
HD |
O |
00659 |
Master File Application Identifier |
||
3 |
3 |
ID |
R |
0178 |
00660 |
File-Level Event Code |
|
4 |
26 |
TS |
O |
00661 |
Entered Date/Time |
||
5 |
26 |
TS |
O |
00662 |
Effective Date/Time |
||
6 |
2 |
ID |
R |
0179 |
00663 |
Response Level Code |
8.4.1.0 MFI field definitions
Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field is a CE data type that identifies a standard HL7 master file. This table may be extended by local agreement during implementation to cover site-specific master files (z-master files). Refer to HL7 table 0175 - Master file identifier code for valid values.
Table 0175 - Master file identifier code
Value |
Description |
CDM |
Charge description master file |
CMA |
Clinical study with phases and scheduled master file |
CMB |
Clinical study without phases but with scheduled master file |
LOC |
Location master file |
OMA |
Numerical observation master file |
OMB |
Categorical observation master file |
OMC |
Observation batteries master file |
OMD |
Calculated observations master file |
PRA |
Practitioner master file |
STF |
Staff master file |
Components: <namespace ID (IS) ^ <universal ID (ST) ^ <universal ID type (ID)
Definition: This field contains an optional code of up to 180 characters which (if applicable) uniquely identifies the application responsible for maintaining this file at a particular site. A group of intercommunicating applications may use more than a single instance of a master file of certain type (e.g., charge master or physician master). The particular instance of the file is identified by this field.
Definition: This field defines the file-level event code. Refer to HL7 table 0178 - File level event code for valid values.
Table 0178 - File level event code
Value |
Description |
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 |
Definition: This field contains the time stamp for file-level event on originating system.
Definition: This optional field contains the effective date/time, which can be included for file-level action specified. It is the date/time the originating system expects that the event is to have been completed on the receiving system. If this field is not present, the action date/time should default to the current date/time (when the message is received).
Definition: These codes specify the application response level defined for a given Master File Message at the MFE segment level as defined in HL7 table 0179 - Response level. Required for MFN-Master File Notification message. Specifies additional detail (beyond MSH-15-accept acknowledgment type and MSH-16-application acknowledgment type) for application-level acknowledgment paradigms for Master Files transactions. MSH-15-accept acknowledgment and MSH-16-application acknowledgment type operate as defined in Chapter 2.
Table 0179 - Response level
Value |
Description |
NE |
Never. No application-level response needed |
ER |
Error/Reject conditions only. Only MFA segments denoting errors must be returned via the application-level acknowledgment for this message |
AL |
Always. All MFA segments (whether denoting errors or not) must be returned via the application-level acknowledgment message |
SU |
Success. Only MFA segments denoting success must be returned via the application-level acknowledgment for this message |