New: Drop-in replacement for Change Healthcare APIs

EDI 650 Maintenance Service Order

Functional Group MO

X12M Supply Chain Subcommittee

This Draft Standard for Trial Use contains the format and establishes then data contents of the Maintenance Service Order Transaction Set (650) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set provides a uniform, singular medium for the exchange of maintenance related information among organizations involved in the reporting, requesting, scheduling, planning, estimating, coordinating and performing of maintenance actions. It provides the structure to convey maintenance-related information, including maintenance action directives, maintenance actions, cost estimates, maintenance action assignments, maintenance action status, and completion reports. This transaction set can be used in a bi-directional environment alone or in conjunction with the Project Schedule Reporting Transaction Set (806) to link schedule and maintenance action information as well as with the Specifications/Technical Information Transaction Set (841) to link maintenance-related, media independent, technical data.

Heading

Position
Segment
Name
Max use
  1. To indicate the start of a transaction set and to assign a control number

  2. To indicate the beginning of a transaction set

  3. To specify identifying information

  4. To specify pertinent dates and times

  5. N1 Loop Optional
    Repeat >1
    1. To identify a party by type of organization, name, and code

      The N1 segment identifies the organization originating and receiving the transaction set.
    2. To specify additional names

    3. To specify the location of the named party

    4. To specify the geographic place of the named party

    5. To identify a person or office to whom administrative communications should be directed

    6. To specify identifying information

  6. LM Loop Optional
    Repeat >1
    1. To transmit standard code list identification information

    2. Code to transmit standard industry codes

    3. To identify a person or office to whom administrative communications should be directed

    4. To specify identifying information

Detail

Position
Segment
Name
Max use
  1. HL Loop Mandatory
    Repeat >1
    1. To identify dependencies among and the content of hierarchically related groups of data segments

      The HL levels are group work candidate and work candidate. Valid HL parent-child relationships are 1) group work candidate-group work candidate and 2) group work candidate-work candidate.
    2. To provide a description of the included specification or technical data items

    3. To specify identifying information

    4. To specify basic item identification data

    5. To specify pertinent dates and times

    6. To specify quantity information

    7. To identify and answer yes and no questions, including the date, time, and comments further qualifying the condition

      The YNQ segment identifies conditions related to a maintenance or repair requirement.
    8. To indicate the total monetary amount

    9. To qualify percent amounts and supply percent amounts

    10. To specify physical measurements or counts, including dimensions, tolerances, variances, and weights (See Figures Appendix for example of use of C001)

    11. CLI Loop Optional
      Repeat >1
      1. To identify the cost line items associated with a specific reporting structure reference (i.e., a work breakdown structure) or summary project level reference

      2. To specify quantity information

      3. To indicate the total monetary amount

      4. To identify rate amounts or percents for a specific cost or other line item

    12. LM Loop Optional
      Repeat >1
      1. To transmit standard code list identification information

        The LM loop identifies management data that pertains to each use of the HL loop.
      2. Code to transmit standard industry codes

      3. To specify identifying information

      4. To specify pertinent dates and times

    13. NM1 Loop Optional
      Repeat >1
      1. To supply the full name of an individual or organizational entity

        The NM1 segment identifies individuals and organizations involved in identifying, coordinating or performing maintenance.
      2. To specify additional names

      3. To specify the location of the named party

      4. To specify the geographic place of the named party

      5. To specify a communication contact number

      6. To specify identifying information

    14. MTX Loop Optional
      Repeat >1
      1. To specify textual data

      2. To specify pertinent dates and times

      3. To supply the full name of an individual or organizational entity

      4. To specify identifying information

  2. To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Stedi is a registered trademark of Stedi, Inc. Stedi's EDI Reference is provided for marketing purposes and is free of charge. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.