NPI Check Route
This route (used as a stateless helper function) makes a request to the web service NPPES NPI Registry and gets the results on whether the NPI is available and is valid.
For each claim, the route makes a REST call to the web service https://npiregistry.cms.hhs.gov/api with the NPI number as a parameter. The web service returns a JSON response with information about the queried NPI. Then, the route parses the response and extracts the information on whether the NPI is valid. Finally, the route aggregates the claims into a single file and returns the file to the caller route (1 Split and Validate).
Route Structure
Route Components Description
| Parent Route Input
|
Parent Route Input |
Receives claims from the Subroute component on the route 1 Split and Validate. |
| Check NPI
|
REST Client |
The component makes a request to the web service https://npiregistry.cms.hhs.gov/api passing the NPI number as a parameter (URI query parameter number). This parameter is the same as the value of the property NPI that was extracted on the route 1 Split and Validate. The web service returns a JSON response with information about the queried NPI. |
| Extract data from JSON
|
JSON Value Extractor |
By using the JSONPath expression "$.result_count", the component extracts the value of the JSON field result_count and sets this value as the XEServer property NPIValidationResult. The value of the field results_count 0 indicates that the Provider with the queried NPI is not available. The value of the results_count non-zero indicates that the Provider with the queried NPI is available.
|
| Aggregation
|
Aggregation |
After the component REST Client makes the last call to the NPPES NPI Registry (the last claim has been checked), this component aggregates the messages by the correlation ID. The component merges the properties of the aggregated messages. On the output, the component creates a single message using the original data file in the native format as the body of the new message.
|
