pa-gov/hospitalization-count-and-rate-of-hospitalization-ns2a-t87x

  • disease
  • disorder
  • doh
  • drug
  • health
  • + 4

Query the Data Delivery Network

Query the DDN

The easiest way to query any data on Splitgraph is via the "Data Delivery Network" (DDN). The DDN is a single endpoint that speaks the PostgreSQL wire procotol. Any Splitgraph user can connect to it at data.splitgraph.com:5432 and query any version of over 40,000 datasets that are hosted or proxied by Splitgraph.

For example, you can query the hospitalization_count_and_rate_of_hospitalization table in this repository, by referencing it like:

"pa-gov/hospitalization-count-and-rate-of-hospitalization-ns2a-t87x:latest"."hospitalization_count_and_rate_of_hospitalization"

or in a full query, like:

SELECT 
    ":id", -- Socrata column ID
    "state_fips_code", -- First 2 digits of the 5-digit Federal Information Processing Standard (FIPS) code that designate the state association. Each state has its own 2-digit number and each county within the state has its own 3-digit number which are combined into a 5-digit number to uniquely identify every US county.
    "geographic_area", -- Region for measure, either total for Commonwealth or individual county.
    "geographic_name", -- Name of geographic area.
    "age", -- Age of individuals hospitalized (12 years and above).
    "time_period", -- Period for measurement (annual, federal fiscal year, or quarterly, if available).
    "hospitalization_rate", -- Hospitalization rate for specified opioid use related disease per 1,000 estimated individuals with Drug Use Disorder.
    "type_of_rate", -- Description of hospitalization rate.
    "hospitalization_count", -- Number of unique individuals hospitalized for specified opioid use related disease in given time frame.
    "hospitalization_count_1", -- Describes hospitalization count.
    "hospitalization_count_notes", -- Indicates if the number of unique individuals primarily hospitalized with the specified opioid use related disease has been suppressed to protect confidentiality. Counts less than 11 are not provided.
    "oud_estimate_notes", -- Indicates if the estimated number of individuals with Drug Use Disorder has been suppressed to protect confidentiality. Counts less than 11 are not provided.
    "county_code_number", -- Pennsylvania county code provided as a number (1-67 for counties, 0 for Commonwealth).
    "county_code_text", -- Pennsylvania county code provided as text (1-67 for counties sorted alphabetically, 0 for Commonwealth).
    "county_fips_code", -- Last 3 digits of the 5-digit Federal Information Processing Standard (FIPS) code that designate the county association. Each state has its own 2-digit number and each county within the state has its own 3-digit number which are combined into a 5-digit number to uniquely identify every US county.
    "latitude_longitude", -- A generic latitudinal point within the county. A point is also provided for outside of the state (on a map it will sit to the southeast of the state). This number represents the total number for the state and this location provides a spot on a map to display the PA number without having it duplicate within a county when using in a mapping visual.
    "longitude", -- A generic longitudinal point within the county. A point is also provided for outside of the state (on a map it will sit to the southeast of the state). This number represents the total number for the state and this location provides a spot on a map to display the PA number without having it duplicate within a county when using in a mapping visual.
    "geocoded_column", -- A generic georeferenced Latitude & Longitude point within the county. These points can be used to create visualizations such as maps to show the data by county. A point is also provided for outside of the state (on a map it will sit to the southeast of the state). This number represents the total number for the state and this location provides a spot on a map to display the PA number without having it duplicate within a county when using in a mapping visual.
    "year", -- Calendar year for measurement (January 1–December 31).
    "time_period_dates", -- Start and end dates of time period.
    "oud_estimate_description", -- Describes number of estimated individuals with Drug Use Disorder. 
    ":@computed_region_nmsq_hqvv",
    ":@computed_region_d3gw_znnf",
    ":@computed_region_amqz_jbr4",
    ":@computed_region_r6rf_p9et",
    ":@computed_region_rayf_jjgk",
    "primary_hospitalization", -- Primary diagnosis for hospitalization.
    "gender", -- Gender of individuals hospitalized.
    "oud_estimate" -- Estimated number of individuals with Drug Use Disorder. 
FROM
    "pa-gov/hospitalization-count-and-rate-of-hospitalization-ns2a-t87x:latest"."hospitalization_count_and_rate_of_hospitalization"
LIMIT 100;

Connecting to the DDN is easy. All you need is an existing SQL client that can connect to Postgres. As long as you have a SQL client ready, you'll be able to query pa-gov/hospitalization-count-and-rate-of-hospitalization-ns2a-t87x with SQL in under 60 seconds.

This repository is an "external" repository. That means it's hosted elsewhere, in this case at data.pa.gov. When you querypa-gov/hospitalization-count-and-rate-of-hospitalization-ns2a-t87x:latest on the DDN, we "mount" the repository using the socrata mount handler. The mount handler proxies your SQL query to the upstream data source, translating it from SQL to the relevant language (in this case SoQL).

We also cache query responses on the DDN, but we run the DDN on multiple nodes so a CACHE_HIT is only guaranteed for subsequent queries that land on the same node.

Query Your Local Engine

Install Splitgraph Locally

bash -c "$(curl -sL https://github.com/splitgraph/splitgraph/releases/latest/download/install.sh)"
 

Splitgraph Cloud is built around Splitgraph Core (GitHub), which includes a local Splitgraph Engine packaged as a Docker image. Splitgraph Cloud is basically a scaled-up version of that local Engine. When you query the Data Delivery Network or the REST API, we mount the relevant datasets in an Engine on our servers and execute your query on it.

It's possible to run this engine locally. You'll need a Mac, Windows or Linux system to install sgr, and a Docker installation to run the engine. You don't need to know how to actually use Docker; sgrcan manage the image, container and volume for you.

There are a few ways to ingest data into the local engine.

For external repositories (like this repository), the Splitgraph Engine can "mount" upstream data sources by using sgr mount. This feature is built around Postgres Foreign Data Wrappers (FDW). You can write custom "mount handlers" for any upstream data source. For an example, we blogged about making a custom mount handler for HackerNews stories.

For hosted datasets, where the author has pushed Splitgraph Images to the repository, you can "clone" and/or "checkout" the data using sgr cloneand sgr checkout.

Mounting Data

This repository is an external repository. It's not hosted by Splitgraph. It is hosted by data.pa.gov, and Splitgraph indexes it. This means it is not an actual Splitgraph image, so you cannot use sgr clone to get the data. Instead, you can use the socrata adapter with the sgr mount command. Then, if you want, you can import the data and turn it into a Splitgraph image that others can clone.

First, install Splitgraph if you haven't already.

Mount the table with sgr mount

sgr mount socrata \
  "pa-gov/hospitalization-count-and-rate-of-hospitalization-ns2a-t87x" \
  --handler-options '{
    "domain": "data.pa.gov",
    "tables": {
        "hospitalization_count_and_rate_of_hospitalization": "ns2a-t87x"
    }
}'

That's it! Now you can query the data in the mounted table like any other Postgres table.

Query the data with your existing tools

Once you've loaded the data into your local Splitgraph engine, you can query it with any of your existing tools. As far as they're concerned, pa-gov/hospitalization-count-and-rate-of-hospitalization-ns2a-t87x is just another Postgres schema.

Related Documentation: