EDI 500 Medical Event Reporting
Functional Group MM
X12N Insurance Subcommittee
This Draft Standard for Trial Use contains the format and establishes the data contents of the Medical Event Reporting Transaction Set (500) for use within the context of an Electronic Data Interchange (EDI) environment. This standard can be used to make voluntary, mandatory, baseline, annual and semi-annual reports on medication and medical device adverse effects and product problems.
Heading
- 010Transaction Set HeaderMandatoryMax 1To indicate the start of a transaction set and to assign a control number 
- 020Beginning SegmentMandatoryMax 1To indicate the beginning of a transaction set 
- NM1 Loop OptionalRepeat >1- 030Individual or Organizational NameMandatoryMax 1To supply the full name of an individual or organizational entity The NM1 loop carries information about the party transmitting the report.
- 040Additional Name InformationOptionalMax 2To specify additional names or those longer than 35 characters in length 
- 050Address InformationOptionalMax 2To specify the location of the named party 
- 060Geographic LocationOptionalMax 1To specify the geographic place of the named party 
- 070Reference IdentificationOptionalMax >1To specify identifying information 
- 080Administrative Communications ContactOptionalMax >1To identify a person or office to whom administrative communications should be directed 
- 090Date/Time ReferenceOptionalMax >1To specify pertinent dates and times 
- 100QuantityOptionalMax >1To specify quantity information 
- 110TraceOptionalMax >1To uniquely identify a transaction to an application 
- LM Loop OptionalRepeat >1- 120Code Source InformationMandatoryMax 1To transmit standard code list identification information 
- 130Industry CodeMandatoryMax >1Code to transmit standard industry codes 
 
- 120Code Source InformationMandatoryMax 1
 
- 030Individual or Organizational NameMandatoryMax 1
Detail
- HL Loop OptionalRepeat >1- 010Hierarchical LevelMandatoryMax 1To identify dependencies among and the content of hierarchically related groups of data segments The HL loop divides a report into sections such as event, patient, device, medication, reporter, user facility, distributor and manufacturer.
- LM Loop OptionalRepeat >1- 020Code Source InformationMandatoryMax 1To transmit standard code list identification information The LM loop provides report data in coded form.
- LQ Loop MandatoryRepeat >1- 030Industry CodeMandatoryMax 1Code to transmit standard industry codes 
- 040Date/Time ReferenceOptionalMax >1To specify pertinent dates and times 
- 050Reference IdentificationOptionalMax >1To specify identifying information 
- 060QuantityOptionalMax >1To specify quantity information 
- 070TextOptionalMax >1To specify textual data 
 
- 030Industry CodeMandatoryMax 1
 
- 020Code Source InformationMandatoryMax 1
- LIN Loop OptionalRepeat >1- 080Item IdentificationMandatoryMax 1To specify basic item identification data The LIN loop provides product device or medication specific information.
- 090Product/Item DescriptionOptionalMax >1To describe a product or process in coded or free-form format 
- 100QuantityOptionalMax >1To specify quantity information 
- 110Date/Time ReferenceOptionalMax >1To specify pertinent dates and times 
- 120Reference IdentificationOptionalMax >1To specify identifying information 
- 130MeasurementsOptionalMax >1To specify physical measurements or counts, including dimensions, tolerances, variances, and weights (See Figures Appendix for example of use of C001) 
- 140TraceOptionalMax >1To uniquely identify a transaction to an application 
- 150TextOptionalMax >1To specify textual data 
 
- 080Item IdentificationMandatoryMax 1
- NM1 Loop OptionalRepeat >1- 160Individual or Organizational NameMandatoryMax 1To supply the full name of an individual or organizational entity The NM1 loop carries party or organization reporting information.
- 170Additional Name InformationOptionalMax 2To specify additional names or those longer than 35 characters in length 
- 180Address InformationOptionalMax 2To specify the location of the named party 
- 190Geographic LocationOptionalMax 1To specify the geographic place of the named party 
- 200Reference IdentificationOptionalMax >1To specify identifying information 
- 210Administrative Communications ContactOptionalMax >1To identify a person or office to whom administrative communications should be directed 
- 220Date/Time ReferenceOptionalMax >1To specify pertinent dates and times 
- 230Demographic InformationOptionalMax >1To supply demographic information 
- 240MeasurementsOptionalMax >1To specify physical measurements or counts, including dimensions, tolerances, variances, and weights (See Figures Appendix for example of use of C001) 
- 250PaperworkOptionalMax >1To identify the type or transmission or both of paperwork or supporting information 
- 260TraceOptionalMax >1To uniquely identify a transaction to an application 
- QTY Loop OptionalRepeat >1- 270QuantityMandatoryMax 1To specify quantity information 
- LM Loop OptionalRepeat >1- 280Code Source InformationMandatoryMax 1To transmit standard code list identification information 
- 290Industry CodeMandatoryMax >1Code to transmit standard industry codes 
 
- 280Code Source InformationMandatoryMax 1
 
- 270QuantityMandatoryMax 1
- PID Loop OptionalRepeat >1- 300Product/Item DescriptionMandatoryMax 1To describe a product or process in coded or free-form format 
- 310Date/Time ReferenceOptionalMax >1To specify pertinent dates and times 
- 320QuantityOptionalMax >1To specify quantity information 
 
- 300Product/Item DescriptionMandatoryMax 1
- MTX Loop OptionalRepeat >1- 330TextMandatoryMax 1To specify textual data 
- 340Date/Time ReferenceOptionalMax >1To specify pertinent dates and times 
 
- 330TextMandatoryMax 1
 
- 160Individual or Organizational NameMandatoryMax 1
 
- 010Hierarchical LevelMandatoryMax 1
- 350Transaction TotalsOptionalMax 1To transmit a hash total for a specific element in the transaction set CTT01 is the number of occurrences of the HL segment.
- 360Transaction Set TrailerMandatoryMax 1To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)