National Practitioner Data Bank

Healthcare Integrity and Protection Data Bank

1. Who should use the Querying and Reporting XML Service (QRXS)?

   The QRXS interface is ideal for large volume queriers and reporters and Proactive Disclosure Service Prototype (PDS) subscribers, who use their own transaction processing systems and want to interface those systems with the Data Banks. The QRXS is similar to the Interface Control Document (ICD) Transfer Program (ITP) interface, but uses eXtensible Markup Language (XML) as the file format for submissions and responses. XML provides the advantage of verifying the reporting format without having to submit transactions and wait for validation responses from the Data Banks system. Also, the XML technology enables a more flexible interface that is changed more easily than the ITP, if report, querying, or PDS (24/7 notification) formats change.

   Queries and PDS (24/7 notification) enrollments submitted through the QRXS are validated instantly with a query or PDS (24/7 notification) confirmation. The confirmation contains the batch Data Bank Document Control Number (DCN), the practitioner information for each practitioner submitted, and a status for each practitioner. If a query or PDS (24/7 notification) enrollment does not pass validation, a list of errors is provided for the submitter to correct. Unlike the ITP, the QRXS will not charge submitters for queries or PDS (24/7 notification) enrollments that are rejected due to data problems.

2. How do I access the QRXS?

   The Data Banks provide a Java-based QRXS client program for sending and receiving transaction files. Those interested in using the QRXS should download and install the QRXS Client program. The Client program is a Java-based tool that allows users to send and receive transactions from the QRXS. It also provides a Java-based Application Programming Interface (API) for creating your own Java-based client program for the QRXS.

   For organizations that are familiar with web services, we also provide a QRXS web service. Web services are appropriate for users who are already familiar with web services, or would prefer to write their own web services client using a non-Java solution.

   The QRXS Client Program and Client Program User Guide, in addition to detailed information about the QRXS, are available on our Using the QRXS page.

3. Can I use the Querying and Reporting XML Service (QRXS) to access the Proactive Disclosure Service Prototype (PDS 24/7 notification)?

   Yes, the QRXS interface is ideal for large volume Proactive Disclosure Service Prototype (PDS 24/7 notification) subscribers who use their own transaction processing systems and want to interface those systems with the Data Banks. The QRXS is similar to the Interface Control Document (ICD) Transfer Program (ITP) interface, but uses eXtensible Markup Language (XML) as the file format for submissions and responses. XML provides the advantage of verifying the reporting format without having to submit transactions and wait for validation responses from the Data Banks system. Also, the XML technology enables a more flexible interface that is changed more easily than the ITP, if report, querying or PDS (24/7 notification) formats change.

   PDS (24/7 notification) enrollments submitted through the QRXS are validated instantly with a PDS (24/7 notification) confirmation. The confirmation contains the batch Data Bank Document Control Number (DCN), the practitioner information for each practitioner submitted, and a status for each practitioner. If a PDS (24/7 notification) enrollment does not pass validation, a list of errors is provided for the submitter to correct. Unlike the ITP, the QRXS will not charge submitters for PDS (24/7 notification) enrollments that are rejected due to data problems.

4. Where can I locate the Querying and Reporting XML Service (QRXS) file format specifications?

   The QRXS file format specifications are available through the File Specifications Access page. Users must first set up an account and log in with their given Vendor ID.

5. How can we test our Querying and Reporting XML Service (QRXS) eXtensible Markup Language (XML) files?

   The Data Banks QRXS test environment allows users to validate their XML submission files in real time. The test environment can be used to test your XML creation software, data validation, and connection issues before submitting to the Data Banks via the QRXS. The QRXS test environment specifications are available through the Using the QRXS page.

6. My QRXS transaction was rejected with an error of V1 (Missing or invalid Vendor ID). What does that mean?

   A valid Vendor ID is required for QRXS transactions and may be obtained through the File Specifications Access page. To learn where to include the Vendor ID in a QRXS submission file, see the QRXS File Format Specifications by logging in to the File Specifications Access page using your Vendor ID.

