Feature Queue

When running long-running queries, it would be valuable to know what the SFTP path is. Ideally you could provide a "last 10" list on the CQ object and also add this path to the email. The reason for this is as we add downstream processing after the CQ object has been processed, but before the data is persisted, if we make an error in our code we should be able to bypass processing the query again and just attach directly to the FTP output.

Recommendation from James: Add timer logic on bulk query execute that waits for success before completing for a more seamless user experience when the user knows they want to do thing synchronously.

Be able to look at a service line, NPI, region, and/or set of Dx/Px and return a potential market value/impact in terms of number of encounters, patients and immediate and long-term value

Create the ability for a user to install CareQuery and make x# of estimate or sample queries before buying the product.

Having accurate provider details on NPI, facility, system, location as we join to each claim is hugely important. As providers move around and we filter on state, system, referrals, etc it gets very complicated to be accurate with one provider record. Ideally the api would let us get all providers at physician, practice/facility/hospital, and system level, and for each the history of movement over time to different regions/systems.

For an NPI, Group of NPI's or a Market - be able to get an understanding of number of providers by type, number of beds per facility, number of chronic conditions managed, readmits, age stratification, payor mix by channel and by payer, acuity of patient population

Create queries which aggregate explicit referral relationship activities by diagnosis and procedures.

Create queries which aggregate provider activities pertaining to procedure and diagnosis volumes.