Return to the beginning of the report
Additional Identified Considerations
In addition to the selected criteria, DOI has identified the following elements as potential considerations in the analysis of network adequacy. This report considers each and describes necessary functionality with prospective toolsets.
Rural vs. Non-Rural Classification
Toolsets must be able to classify provider networks based on population and population density within said networks (i.e., see CMS’ categorization of counties into Large Metro, Metro, Micro, Rural and Counties with Extreme Access Considerations). Toolsets should have the ability to make calculations at multiple geographic levels, including county level, ZIP code level and Census-tract level. DOI must retain the ability to adjust thresholds for these classifications within the toolset at a future date, if warranted by population growth.
Additionally, for purposes of analysis, the toolset must be able to apply different adequacy standards depending upon the network’s rural/non-rural classification. Toolsets that cannot calculate this information natively would, at minimum, need to allow the information to be imported and incorporated as an additional data element for analytical purposes.
Analysis by Categorical Designation
Toolsets must have the ability to filter analysis of provider networks according to DOI designated classifications, such as specific provider types or specific health plan types. Toolset must have the ability to create new fields of data that consist of categorical designations determined by DOI. These categorical designations should be possible at multiple levels of analysis, most importantly at the network-level. Toolsets should be able to filter network adequacy results by each category, or by a combination of categories and indicators. DOI must have the ability to alter the number and types of categories and indicators, as well as require specific designations for each category.
Toolsets should be able to natively generate new variables as a result of logical expressions and numeric formulas using existing variables. If not, they must allow for the information to be imported for subsequent integration into the tool’s network analysis.
Network Classification
Toolsets must have the ability to classify provider networks into DOI-designated categories such as basic, standard or broad. Toolsets must be able to use combinations of existing variables to generate new variables with logical expressions and numeric formulas. The DOI will determine indicators and standards for network classification that are subject to change with DOI’s discretion and toolset must be able to incorporate those changes when they occur. Standards will vary by network category. To ensure classifications stay up to date, calculations will need to be periodically updated at a frequency determined by DOI. Toolsets should also allow for analytical results to be filtered according to these classifications.
Toolset must allow for the integration of this network classification information into the State’s Your Health Idaho (YHI) shopping portal. Toolsets should either have an ability to mirror the data on the public facing website, whether as a spatial representation or data card element, or allow for regular exportation of data that can be transferred to a more web-friendly interface (to be determined in consultation with YHI’s web manager/ designer).
Specific Populations
Toolsets must be able to incorporate demographic data into network adequacy analysis. These include, but are not limited to, tribal members, non-English speakers or those with disabilities. Toolsets should be able to import demographic data of geographic areas, such as cities, counties, ZIP codes or Census-tracts, and intersect this data with provider network coverage. Toolsets must also be able to import network specific demographic information, as reported to DOI by insurance carriers. Toolsets should be able to filter results for specific demographic characteristics in combination with other indicators.
Changes in Network
Toolsets should provide a mechanism to verify when an individual record was last checked or updated, as well as allow for identification of out-of-date records that may need to be excluded from future analyses. Toolsets must be able to adjust analytical results to account for providers entering or leaving an existing network. Ability to perform disruption analysis is preferred.
Licensing Costs
Toolsets should provide options for DOI to produce customized network reports in-house. Toolsets should integrate open source alternatives, where feasible, to minimize costs.
Toolset Considerations
Most of the identified considerations require reporting from insurance carriers and must be entered into a database for any subsequent analysis to occur. Once these data are entered, however, most of the identified toolsets can use them in concert with other evaluative variables. Table 2 summarizes which of the identified toolsets are able to meet each indicator’s requirements.
Table 2: Toolset Functionality Suitability by Consideration
| Toolset |
Consideration |
|
Rural vs. Non-Rural |
Categorical Designation |
Network Classification |
Specific Populations |
Changes in Network |
Licensing Costs |
| ArcGIS |
x |
x |
x |
x |
– |
|
| QGIS |
x |
x |
x |
x |
– |
x |
| Quest Analytics |
x |
x |
x |
x |
– |
|
| Optum GeoAccess |
x |
x |
x |
– |
x |
|
| Encompass |
|
|
|
|
|
x |
| AccessMod 5 |
x |
|
|
x |
|
x |
| R |
– |
– |
– |
– |
|
x |
x toolset has functionality
– potential for added functionality