FDA · ELECTRONIC MEDICAL DEVICE REPORTING

FDA eMDR: submit case information from Excel electronically

Structured data entry, HL7 ICSR conversion, M2M transfer and interpreted FDA feedback with the Europe IT Consulting eMDR solution.

eMDR stands for Electronic Medical Device Reporting: electronic submission of medical device incident reports to the FDA. Unlike GUDID, it concerns a specific case, rather than registration of a device master record.

Our solution helps Regulatory Affairs, Quality Assurance and vigilance teams provide case information using an Excel template. Technical processing generates the required HL7 ICSR XML and uses the configured M2M route. Incoming acknowledgments are evaluated. Your specialist team remains responsible for assessment, data approval and necessary corrections.

Enquire about your eMDR process

Want to register device information instead? Start with FDA UDI and GUDID or the GUDID Excel template . Official FDA explanation of eMDR.

How Europe IT supports your reporting process

01 · Capture case information

The Excel template guides your departments through structured data entry. You do not have to build the HL7 XML file by hand. This technical simplification does not replace complete case documentation and substantive review.

02 · Validate and convert to HL7 ICSR

The application processes the entered data and generates the electronic report format. Pre-submission validation helps detect entry and structural errors. The customer corrects the substantive data.

03 · Send through the configured M2M route

Approved data is sent to the FDA gateway through the agreed transfer process. The existing Europe IT process diagram shows an AS2 connection. Customer-specific integration and the applicable gateway configuration are agreed during onboarding.

04 · Evaluate acknowledgments

The solution receives and interprets FDA feedback. Success, error and, where applicable, warning information support processing. In the described service process, results can be forwarded by email to the responsible staff in the agreed form.

Existing Europe IT eMDR process: Excel case data, web service with HL7 conversion, AS2 transfer and ACK feedback
Existing illustration of the Europe IT service route. The email route shown is not a GSP portal upload. The communication channel and handling of sensitive case data must be agreed before use.

Service process or Global Submission Portal?

The existing eMDR solution and the Global Submission Portal provide different working interfaces for the agreed process. In GSP, the customer uploads the designated module template, addresses validation feedback and initiates transfer after successful validation.

If you already use SAP and GUDI we discuss the appropriate integration in your system landscape. The specific eMDR module scope and data provision are expressly defined; UDI data management alone does not create a complete incident report.

Your benefits: less manual technical file creation, repeatable processing and easier assignment of feedback. Time saved depends on data quality and case complexity; no fixed number of minutes or guaranteed acceptance is promised.

ACK1 to ACK4: what does the FDA actually confirm?

A received data package is not yet a successfully processed eMDR report. Check more than the gateway status.

Context for the eMDR process, not a universal scheme for every FDA submission
Acknowledgment Meaning What your team checks
ACK1 Receipt by ESG NextGen. Was the transfer received at the gateway?
ACK2 Forwarding to CDRH. Did the package reach the next processing point?
ACK3 / ACK4 eMDR result: HTML or XML with the same substantive feedback. “Passed” or “Failed” and the corresponding error details.

Technical acceptance is determined by the eMDR processing result, not ACK1 alone. Source: FDA eMDR FAQ. Successful technical acceptance is not a comprehensive regulatory assessment of your case.

Discuss automation for your vigilance team

What case data is available, how do your departments work and which submission route do you use today? Process information is sufficient for an initial enquiry. Please do not send identifiable patient data or complete case files through this form.

Before production: access, testing and responsibilities

Gateway access and eMDR setup should be planned together. For third-party software, the FDA describes the High-Volume onboarding process; the name is not a fixed minimum case threshold. Consider the chosen communication method, test reports and required steps before production use. Current FDA eMDR onboarding guidance.

ESG NextGen supports AS2 and API, among other methods. The former WebTrader interface was replaced by the Unified Submission Portal. The method configured for your Europe IT process is a specific technical decision, not an automatic commitment to every option. FDA ESG NextGen.

  • Customer: Case assessment, correct source data, approval and resolution of content errors.
  • Europe IT: agreed software, conversion and transfer support, plus onboarding instructions.
  • FDA: authority systems and processing of submitted data.

Form versions, data mapping and technical rules must be maintained in operation. The FDA publishes changes under eMDR System Enhancements; announced changes are not automatically live in production.

Handle errors while keeping track

Feedback should stay associated with its submission. Record the report reference, submission reference, environment and specific error message for processing.

If rejected, the customer corrects the cause and arranges resubmission. Missing feedback should first be distinguished from a content error. The FDA lists different contacts for gateway problems, missing centre acknowledgments and rejected eMDR reports. FDA eMDR troubleshooting and contact information.

Frequently asked questions about eMDR submission

Does my team need to program HL7 or XML?

Not for the Excel-based data entry described. The Europe IT solution handles technical conversion. Your specialist department must still provide and approve accurate case information.

Do we also need FDA eSubmitter?

eSubmitter is not needed as a data entry tool for the Europe IT conversion route described. The FDA’s required onboarding and testing steps for the selected process still apply.

Is HL7 ICSR the same as HL7 SPL?

No. eMDR uses the HL7 ICSR case report format; GUDID uses HL7 SPL for device information. These XML files are not interchangeable. FDA: technical ICSR documentation.

Does error-free XML guarantee full compliance?

No. Technical validation does not automatically assess the entire reporting obligation, timeliness or medical evaluation. These responsibilities must be organised within the responsible company.

What is the difference between MIR and eMDR?

MIR is the European Manufacturer Incident Report. FDA eMDR is the US reporting process. Similar case information may be needed, but formats, rules and recipients must be treated separately.

Agree the next step together

Whether you use an existing service route or a portal process, we discuss how data entry, technical processing and feedback handling should work together for your company.

Get in contact with us

All FDA sources and support routes · FDA UDI overview

Sources checked: . No commitment to a specific authority processing time.