Chapter 08: Master Files
This chapter covers the reference lists that two systems share. It defines how staff, locations, test catalogues and charge codes are kept in step between systems.
Two systems must agree on the same lists before their clinical messages make sense. This chapter covers those lists: staff, locations, test catalogues and charge codes. A master file message, MFN, sends one list or a change to it from one system to another. These messages are sent rarely, often only when a list changes. When two systems disagree on a list, messages fail in ways that are hard to find.
What is in this chapter
- 15 trigger eventsthe real-world things that cause one of these messages to be sent
- 22 segmentsthe lines these messages are built from, and the fields on each
- 38 code tablesthe value sets the fields in this chapter draw from
- 5 message typesMFD, MFK, MFN, MFQ, MFR
Message types defined here
MFDMaster files delayed application acknowledgmentNamed by the standard without a structure of its own.
MFKMaster files application acknowledgment1 structure, fired by 15 trigger events.
MFNMaster files notification15 structures, fired by 14 trigger events.
MFQMaster files query1 structure, fired by 0 trigger events.
MFRMaster files response5 structures, fired by 5 trigger events.
Segments defined here
These 22 segments are defined in chapter 08. Messages in other chapters may still carry them.
CDMCharge Description Master SegmentCM0Clinical Study Master SegmentCM1Clinical Study Phase Master SegmentCM2Clinical Study Schedule Master SegmentIIMInventory Item Master SegmentLCCLocation Charge Code SegmentLCHLocation Characteristic SegmentLDPLocation Department SegmentLOCLocation Identification SegmentLRLLocation Relationship SegmentMFAMaster File Acknowledgment SegmentMFEMaster File Entry SegmentMFIMaster File Identification SegmentOM1General Segment (Fields That Apply to Most Observations)OM2Numeric Observation SegmentOM3Categorical Service/Test/Observation SegmentOM4Observations That Require Specimens SegmentOM5Observation Batteries (Sets) SegmentOM6Observations that are Calculated from Other ObservationsOM7Additional Basic Attributes (Fields That Apply to Most Observations/Services)PRCPricing SegmentZL7(proposed example only)
Trigger events
A trigger event is the thing that happens in the hospital and causes a message to be sent. Chapter 08 defines 15 of them.
M01Master File NotificationM02Staff/Practitioner Master File MessageM03Master File Notification - Test/ObservationM04Charge Description Master File MessageM05Patient Location Master File MessageM06Clinical study with phases and schedules master fileM07Clinical study without phases but with schedules master fileM08Master File Notification - Test/Observation (Numeric)M09Test/observation (categorical) master fileM10Master File Notification - Test/Observation BatteriesM11Master File Notification - Test/Calculated ObservationsM12Master file notification messageM13Master File Notification - GeneralM14Master File Notification - Site DefinedM15Inventory Item Master File Message