After uploading templates or QRDA-I files to the portal, any files that fail to process can be reviewed under Imports > Failures in the left-hand navigation. The table below lists common failure reasons along with additional details about each one. Where applicable, the relevant XPath is included in italics for reference.


If you see a failure reason in the portal, find the matching entry in the Reason column below for more context on what it means.


ReasonAdditional Details
Corrupted archive formatThe ZIP archive is corrupted or password-protected and cannot be extracted for processing.

Action: Recreate the ZIP file, verify size is not zero, verify ZIP contains files that end in ".xml"
Document contains no measure entriesThe QRDA-I file contains no entries under the Measure Section.

Action: Open a support ticket with your EHR:
QRDAIs are being generated without the required measure entry section
/ClinicalDocument/component/structuredBody/component/section[./code/@code='55186-1']/entry. 
Document contains no patient data entriesThe QRDA-I file contains no entries under the Patient Data Section (i.e., contains no clinical data)

Action: Open a support ticket with your EHR:
QRDAIs are being generated without the required entries for clinical data
/ClinicalDocument/component/structuredBody/component/section[./code/@code='55188-7']/entry
Document contains no reporting parameter entriesThe QRDA-I file contains no entries under the Reporting Parameters Section.

Action: Open a support ticket with your EHR:
QRDAIs are being generated without the required reporting parameter entries
/ClinicalDocument/component/structuredBody/component/section[./code/@code='55187-9']/entry
Measures section not foundThe Measure Section itself is missing from the file.

Action: Open a support ticket with your EHR:
QRDAIs are being generated without the required measure section
/ClinicalDocument/component/structuredBody/component/section[./code/@code='55186-1']
Measure number [XXX] are not allowed to process.The measure listed is not on the approved list for processing — it may be retired, unsupported, or invalid for the current reporting year.

Action: This may be ignored if the measure number is not expected to be imported. Otherwise open a support ticket with Patient360.
Missing/Invalid document type codeThe document type code is missing or does not match the expected QRDA-I code.

Action: Open a support ticket with your EHR:
QRDAIs are being generated without the required document type code
/ClinicalDocument/code[@code='55182-0']
Missing/Invalid patient genderThe patient's administrative gender is missing or contains an unrecognized value.

Action: 
Step 1: Is clinical staff documenting gender in the correct EHR field? If no, stop here and address clinical documentation. If yes, proceed to Step 2.
Step 2: Open a support ticket with the EHR:
QRDAIs are being generated without the required gender data
/ClinicalDocument/recordTarget/patientRole/patient/administrativeGenderCode
No patient identifiers foundThe file does not contain any patient identifier values (e.g., MRN) needed to match the patient record at the TIN.

Action: Open a support ticket with your EHR:
QRDAIs are being generated without a required patient identifier /ClinicalDocument/recordTarget/patientRole/id
  • NPI 1234567890 is not provisioned in P360
  • NPI listed is not provisioned in Patient360.
  • QRDA-I NPI 1234567890 not found in Patient360
The NPI listed in the QRDA-I file has not been provisioned in Patient360 and cannot be matched to a provider record.  

/ClinicalDocument/documentationOf/performer/assignedEntity/id[@extension]

Action: Add the Provider/NPI to Patient360 and re-upload the files.

Patient data section not foundThe Patient Data Section is missing from the file.

Action: Open a support ticket with your EHR:
QRDAIs are being generated without the required patient data section
/ClinicalDocument/component/structuredBody/component/section[./code/@code='55188-7']
Patient information not foundThe patient demographic/identification information is missing.

Action: Open a support ticket with your EHR:
QRDAIs are being generated without the required patient data section
/ClinicalDocument/recordTarget/patientRole
QRDA-I file includes no valid measure eUIDs for the reporting yearNo measureId (eUID) values in the file match the eCQMs published for the current reporting year — often due to an outdated measure version.

Action: Open a support ticket with your EHR:
QRDAIs are being generated without the required measure identifiers

/ClinicalDocument/component/structuredBody/component/section

/entry/organizer/reference/externaldocument/id[@root='2.16.840.1.113883.4.738']/@extension

We are expecting one or more of the following values:

EUID Values by Measure
M001 9700a8b9-9f65-41a8-8464-1da26cda857b
M112 dbd9eccd-c3ea-42db-9344-72ad44f84f51
M113 5f4ca523-517d-4872-ba8d-63a29e337d85
M134 fbaecc84-b452-4188-95a6-21246e8ca619
M236 cd9a5c8e-ac16-4e10-a1f4-4dfe48e02cab

Reporting parameters section not foundThe Reporting Parameters Section is missing from the file.

Action: Open a support ticket with your EHR:
QRDAIs are being generated without the required reporting parameters section

/ClinicalDocument/component/structuredBody/component/section[./code/@code='55187-9']
Reporting Period is not found!The reportingPeriod element is missing or malformed — the file doesn't specify the start/end dates the data covers.