Professional Documents
Culture Documents
1
eMDR HL7 Pointers - Change Log
2
eMDR HL7 Pointers - Change Log
C6
3
eMDR HL7 Pointers - Change Log
4
eMDR HL7 Pointers - Change Log
5
eMDR HL7 Pointers - Change Log
Change Description
Updated the text for field name from 'Device Returned to Manufacturer for Evaluation' to 'Device Not Returned to Manufacturer for Evaluation'
6
eMDR HL7 Pointers - Change Log
Change Description
Updated the text for field name from 'Device Returned to Manufacturer for Evaluation' to 'Device Not Returned to Manufacturer for Evaluation'
Updated the text for field name from 'Device Returned to Manufacturer for Evaluation' to 'Device Not Returned to Manufacturer for Evaluation'
Inserted new Route of Administration option - "045 - Nasal" and incremented numbers afterwards
Added note to E3: Please do not use any occupation codes that has been retired. Any retired occupation code found in the submission will be
rejected
Updated Text in Column D (HL7 ICSR Implementation pointers) for G7
Updated Thirty-Day columns F (Concept Preferred Term) and G (Definition)
Removing the statement “For all follow-up MDRs, please provide 'NEW' or 'Updated' information ONLY. Do not submit an MDR that includes
old (prior submitted information) and new or updated information”
Removing the statement “Use nullFlavor attribute to indicate unknown.”
Updated NON-HEALTHCARE PROFESSION with C-Code=C134833
Updated list of Event Locations.
Updated X-Path with correct code C9 - C86045
Updated X-Path with correct code C10 - C54055
Updated X-Path with correct code C9 - C86045
Updated X-Path with correct code C10 - C54055
Logging in Change Log that Administrator/Supervisor C Code was updated to C134832 (was C48905) on June 28, 2018.
Changed the 'kgs' unit value to 'kg'
ASKU is not allowed for D8 field in R2. Removed the note to “use ASKU”.
7
eMDR HL7 Pointers - Change Log
Change Description
Renumbered MW Form Reference. Old Numbering: C8, C9, C10 respectively; These fields have had their number reduced by one because C7
was rolled into C6
Renamed option "Lay User/Patient" to "Patient/Consumer"
D6 (Implant Date) and D7 (Explant Date) are now renumbered D6a and D6b. D8 (Reprocessed single-use device?) and D9 (Address of
reprocessor) are now renumbered D7a and D7b. D10 (Device Available for Evaluation) and D11 (Concomitant Products and Therapy Dates)
have been reduced by 1 to D9 and D10 because of the reduction in the number of section D fields
Added code "Third Party Servicer"
Renamed Headings
Same xpath. Renamed Section Name "Device Problem Code"
8
eMDR HL7 Pointers - Change Log
Change Description
Removal of G2 phone number means that all of these fields have their numbers reduced by one
Renamed Section Header. Old label: "If IND, Give Protocol #" (G6)
Added Summary Report Option; Added Ccode to Summary report - C84831
Added No. of events (NOE) summarized Field
Renamed Headings
Removed "XPATH" excel sheet. Use xpaths defined in 'xPath to Form'. Some xpaths may differ from the earlier version of this document.
Renamed Section Name "Device Problem Code". Note: The xpath has been updated
Introduced new xpath and CCode ( C54577 )
Renamed Section Name "Patient Problem Code". Note: The xpath has been updated
Introduced new xpath and CCode ( C122929 )
Same xpath. Renamed Section Name "Evaluation code method"
Same xpath. Renamed Section Name "Evaluation code results"
Same xpath. Renamed Section Name "Evaluation code conclusions"
Added new MW Section.
9
eMDR HL7 Pointers - Change Log
Change Description
10
eMDR HL7 Pointers - Change Log
11
eMDR HL7 Pointers - Change Log
12
eMDR HL7 Implementation Pointers
FDA\CDRH\OSB 03/23/2023
Med Watch Form MedWatch Field/Section Name MedWatch 3500A (paper) Instructions HL7 ICSR Implementation pointers
(https://www.fda.gov/downloads/AboutFDA/ReportsManualsForms/Forms/UCM295636.pdf)
NOTE: Please use one of the following three values for all instances with a nullFlavor attribute: ASKU, NI, or NA
VALIDATION -- the following are validated on your submission: CFN/FEI/HCFA number, field lengths, required fields, FDA/NCI Codes and additional fields marked on this spreadsheet, F10 and H6 codes
Warning: When testing, you must enter
Initial a valid
reports CFN
-- we or FEI encourage
strongly number or your report
you to will values
use null be rejected. Please
defined abovedoinstead
not send a report
of blank number starting with "5555555-".
fields
Supplemental/Follow-up Reports - required fields are -- report number and G7 -- check follow-up and provide a follow-up number; provide discrete data in appropriate field vs. H10. Refer to ICSR Implementation Guide for more details. Note: Supplemental reports are
obtain repeated information from the initial report.
If you submit an initial report and realize that you want to remove the data from the report, you will NOT be able to by submitting a supplemental report and adding a ‘blank’ or ‘null” value to the field. The system will interpret the field as no change from the initial rep
database will not be updated for that field.
Report Number For Manufacturer report number, please use the following format -- 10 digitFEI-4
digit year-5 digit sequence number E.g. 1234567890-2006-00001; 7 digit CFN-4
digit year-5 digit sequence number E.g.- 5555555-2006-00001. At the start of
every new year the 5 digit report sequence number must be reset to 00001 for
the first new initial MDR.
Warning: When testing, you must enter a valid CFN or FEI number or your
report will be rejected. Please do not send a report number starting with
"5555555-".
For User Facility, same format but replace FEI/CFN with HCFA number and pad
with enough zeros in the beginning to make the first part a 10 digit number;
CFN, FEI and HCFA numbers are validated; during testing, please use a
leading 7 with sequence numbers -- example -- CFN-YEAR-70001 or
FEI/HCFA-YEAR-70001; REQUIRED FIELD
Not on Form Form Code Form Code is a field used to identify reports based upon a pre-defined category of reporter. Form code is assigned Enter entire code (including letters and numbers) if instructed by FDA.
and used for analysis of reported events. This is only used when specifically assigned by FDA. Typical format is
F12345.
Not on Form Exemption Number Exemption Number is an administrative identifier used for tracking purposes of approved exemptions, variances, or Enter exemption number if this report has an approved, applicable exemption
alternative forms of adverse event reporting. Exemption Numbers are also referenced in
correspondences/communications between FDA and the recipient of the exemption approval. Typical format is
E1234567.
A Patient Information
A1 Patient Identifier Provide the patient's initials or some other type of identifier that will allow both the submitter and the initial reporter
(if different) to locate the case if contacted for follow-up. Do not use the patient's name or social security number.
The patient's identity is held in strict confidence by FDA and protected to the fullest extent of the law.
A2 Date of Birth Provide the most precise information available. Enter the patient's birthdate, if known, or the patient's age at the DOB is preferred. Use YYYYMMDD format; use full date format; if month or day
time of event onset. is unknown, then use 01 for either
A2 Age If the patient is 3 years or older, use years (e.g., 4 YR) See MedWatch instructions.
If the patient is less than 3 years old, use months (e.g., 24 MO) Indicate time units used as DA - day; MO - Month; YR - Year; WK - Week.
If the patient is less than 1 month old, use weeks (e.g., 2 WK) Stored unit of measure is Days.
A2 Age Unit If the patient is less than 1 week old, use days (e.g., 5 DA) Note: Age Unit is REQURIED if Age is provided and vice versa. Do not send
Provide the best estimate if exact age is unknown one without the other.
A3 Gender Enter the patient's gender. If the adverse event is a congenital anomaly, report the sex of the child Please look at the vocabulary attachment. Use a code to indicate the
appropriate gender
A4 Weight Indicate whether the weight is in pounds (lbs) or kilogram (kg). Make a best estimate if exact weight is unknown. Indicate weight units used as lbs - pounds; kg - kilogram.
A5 Ethnicity Indicate the ethnicity of the patient. Choose only one response. Please do NOT make a best guess. Please look at the vocabulary attachment. Use a code to indicate the
appropriate ethnicity Indicate the ethnicity of the patient. Choose only one
response. Please do NOT make a best guess.
A6 Race Indicate the race of the patient as reported by the patient. You may choose multiple answers for race. Please do Please look at the vocabulary attachment. Use a code to indicate the
NOT make a best guess. appropriate race. Indicate the race of the patient as reported by the patient.
You may choose multiple answers for race. Please do NOT make a best guess.
Adverse event: Any incident where the use of a medication (drug or biologic, including human cell, tissue, or cellular
or tissue-based product (HCT/P), at any dose, or a medical device (including in vitro diagnostics) is suspected to
have resulted in an adverse outcome in a patient.
Product problem (e.g., defects/malfunctions): Any report regarding the quality, performance, or safety of any
medical product. This category is selected when reporting device malfunctions that could lead to a death or serious
injury if the malfunction were to recur.
13
eMDR HL7 Implementation Pointers
FDA\CDRH\OSB 03/23/2023
Med Watch Form MedWatch Field/Section Name MedWatch 3500A (paper) Instructions HL7 ICSR Implementation pointers
(https://www.fda.gov/downloads/AboutFDA/ReportsManualsForms/Forms/UCM295636.pdf)
B2 Outcomes attributed to adverse event Indicate ALL that apply to the reported event: Please look at the vocabulary attachment. Use a code(s) to indicate an
Death: Check if death was an outcome of the adverse event, or if the cause of the death is unknown. Include the outcome(s).
date of death, if known.
DO NOT check if: The patient died while using a medical product, but there was no suspected association between
the death and the use of the product
A fetus is aborted because of a congenital anomaly, or is miscarried
Life-threatening: Check if suspected that:
The patient was at substantial risk of dying at the time of the adverse event, or
Use or continued use of the device might have resulted in the death of the patient
Hospitalization (initial or prolonged): Check if admission to the hospital or prolongation of hospitalization was a
result of the adverse event.
DO NOT check if:
A patient in the hospital received a medical product and subsequently developed an otherwise non-serious adverse
event, UNLESS the adverse event prolonged the hospital stay
DO check if:
A patient is admitted to the hospital for one or more days, even if released on the same day
An emergency room visit results in admission to the hospital
Note: Emergency room visits that do not result in admission to the hospital should be evaluated for one of the other
serious outcomes (e.g., life-threatening; required intervention to prevent permanent impairment or damage; other
serious (medically important event)
Disability or Permanent Damage: Check if the adverse event resulted in a substantial disruption of a person's ability
to conduct normal life functions.
Congenital Anomaly/Birth Defect: Check if suspected that exposure to a medical product prior to conception or
during pregnancy may have resulted in an adverse outcome in the child.
Required Intervention to Prevent Permanent Impairment/Damage (Devices): if either situation may be due to the
use of a medical device and medical or surgical intervention was necessary to:
Preclude permanent impairment of a body function, or
Prevent permanent damage to a body structure.
Other Serious (Important Medical Events):
Check when, based on appropriate medical judgment, the event may jeopardize the patient and may require
medical or surgical intervention to prevent one of the other outcomes. Examples include allergic bronchospasm
requiring emergency treatment, blood dyscrasias or convulsions that do not result in hospitalization, or the
development of drug dependency or drug abuse. For human cells, tissues, and cellular and tissue-based products
(HCT/P’s), such interventions could include antibiotics in response to a positive culture or clinical suspicion of an
infection, but not as prophylaxis for infection.
Devices: Check ONLY if the other categories are not applicable to the event. Describe the patient outcome in the
actual narrative of the event in block B5.
B2 Date of death Populate Date of Death in 'deceaseTime Value'; use YYYYMMDD format
B3 Date of Event Provide the actual or best estimate of the date of first onset of the adverse event. If day is unknown, month and year Use YYYYMMDD format
are acceptable. If day and month are unknown, year is acceptable.
When a newborn baby is found to have a congenital anomaly, the event onset date is the date of birth of the child
When a fetus is aborted because of a congenital anomaly, or is miscarried, the event onset date is the date
pregnancy is terminated.
If information is available as to time during pregnancy when exposure occurred, indicate that information in narrative
block B5.
B4 Date of this Report Drugs and Biologics, including Human Cells, Tissues, and Cellular and Tissue-Based Products: The date the report Populate with the 'Date report filled out' by manufacturer. CDRH will be
is filled out. changing med watch instructions to coincide with Drugs and Biologics for
electronic reporting; Use YYYYMMDD format
Devices: The date the initial reporter provided the information about the event [i.e., the first person or entity who
initially provided the information to the user facility, manufacturer, or Distributor (Importer)].
14
eMDR HL7 Implementation Pointers
FDA\CDRH\OSB 03/23/2023
Med Watch Form MedWatch Field/Section Name MedWatch 3500A (paper) Instructions HL7 ICSR Implementation pointers
(https://www.fda.gov/downloads/AboutFDA/ReportsManualsForms/Forms/UCM295636.pdf)
B6 Relevant tests/laboratory data Provide all appropriate information, including relevant negative test and laboratory findings, in order to most Please look at the vocabulary attachment. Use the 'text' area to describe
completely convey how the medical work-up/assessment led to strong consideration of medical-product-induced relevant tests/laboratory data
disease as etiology for clinical status, as other differential diagnostic considerations were being eliminated.
Include: Any relevant baseline laboratory data prior to the administration or use of the medical product
All laboratory data used in diagnosing the event; Any available laboratory data/engineering analyses (for devices)
that provide further information on the course of the event
If available, include:
Any pre- and post-event medication levels and dates (if applicable)
Synopses of any relevant autopsy, pathology, engineering, or lab reports
If preferred, copies of any reports may be submitted as attachments, with all confidential information deleted. DO
NOT identify any patient, physician or institution by name. The initial's reporter's identity should be provided in full in
section E.
B7 Other relevant history, including preexisting If available, provide information on: Please look at the vocabulary attachment. Use 'text' for narrative description
medical conditions
Other known conditions in the patient, e.g.,
Hypertension
Diabetes mellitus
Renal/hepatic dysfunction, etc.
Significant history
Race
Allergies
Pregnancy history
Smoking and alcohol use
Drug abuse, etc.
C Suspect Product(s)
C1 Drug Sequence Number Only applies to electronic submissions: Only applies to electronic submissions: If entering a suspect product, then a
For Initial Reports: Drug Sequence Number is a REQUIRED FIELD.
* Assign each suspect drug with a different drug sequence number (1-20).
* No duplicate sequence numbers in the submission.
* Be sure not to have any gaps with your sequence numbers in the submission
* Example: 3 suspect products added. Drug sequence numbers should be 1, 2, and 3. It cannot be 1, 2, and 4.
If you fail to comply with these requirements, your submission will fail during processing.
Drug Type Only applies to electronic submissions: Enter the drug type: NDA, ANDA, BLA, or IND
Approval Number Only applies to electronic submissions: Provide the approval number for the selected drug type
If IND/PreANDA, Give Protocol # Only applies to electronic submissions: If drug type is IND or PreANDA, provide the Protocol #.
Name and Strength Use the trade name as marketed (e.g., if there is a Structured Product Labeling (SPL) for the product, then use the
Product name and/or Active ingredient as it appears in SPL; If there is no SPL and a label is attached to the report,
then use the same naming convention as in the attached label). If unknown or if no trade name, use the generic
Manufacturer/Compounder name (with the manufacturer or labeler’s name, if known). For foreign reports, use both the foreign trade name and
the U.S. generic name.
For human cells, tissues, and cellular and tissue-based products (HCT/Ps), please provide the common name of the
HCT/P and the name of the manufacturer. You can also indicate if the HCT/P has a proprietary or trade name, in
addition to the common name of the HCT/P (e.g., Brand A bone chips, or Brand B skin tissue). Examples: Achilles
tendon, Iliac crest bone, Islet Cells, or human skin.
NDC # or Unique ID The National Drug Code (NDC #) is a universal product identifier for human drugs. NDC is a three-segment number;
zeros and dashes should be included as they appear on the original manufacturer’s product label and/ or
packaging. NDC numbers are particularly useful to the FDA in investigating drug product quality problems.
Human Cells, Tissues, and Cellular and Tissue-Based Products (HCT/Ps) must have a Unique ID number to track
the product. For reports involving HCT/Ps, this unique ID should be provided in this box.
Lot # If known, include the lot number(s) with all product problem reports, or any adverse event report with a biologic or
medication.
C2 List Medical Product and Treatment Given at the Enter all Suspect Medical Products and Therapy Dates in Section D10
Same Time of the Event and Date
C3 Dose Describe how the product was used by the patient (e.g., 500 mg QID orally or 10 mg every other day IV). For
reports involving overdoses, the amount of product used in the overdose should be listed, NOT the prescribed
amount. Maximum whole number length = 7. Maximum Decimal length = 3.
15
Refer to the General Instructions for Form FDA 3500A MedWatch-APPENDIX for list of Routes of Administration
eMDR HL7 Implementation Pointers
FDA\CDRH\OSB 03/23/2023
Med Watch Form MedWatch Field/Section Name MedWatch 3500A (paper) Instructions HL7 ICSR Implementation pointers
C3 Describe how the product was used by the patient (e.g., 500 mg QID orally or 10 mg every other day IV). For
(https://www.fda.gov/downloads/AboutFDA/ReportsManualsForms/Forms/UCM295636.pdf)
reports involving overdoses, the amount of product used in the overdose should be listed, NOT the prescribed
Dose Unit Please look at the vocabulary attachment for ICSH-M2 code list
amount. Maximum whole number length = 7. Maximum Decimal length = 3.
Number of separate dosages
Refer to the General Instructions for Form FDA 3500A MedWatch-APPENDIX for list of Routes of Administration
Frequency
Frequency Unit Please look at the vocabulary attachment for ICSH-M2 code list
Route Used Please look at the vocabulary attachment for ICSH-M2 code list
C4 Treatment Dates/Therapy Dates - Start Date Provide the date administration was started (or best estimate) and the date stopped (or best estimate). If no dates
are known, an estimated duration is acceptable (e.g., 2 years) or, if therapy was less than one day, then duration is
appropriate (e.g., 1 dose or 1 hour for an IV).
For human cells, tissues, and cellular and tissue-based products HCT/Ps, provide the date of transplant and if
Treatment Dates/Therapy Dates - Stop Date applicable, the date of explanation.
NOTE: Use block C4 to record the date that a diagnostic test was performed for reports that involve an in vitro
diagnostic product or radiation therapy.
C5 Diagnosis Use For Provide the indication for which the product was prescribed or used in this particular patient.
C6 Product Type If the product was compounded, select the checkbox. Please look at the attached vocabulary. Populate TRUE if answer is YES;
If the product is sold over the counter, select the checkbox populate FALSE if answer is NO.
If the product is Generic, select the checkbox
If the product is Biosimilar, select the checkbox Multiple selection / codes can be provided.
If the product is PreANDA, select the checkbox
If the product is PRE1938, select the checkbox
C7 Expiration date Include ONLY with all product problem reports and events involving human cells, tissues, and tissue and cellular- Use YYYYMMDD format
based products (HCT/Ps).
C8 Event Abated After Use Stopped or Dose In addition to checking the appropriate box, provide supporting lab tests and dates, if available Please look the vocabulary attachment. Choose a code; populate TRUE if
Reduced? answer is YES; populate FALSE if answer is NO under 'value'
C9 Event Reappeared After Reintroduction In addition to checking the appropriate box, provide supporting lab tests and dates, if available Please look the vocabulary attachment. Choose a code; populate TRUE if
answer is YES; populate FALSE if answer is NO under 'value'
D Suspect Medical Device
D1 Brand Name The trade or proprietary name of the suspect medical device as used in product labeling or in the catalog (e.g., Flo-
Easy Catheter, Reliable Heart Pacemaker, etc.). This information may 1) be on a label attached to a durable device,
2) be on a package of a disposable device, or 3) appear in labeling materials of an implantable device.
Single use reprocessed devices may bear the OEM's brand name. If the suspect device is a reprocessed single-use
device, enter "NA".
D3 Manufacturer name & address If available, enter the full name and mailing address of the manufacturer of the suspect medical device. If Block D7A For HL7 Name and Address, please provide the following, as applicable --
below is 'Yes', enter the name and address of the reprocessor. Manufacturer Name, Street Address Line 1, Street Address Line 2, City, State,
Postal Code, Country;
Manufacturer Name
Manufacturer Address Street Line 1
Manufacturer Address Street Line 2
Manufacturer City Enter US City or Foreign (State/Territory/Province)
Manufacturer State Code Please refer to https://pe.usps.com/text/pub28/28apb.htm for appropriate state
codes for United States
Manufacturer Zip Code The Five digit zip code
Manufacturer Zip Code Extension The 4 digit zip code extension
Manufacturer Country Code Current CDRH Implementation will support both 2 character and 3 character
country codes. Please refer to the countryCodeMapping sheet.
Manufacturer Postal Code Postal Code for international addresses - 10 digit string
Manufacturer Email
Manufacturer Fax Number provide a string with no formatting, can not be longer than 26 chars
16
eMDR HL7 Implementation Pointers
FDA\CDRH\OSB 03/23/2023
Med Watch Form MedWatch Field/Section Name MedWatch 3500A (paper) Instructions HL7 ICSR Implementation pointers
(https://www.fda.gov/downloads/AboutFDA/ReportsManualsForms/Forms/UCM295636.pdf)
D4 Model #, Lot #, Catalog #, Expiration Date, Model #, Catalog #, Serial #, Lot #, Expiration date, Unique Identifier (UDI) NOTE: Do not add "Other #" as part of section D4 or in the UDI field. Any
Serial #, Unique Identifier (UDI)# submission that contains "Other #" data will be rejected
If available, provide any expiration date or any or all identification numbers associated with the suspect medical
device exactly as they appear on the device or device labeling. This includes spaces, hyphens, etc.
Model #: The exact model number found on the device label or accompanying packaging
Catalog #: The exact number as it appears in the manufacturer's catalog, device labeling, or accompanying
packaging
Serial #: This number can be found on the device label or accompanying packaging; it is assigned by the
manufacturer and should be specific to each device
Lot #: This number can be found on the label or packaging material
Expiration date: If available; this date can often be found on the device itself or printed on the accompanying
packaging.
Unique Identifier (UDI) #: The Unique identification number for the suspect device - Provide only the DI # portion of
the UDI
D4 Model Number
D4 Lot Number
D4 Catalog Number
D4 Expiration Date Use YYYYMMDD format
D4 Serial Number
D4 Unique Identifier (UDI) # An identifier that adequately identifies a device through its distribution and use by meeting the requirements of 21 NOTE: Do not add "Other #" as part of section D4 or in the UDI field. Any
CFR 830.20 of this chapter. A unique device identifier is composed of a (1) device identifier and (2) production submission that contains "Other #" data will be rejected
identifier.2 21 CFR 801.3. For more information regarding UDI, refer to the following FDA link:
http://www.fda.gov/downloads/MedicalDevices/DeviceRegulationandGuidance/GuidanceDocuments/
UCM410439.pdf
NOTE: Manufacturer and distributor reports should include the DI only. User Facility reporters who cannot parse
the DI out of the complete UDI should include the whole human-readable UDI.
D5 Operator of device - Code Indicate the type (not the name) of person operating or using the suspect medical device on the patient at the time Please look at the vocabulary attachment.
of the event as follows:
D7A Is this a single-use device that was reprocessed Indicate "Yes" or "No" Please look at the vocabulary attachment. Choose a code; populate TRUE if
and reused on a patient? If the original equipment manufacturer (OEM) is unable to determine if their single use device was reprocessed and answer is YES; populate FALSE if answer is NO under 'value'.
reused on a patient, then the OEM should enter 'UNK' in Block D8 and in Block H10 (Additional Manufacturer
Narrative) describe the efforts made to obtain the information and any responses.
D7B If yes to item D7A, enter name and address of Enter the name and address of the reprocessor of the single-use device. For Name and Address, please provide the following, as applicable --
reprocessor Reprocessor Name, Street Address Line 1, Street Address Line 2, City, State,
Any entity that reprocesses single-use devices for reuse in humans is the manufacturer of the reprocessed single- Postal Code, Country;
use device.
Reprocessor Name
Reprocessor Address Street Line 1
Reprocessor Address Street Line 2
Reprocessor City Enter US City or Foreign (State/Territory/Province)
Reprocessor State Code Please refer to https://pe.usps.com/text/pub28/28apb.htm for appropriate state
codes for United States
Reprocessor Zip Code The Five digit zip code
Reprocessor Zip Code Extension The four digit Zip code extension
Reprocessor Country Code Current CDRH Implementation will support both 2 character and 3 character
country codes. Please refer to the countryCodeMapping sheet.
Reprocessor Postal Code Postal Code for international addresses - 10 digit string
Reprocessor Email
Reprocessor Fax Number provide a string with no formatting, can not be longer than 26 chars
D8 Was this Device serviced by a third party? Indicate "Yes" or "No" or Unknown Please look the vocabulary attachment. Choose a code; populate TRUE if
answer is YES; populate FALSE if answer is NO under 'value'
D9 Device available for evaluation? Date returned to Indicate whether the device is available for evaluation by the manufacturer. Indicate if the device was returned to Please look the vocabulary attachment. Choose a code; populate TRUE if
Manufacturer the manufacturer and, if so, the date of the return. answer is YES; populate FALSE if answer is NO under 'value'
Do not send the device to FDA.
17
eMDR HL7 Implementation Pointers
FDA\CDRH\OSB 03/23/2023
Med Watch Form MedWatch Field/Section Name MedWatch 3500A (paper) Instructions HL7 ICSR Implementation pointers
(https://www.fda.gov/downloads/AboutFDA/ReportsManualsForms/Forms/UCM295636.pdf)
D9 - Part 2 Date device returned to manufacturer Indicate whether the device is available for evaluation by the manufacturer. Indicate if the device was returned to Populate a date if answer is YES under 'effectiveTime value';
the manufacturer and, if so, the date of the return. Use YYYYMMDD format
D10 Concomitant Medical Products and Therapy List and provide product names and therapy dates for any other medical products (drugs, biologics, including Please look at the vocabulary attachment. ; Use 'text' for narrative; multiple
Dates human cells, tissues, and cellular and tissue-based products (HCT/Ps), or medical devices, etc.) that the patient products can be entered
was using at the time of the event. Do not include products used to treat the event.
NOTE: Enter any Concomitant Medical Products and Therapy Dates from Section C2 in Suspect Products into
Section D10
D10 - Part 2 Concomitant Medical Products and Therapy Therapy Dates Indicate Therapy date if available under 'effectiveTime value';
Dates Use YYYYMMDD format;
E Initial Reporter
E1 Initial Reporter Name Name should be reported as -- First Name, Middle Name, Last Name;
Please provide the name, mailing address, and phone number of the person who initially reported the adverse
event to the user facility, manufacturer, or Distributor (Importer), and who can be contacted to provide information
on the event if follow-up is necessary. If available, provide reporter's E-mail address and/or fax number.
For medical device reporting by user facilities, this person may or may not be the designated medical device
reporting (MDR) contact.
Initial Reporter First Name
Initial Reporter Middle Name
Initial Reporter Last Name
Initial Reporter Title
E1 Address Address as -- Street Address Line 1, Street Address Line 2, City, State, Postal
Code, Country;
Initial Reporter Facility Name
Initial Reporter Street Address Line 1
Initial Reporter Address Street Line 2
Initial Reporter City Enter US City or Foreign (State/Territory/Province)
Initial Reporter State Code Please refer to https://pe.usps.com/text/pub28/28apb.htm for appropriate state
codes for United States
Initial Reporter Zip Code The Five digit zip code
Initial Reporter Zip Code Extension The four digit Zip code extension
Initial Reporter Country Code Current CDRH Implementation will support both 2 character and 3 character
country codes. Please refer to the countryCodeMapping sheet.
Initial Reporter Postal Code Postal Code for international addresses - 10 digit string
Initial Reporter Email provide email address under 'telecom value' following prefix "mailto:"
Initial Reporter Fax Number provide a string with no formatting, can not be longer than 26 chars
E1 Phone # Please provide phone number in the following format -- “+” country_code “(“
area_code “)” 3-digit prefix “-“ 4-digit number “x“ up to 5-digit extension
e.g. +1(240)276-0001x12345; if extension is not applicable, leave it out;
international numbers would follow the same format -- e.g. “+” phone_country “(“
phone_city “)” phone_local -- +011(123)1234567890 or if there is no phone_city:
+011()1234567890
E2 Health Professional? E2: Health Professional?: Indicate whether the initial reporter is a health professional (e.g., physician, pharmacist, For HL7, value of E2 will be inferred from E3
nurse, etc.) or not. If not a health professional, complete block E3 by filling in NA.
E3 Occupation Indicate the initial reporter's occupation (particularly type of health professional), and include specialty if appropriate. Please look at the vocabulary attachment. Occupation is not a required field.
NOTE: The information you provide for occupation title will not be used in any
downstream systems.
NOTE: Please do not use any occupation codes that has been retired. Any
retired occupation code found in the submission will be rejected
E4 Initial reporter also sent report to FDA Indicate whether the initial reporter also notified or submitted a copy of this report to FDA. Populate 'false' if answer is YES; populate 'true' if answer is NO
F For Use by User Facility/Distributor (Importer) (Devices Only)
F1 Check one: user facility, importer Indicate whether the report is from a user facility or Distributor (Importer). Please look at the vocabulary attachment under Type_of_Reporter. Choose an
appropriate code
F2 UF/Distributor (Importer) Report Number Enter the complete number of the report exactly as entered in the upper right corner of the front page. For a follow-
up report, the UF/Distributor (Importer) report number must be identical to the number assigned to the initial report.
NOTE: Once you have filled out F2 (user facility number), F1 will automatically get populated.
F3 User Facility or Distributor (Importer) Enter the full name and address of the user facility or Distributor (Importer) reporting site. For Name and Address, please provide the following, as applicable -- User
Name/Address Facility Name, Street Address Line 1, Street Address Line 2, City, State, Postal
Code, Country;
F3 User Facility Name
User Facility Address Street Line 1
User Facility Address Street Line 2
User Facility City Enter US City or Foreign (State/Territory/Province)
User Facility State Code Please refer to https://pe.usps.com/text/pub28/28apb.htm for appropriate state
codes for United States
User Facility Zip Code The Five digit zip code
18
eMDR HL7 Implementation Pointers
FDA\CDRH\OSB 03/23/2023
Med Watch Form MedWatch Field/Section Name MedWatch 3500A (paper) Instructions HL7 ICSR Implementation pointers
(https://www.fda.gov/downloads/AboutFDA/ReportsManualsForms/Forms/UCM295636.pdf)
User Facility Zip Code Extension The four digit Zip code extension
User Facility Country Code Current CDRH Implementation will support both 2 character and 3 character
country codes. Please refer to the countryCodeMapping sheet.
User Facility Postal Code Postal Code for international addresses - 10 digit string
F4 Contact person Enter the full name of the medical device reporting (MDR) contact person. This is the person designated by the Name should be reported as -- First Name, Middle Name, Last Name; provide
facility's most responsible person as the device user facility/Distributor (Importer) contact for this requirement. FDA title.
will conduct its MDR correspondence with this individual. The contact person may or may not be an employee of the
facility. However, the facility and its responsible officials will remain the parties ultimately responsible for compliance
with the MDR requirements.
F6 Date user facility or Distributor (importer) Enter the date that the user facility's medical personnel or the Distributor (Importer) became aware that the device Use YYYYMMDD format
became aware of event has or may have caused or contributed to the reported event.
F7 Type of report Check the appropriate box to identify the type of report being filed, i.e., an initial report of an event or a follow-up to Please look at the vocabulary attachment. Choose an appropriate code;
a previously submitted report.
If a follow-up report, make sure that the UF/ Distributor (Importer) report number for the previously submitted initial
report is recorded in block F2. In the blank provided in block F7, record the appropriate sequence of follow-up to
that particular initial report (e.g., first follow-up report=follow-up #1, second follow-up report=follow-up #2, and so
on).
Follow-up reports should not repeat material that was submitted in the initial report, but should ONLY provide
additional or corrected information on the previously reported event.
F9 Approximate age of device Enter the age of the device or a best estimate (include unit of time used: e.g., day, week, month, year). Please look at the vocabulary attachment. Choose an appropriate code.
Populate appropriate number or text; Indicate time units used as DA - day; MO
- Month; YR - Year; WK - Week.
F9 Approximate age of device\Text Please look at the vocabulary attachment. Choose an appropriate code. Device
age text
F10 Event problem codes (refer to coding manual) Enter up to 3 "patient" and 3 "device" codes from the Codes Manual that most accurately describe the event. Provide as many adverse event codes as appropriate; no limitation on number
Patient codes describe what happened to the patient as a result of the event and device codes describe device of values; Please visit
failures or problems encountered during the event. If more than 3 "patient" codes or more than 3 "device" codes are https://www.fda.gov/MedicalDevices/DeviceRegulationandGuidance/
needed, record them on a separate sheet, mark it "F10", and provide the report number and page number. PostmarketRequirements/ReportingAdverseEvents/MDRAdverseEventCodes/
ucm584205.htm for the list of valid values
If a user facility or a Distributor (Importer) has reason to believe that a reused device has or may have caused or
contributed to an adverse event, the device problem code 1537 ("Reuse") should be entered in F10 along with any Note: At least 1 HECC and 1 DPC code is REQUIRED
other applicable device and/or patient-related codes
F11 part 1 Report sent to FDA? Check yes or no and indicate the date sent, if applicable. Please look at the vocabulary attachment. Populate 'false' if answer is YES;
populate 'true' if answer is NO
F11 Part 2 Date Report Sent Check yes or no and indicate the date sent, if applicable. If answer is YES, provide date report sent to FDA under 'time value';
Use YYYYMMDD format
F12 Location where event occurred Check the location of the actual occurrence of the event. If none of the designated location options apply, check the Please look at the vocabulary attachment. Choose an appropriate code.
other box and provide the location.
19
eMDR HL7 Implementation Pointers
FDA\CDRH\OSB 03/23/2023
Med Watch Form MedWatch Field/Section Name MedWatch 3500A (paper) Instructions HL7 ICSR Implementation pointers
(https://www.fda.gov/downloads/AboutFDA/ReportsManualsForms/Forms/UCM295636.pdf)
F12 Location where event occurred\text to explain Use 'text' to describe 'Other'
OTHER
F13 Report sent to manufacturer? Check yes or no and indicate the date sent, if applicable. Please look at the vocabulary attachment. Populate 'false' if answer is YES;
populate 'true' if answer is NO; Please look at the vocabulary attachment.
F13 Part 2 Date Sent to Manufacturer If answer is YES, provide date report sent to FDA under 'low value' (Beginning
of the time interval captures when the report was sent to manufacturer. 'high
value' will be populated under G4 to indicate when the report was received by
the manufacturer; Use YYYYMMDD format
F14 Manufacturer name/address Enter full name and address of the device manufacturer, if available. This would normally be identical to the address For Name and Address, please provide the following, as applicable --
in D3. However, if the device was reprocessed, then F14 is identical to D7B, the name and address of the Manufacturer Name, Street Address Line 1, Street Address Line 2, City, State,
reprocessor. Postal Code, Country;
F14 Manufacturer Name
Manufacturer Address Street Line 1
Manufacturer Address Street Line 2
Manufacturer City Enter US City or Foreign (State/Territory/Province)
Manufacturer State Code Please refer to https://pe.usps.com/text/pub28/28apb.htm for appropriate state
codes for United States
Manufacturer Zip Code The Five digit zip code
Manufacturer Zip Code Extension The four digit Zip code extension
Manufacturer Country Code Current CDRH Implementation will support both 2 character and 3 character
country codes. Please refer to the countryCodeMapping sheet.
Manufacturer Postal Code Postal Code for international addresses - 10 digit string
Manufacturer Email
Manufacturer Fax Number provide a string with no formatting, can not be longer than 26 chars
G All manufacturers
G1 Contact Office (and Manufacturing Site for Enter the full name and address of the manufacturer reporting site [contact office], including contact name. If the Please ALWAYS submit the MDR CONTACT information as the first address in
Devices) manufacturing site of the device is not the same as the contact office, enter site and the name and address of the the HL7 message. Repeat the <contactParty> block second time and provide
or Compounding Outsourcing Facility manufacturing site after the contact office name and address. MANUFACTURING SITE address. Please note that the sequence of the
address is extremely important and you MUST maintain the order of MDR
Contact Info first and Manufacturing Site info second. For Name and Address,
please provide the following, as applicable -- Name -- Title or prefix, First Name,
Middle Name, Last Name; Address -- Manufacturer Facility Name, Street
Address Line 1, Street Address Line 2, City, State, Postal Code, Country;
20
eMDR HL7 Implementation Pointers
FDA\CDRH\OSB 03/23/2023
Med Watch Form MedWatch Field/Section Name MedWatch 3500A (paper) Instructions HL7 ICSR Implementation pointers
(https://www.fda.gov/downloads/AboutFDA/ReportsManualsForms/Forms/UCM295636.pdf)
G2 Report source Check the box(es) that most accurately describe(s) how the manufacturer [contact office] became aware of the Please look at the vocabulary attachment. Choose an appropriate code; use
reported adverse event or from where the information about the adverse event originated. Foreign: Foreign 'text' to explain 'OTHER'
sources include foreign governments, foreign affiliates of the application/license holder, foreign licensors and
licensees, foreign medical facilities, etc. The country of origin should be included.
Study: Post marketing, clinical trial, surveillance, or other study that involves a systematic collection of adverse
events from a protocol designed specifically to investigate product safety.
Literature: If the report source is the scientific literature or an unpublished manuscript, a copy of the article or
manuscript must be attached. Foreign language articles should be translated into English. Record the date of the
article as the date of the event (block B3), and provide a full literature citation in block H10. Drugs and Biologics,
including HCT/Ps : A separate 3500A form must be completed for each identifiable patient described in the article or
manuscript. Consumer (including attorneys): Additional information, whenever possible, should be sought from the
treating healthcare provider. A determined effort should be made to obtain additional detailed information from
health professionals for all serious reactions, adverse events & product problems initially reported by consumers.
When this additional information is obtained, the follow-up report should check health professional rather than
consumer in block G3. Health professional: Physician, pharmacist, nurse, etc.
User facility: User facility should be checked if the manufacturer received the report from the MDR contact in a user
facility as identified in section F. The health professional should be listed as the initial reporter on the front page of
the form. Company representative: This check box would be selected if a company representative reported the
event to the contact office based on information received from a health professional. The health professional should
be listed as the initial reporter in Section E. Distributor: This check box would be selected for a report received from
the distributor (importer) of the suspect product. The health professional or other reporter should be listed as the
initial reporter on the front page of the form. Other: Any source not covered by the previous categories. For drug or
biologic, including HCT/P manufacturers, this check box would be selected when submitting a follow-up to a report
originally obtained from FDA through a MedWatch to Manufacturer program transmission of a serious direct report,
and the FDA-assigned report number entered into the space provided. Other may also be used to identify when the
source is another manufacturer - include the Manufacturer Report Number of the other manufacturer.
G3 Date received by manufacturer This means the date when the applicant, manufacturer, corporate affiliate, etc. receives information that an adverse Populate the date as 'high value' under
event or medical device malfunction has occurred. This would apply to a report received anywhere in the world. /pertinentInformation1/secondaryCaseNotification/receiver
(YYYYMMDD format) negationInd/time/high value; Use YYYYMMDD format
Follow-up reports: Use the date that the follow-up information was received.
G4 Premarket Application Numbers and Premarket This block is for use by all manufacturers of drug, device, biological products [including cell, tissue, and cellular and Provide either the PMA/510(k) number or Device BLA number. DO NOT use
Checkboxes tissue-based products (HCT/P)] and combination products. Provide whatever information is applicable to the this field for Drug BLAs. If there are any suspect products (or Drugs) associated
suspect product identified in section C or suspect medical device identified in Section D. If the report lists two with the adverse event, enter the suspect product information in Section C of
products by the same applicant as suspect, the report should be submitted to the application file of the product the 3500A Form including the product type and approval number for (A)NDA,
thought by the initial reporter to be the more likely cause of the adverse event. If they are equally suspect, the report IND, or BLA.
should be submitted to the application file of the product that is first alphabetically. (A)NDA #: The abbreviated new
drug application or the new drug application (NDA) number. The report should be filed to the first approved NDA if a Product Type checkboxes such as Combination Product, Compounded, OTC,
product has several NDAs and the specific one cannot be determined. PMA/510(k) #: The pre-market application Pre-1938 and PreANDA, should be entered in Section C
(PMA) or pre-market notification [510(k)] submission number for the approved / cleared medical device or
combination product. If a product has several applicable PMA/510(k)’s and the specific one cannot be determined,
then the first approved / cleared PMA or 510(k) number should be reported. Combination Product: Check the box if
the suspect product is comprised of a drug-device, device-biological, drug-biological , or a drug-device-biological
product, Pre-1938: Check the box if the suspect medication was marketed prior to 1938 and does not have an NDA
#.
G4 PMA / 510k Enter CDRH supplied PMA / 510k Application number Enter CDRH apporved application number with prefix
G4 BLA # Enter Device BLA number, if available Enter Device BLA application number along with the prefix eg. BLA.
DO NOT use this field to capture Drug BLA number, for which, use Section C.
G4 Combination Product If the product is a Combination product, select the checkbox Include the C-code listed in the vocabulary attachment, if this is a combination
product device. Note that Suspect Product information is NOT required in
Section C to identify a combination product.
G5 If IND/PreANDA, Give Protocol # This block is for use by drug and biologic, including HCT/P manufacturers only. If the form is being used as a written If available, enter the Protocol # in Section C Suspect Product Information. Be
IND safety report, enter the protocol number. sure to select IND or PreANDA as the Suspect Drug Product Type.
21
eMDR HL7 Implementation Pointers
FDA\CDRH\OSB 03/23/2023
Med Watch Form MedWatch Field/Section Name MedWatch 3500A (paper) Instructions HL7 ICSR Implementation pointers
(https://www.fda.gov/downloads/AboutFDA/ReportsManualsForms/Forms/UCM295636.pdf)
G6 Type of report Select ALL the check boxes that apply to reported event. 5-day: As specified in the device regulations, for reports of Please look at the vocabulary attachment. Choose an appropriate code.
adverse events that necessitate remedial action to prevent an unreasonable risk of substantial harm to the public
health, or are required by FDA by written notice.
30-day: This choice was added in the 2006 version of the 3500A. DO NOT USE THIS OPTION for an initial
report - preferred selection is Initial. As specified in device regulations, for initial reports of a device that may
have caused or contributed to a death or serious injury or for a device malfunction that would be likely to contribute
to a death or serious injury if it were to recur. Periodic: As specified in the drug and biologic regulations, for reports
of serious labeled and non-serious (labeled and unlabeled) adverse events.
Initial: Check if the report is the first submission of a manufacturer report. For devices, this is the 30-day report.
USE INITIAL report, NOT 30-day report, to specify an initial report to the FDA CDRH.
Follow-up: Check if the report is a follow-up to a previously submitted report. Follow-up reports on drugs and
biologics, including HCT/Ps, should contain information that was submitted in the original report if the information is
still correct.
If a follow-up report, make sure that the manufacturer report number for the previously submitted initial report is
recorded in block G9. In the blank provided in block G7 after follow-up, record the appropriate sequence of
follow-up to that particular initial report (e.g., first follow-up report=follow-up #1, second follow-up report=follow-up
#2, and so on).
G8 MFR Report # For all manufacturers: Entry of the Manufacturer Number is not necessary for section G9 since it was
Enter the Manufacturer report number exactly as it appears in the “Mfr Report #” field in the upper right corner of the captured initially within the Report Number screen.
first page. For a follow-up report, the Manufacturer report number must be identical to the number assigned to the
initial report
For drug and biologic manufacturers:
The manufacturer report number is the number the manufacturer chooses to uniquely identify the report, and
should conform to any applicable regulations or guidance.
If submitting a follow-up to a report originally obtained from FDA through a MedWatch to Manufacturer program
transmission of a serious direct report, check the other box in block G3 and enter the FDA-assigned report number
there.
For human cell, tissue, and cellular and tissue-based product (HCT/P) manufacturers:
The report number should consist of three numbers separated by dashes. The first number will be the 10-digit FDA
Establishment Identifier (FEI) number, which was assigned to you as part of the Human Cells and Tissue
Establishment Registration (HCTERS). The second number should be the year that you are submitting the report.
The last number should be a consecutive 5-digit number for each report filed during the year by the manufacturer.
Example: 1234567890-2005-00005.
Death: Check only if the death was an outcome of the adverse event. Please choose one of the following: Death/Serious Injury/Malfunction.
Serious injury: An adverse event that is life-threatening; results in permanent impairment of a body function or Summary report information is contained in H1 Part2.
permanent damage to a body structure; or necessitates medical or surgical intervention to preclude permanent
impairment of a body function or permanent damage to a body structure.
Malfunction: See the guidelines. ("See the guidelines" refers to the applicable sections in 21 CFR Part 803 reporting
guidelines associated with device malfunctions).
H1 Part 2 No. of events (NOE) summarized A measurement of the total number of events that have occurred. Leave blank for non-summary reports, for summary reports include a positive
integer
22
eMDR HL7 Implementation Pointers
FDA\CDRH\OSB 03/23/2023
Med Watch Form MedWatch Field/Section Name MedWatch 3500A (paper) Instructions HL7 ICSR Implementation pointers
(https://www.fda.gov/downloads/AboutFDA/ReportsManualsForms/Forms/UCM295636.pdf)
H2 If follow-up, what type? Check the box(es) that most accurately describes the nature of the follow-up report. Please look at the vocabulary attachment. Choose an appropriate code. If you
want to send attachments, please submit them under
Correction: Changes to previously submitted information. /pertinentInformation3/document.
Additional information: Information concerning the event that was not provided in the initial report because it was not Base64 is an encoding method that converts binary data (zeros and ones) into
known/available when the report was originally submitted. ASCII text and vice versa. It was originally devised to make it possible to
Response to FDA request: Additional information requested by FDA concerning the device/event. reliably transmit data and is one of the methods used by MIME. Base64 divides
Device evaluation: Evaluation/analysis of device. each three bytes of the original data into four 6-bit units, which it represents as
four 7-bit ASCII characters. It is typical to use MIME base64 encoding to
encode email attachments as well as binary data in XML files. To embed a file
type within an XML document, you have to encode it in a fashion that is
compatible with text. Base64 encoding is used to accomplish this.
As an example, the process would roughly be the following to encode a PDF:
1. Run a program/method which would convert the PDF file to base-64:
PDFInBase64 = convertToBase64("c:\myAttachment.pdf")
2. Insert it into a XML instance after converting to string.
<document><text mediaType="text/plain">Base64 representation of
PDF</text></document>
There are several free, base64 encoding utilities and libraries available on the
internet in a variety of languages and platforms.
H3 part 1 Device evaluated by mfr? YES/NO Check the box marked not returned to mfr. if an evaluation could not be made because the device was not returned Please look at the vocabulary attachment. Populate 'true' for YES, Device
to, or made available to, the manufacturer. Check the box marked yes if an evaluation was made of the suspect or Evaluated; 'false' for NO, Device not evaluated
related medical device. If an evaluation was conducted, attach a summary of the evaluation and check the box
marked evaluation summary attached. If an evaluation of a returned suspect or related medical device was not
conducted, check the box marked no and attach a page to explain why not or provide the appropriate code from the
codes manual in the space provided.
H3 part 2 Device evaluated by mfr? Summary Attached Please look at the vocabulary attachment. Populate 'true' for YES, Evaluation
YES/NO Summary Attached; 'false' for NO, Evaluation Summary not attached;
H3 part 3 Device evaluated by mfr? Evaluation Summary Please look at the vocabulary attachment. Please use the appropriate concept
or reason for not evaluating code; use FDA codes to explain reason for non-evaluation as defined in
http://www.fda.gov/cdrh/mdrcode.pdf, for section H3. For other, please provide
explanation under the text field
H3 part 4 Device Not Returned to Manufacturer for Enter false for not returned to manufacturer, or enter true for returned to
Evaluation? manufacturer.
H4 Device manufacture date Enter the month and year of manufacture of the suspect medical device using a MM/YYYY date format. Use YYYYMMDD format
H5 Labeled for single use? Indicate whether the device was labeled for single use or not. If the question is not relevant to the device being Please look at the attached vocabulary. Choose an appropriate code. Populate
reported (e.g., an X-ray machine), check no. 'true' for YES; 'false' for NO;
H6 Adverse Event Problem Codes (refer to coding Enter up to 3 "patient" and 3 "device" codes from the Codes Manual that most accurately describe the event. Provide as many adverse event codes as appropriate; no limitation on number
manual) Patient codes describe what happened to the patient as a result of the event and device codes describe device of values; Please visit
failures or problems encountered during the event. If more than 3 "patient" codes or more than 3 "device" codes are https://www.fda.gov/MedicalDevices/DeviceRegulationandGuidance/
needed, record them on a separate sheet, mark it "F10", and provide the report number and page number. PostmarketRequirements/ReportingAdverseEvents/MDRAdverseEventCodes/
ucm584205.htm for the list of valid values
If a manufacturer has reason to believe that a reused device has or may have caused or contributed to an adverse
event, the device problem code 1537 ("Reuse") should be entered in F10 along with any other applicable device Note: At least 1 HECC and 1 DPC code is REQUIRED
and/or patient-related codes.
H6 Component Code
H6 Type of Investigation
H6 Investigation Findings
H6 Investigation Conclusions
H7 If remedial action initiated, check type Indicate the applicable action(s). If other, specify the type of action in the space provided. Most of these terms are Please look at the attached vocabulary. Choose an appropriate code.
defined or further explained in the Act or in the FDA regulations concerning remedial action (see 21 USC 360h and
21 CFR Parts 7, 803 and 806).
23
eMDR HL7 Implementation Pointers
FDA\CDRH\OSB 03/23/2023
Med Watch Form MedWatch Field/Section Name MedWatch 3500A (paper) Instructions HL7 ICSR Implementation pointers
(https://www.fda.gov/downloads/AboutFDA/ReportsManualsForms/Forms/UCM295636.pdf)
H8 Usage of device Indicate whether the use of the suspect medical device was the initial use, reuse, or unknown. Please look at the attached vocabulary. Choose an appropriate code.
If a manufacturer receives an adverse event report that indicates that the event was caused by or contributed to by
reuse of a single use device they manufactured, this block is to be appropriately marked and the facts of the firm's
investigation provided with an explanation of how the reuse of the product contributed to the outcome. The
appropriate manufacturer Result codes for reuse are also to be entered into H6.
H9 If action reported to FDA under 21 USC 360i(f), Enter the number that FDA assigned to the corrective action. If a number has not yet been assigned by FDA, the Please look at the attached vocabulary. Choose an appropriate code. Populate
list correction/removal reporting number number assigned by the firm for the action may be used. removal reporting number under 'value'
H10/H11 Additional manufacturer narrative Enter any additional information, evaluation, or clarification of data presented in previous sections. Do not duplicate Additional information can be included in the manufacturer narrative text or as
information that has already been provided elsewhere. embedded files as described in section H2 above. If you have additional
information that can be provided as a discrete data element on the 3500A form,
please provide it with the appropriate tags. For example, if you would like to
add/append/change device problem codes, please do not include it as part of
'originalText' under H10. Instead, include it in the document where you would
normally provide device problem codes with right xml tags attached.
24
eMDR HL7 Implementation Pointers
FDA\CDRH\OSB 03/23/2023
Field Lengths
VARCHAR2(6)
VARCHAR2(10)
VARCHAR2(10)
DATE
NUMBER(5)
VARCHAR2(10)
NUMBER(3)
25
eMDR HL7 Implementation Pointers
FDA\CDRH\OSB 03/23/2023
Field Lengths
DATE
DATE
DATE
26
eMDR HL7 Implementation Pointers
FDA\CDRH\OSB 03/23/2023
Field Lengths
Number(2)
Valid numbers are
1 thru 20
VARCHAR2(4)
VARCHAR2(35)
VARCHAR2(35)
VARCHAR2(500 CHAR)
VARCHAR2(500 CHAR)
VARCHAR2(100 CHAR)
VARCHAR2(100 CHAR)
VARCHAR2(500 CHAR)
Number (7,3)
27
eMDR HL7 Implementation Pointers
FDA\CDRH\OSB 03/23/2023
Field Lengths
Number (3,2)
Number (3)
DATE
DATE
VARCHAR2(500 CHAR)
VARCHAR2(80)
VARCHAR2(80)
VARCHAR2(3)
VARCHAR2(50)
VARCHAR2(30)
VARCHAR2(30)
VARCHAR2(30)
VARCHAR2(2)
VARCHAR2(5)
VARCHAR2(4)
VARCHAR2(10)
VARCHAR2(50)
VARCHAR2(26)
28
eMDR HL7 Implementation Pointers
FDA\CDRH\OSB 03/23/2023
Field Lengths
VARCHAR2(80)
VARCHAR2(30)
VARCHAR2(30)
DATE
VARCHAR2(30)
VARCHAR2(150)
VARCHAR2(40)
DATE
DATE
VARCHAR2(80)
VARCHAR2(30)
VARCHAR2(30)
VARCHAR2(30)
VARCHAR2(2)
VARCHAR2(5)
VARCHAR2(4)
VARCHAR2(10)
VARCHAR2(50)
VARCHAR2(26)
29
eMDR HL7 Implementation Pointers
FDA\CDRH\OSB 03/23/2023
Field Lengths
DATE
VARCHAR2(50)
DATE
VARCHAR2(15)
VARCHAR2(15)
VARCHAR2(25)
VARCHAR2(4)
VARCHAR2(60)
VARCHAR2(30)
VARCHAR2(30)
VARCHAR2(30)
VARCHAR2(2)
VARCHAR2(5)
VARCHAR2(4)
VARCHAR2(10)
VARCHAR2(50)
VARCHAR2(26)
VARCHAR2(3)
VARCHAR2(1)
VARCHAR2(21)
VARCHAR2(60)
VARCHAR2(30)
VARCHAR2(30)
VARCHAR2(30)
VARCHAR2(2)
VARCHAR2(5)
30
eMDR HL7 Implementation Pointers
FDA\CDRH\OSB 03/23/2023
Field Lengths
VARCHAR2(4)
VARCHAR2(10)
VARCHAR2(25)
VARCHAR2(15)
VARCHAR2(1)
VARCHAR2(4)
VARCHAR2(50)
VARCHAR2
DATE
NUMBER(3)
NUMBER(5)
VARCHAR2(10)
DATE
31
eMDR HL7 Implementation Pointers
FDA\CDRH\OSB 03/23/2023
Field Lengths
VARCHAR2(40)
DATE
VARCHAR2(50)
VARCHAR2(30)
VARCHAR2(30)
VARCHAR2(30)
VARCHAR2(2)
VARCHAR2(5)
VARCHAR2(4)
VARCHAR2(10)
VARCHAR2(50)
VARCHAR2(26)
VARCHAR2(4)
VARCHAR2(15)
VARCHAR2(15)
VARCHAR2(25)
VARCHAR2(60)
VARCHAR2(30)
VARCHAR2(30)
VARCHAR2(30)
VARCHAR2(2)
VARCHAR2(5)
VARCHAR2(4)
VARCHAR2(10)
VARCHAR2(50)
VARCHAR2(26)
VARCHAR2
32
eMDR HL7 Implementation Pointers
FDA\CDRH\OSB 03/23/2023
Field Lengths
VARCHAR2(40)
DATE
VARCHAR2(12)
33
eMDR HL7 Implementation Pointers
FDA\CDRH\OSB 03/23/2023
Field Lengths
NUMBER(3)
VARCHAR2(300)
VARCHAR2(21)
34
eMDR HL7 Implementation Pointers
FDA\CDRH\OSB 03/23/2023
Field Lengths
DATE
VARCHAR2(40)
35
eMDR HL7 Implementation Pointers
FDA\CDRH\OSB 03/23/2023
Field Lengths
VARCHAR2(24)
36
FDA\CDRH\OSB HL7 ICSR Vocabulary 03/23/2023
Med Watch Med Watch Form Label MAUDE Values Vocabulary Source (OID) Concept Code Concept Preferred Term (PT)
Form Ref # NCI:
2.16.840.1.113883.3.26.1.1
FDA: 2.16.840.1.113883.3.24
37
FDA\CDRH\OSB HL7 ICSR Vocabulary 03/23/2023
Med Watch Med Watch Form Label MAUDE Values Vocabulary Source (OID) Concept Code Concept Preferred Term (PT)
Form Ref # NCI:
2.16.840.1.113883.3.26.1.1
FDA: 2.16.840.1.113883.3.24
B1 Adverse Event Or Product Problem Report Adverse event NCI C41331 Adverse_Event
Reported issue is both an adverse event FDA F55555 Adverse_Event and Product Problem
and Product Problem
B2 Outcomes Attributed to Adverse Event NCI C49489 Adverse_Event_Outcome
LIFE THREATENING NCI C41337 Life_Threatening_Adverse_Event
38
FDA\CDRH\OSB HL7 ICSR Vocabulary 03/23/2023
Med Watch Med Watch Form Label MAUDE Values Vocabulary Source (OID) Concept Code Concept Preferred Term (PT)
Form Ref # NCI:
2.16.840.1.113883.3.26.1.1
FDA: 2.16.840.1.113883.3.24
C6 Product Type
OTC NCI C54068 OTC
Compounded NCI C94031 Compounded
Generic NCI C151960 Generic
Biosimilar NCI Biosimilar
C156644
C8 Event Abated After Use Stopped or Dose Reduced? NCI C86045 Abate
D8 Was this Device Serviced by Third Party? NCI C85488 Service Occupation
D9 Device Available for Evaluation? NCI C53449 Device Available for Evaluation
D10 Concomitant Medical Products and Therapy Dates TEXT NCI C53630 Concomitant_Therapy
39
FDA\CDRH\OSB HL7 ICSR Vocabulary 03/23/2023
Med Watch Med Watch Form Label MAUDE Values Vocabulary Source (OID) Concept Code Concept Preferred Term (PT)
Form Ref # NCI:
2.16.840.1.113883.3.26.1.1
FDA: 2.16.840.1.113883.3.24
F10 part 1 Health Effect - Clinical Code Currently available at FDA C53983 Patient_Problem_Code
https://www.fda.gov/MedicalDevices/Devic
eRegulationandGuidance/PostmarketReq
uirements/ReportingAdverseEvents/
MDRAdverseEventCodes/ucm584205.htm
F10 part 2 Medical Device Problem Code Currently available at FDA C53982 Device_Problem_Code
https://www.fda.gov/MedicalDevices/
DeviceRegulationandGuidance/
PostmarketRequirements/
ReportingAdverseEvents/
MDRAdverseEventCodes/ucm584205.htm
F10 part 3 Component code Currently available at FDA C54577 Component Code
https://www.fda.gov/MedicalDevices/Devic
eRegulationandGuidance/PostmarketReq
uirements/ReportingAdverseEvents/
MDRAdverseEventCodes/ucm584205.htm
F10 part 4 Health Effect - Impact Code Currently available at FDA C122929 Impact Code
https://www.fda.gov/MedicalDevices/Devic
eRegulationandGuidance/PostmarketReq
uirements/ReportingAdverseEvents/
MDRAdverseEventCodes/ucm584205.htm
40
FDA\CDRH\OSB HL7 ICSR Vocabulary 03/23/2023
Med Watch Med Watch Form Label MAUDE Values Vocabulary Source (OID) Concept Code Concept Preferred Term (PT)
Form Ref # NCI:
2.16.840.1.113883.3.26.1.1
FDA: 2.16.840.1.113883.3.24
41
FDA\CDRH\OSB HL7 ICSR Vocabulary 03/23/2023
Med Watch Med Watch Form Label MAUDE Values Vocabulary Source (OID) Concept Code Concept Preferred Term (PT)
Form Ref # NCI:
2.16.840.1.113883.3.26.1.1
FDA: 2.16.840.1.113883.3.24
H3 part 4 Device Not Returned to Manufacturer for Evaluation? NCI C53591 Device_Returned_to_Manufacturer_for_Evalu
ation
H6 Part 2 Medical Device Problem Code Currently available at FDA C53982 Device_Problem_Code
https://www.fda.gov/MedicalDevices/
DeviceRegulationandGuidance/
PostmarketRequirements/
ReportingAdverseEvents/
MDRAdverseEventCodes/ucm584205.htm
H6 Part 3 Component Code Currently available at NCI C54577 FDA Device Component Code Hierarchy
https://www.fda.gov/MedicalDevices/
DeviceRegulationandGuidance/
PostmarketRequirements/
ReportingAdverseEvents/
MDRAdverseEventCodes/ucm584205.htm
H6 Part 4 Health Effect - Impact Code Currently available at NCI C122929 Impact Code
https://www.fda.gov/MedicalDevices/
DeviceRegulationandGuidance/
PostmarketRequirements/
H6 Part 5 Type of Investigation ReportingAdverseEvents/
Currently available at NCI C53984 Evaluation_Code_Method
MDRAdverseEventCodes/ucm584205.htm
https://www.fda.gov/MedicalDevices/
DeviceRegulationandGuidance/
PostmarketRequirements/
ReportingAdverseEvents/
MDRAdverseEventCodes/ucm584205.htm
H6 Part 6 Investigation Findings Currently available at NCI C53985 Device Evaluation Result
https://www.fda.gov/MedicalDevices/
DeviceRegulationandGuidance/
PostmarketRequirements/
ReportingAdverseEvents/
MDRAdverseEventCodes/ucm584205.htm
H6 Part 7 Investigation Conclusions Currently available at NCI C53986 Device Evaluation Conclusion
https://www.fda.gov/MedicalDevices/
DeviceRegulationandGuidance/
PostmarketRequirements/
ReportingAdverseEvents/
MDRAdverseEventCodes/ucm584205.htm
H7 Type of remedial action NCI C53603 Type_of_Remedial_Action
INSPECTION NCI C53604 Inspection
MODIFICATION/ADJUSTMENT NCI C53606 Modification_or_Adjustment
NOTIFICATION NCI C25297 Notification
OTHER NCI C17649 Other
PATIENT MONITORING NCI C53607 Patient_Monitoring
RELABELING NCI C53608 Relabeling
RECALL NCI C53609 Recall
REPLACE NCI C53610 Replacement
REPAIR NCI C53611 Repair
Med Watch Med Watch Form Label MAUDE Values Vocabulary Source (OID) Concept Code Concept Preferred Term (PT)
Form Ref # NCI:
2.16.840.1.113883.3.26.1.1
FDA: 2.16.840.1.113883.3.24
43
FDA\CDRH\OSB HL7 ICSR Vocabulary 03/23/2023
FDA/NCI Definition
Version code used to identify HL7 ICSR rel. 2 version (ICSR R2)
Asked but unknown. (Answer could be available but no information was provided)
Device user facility means a hospital, ambulatory surgical facility, nursing home, outpatient diagnostic facility, or outpatient
treatment facility as defined in this section, which is not a physician's office, as defined in this section. School nurse offices
and employee health units are not device user facilities.
Manufacturer means any person who manufactures, prepares, propagates, compounds, assembles, or processes a device
by chemical, physical, biological, or other procedure
Any person who imports a device into the United States and who furthers the marketing of a device from the original place
of manufacture to the person who makes final delivery or sale to the ultimate user, but who does not repackage or
otherwise change the container, wrapper, or labeling of the device or device package. If you repackage or otherwise
change the container, wrapper, or labeling, you are considered a manufacturer as defined in this section.
A person who belongs to the sex that normally produces sperm. The term is used to indicate biological sex distinctions, or
cultural gender role distinctions, or both.
A person who belongs to the sex that normally produces ova. The term is used to indicate biological sex distinctions, or
cultural gender role distinctions, or both.
A person whose gender identity or gender expression differs from their assigned sex
A person (one of unisexual specimens) who is born with genitalia and/or secondary sexual characteristics of indeterminate
sex, or which combine features of both sexes.
A response indicating that an individual prefers or preferred not to answer.
A person of Cuban, Mexican, Puerto Rican, South or Central American, or other Spanish culture or origin, regardless of
race. The term, "Spanish origin," can be used in addition to "Hispanic or Latino."
A person not of Cuban, Mexican, Puerto Rican, South or Central American, or other Spanish culture or origin, regardless
of race.
An arbitrary classification of taxonomic group that is a division of a species; usually arise as a consequence of
geographical isolation within a species and characterized by shared heredity, physical attributes and behavior, and in case
of humans, by common history, nationality, or geographic distribution.
African American; term used in the United States to categorize a population group comprised of persons having origins in
any of the black racial groups of Africa, most of whose ancestors were brought from Africa to the Americas as slaves
between the sixteenth and nineteenth centuries. Includes population subgroups, e.g. Kenyan, Nigerian, or Haitian. The
concept refers also to individuals who classify themselves as described.
A person having origins in one of the indigenous peoples of North America, who lived on the continent prior to the
European colonization. The term includes individuals belonging to a large number of tribes, states, and ethnic groups,
many of them still enduring as communities.
A person having origins in any of the original peoples of the Far East, Southeast Asia, or the Indian subcontinent, including
Cambodia, China, India, Japan, Korea, Malaysia, Mongolia, Pakistan, the Philippine Islands, Thailand, and Vietnam.
A person having origins in any of the original peoples of Hawaii, Guam, Samoa, or other Pacific Islands. The term covers
particularly people who identify themselves as part-Hawaiian, Native Hawaiian, Guamanian or Chamorro, Carolinian,
Samoan, Chuukese (Trukese), Fijian, Kosraean, Melanesian, Micronesian, Northern Mariana Islander, Palauan, Papua
New Guinean, Pohnpeian, Polynesian, Solomon Islander, Tahitian, Tokelauan, Tongan, Yapese, or Pacific Islander, not
specified.
A person with European, Middle Eastern, or North African ancestral origin who identifies, or is identified, as White.
44
FDA\CDRH\OSB HL7 ICSR Vocabulary 03/23/2023
FDA/NCI Definition
Any unfavorable or unintended symptom, sign, or disease (including abnormal lab) temporally associated with the use of a
medical treatment or procedure that may or may not be considered related to the medical treatment or procedure. Such
events can be intervention related, dose related, route related, patient related, or caused by an interaction with another
drug(s) or procedure(s).
An issue with quality, authenticity, performance, or/and safety of medication or medical device. The concept encompasses
any problems that may occur during manufacturing, shipping, storage, or use of the medical product including but not
limited to such concerns as suspect counterfeit product, product contamination, super potent or subpotent medication,
defective item or its component, poor packaging or product confusion, questionable stability, device failure or malfunction,
and labeling concerns.
Temporary use of vocabulary to allow submitters to identify a reported issue as both an adverse event and a product
problem. Schema will change in future ICSR releases to identify these type of issues.
A condition or event that is attributed the adverse event.
An adverse event, and/or its immediate sequelae, which is associated with an imminent risk of death or which is
associated with physical or mental disabilities that affect or limit the ability of a person to perform activities of daily living
(eating, ambulation, toileting, etc.) See NCI Common Terminology Criteria for Adverse Events.
The condition of being treated as a patient in a hospital.
Any physical, mental, or functional impairment that limits a major activity. It may be partial or complete. (Taber's)
Any abnormality, anatomical or biochemical, evident at birth or during the neonatal period.
A patient condition when action or ministration whose purpose is to improve health or to alter the course of a disease is
considered essential and mandatory in order to prevent permanent
impairment or damage.
Different than the one(s) previously specified or mentioned.
The absence of life or state of being dead.
The outcome of a laboratory test.
Relevant elements of medical history, including preexisting medical conditions, events and facts (e.g., allergies, race,
pregnancy, smoking and alcohol use, hepatic/renal dysfunction, etc.) not listed in MedWatch form.
FDA/NCI Definition
A sign, signal, circumstance, or symptom which serves to indicate or point out the cause, pathology, treatment, or issue of
an attack of disease; the basis for initiation of a treatment for a disease or of a diagnostic test (causal, or symptomatic, or
disease-specific indication).
Specifies whether the entity qualifies under the 1938 Grandfather Clause, contained in section 20l(p)(l) of the U.S. Federal
Food, Drug and Cosmetic Act.
Become less in amount or intensity.(WordNet)
An identifier that adequately identifies a device through its distribution and use by meeting the requirements of 21 CFR
830.20 of this chapter. A unique device identifier is composed of a (1) device identifier and (2) production identifier.2 21
CFR 801.3. For more information regarding UDI, refer to the following FDA link:
http://www.fda.gov/downloads/MedicalDevices/DeviceRegulationandGuidance/GuidanceDocuments/UCM410439.pdf
An individual who handles and controls the functioning of medical device.
A person qualified to be engaged in activity directed at preservation of mental and physical health by diseases prevention
and treatment as a source of livelihood.
A person who receives medical attention, care, or treatment, or who is registered with medical professional or institution
with the purpose to receive medical care when necessary.
Different than the one(s) previously specified or mentioned.
An original device that has previously been used on a patient and has been subjected to additional processing and
manufacturing for the purpose of an additional single use on a patient. The subsequent processing and manufacture of a
reprocessed single-use device shall result in a device that is reprocessed within the meaning of this definition. (FDA
definition)
An occupation which provides a service to others rather than creating a product.
Indicates whether the device is available for evaluation by the manufacturer.
This is text that should include any drugs, devices, or other therapies that the patient was using. If you do not know the
date of therapy, but you know frequency, include in this section.
The principal activity that a person does to earn money. Occupation is not a required field.
NOTE: The information you provide for occupation title will not be used in any downstream systems.
NOTE: Please do not use any occupation codes that has been retired. Any retired occupation code found in the
submission will be rejected
An individual who is responsible for managing or operating a business, organization, team or department.
An individual whose profession is to apply engineering principles to understand, modify, or control biologic systems, as well
as design and manufacture products that can monitor physiologic functions and assist in the diagnosis and treatment of
patients.
An individual licensed for the prevention, diagnosis, and treatment of diseases in the oral cavity, adjacent tissues, and
related structures.
A professional healthcare provider who has graduated from an accredited nursing program, has passed the state exam for
licensure, and been registered or licensed to practice by a state authority. Nurses are educationally prepared as functional
(LPN/LVN) or professional (RN).
46
FDA\CDRH\OSB HL7 ICSR Vocabulary 03/23/2023
FDA/NCI Definition
A registered nurse (RN) with advanced training in diagnosing and treating illness. NPs are master's degree prepared
health experts that focus on helping patients achieve total health and prevent disease. NPs focus on disease prevention,
wellness, and patient education. NPs prescribe medications, treat illness, and perform physical examinations. NPs can
function independently of physician intervention, but require a practice agreement with a physician. NPs are licensed by a
state authority
A person trained in pharmacy who prepares and dispenses drugs prescribed by physicians and health practitioners. The
responsibilities include instructing patients on the use, hazards, interactions, and side effects of any drug dispensed.
Additionally, computerized and detailed records of patient drug use and medical profiles are maintained to eliminate
dangerous drug interactions and to ensure accuracy of use.
Individuals licensed to practice medicine.
A person trained and qualified to provide comprehensive diagnostic, preventive, and therapeutic medical care and services
to patients under the guidance of the physician. A scope of physician assistant professional activity does not include the
full range of interpretation
of medical findings requiring the full professional background of the licensed physician.
An occupation which provides a service to others rather than creating a product.
A person trained and licensed to implement and oversight health care risk management programs aimed on assuring
greater patient safety in health care facility or institution. The main thrust of the risk manager activity is in identifying
incidents occurring in the health care organization, which have an outcome of patient injury and may reflect error in the
course of the delivery of health care services, adverse incidents reporting, tracking, trending and elaboration of risk
reduction and risk prevention strategies and measures.
A publicly or privately owned institution which is primarily established and licensed for the purpose of providing elective
surgical treatment of outpatients whose recovery, under normal and routine circumstances, will not require inpatient care.
Such facility as herein defined does not include the offices of private physicians or dentists whether practicing individually
or in groups.
A person's permanent place of residence.
47
FDA\CDRH\OSB HL7 ICSR Vocabulary 03/23/2023
FDA/NCI Definition
An institution that provides medical, surgical, or psychiatric care and treatment for the sick or the injured.
A person appointed by the company to speak on its behalf and/or to provide defined service and work
A person who uses goods or services.
A person or group with authority to allot or deal out or apportion.
Not belonging to that in which it is contained; introduced from an outside source.
A person qualified to be engaged in activity directed at preservation of mental and physical health by diseases prevention
and treatment as a source of livelihood.
A product comprised of two or more regulated components, i.e., drug and device, biologic and device, that are physically,
chemically, or otherwise combined or mixed and produced as a single entity; or two or more separate products packaged
together in a single package or as a unit and comprised of drug and device products, device and biological products, or
biological and drug products; or a drug, device, or biological product packaged separately that according to its
investigational plan or proposed labeling is intended for use only with an approved individually specified drug, device, or
biological product where both are required to achieve the intended use, indication, or effect and where upon approval of
the proposed product the labeling of the approved product would need to be changed, e.g., to reflect a change in intended
use, dosage form, strength, route of administration, or significant change in dose; or any investigational drug, device, or
biological product packaged separately that according to its proposed labeling is for use only with another individually
specified investigational drug, device, or biological product where both are required to achieve the intended use, indication,
or effect.
Reports on events that require remedial action to prevent an unreasonable risk of substantial harm to the public health and
other types of events designated by FDA
Not used for MDR reporting
Not used for MDR reporting
Typical 30-Day MDR
Initial report of adverse event
The loss of the ability to function normally; something that does not accomplish its intended purpose.
48
FDA\CDRH\OSB HL7 ICSR Vocabulary 03/23/2023
FDA/NCI Definition
Terminology used for device components or accessories in safety reports and FDA CDRH documents during both pre and
post approval periods of device development and usage.
Informing by words.
Different than the one(s) previously specified or mentioned.
FDA/NCI Definition
50
FDA\CDRH\OSB HL7 ICSR X_path mapping to MedWatch 3500A 03/23/2023
Med Watch
Form Ref # MedWatch Field/Section Name
Version Code
Batch ID
Message ID
Form Source
Exemption Number
Attachment Filename
Attachment
A Patient Information
A1 Patient Identifier
A2 Date of birth
A2 Age at time of event
A2 Age at time of event Unit
A3 Gender
A4 Weight
A4 Weight Unit
A5 Ethnicity
A6 Race
B Adverse Event or Product Problem
Type of Report
B1
Outcomes attributed to adverse event
B2
B2 Date of Death
B3 Date of Event
B4 Date of this report
B5 Describe event or problem
B6 Relevant tests/laboratory data
Other relevant history, including
B7 preexisting medical conditions
C Suspect Product(s)
C Drug Sequence Number
C Drug Type
C Approval Number
C (& G6) If IND/PreANDA, Give Protocol #
C1 Name and Strength
C1 Manufacturer/Compounder
51
FDA\CDRH\OSB HL7 ICSR X_path mapping to MedWatch 3500A 03/23/2023
Med Watch
Form Ref # MedWatch Field/Section Name
C1 NDC # or Unique ID
C1 Lot #
C3 Dose
C3 Dose Unit
C3 Number of separate dosages
C3 Frequency
C3 Frequency Unit
C3 Route Used
Treatment Dates/Therapy Dates - Start
C4 Date
Treatment Dates/Therapy Dates - Stop
C4 Date
C5 Diagnosis Use For
C6 Product Type
C6 OTC
C6 Compounded
C6 Generic
C6 Biosimilar
C6 PreANDA
C6 Pre1938
C7 Expiration date
Event Abated After Use Stopped or
C8 Dose Reduced?
Event Reappeared After Reintroduction
C9
D Suspect medical device
D1 Brand Name
D2 Type of device
D2 Device Type Name
D3 Manufacturer name & address
D3 mfr_name
D3 mfr_street_1
D3 mfr_street_2
D3 mfr_city
D3 mfr_state
D3 mfr_postalCode
D3 mfr_country
52
FDA\CDRH\OSB HL7 ICSR X_path mapping to MedWatch 3500A 03/23/2023
Med Watch
Form Ref # MedWatch Field/Section Name
D3 email address
D3 fax number
Model #, Lot #, Catalog #, Expiration
Date, Serial #, Unique Identifier (UDI) #
D4
D4 Model Number
D4 Lot Number
D4 Catalog Number
D4 Expiration Date
D4 Serial Number
D4 Unique Identifier (UDI) #
D5 Operator of device
D5 Other Operator
D6A If Implanted give date
D6B If explanted, give date
Is this a single-use device that was
D7A reprocessed and reused on a patient?
D7B If yes to item D7A, enter name and address of reprocessor
D7B mfr_name
D7B mfr_street_1
D7B mfr_street_2
D7B mfr_city
D7B mfr_state
D7B mfr_postalCode
D7B mfr_country
D7B email address
D7B fax number
Was this device serviced by a third
D8 party?
Device available for evaluation? Date
D9 returned to Manufacturer
D9 Date returned to manufacturer
D10 Concomitant medical products
D10 Therapy dates
E INITIAL REPORTER
E1 Name and Address
E1 Reporter_First_Name
53
FDA\CDRH\OSB HL7 ICSR X_path mapping to MedWatch 3500A 03/23/2023
Med Watch
Form Ref # MedWatch Field/Section Name
E1 Reporter_Middle_Name
E1 Report_Last_Name
E1 Title
E1 Facility name
E1 streetAddressLine
E1 streetAddressLine 2
E1 city
E1 state
E1 postalCode
E1 country
E1 email address
E1 Phone #
E1 Fax number
E2 Health Professional?
E3 Occupation
E4 Initial reporter also sent report to FDA
For use by user facility/distributor -
F devices only
F1 Check one: user facility, distributor
UF/Distributor (Importer) Report
F2 Number
User Facility or Distributor (Importer)
F3 Name/Address
F3 streetAddressLine
F3 streetAddressLine 2
F3 city
F3 state
F3 zip_code
F3 country
F4 Contact person
F4 contact_first_name
F4 contact_mi_name
F4 contact_last_name
F4 contact_title
F4 email address
F5 Phone #
54
FDA\CDRH\OSB HL7 ICSR X_path mapping to MedWatch 3500A 03/23/2023
Med Watch
Form Ref # MedWatch Field/Section Name
Date user facility or distributor became
F6 aware of event
F7 Type of report
F7 Follow up number
F8 Date of this report
F9 Approximate age of device
F9 Approximate age of device unit
F10 Adverse Event Problem
F10 Health Effect - Clinical Code
F10 Medical Device Problem Code
F10 Component Code
F10 Health Effect - Impact Code
F11 Report sent to FDA?
F11 Date report was sent to FDA
F12 Location where event occurred
F12 Other
F13 Report sent to manufacturer?
F13 Date report was sent to manufacturer?
F14 Manufacturer name/address
F14 Manufacturer Name
F14 Manufacturer Address Street Line 1
F14 Manufacturer Address Street Line 2
F14 Manufacturer City
F14 Manufacturer State Code
F14 Manufacturer Country Code
F14 Manufacturer Postal Code
F14 Manufacturer Email
F14 Manufacturer Fax Number
G All manufacturers
G1 Contact Office (and Manufacturing Site for Devices)
G1 or Compounding Outsourcing Facility
Site Name (Mfg. - Name and Address
Site)
G1 streetAddressLine (Mfg. Site)
G1 streetAddressLine2 (Mfg. Site)
G1 city (Mfg. Site)
G1 state (Mfg. Site)
G1 postal code (Mfg. Site)
G1 country (Mfg. Site)
55
FDA\CDRH\OSB HL7 ICSR X_path mapping to MedWatch 3500A 03/23/2023
Med Watch
Form Ref # MedWatch Field/Section Name
G1 email address (Mfg. Site)
G1 Fax number (Mfg. Site)
G1 Prefix (Contact Off.)
G1 First name (Contact Off.)
G1 Middle name (Contact Off.)
G1 Last name (Contact Off.)
G1 Site Name (Contact Off.)
G1 streetAddressLine (Contact Off.)
G1 streetAddressLine2 (Contact Off.)
G1 City (Contact Off.)
G1 State (Contact Off.)
G1 Postal code (Contact Off.)
G1 Country (Contact Off.)
G1 Email address (Contact Off.)
G1 Fax number (Contact Off.)
G1 Phone number (Contact Off.)
Contact Report source
G2
G2 Contact Report Source - Other Text
G3 Date received by manufacturer
Premarket Application Numbers and
G4 Premarket Checkboxes
G4 PMA/510k (or) BLA #
G4 Combination product
Type of report
G6
G6 Follow up number
G7 Adverse Event Terms
G8 MFR Report #
H Device manufacturers only
Type of reportable event
H1 Part 1
H1 Part 2 No. of events (NOE) summarized
H2 If follow-up, what type?
H2 Response to FDA Request
H2 Additional Information
56
FDA\CDRH\OSB HL7 ICSR X_path mapping to MedWatch 3500A 03/23/2023
Med Watch
Form Ref # MedWatch Field/Section Name
H2 Device Evaluation
H2 Correction
H3 Device evaluated by mfr?
H3 Yes or No
(Attach page to explain why not) or
H3 provide code
Reason for Non-evaluation, explain
H3 Other
H3 Not Returned to Manufacturer
H3 Evaluation Summary Attached
H4 Device manufacture date
H5 Labeled for single use?
H6 Adverse Event Problem
H6 Health Effect - Clinical Code
H6 Medical Device Problem Code
H6 Component Code
H6 Health Effect - Impact Code
Type of Investigation
H6
H6 Investigation Findings
H6 Investigation Conclusions
If remedial action initiated, check type
H7
H8 Usage of device
If action reported to FDA under 21 USC
360i(f), list correction/removal reporting
H9 number
H10 Additional manufacturer narrative
57
FDA\CDRH\OSB HL7 ICSR X_path mapping to MedWatch 3500A 03/23/2023
X-Path
//versionCode/@code
//id[@assigningAuthorityName="MessageSender"]/@extension
//message/id/@extension
//message/controlActProcess/reasonOf/detectedIssueEvent/code[@code='F77770']/../value/@code
//message/controlActProcess/reasonOf/detectedIssueEvent/code[@code='F77776']/../value/@code
//message/attachment/text/reference/@value
//message/attachment/text/text()
//message/controlActProcess/subject/investigationEvent/trigger/reaction/subject/investigativeSubject/subjectAffectedPerson/name/text()
//message/controlActProcess/subject/investigationEvent/trigger/reaction/subject/investigativeSubject/subjectAffectedPerson/birthTime/@value
//message/controlActProcess/subject/investigationEvent/trigger/reaction/subject/investigativeSubject/subjectOf/observation/code[@code='C25150']/../value/@value
//message/controlActProcess/subject/investigationEvent/trigger/reaction/subject/investigativeSubject/subjectOf/observation/code[@code='C25150']/../value/@unit
//message/controlActProcess/subject/investigationEvent/trigger/reaction/subject/investigativeSubject/subjectAffectedPerson/administrativeGenderCode/@code
//message/controlActProcess/subject/investigationEvent/trigger/reaction/subject/investigativeSubject/subjectOf/observation/code[@code='C25208']/../value/@value
//message/controlActProcess/subject/investigationEvent/trigger/reaction/subject/investigativeSubject/subjectOf/observation/code[@code='C25208']/../value/@unit
//message/controlActProcess/subject/investigationEvent/trigger/reaction/subject/investigativeSubject/subjectAffectedPerson/ethnicGroupCode/@code
//message/controlActProcess/subject/investigationEvent/trigger/reaction/subject/investigativeSubject/subjectAffectedPerson/raceCode/@code
//message/controlActProcess/subject/investigationEvent/code/@code
//message/controlActProcess/subject/investigationEvent/pertinentInformation2/caseSeriousness/code[@code='C49489']/../value/@code
//message/controlActProcess/subject/investigationEvent/trigger/reaction/subject/investigativeSubject/subjectAffectedPerson/deceasedTime/@value
//message/controlActProcess/subject/investigationEvent/trigger/reaction/effectiveTime/@value
//message/controlActProcess/code[@codeSystem='HL7'][@code='PORR_TE040001UV01'][@codeSystemName='HL7 Trigger Event Id']/../effectiveTime/@value
//message/controlActProcess/subject/investigationEvent/trigger/reaction/text/text()
//message/controlActProcess/subject/investigationEvent/trigger/reaction/subject/investigativeSubject/subjectOf/observation/code[@code='C36292']/../value/text()
//message/controlActProcess/subject/investigationEvent/trigger/reaction/subject/investigativeSubject/subjectOf/observation/code[@code='C53263']/../value/text()
//message[1]/controlActProcess/subject/investigationEvent/component/adverseEventAssessment/subject1/primaryRole/subjectOf2/@drugSeqNo
//message[1]/controlActProcess/subject/investigationEvent/component/adverseEventAssessment/subject1/primaryRole/subjectOf2/organizer/component/substanceAdministrat
//message[1]/controlActProcess/subject/investigationEvent/component/adverseEventAssessment/subject1/primaryRole/subjectOf2/organizer/component/substanceAdministrat
//message[1]/controlActProcess/subject/investigationEvent/component/adverseEventAssessment/subject1/primaryRole/subjectOf2/organizer/component/substanceAdministrat
//message[1]/controlActProcess/subject/investigationEvent/component/adverseEventAssessment/subject1/primaryRole/subjectOf2/organizer/component/substanceAdministrat
//message[1]/controlActProcess/subject/investigationEvent/component/adverseEventAssessment/subject1/primaryRole/subjectOf2/organizer/component/substanceAdministrat
58
FDA\CDRH\OSB HL7 ICSR X_path mapping to MedWatch 3500A 03/23/2023
X-Path
//message[1]/controlActProcess/subject/investigationEvent/component/adverseEventAssessment/subject1/primaryRole/subjectOf2/organizer/component/substanceAdministrat
//message[1]/controlActProcess/subject/investigationEvent/component/adverseEventAssessment/subject1/primaryRole/subjectOf2/organizer/component/substanceAdministrat
//message[1]/controlActProcess/subject/investigationEvent/component/adverseEventAssessment/subject1/primaryRole/subjectOf2/organizer/component/substanceAdministrat
//message[1]/controlActProcess/subject/investigationEvent/component/adverseEventAssessment/subject1/primaryRole/subjectOf2/organizer/component/substanceAdministrat
//message[1]/controlActProcess/subject/investigationEvent/component/adverseEventAssessment/subject1/primaryRole/subjectOf2/organizer/component/substanceAdministrat
//message[1]/controlActProcess/subject/investigationEvent/component/adverseEventAssessment/subject1/primaryRole/subjectOf2/organizer/component/substanceAdministrat
//message[1]/controlActProcess/subject/investigationEvent/component/adverseEventAssessment/subject1/primaryRole/subjectOf2/organizer/component/substanceAdministrat
//message[1]/controlActProcess/subject/investigationEvent/component/adverseEventAssessment/subject1/primaryRole/subjectOf2/organizer/component/substanceAdministrat
//message[1]/controlActProcess/subject/investigationEvent/component/adverseEventAssessment/subject1/primaryRole/subjectOf2/organizer/component/substanceAdministrat
//message[1]/controlActProcess/subject/investigationEvent/component/adverseEventAssessment/subject1/primaryRole/subjectOf2/organizer/component/substanceAdministrat
//message[1]/controlActProcess/subject/investigationEvent/component/adverseEventAssessment/subject1/primaryRole/subjectOf2/organizer/component/substanceAdministrat
//message[1]/controlActProcess/subject/investigationEvent/component/adverseEventAssessment/subject1/primaryRole/subjectOf2/organizer/component/substanceAdministrat
//message[1]/controlActProcess/subject/investigationEvent/component/adverseEventAssessment/subject1/primaryRole/subjectOf2/organizer/component/substanceAdministrat
//message[1]/controlActProcess/subject/investigationEvent/component/adverseEventAssessment/subject1/primaryRole/subjectOf2/organizer/component/substanceAdministrat
//message[1]/controlActProcess/subject/investigationEvent/component/adverseEventAssessment/subject1/primaryRole/subjectOf2/organizer/component/substanceAdministrat
//message[1]/controlActProcess/subject/investigationEvent/component/adverseEventAssessment/subject1/primaryRole/subjectOf2/organizer/component/substanceAdministrat
//message[1]/controlActProcess/subject/investigationEvent/component/adverseEventAssessment/subject1/primaryRole/subjectOf2/organizer/component/substanceAdministrat
//message[1]/controlActProcess/subject/investigationEvent/component/adverseEventAssessment/subject1/primaryRole/subjectOf2/organizer/component/substanceAdministrat
//message[1]/controlActProcess/subject/investigationEvent/component/adverseEventAssessment/subject1/primaryRole/subjectOf2/organizer/component/substanceAdministrat
//message[1]/controlActProcess/subject/investigationEvent/component/adverseEventAssessment/subject1/primaryRole/subjectOf2/organizer/component/substanceAdministrat
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/device/identifiedDevice/identifiedDevice/inventoryItem/manufacturedDeviceModel/manufac
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/device/identifiedDevice/identifiedDevice/inventoryItem/manufacturedDeviceModel/code/@
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/device/identifiedDevice/identifiedDevice/inventoryItem/manufacturedDeviceModel/code/ori
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproces
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproces
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproces
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproces
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproces
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproces
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproces
59
FDA\CDRH\OSB HL7 ICSR X_path mapping to MedWatch 3500A 03/23/2023
X-Path
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproces
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproces
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/device/identifiedDevice/identifiedDevice/inventoryItem/manufacturedDeviceModel/id/@ext
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/device/identifiedDevice/identifiedDevice/lotNumberText/text()
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/id/@extension
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/device/identifiedDevice/identifiedDevice/expirationTime/@value
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/device/identifiedDevice/identifiedDevice/id/@extension
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct[1]/code/@code
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/authorOrPerformer/assignedEntity/code/@code
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/authorOrPerformer/assignedEntity/code/originalText/text()
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/component1/implantation/effectiveTime/@value
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/component2/explantation/effectiveTime/@value
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/pertinentInformation1/observation/code[@code='C53563']/../value/@value
address of reprocessor
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproces
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproces
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproces
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproces
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproces
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproces
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproces
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproces
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproces
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/pertinentInformation1/observation/code[@code='C85488']/../value/@value
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/device/identifiedDevice/subjectOf/deviceObservation/code[@code='C53449']/../value/@va
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/device/identifiedDevice/subjectOf/deviceObservation/code[@code='C53449']/../effectiveTim
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/pertinentInformation1/observation/code[@code='C53630']/../../observation/value/text()
//message/controlActProcess/subject/investigationEvent/pertainsTo[1]/procedureEvent/pertinentInformation1/observation[1]/code[@code='C53630']/../effectiveTime/@value
//message/controlActProcess/subject/investigationEvent/trigger/reaction/pertinentInformation/primarySourceReport/author/assignedEntity/assignedPerson/name/given[1]/text()
60
FDA\CDRH\OSB HL7 ICSR X_path mapping to MedWatch 3500A 03/23/2023
X-Path
//message/controlActProcess/subject/investigationEvent/trigger/reaction/pertinentInformation/primarySourceReport/author/assignedEntity/assignedPerson/name/given[2]/text()
//message/controlActProcess/subject/investigationEvent/trigger/reaction/pertinentInformation/primarySourceReport/author/assignedEntity/assignedPerson/name/family/text()
//message/controlActProcess/subject/investigationEvent/trigger/reaction/pertinentInformation/primarySourceReport/author/assignedEntity/assignedPerson/name/prefix/text()
//message/controlActProcess/subject/investigationEvent/trigger/reaction/pertinentInformation/primarySourceReport/author/assignedEntity/representedOrganization/name/text()
//message/controlActProcess/subject/investigationEvent/trigger/reaction/pertinentInformation/primarySourceReport/author/assignedEntity/assignedPerson/addr/streetAddressL
//message/controlActProcess/subject/investigationEvent/trigger/reaction/pertinentInformation/primarySourceReport/author/assignedEntity/assignedPerson/addr/streetAddressL
//message/controlActProcess/subject/investigationEvent/trigger/reaction/pertinentInformation/primarySourceReport/author/assignedEntity/assignedPerson/addr/city/text()
//message/controlActProcess/subject/investigationEvent/trigger/reaction/pertinentInformation/primarySourceReport/author/assignedEntity/assignedPerson/addr/state/text()
//message/controlActProcess/subject/investigationEvent/trigger/reaction/pertinentInformation/primarySourceReport/author/assignedEntity/assignedPerson/addr/postalCode/tex
//message/controlActProcess/subject/investigationEvent/trigger/reaction/pertinentInformation/primarySourceReport/author/assignedEntity/assignedPerson/addr/country/text()
//message/controlActProcess/subject/investigationEvent/trigger/reaction/pertinentInformation/primarySourceReport/author/assignedEntity/assignedPerson/telecom[starts-with(@
//message/controlActProcess/subject/investigationEvent/trigger/reaction/pertinentInformation/primarySourceReport/author/assignedEntity/assignedPerson/telecom[starts-with(@
//message/controlActProcess/subject/investigationEvent/trigger/reaction/pertinentInformation/primarySourceReport/author/assignedEntity/assignedPerson/telecom[starts-with(@
<!-- The value of BOX.E.2 will be inferred from the choice offered for E.3 -->
//message/controlActProcess/subject/investigationEvent/trigger/reaction/pertinentInformation/primarySourceReport/author/assignedEntity/code/@code
//message/controlActProcess/subject/investigationEvent/trigger/reaction/pertinentInformation/primarySourceReport/receiver/@negationInd
//message/controlActProcess/subject/investigationEvent/pertinentInformation1/secondaryCaseNotification/author/assignedEntity/code[@codeSystemName='Type_of_Reporter
//message/controlActProcess/subject/investigationEvent/pertinentInformation1/secondaryCaseNotification/id/@extension
//message/controlActProcess/subject/investigationEvent/pertinentInformation1/secondaryCaseNotification/author/assignedEntity/assignedOrganization/addr/additionalLocator/t
//message/controlActProcess/subject/investigationEvent/pertinentInformation1/secondaryCaseNotification/author/assignedEntity/assignedOrganization/addr/streetAddressLine
//message/controlActProcess/subject/investigationEvent/pertinentInformation1/secondaryCaseNotification/author/assignedEntity/assignedOrganization/addr/streetAddressLine
//message/controlActProcess/subject/investigationEvent/pertinentInformation1/secondaryCaseNotification/author/assignedEntity/assignedOrganization/addr/city/text()
//message/controlActProcess/subject/investigationEvent/pertinentInformation1/secondaryCaseNotification/author/assignedEntity/assignedOrganization/addr/state/text()
//message/controlActProcess/subject/investigationEvent/pertinentInformation1/secondaryCaseNotification/author/assignedEntity/assignedOrganization/addr/postalCode/text()
//message/controlActProcess/subject/investigationEvent/pertinentInformation1/secondaryCaseNotification/author/assignedEntity/assignedOrganization/addr/country/text()
//message/controlActProcess/subject/investigationEvent/pertinentInformation1/secondaryCaseNotification/author/assignedEntity/assignedOrganization/contactParty/contactPe
//message/controlActProcess/subject/investigationEvent/pertinentInformation1/secondaryCaseNotification/author/assignedEntity/assignedOrganization/contactParty/contactPe
//message/controlActProcess/subject/investigationEvent/pertinentInformation1/secondaryCaseNotification/author/assignedEntity/assignedOrganization/contactParty/contactPe
//message/controlActProcess/subject/investigationEvent/pertinentInformation1/secondaryCaseNotification/author/assignedEntity/assignedOrganization/contactParty/contactPe
//message/controlActProcess/subject/investigationEvent/pertinentInformation1/secondaryCaseNotification/author/assignedEntity/assignedOrganization/contactParty/contactPe
//message/controlActProcess/subject/investigationEvent/pertinentInformation1/secondaryCaseNotification/author/assignedEntity/assignedOrganization/contactParty/contactPe
61
FDA\CDRH\OSB HL7 ICSR X_path mapping to MedWatch 3500A 03/23/2023
X-Path
//message/controlActProcess/subject/investigationEvent/pertinentInformation1/secondaryCaseNotification/effectiveTime/@value
//message/controlActProcess/subject/investigationEvent/pertinentInformation1/secondaryCaseNotification/code/@code
//message/controlActProcess/subject/investigationEvent/pertinentInformation1/sequenceNumber/@value
<--! This will be inferred from F11 or F13 value -->
//message/controlActProcess/subject/investigationEvent/pertainsTo[1]/procedureEvent/device/identifiedDevice/subjectOf/deviceObservation/code[@code='C53451']/../value/@
//message/controlActProcess/subject/investigationEvent/pertainsTo[1]/procedureEvent/device/identifiedDevice/subjectOf/deviceObservation/code[@code='C53451']/../value/@
//message/controlActProcess/subject/investigationEvent/trigger/reaction/subject/investigativeSubject/subjectOf/observation/code[@code='C53983']/../value/@code
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/device/identifiedDevice/subjectOf/deviceObservation/code[@code='C53982']/../value/@co
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/device/identifiedDevice/subjectOf/deviceObservation/code[@code='C54577']/../value/@co
//message/controlActProcess/subject/investigationEvent/trigger/reaction/subject/investigativeSubject/subjectOf/observation/code[@code='C122929']/../value/@code
//message/controlActProcess/subject/investigationEvent/pertinentInformation1[1]/secondaryCaseNotification/receiver/@negationInd
//message/controlActProcess/subject/investigationEvent/pertinentInformation1[1]/secondaryCaseNotification/receiver/time/@value
//message/controlActProcess/subject/investigationEvent/trigger/reaction/location/locatedEntity/location/code/@code
//message/controlActProcess/subject/investigationEvent/trigger/reaction/location/locatedEntity/location/code/originalText/text()
//message/controlActProcess/subject/investigationEvent/pertinentInformation1[2]/secondaryCaseNotification/receiver/@negationInd
//message/controlActProcess/subject/investigationEvent/pertinentInformation1[2]/secondaryCaseNotification/receiver/time/low/@value
//message/controlActProcess/subject/investigationEvent/pertinentInformation1[2]/secondaryCaseNotification/receiver/assignedEntity/assignedOrganization/name/text()
//message/controlActProcess/subject/investigationEvent/pertinentInformation1[2]/secondaryCaseNotification/receiver/assignedEntity/assignedOrganization/addr/streetAddress
//message/controlActProcess/subject/investigationEvent/pertinentInformation1[2]/secondaryCaseNotification/receiver/assignedEntity/assignedOrganization/addr/streetAddress
//message/controlActProcess/subject/investigationEvent/pertinentInformation1[2]/secondaryCaseNotification/receiver/assignedEntity/assignedOrganization/addr/city/text()
//message/controlActProcess/subject/investigationEvent/pertinentInformation1[2]/secondaryCaseNotification/receiver/assignedEntity/assignedOrganization/addr/state/text()
//message/controlActProcess/subject/investigationEvent/pertinentInformation1[2]/secondaryCaseNotification/receiver/assignedEntity/assignedOrganization/addr/country/text()
//message/controlActProcess/subject/investigationEvent/pertinentInformation1[2]/secondaryCaseNotification/receiver/assignedEntity/assignedOrganization/addr/postalCode/te
//message/controlActProcess/subject/investigationEvent/pertinentInformation1[2]/secondaryCaseNotification/receiver/assignedEntity/assignedOrganization/telecom[starts-with(
//message/controlActProcess/subject/investigationEvent/pertinentInformation1[2]/secondaryCaseNotification/receiver/assignedEntity/assignedOrganization/telecom[starts-with(
62
FDA\CDRH\OSB HL7 ICSR X_path mapping to MedWatch 3500A 03/23/2023
X-Path
//message/controlActProcess/subject/investigationEvent/pertainsTo[1]/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproc
//message/controlActProcess/subject/investigationEvent/pertainsTo[1]/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproc
//message/controlActProcess/subject/investigationEvent/pertainsTo[1]/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproc
//message/controlActProcess/subject/investigationEvent/pertainsTo[1]/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproc
//message/controlActProcess/subject/investigationEvent/pertainsTo[1]/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproc
//message/controlActProcess/subject/investigationEvent/pertainsTo[1]/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproc
//message/controlActProcess/subject/investigationEvent/pertainsTo[1]/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproc
//message/controlActProcess/subject/investigationEvent/pertainsTo[1]/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproc
//message/controlActProcess/subject/investigationEvent/pertainsTo[1]/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproc
//message/controlActProcess/subject/investigationEvent/pertainsTo[1]/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproc
//message/controlActProcess/subject/investigationEvent/pertainsTo[1]/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproc
//message/controlActProcess/subject/investigationEvent/pertainsTo[1]/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproc
//message/controlActProcess/subject/investigationEvent/pertainsTo[1]/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproc
//message/controlActProcess/subject/investigationEvent/pertainsTo[1]/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproc
//message/controlActProcess/subject/investigationEvent/pertainsTo[1]/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproc
//message/controlActProcess/subject/investigationEvent/pertainsTo[1]/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproc
//message/controlActProcess/reasonOf/detectedIssueEvent/code[@code='C53566']/../value/@code
//message/controlActProcess/reasonOf/detectedIssueEvent/value[@code='C17649']/../code/originalText/text()
//message/controlActProcess/subject/investigationEvent/pertinentInformation1/secondaryCaseNotification/receiver/time/high/@value
//message/controlActProcess/subject/investigationEvent/pertainsTo[1]/procedureEvent/device/identifiedDevice/identifiedDevice/inventoryItem/manufacturedDeviceModel/asRe
//message/controlActProcess/reasonOf/detectedIssueEvent/code[@code='C53571']/../value/@code
//message/controlActProcess/reasonOf/detectedIssueEvent/code[@code='C53571']/../value/@code
//message/controlActProcess/reasonOf/detectedIssueEvent/code[@code='C53571']/../value[@code='C53579']/../text/text()
//message/controlActProcess/subject/investigationEvent/trigger/reaction/term/text()
//message/controlActProcess/subject/investigationEvent/id/@extension
//message/controlActProcess/reasonOf/detectedIssueEvent/code[@code='C53570']/../value/@code
//message/controlActProcess/reasonOf/detectedIssueEvent/code[@code='C53570']/../value[@code='C84831']/../text/text()
//message/controlActProcess/reasonOf/detectedIssueEvent/code[@code='C53584']/../value/@code='C53587'
//message/controlActProcess/reasonOf/detectedIssueEvent/code[@code='C53584']/../value/@code='C53586'
63
FDA\CDRH\OSB HL7 ICSR X_path mapping to MedWatch 3500A 03/23/2023
X-Path
//message/controlActProcess/reasonOf/detectedIssueEvent/code[@code='C53584']/../value/@code='C53588'
//message/controlActProcess/reasonOf/detectedIssueEvent/code[@code='C53584']/../value/@code='C53585'
//message/controlActProcess/subject/investigationEvent/pertainsTo[1]/procedureEvent/device/identifiedDevice/subjectOf/deviceObservation/code[@code='C53629']/../value/@
//message/controlActProcess/subject/investigationEvent/pertainsTo[1]/procedureEvent/device/identifiedDevice/subjectOf/deviceObservation/code[@code='C53593']/../value/@
//message/controlActProcess/subject/investigationEvent/pertainsTo[1]/procedureEvent/device/identifiedDevice/subjectOf/deviceObservation/code[@code='C53593']/../value/or
//message/controlActProcess/subject/investigationEvent/pertainsTo[1]/procedureEvent/device/identifiedDevice/subjectOf/deviceObservation/code[@code='C53591']/../value/@
//message/controlActProcess/subject/investigationEvent/pertainsTo[1]/procedureEvent/device/identifiedDevice/subjectOf/deviceObservation/code[@code='C53592']/../value/@
//message/controlActProcess/subject/investigationEvent/pertainsTo[1]/procedureEvent/device/identifiedDevice/identifiedDevice/existenceTime/@value
//message/controlActProcess/subject/investigationEvent/pertainsTo[1]/procedureEvent/device/identifiedDevice/subjectOf/deviceObservation/code[@code='C53602']/../value/@
//message/controlActProcess/subject/investigationEvent/trigger/reaction/subject/investigativeSubject/subjectOf/observation/code[@code='C53983']/../value/@code
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/device/identifiedDevice/subjectOf/deviceObservation/code[@code='C53982']/../value/@co
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/device/identifiedDevice/subjectOf/deviceObservation/code[@code='C54577']/../value/@co
//message/controlActProcess/subject/investigationEvent/trigger/reaction/subject/investigativeSubject/subjectOf/observation/code[@code='C122929']/../value/@code
//message/controlActProcess/subject/investigationEvent/pertainsTo[1]/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproc
//message/controlActProcess/subject/investigationEvent/pertainsTo[1]/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproc
//message/controlActProcess/subject/investigationEvent/pertainsTo[1]/procedureEvent/device/identifiedDevice/identifiedDevice/asManufacturedProduct/manufacturerOrReproc
//message/controlActProcess/subject/investigationEvent/pertainsTo[1]/procedureEvent/device/identifiedDevice/subjectOf/deviceObservation/code[@code='C53603']/../value/@
//message/controlActProcess/subject/investigationEvent/pertainsTo[1]/procedureEvent/device/identifiedDevice/subjectOf/deviceObservation/code[@code='C53645']/../value/@
//message/controlActProcess/subject/investigationEvent/pertainsTo/procedureEvent/device/identifiedDevice/subjectOf/deviceObservation/code[@code='C53619']/../value/text(
//message/controlActProcess/subject/investigationEvent/text/text()
64
CDRH eMDR - HL7 ICSR Implementation -- Country Code Mapping 03/23/2023
Current CDRH implementation of HL7 ICSR will support -- 2 character FIPS/NIST country codes
and the three character GENC codes. Eventually CDRH will phase out the 2 character codes.
Below, we have provided mapping between the FIPS/NIST,GENC three character codes for your
use.
AFGHANISTAN AF AFG
AKROTIRI XQZ
ALBANIA AL ALB
ALGERIA AG DZA
ANDORRA AN AND
ANGOLA AO AGO
ANGUILLA AV AIA
ANTARCTICA AY ATA
ARGENTINA AR ARG
ARMENIA AM ARM
ARUBA AA ABW
AUSTRALIA AS AUS
AUSTRIA AU AUT
AZERBAIJAN AJ AZE
BAHAMAS BF BHS
BAHRAIN BA BHR
65
CDRH eMDR - HL7 ICSR Implementation -- Country Code Mapping 03/23/2023
Current CDRH implementation of HL7 ICSR will support -- 2 character FIPS/NIST country codes
and the three character GENC codes. Eventually CDRH will phase out the 2 character codes.
Below, we have provided mapping between the FIPS/NIST,GENC three character codes for your
BAKER ISLAND use. FQ XBK
BANGLADESH BG BGD
BARBADOS BB BRB
BELARUS BO BLR
BELGIUM BE BEL
BELIZE BH BLZ
BENIN BN BEN
BERMUDA BD BMU
BHUTAN BT BTN
BOLIVIA BL BOL
BOTSWANA BC BWA
BRAZIL BR BRA
BRUNEI BX BRN
BULGARIA BU BGR
BURKINA UV BFA
BURMA MMR
66
CDRH eMDR - HL7 ICSR Implementation -- Country Code Mapping 03/23/2023
Current CDRH implementation of HL7 ICSR will support -- 2 character FIPS/NIST country codes
and the three character GENC codes. Eventually CDRH will phase out the 2 character codes.
Below, we have provided mapping between the FIPS/NIST,GENC three character codes for your
BURUNDI use. BY BDI
CAMBODIA CB KHM
CAMEROON CM CMR
CANADA CA CAN
CHAD CD TCD
CHILE CI CHL
CHINA CH CHN
COLOMBIA CO COL
COMOROS CN COM
CONGO CF COG
67
CDRH eMDR - HL7 ICSR Implementation -- Country Code Mapping 03/23/2023
Current CDRH implementation of HL7 ICSR will support -- 2 character FIPS/NIST country codes
and the three character GENC codes. Eventually CDRH will phase out the 2 character codes.
Below, we have provided mapping between the FIPS/NIST,GENC three character codes for your
CROATIA use. HR HRV
CUBA CU CUB
CURACAO CUW
CYPRUS CY CYP
CZECHIA EZ CZE
DENMARK DA DNK
DHEKELIA XXD
DJIBOUTI DJ DJI
DOMINICA DO DMA
ECUADOR EC ECU
EGYPT EG EGY
EL SALVADOR ES SLV
ERITREA ER ERI
ESTONIA EN EST
ETHIOPIA ET ETH
FIJI FJ FJI
FINLAND FI FIN
68
CDRH eMDR - HL7 ICSR Implementation -- Country Code Mapping 03/23/2023
Current CDRH implementation of HL7 ICSR will support -- 2 character FIPS/NIST country codes
and the three character GENC codes. Eventually CDRH will phase out the 2 character codes.
Below, we have provided mapping between the FIPS/NIST,GENC three character codes for your
FRANCE use. FR FRA
GABON GB GAB
GAMBIA GA GMB
GEORGIA GG GEO
GERMANY GM DEU
GHANA GH GHA
GIBRALTAR GI GIB
GREECE GR GRC
GREENLAND GL GRL
GRENADA GJ GRD
GUADELOUPE GP GLP
GUAM GUM
GUATEMALA GT GTM
GUERNSEY GK GGY
GUINEA GV GIN
GUINEA-BISSAU PU GNB
GUYANA GY GUY
69
CDRH eMDR - HL7 ICSR Implementation -- Country Code Mapping 03/23/2023
Current CDRH implementation of HL7 ICSR will support -- 2 character FIPS/NIST country codes
and the three character GENC codes. Eventually CDRH will phase out the 2 character codes.
Below, we have provided mapping between the FIPS/NIST,GENC three character codes for your
HAITI use. HA HTI
HONDURAS HO HND
HUNGARY HU HUN
ICELAND IC ISL
INDIA IN IND
INDONESIA ID IDN
IRAN IR IRN
IRAQ IZ IRQ
IRELAND EI IRL
ISRAEL IS ISR
ITALY IT ITA
JAMAICA JM JAM
JAPAN JA JPN
JERSEY JE JEY
70
CDRH eMDR - HL7 ICSR Implementation -- Country Code Mapping 03/23/2023
Current CDRH implementation of HL7 ICSR will support -- 2 character FIPS/NIST country codes
and the three character GENC codes. Eventually CDRH will phase out the 2 character codes.
Below, we have provided mapping between the FIPS/NIST,GENC three character codes for your
JORDAN use. JO JOR
KAZAKHSTAN KZ KAZ
KENYA KE KEN
KIRIBATI KR KIR
KOSOVO XKS
KUWAIT KU KWT
KYRGYZSTAN KG KGZ
LA REUNION RE REU
LAOS LA LAO
LATVIA LG LVA
LEBANON LE LBN
LESOTHO LT LSO
LIBERIA LI LBR
LIBYA LY LBY
LIECHTENSTEIN LS LIE
LITHUANIA LH LTU
LUXEMBOURG LU LUX
MACAO MC MAC
71
CDRH eMDR - HL7 ICSR Implementation -- Country Code Mapping 03/23/2023
Current CDRH implementation of HL7 ICSR will support -- 2 character FIPS/NIST country codes
and the three character GENC codes. Eventually CDRH will phase out the 2 character codes.
Below, we have provided mapping between the FIPS/NIST,GENC three character codes for your
MACAU use. MC MAC
MACEDONIA MK MKD
MADAGASCAR MA MDG
MALAWI MI MWI
MALAYSIA MY MYS
MALDIVES MV MDV
MALI ML MLI
MALTA MT MLT
MARTINIQUE MB MTQ
MAURITANIA MR MRT
MAURITIUS MP MUS
MAYOTTE MF MYT
MEXICO MX MEX
MOLDOVA MD MDA
MONACO MN MCO
MONGOLIA MG MNG
MONTENEGRO MNE
MONTSERRAT MH MSR
MOROCCO MO MAR
MOZAMBIQUE MZ MOZ
MYANMAR MMR
72
CDRH eMDR - HL7 ICSR Implementation -- Country Code Mapping 03/23/2023
Current CDRH implementation of HL7 ICSR will support -- 2 character FIPS/NIST country codes
and the three character GENC codes. Eventually CDRH will phase out the 2 character codes.
Below, we have provided mapping between the FIPS/NIST,GENC three character codes for your
NAMIBIA use. WA NAM
NAURU NR NRU
NEPAL NP NPL
NETHERLANDS NL NLD
NETHERLANDS ANTILLES NT
NICARAGUA NU NIC
NIGER NG NER
NIGERIA NI NGA
NIUE NE NIU
NORWAY NO NOR
OMAN MU OMN
PAKISTAN PK PAK
PALAU PLW
PANAMA PM PAN
PARAGUAY PA PRY
73
CDRH eMDR - HL7 ICSR Implementation -- Country Code Mapping 03/23/2023
Current CDRH implementation of HL7 ICSR will support -- 2 character FIPS/NIST country codes
and the three character GENC codes. Eventually CDRH will phase out the 2 character codes.
Below, we have provided mapping between the FIPS/NIST,GENC three character codes for your
PERU use. PE PER
PHILIPPINES RP PHL
PITCAIRN PC PCN
POLAND PL POL
PORTUGAL PO PRT
QATAR QA QAT
REUNION RE REU
ROMANIA RO ROU
RUSSIA RS RUS
RWANDA RW RWA
SAMOA WS WSM
SENEGAL SG SEN
74
CDRH eMDR - HL7 ICSR Implementation -- Country Code Mapping 03/23/2023
Current CDRH implementation of HL7 ICSR will support -- 2 character FIPS/NIST country codes
and the three character GENC codes. Eventually CDRH will phase out the 2 character codes.
Below, we have provided mapping between the FIPS/NIST,GENC three character codes for your
SERBIA use. SRB
SEYCHELLES SE SYC
SINGAPORE SN SGP
SLOVAKIA LO SVK
SLOVENIA SI SVN
SOMALIA SO SOM
SPAIN SP ESP
SUDAN SU SDN
SURINAME NS SUR
SVALBARD SV XSV
75
CDRH eMDR - HL7 ICSR Implementation -- Country Code Mapping 03/23/2023
Current CDRH implementation of HL7 ICSR will support -- 2 character FIPS/NIST country codes
and the three character GENC codes. Eventually CDRH will phase out the 2 character codes.
Below, we have provided mapping between the FIPS/NIST,GENC three character codes for your
SVALBARD AND JAN MAYEN use. SV XSV
SWAZILAND WZ SWZ
SWEDEN SW SWE
SWITZERLAND SZ CHE
SYRIA SY SYR
TAIWAN TW TWN
TAJIKISTAN TI TJK
TANZANIA TZ TZA
THAILAND TH THA
TIMOR-LESTE TLS
TOGO TO TGO
TOKELAU TL TKL
TONGA TN TON
TUNISIA TS TUN
TURKEY TU TUR
TURKMENISTAN TX TKM
TUVALU TV TUV
UGANDA UG UGA
76
CDRH eMDR - HL7 ICSR Implementation -- Country Code Mapping 03/23/2023
Current CDRH implementation of HL7 ICSR will support -- 2 character FIPS/NIST country codes
and the three character GENC codes. Eventually CDRH will phase out the 2 character codes.
Below, we have provided mapping between the FIPS/NIST,GENC three character codes for your
UKRAINE use. UP UKR
UNKNOWN AX1
URUGUAY UY URY
UZBEKISTAN UZ UZB
VANUATU NH VUT
VENEZUELA VE VEN
VIETNAM VM VNM
YEMEN YM YEM
ZAIRE CG COD
77
CDRH eMDR - HL7 ICSR Implementation -- Country Code Mapping 03/23/2023
Current CDRH implementation of HL7 ICSR will support -- 2 character FIPS/NIST country codes
and the three character GENC codes. Eventually CDRH will phase out the 2 character codes.
Below, we have provided mapping between the FIPS/NIST,GENC three character codes for your
ZAMBIA use. ZA ZMB
ZIMBABWE ZI ZWE
78