Repository files navigation

• Installation Instructions
• Running the Converter
• Sample Files
• Want to Contribute?
• Public Domain

Before you can use the qpp-conversion-tool application, you must install and configure the following products on your machine:

• Git and/or theGitHub application.

  GitHub's Guide to Installing Git is a good source of information.

• Java Runtime (version>= 17).

  It is important that you have the right version ofjava on your path.

  # When you run 'java -version', you should get 17. For example:java -versionjava version"17"...

  Sometimes the Java Runtime installer doesn't update your path. So you must do it manually. Alternatively, download and installtheJava Development Kit (version>= 17). The JDK isbetter at updating your path.

• Maven (version>= 3.9.6).

  Maven is used to build the application, manage dependencies, and run tests. After you unzip the Maven archive, you need to addthebin directory to your path, as described theMaven installation instructions.

  # When you run 'mvn -v', you should get 3.8.4. For example:mvn -vApache Maven 3.9.6...

• Docker.

  Docker is not required but is an alternative to the above requirements if all you need is to run the converter.

Use the GitHub application or the command line to clone this repository.

# Clone the GitHub repository.git clone https://github.com/CMSgov/qpp-conversion-tool.git# Go to the qpp-conversion-tool directory.cd ./qpp-conversion-tool

In order to run converter locally, HTTPS may need to be disabled. It can be done by removing or commenting server.port and server.ssl.key-store-type in application.properties file underrest-api/src/main/resources

The Conversion Tool can be executed through a ReST API. Using the ReST API has the added benefit of having theQPP validated if you so choose. For the examples below, make sure you're in theqpp-conversion-tooldirectory.

# Build the Docker image and run the container using docker-compose.docker-compose -f ./docker-compose.test.yaml up --build

curl -X POST \  http://localhost:3000 \  -H'cache-control: no-cache' \  -H'content-type: multipart/form-data; boundary=----WebKitFormBoundary7MA4YWxkTrZu0gW' \  -F file=@./qrda-files/valid-QRDA-III-latest.xml

The response body will either be the QPP JSON on success or error JSON on an error.The HTTP Status will be201 Created on success or422 Unprocessable entity on an error.

While the converter will validate the format of the QRDA-III file and some basic semantics, deeper semantic checks are onlyavailable if you enable the public submission validation API. If any errors are found by the public submission validation API,error JSON will be returned from the ReST API like normal.

To enable the public submission validation API, modify the.env file withVALIDATION_URL=https://qpp.cms.gov/api/submissions/public/validate-submission and thenrestart the ReST API endpoint.

Ensure the environment variableCPC_END_DATE is set to a valid date, in the formatYYYY-MM-DD, or a validation error may be thrown.

Step 1: Check the Current New Relic Agent Version in new relic dashboard using metadata

Step 2: Download the Latest New Relic Agent

# Download the latest New Relic Java agent.curl -O https://download.newrelic.com/newrelic/java-agent/newrelic-java.zip

Step 3: Replace the Existing Files

# Extract the downloaded New Relic agent files.unzip newrelic-java.zip -d newrelic-latest# Replace the existing newrelic.jar file.cp newrelic-latest/newrelic/newrelic.jar tools/docker/docker-artifacts/newrelic/# Update the newrelic.yml file:- Compare the existing file with the newly downloaded one.- Merge any new configurationswhile retaining custom settings such as license_key and app_name.

Step 4: Restart the Application and Check in New Relic dashboard

# Rebuild and restart the application:docker-compose -f ./docker-compose.test.yaml up --build

For the examples below, make sure you're in theqpp-conversion-tool directory.

Note: If you are using Windows, replace./convert.sh in the examples below withconvert.bat.

# Try the convert script. If the JAR isn't built yet, the script will build it for you first../convert.sh ./qrda-files/valid-QRDA-III-latest.xml

If a QRDA-III XML file is successfully converted, a QPP JSON file is created in the current working directory.The file name will have the same name as the input file but with the extension.qpp.json.For example,valid-QRDA-III-latest.qpp.json.

When an invalid file is provided to the converter, an error JSON file is created in the current working directory.The file name will be the same as the input file but with the extension.err.json.For example,not-a-QRDA-III-file.err.json. This error file contains descriptions and XPaths that help in identifying theerrors in the provided input file.

View all commands withconvert.sh.

Sample QRDA-III files that cover all of the eCQM, PI, and IA measures as well as other scenarioscan be found in thesample-files folder.

Swagger will be enabled under/swagger-ui/index.html#/ path. And the api docs are avilable underv3/api-docs.

Want to file a bug or contribute some code? Read up on our guidelines forcontributing anddeveloper instructions.

This project is in the public domain within the United States, and copyright and related rights in the work worldwide are waivedthrough the CC0 1.0 Universal public domain dedication.

All contributions to this project will be released under the CC0 dedication. By submitting a pull request, you are agreeing tocomply with this waiver of copyright interest.

See theformal LICENSE file.