This page is made available through the support of Berry College.

NOTICE: This is not an official Berry College web page. The contents of this page are the sole responsibility of John R. Grout and do not represent the opinions or policies of Berry College.

This web page accompanies “Using Process Mapping to Identify Patient Safety Hazards in Micro-Systems” in Quality and Safety in Healthcare. by John Grout

INTEGRATION DEFINITION FOR FUNCTION MODELING (IDEF0) is a process mapping technique specified in Draft Federal Information Processing Standards Publication 183 (FIPS 183).  It has a precise syntax. Multiple flows are shown by how the arrows enter process boxes.  “Each side of the function box has a standard meaning in terms of box/arrow relationships. The side of the box with which an arrow interfaces reflects the arrow's role. Arrows entering the left side of the box are inputs. Inputs are transformed or consumed by the function to produce outputs. Arrows entering the box on the top are controls. Controls specify the conditions required for the function to produce correct outputs[usually interpretted as “information”]. Arrows leaving a box on the right side are outputs. Outputs are the data or objects produced by the function.” (FIPS 183)

“Arrows connected to the bottom side of the box represent mechanisms . Upward pointing arrows identify some of the means that support the execution of the function [usually interpretted as tools and equipment]... Mechanism arrows that point downward are call arrows. Call arrows enable the sharing of detail between models (linking them together) or between portions of the same model. The called box provides detail for the caller box” (FIPS 183).                         

Function boxes are linked together to map the process. Some boxes are complex enough that the task within the box can have its own “child” process map diagram.  These “parent” and “child” diagrams are linked together in a “context diagram” which can be represented as a tree or as an indented list as shown in the menu on the left.  Diagram numbers listed in parentheses have not been completed. The figure below (from FIPS183) shows the relationships between diagrams.

According to the specification, IDEF-0 maps should only contain 4-6 process boxes per map. Additional detail will force the mapping to continue on another map at a lower level in the hierarchy. The map numbering convention that provides the hierarchical links between maps will not provide unique numbering schemes for more than 9 boxes per map.  This limit to the number of boxes per map does not impede the documentation and presentation of detailed process information. To the contrary, using multiple levels of hierarchy provide the capability to specify at whatever detail is needed.  Moreover, those needing less detail are not forced to absorb all the details. IDEF-0 is at once easy to read and extremely detailed. 

Logical operators that control “if-then” or iterative loops are not explicitly provided by IDEF-0. They can be described using the multiple arrows with labels specifying the conditions under which they are used.