EDI 175 Court Notice
Functional Group FC
X12F Finance Subcommittee
This Draft Standard for Trial Use contains the format and establishes the data contents of the Court Notice Transaction Set (175) for use within an Electronic Data Interchange (EDI) environment. This transaction set can be used to notify interested parties about important court events and actions related to a specific court case.
Heading
- 010Transaction Set HeaderMandatoryMax 1
To indicate the start of a transaction set and to assign a control number
- 020Beginning SegmentMandatoryMax 1
To indicate the beginning of a transaction set.
- 030Reference NumbersOptionalMax >1
To specify identifying numbers.
- CDS Loop MandatoryRepeat >1
- 050Case DescriptionMandatoryMax 1
To identify and describe a specific court case
- 052Specification IdentifierOptionalMax 1
To provide a description of the included specification or technical data items.
- 058Loop HeaderMandatoryMax 1
To indicate that the next segment begins a loop
- CED Loop MandatoryRepeat >1
- 060Court Event DescriptionMandatoryMax 1
To describe court events and actions in a specific court case
- 070Date/Time ReferenceMandatoryMax >1
To specify pertinent dates and times
- 072Specification IdentifierOptionalMax 1
To provide a description of the included specification or technical data items.
- 080Reference NumbersOptionalMax >1
To specify identifying numbers.
- 090Monetary AmountOptionalMax >1
To indicate the total monetary amount.
- 095Period AmountOptionalMax >1
To indicate a quantity and/or amount for an identified period
- 100QuantityOptionalMax >1
To specify quantity information.
- 110Case DescriptionOptionalMax >1
To identify and describe a specific court case
CDS describes a different case, usually from a different court, related to a specific court event. - 120Message TextOptionalMax >1
To provide a free form format that would allow the transmission of text information.
- LM Loop OptionalRepeat >1
- 125Code Source InformationMandatoryMax 1
To transmit standard code list identification information
- 126Industry CodeOptionalMax >1
Code to transmit standard industry codes
- 125Code Source InformationMandatoryMax 1
- NM1 Loop OptionalRepeat >1
- 130Individual or Organizational NameMandatoryMax 1
To supply the full name of an individual or organizational entity
- 132Specification IdentifierOptionalMax 2
To provide a description of the included specification or technical data items.
- 140Additional Name InformationOptionalMax >1
To specify additional names or those longer than 35 characters in length
- 150Address InformationOptionalMax >1
To specify the location of the named party
- 160Geographic LocationOptionalMax 1
To specify the geographic place of the named party
- 170Reference NumbersOptionalMax >1
To specify identifying numbers.
- 180Date/Time ReferenceOptionalMax 1
To specify pertinent dates and times
- 190Administrative Communications ContactOptionalMax >1
To identify a person or office to whom administrative communications should be directed
- 193Demographic InformationOptionalMax 1
To supply demographic information
- 197MeasurementsOptionalMax 3
To specify physical measurements or counts, including dimensions, tolerances, variances, and weights (See Figures Appendix for example of use of C001.)
- LX Loop OptionalRepeat >1
- 200Assigned NumberMandatoryMax 1
To reference a line number in a transaction set.
- 210Reference NumbersOptionalMax >1
To specify identifying numbers.
- 220InformationOptionalMax 1
To report information
- LM Loop OptionalRepeat >1
- 230Code Source InformationMandatoryMax 1
To transmit standard code list identification information
- 240Industry CodeMandatoryMax >1
Code to transmit standard industry codes
- 230Code Source InformationMandatoryMax 1
- 200Assigned NumberMandatoryMax 1
- 130Individual or Organizational NameMandatoryMax 1
- 060Court Event DescriptionMandatoryMax 1
- 250Loop TrailerMandatoryMax 1
To indicate that the loop immediately preceding this segment is complete
- 050Case DescriptionMandatoryMax 1
- 260Transaction Set TrailerMandatoryMax 1
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments).