This X12 Transaction Set 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.
To indicate the start of a transaction set and to assign a control number
To indicate the beginning of a transaction set
To supply the full name of an individual or organizational entity
To specify additional names
To specify the location of the named party
To specify the geographic place of the named party
To specify identifying information
To identify a person or office to whom administrative communications should be directed
To specify pertinent dates and times
To specify quantity information
To uniquely identify a transaction to an application
To transmit standard code list identification information
To identify standard industry codes
To identify dependencies among and the content of hierarchically related groups of data segments
To transmit standard code list identification information
To identify standard industry codes
To specify pertinent dates and times
To specify identifying information
To specify quantity information
To specify textual data
To specify basic item identification data
To describe a product or process in coded or free-form format
To specify quantity information
To specify pertinent dates and times
To specify identifying information
To specify physical measurements or counts, including dimensions, tolerances, variances, and weights
(See Figures Appendix for example of use of C001)
To uniquely identify a transaction to an application
To specify textual data
To supply the full name of an individual or organizational entity
To specify additional names
To specify the location of the named party
To specify the geographic place of the named party
To specify identifying information
To identify a person or office to whom administrative communications should be directed
To specify pertinent dates and times
To supply demographic information
To specify physical measurements or counts, including dimensions, tolerances, variances, and weights
(See Figures Appendix for example of use of C001)
To identify the type or transmission or both of paperwork or supporting information
To uniquely identify a transaction to an application
To specify quantity information
To transmit standard code list identification information
To identify standard industry codes
To describe a product or process in coded or free-form format
To specify pertinent dates and times
To specify quantity information
To specify textual data
To specify pertinent dates and times
To transmit a hash total for a specific element in the transaction set
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
