Community Spring Cleaning week is here! Join your fellow Maveryx in digging through your old posts and marking comments on them as solved. Learn more here!
The Product Idea boards have gotten an update to better integrate them within our Product team's idea cycle! However this update does have a few unique behaviors, if you have any questions about them check out our FAQ.

Alteryx Designer Desktop Ideas

Share your Designer Desktop product ideas - we're listening!
Submitting an Idea?

Be sure to review our Idea Submission Guidelines for more information!

Submission Guidelines

Estimated Driving Distances needed for CMS Reporting and Compliance

Currently I am unable to use Alteryx's spatial calculations in completing required reporting for CMS.  Its unfortunate, because in my mind Alteryx is a superior approach allowing for customization and seamless integration with varied data sources used within our company.

 

You might ask, why don't you just use actual driving distance?  The datasets that we are measuring are enormous. +60M member files are being compared to 70K providers.  Alteryx is missing a huge opportunity to get into this market.

 

Reference

https://www.cms.gov/Medicare/Prescription-Drug-Coverage/PrescriptionDrugCovContra/downloads/hsd_meth...

Travel Distance to Providers and Facilities

The second component of the review process tests the percentage of beneficiaries resident in a given county with access to a particular specialty type within the maximum travel distance. For a given county and specialty type, CMS uses the geographic coordinates for the associated providers or facilities and the geographic coordinates for the beneficiaries resident in the county and calculates the travel distance between them. The travel distance is calculated using a formula to determine the estimated driving distance (miles) between the latitude and longitude coordinates and provides an average for the total beneficiaries in the given county

2 Comments
RickPack
8 - Asteroid

Clarifying that the issue appears to be the driving distance (DriveTime included) calculations are very slow on Alteryx. I have been comparing data containing 200k elements with data containing 2k elements and the workflows take hours to complete on a fairly powerful I7-6820HQ at 2.7GHZ with 8 GB ram. Reducing the max distance helps a great deal, to the point of being necessary, but the workflows still take hours and the reduction of max distance reduces the usefulness.

EDIT: Using Find Nearest to select the nearest "as the crow flies" of the 2k elements and then clicking the Distance tool's "Allow Reversed Routing for Optimal Speed" [this may not be valid for use case] also dropped the runtime.

AlteryxCommunityTeam
Alteryx Community Team
Alteryx Community Team
Status changed to: Accepting Votes