7. How often will there be changes to the eXtensible Markup Language (XML) format, and will we be informed in advance of such changes?

   The Querying and Reporting XML Service (QRXS) and Integrated Querying and Reporting Service (IQRS) Subject Database Import format specifications are updated periodically by the Data Banks. The Data Banks will notify users at least one month in advance of an update to the code lists, which are expected to occur quarterly. Users will be notified six months in advance of other periodic updates to the format specifications. It is strongly recommended that users join the appropriate Mailing List to receive notice of updates. Addresses must be kept current or notices will not be received.

8. How can we test our eXtensible Markup Language (XML) subject database import files before live submission?

   It is recommended that you use an XML validator to verify that your XML files conform to the XML Import Format Schema provided by the Data Banks. You may also e-mail your test import files to our Customer Service Center, at help@npdb-hipdb.hrsa.gov. Your test files will be checked for validity and will be e-mailed back to you with any corrections.

9. Can an imported practitioner be marked as incomplete even after validation by an eXtensible Markup Language (XML) validator prior to import?

   Yes. An XML validator checks that your XML files are correctly formatted prior to importing them into the Integrated Querying and Reporting Service (IQRS). A validator will not reveal which practitioners are incomplete, since this is a function of the practitioner data rather than the file format.

10. Is there a particular validator that you would recommend?

    The Data Banks neither recommends nor supports any particular validator; however there are many commercial and open-source eXtensible Markup Language (XML) brands available.

11. Can I query and report or enroll in PDS (24/7 notification) using my Entity Data Bank Administrator account?

    No, the Entity Data Bank Administrator user ID can only be used to perform administrative functions. The Entity Data Bank Administrator must create individual user accounts for each authorized user to submit queries and reports or to enroll in PDS (24/7 notification). The Entity Data Bank Administrator must also create an individual user account for his or her own use if he or she routinely accesses the PDS (24/7 notification), queries or reports to the Data Banks. (Also in Interface Control Document Transfer Program [ITP] FAQ and Integrated Querying and Reporting Service [IQRS] FAQ.)

12. What security measures are in place to protect data transmissions to and from the Data Banks?

    All data transmissions are protected using Secure Socket Layer (SSL) protocol. SSL interface between applications (such as browsers) and the Transmission Control Protocol/Internet Protocol (TCP/IP) protocols to provide server authentication, client authentication, and an encrypted communication channel between client and server. Software is installed to protect against viruses, malware, and spyware. A firewall is used to filter all traffic and to keep malicious traffic outside the protected environment. An intrusion detection system monitors activity to identify malicious or suspicious events. (Also in Security FAQ and Interface Control Document Transfer Program [ITP] FAQ.)

13. How can we find out if our Querying and Reporting XML Service (QRXS) report submission file(s) were received, and how long should we wait for a response file?

    To confirm that your submission file(s) were received, the Data Banks immediately generate a status code indicating whether the file(s) were successfully received.

    The response file(s) should be available for download within two to four hours. Under certain circumstances, additional processing may be required. Please do not re-submit your report on the subject in question, since this will result in duplicate transactions. If you do not receive your response within two business days of submission, please call the Customer Service Center at 1-800-767-6732. Information Specialists are available to speak with you weekdays from 8:30 a.m. to 6:00 p.m. (5:30 p.m. on Fridays) Eastern Time. The Customer Service Center is closed on all Federal holidays.

14. How long is a Querying and Reporting XML Service (QRXS) report response file available for download?

    Report responses are available for download for up to 45 days from the date of submission. Password responses are available for download for five days.

15. Can I correct a Revision-to-Action Report?

    Yes. The reporting organization may correct a Revision-to-Action Report. Log in to the IQRS, located on the Data Banks home page, and select Report on the Options screen. Enter the Data Bank Control Number (DCN) of the report to correct and select Correct or Modify a Report on the Report Type screen. Make the corrections to the report and submit the changes. A Revision-to-Action Report may also be corrected using the Querying and Reporting XML Service (QRXS). Refer to the appropriate QRXS File Format Specifications for additional information. (Also in Integrated Querying and Reporting Service [IQRS] FAQ and Reporting FAQ.)