Quickstart
From install to a populated change watchlist in about 10 minutes.
Prerequisites: a Snowflake role that can install Marketplace apps, and read access to a table holding your facility list (one row per facility, with its CMS Certification Number — CCN). Installing the app requires no account-level privileges, and FacilityGuard reads nothing in your account until you connect a facility list in step 3. In a hurry, or don't have your list ready? Skip to the demo and be exploring real data in two clicks.
1. Install the app
Get FacilityGuard from the Snowflake Marketplace and install it into your account. When the install finishes, open the app from Data Products → Apps in Snowsight. You'll land on the Portfolio setup page.
2. Give your team access
FacilityGuard installs with two roles you grant to your own team:
User
Analysts, reviewers
Browse the watchlist, ownership chains, and portfolio health; record reviews; export
Admin
Admins
Everything above, plus connecting a facility list and mapping columns
An account admin grants these in Snowsight — for example:
GRANT APPLICATION ROLE <app_name>.app_user TO ROLE <your_analyst_role>;
GRANT APPLICATION ROLE <app_name>.app_admin TO ROLE <your_admin_role>;<app_name> is whatever your admin named FacilityGuard at install.
3. Connect your facility list
On the Portfolio setup page, choose Connect your facility list. Snowflake's own grant dialog opens: pick the table or view that holds your facility list, and Save. The grant is read-only SELECT on that one table — FacilityGuard can see nothing else in your account, and you can revoke or reconnect a different table at any time. The setup page then confirms the connection, naming the exact table you picked and how many rows and columns it found.
Any table with one row per facility works. The one required field is the CCN; a facility-name column is helpful for display.
Required table shape — one row per facility:
CCN
TEXT
Yes
6-character CMS Certification Number. Store as text — CCNs can have leading zeros that a number column would strip; FacilityGuard restores them automatically.
facility name
TEXT
No
Display only.
Sample rows:
Prefer to try it first? The setup page offers a bundled demo portfolio of 14 real, public CMS facilities, hand-picked to show every coverage state — fully-disclosed, private-equity-owned, dead-end, partial, and not-yet-in-the-enrollment-data. Choose Use demo portfolio and continue → to explore genuine ownership chains, a live change watchlist, and the coverage breakdown before connecting your own CCNs.
4. Map your CCN column
Point FacilityGuard at your CCN column (and optionally a facility-name column), then choose Save mapping. The page shows a match meter — how many of your rows read as valid 6-character CCNs — so you can confirm the mapping before binding.
5. Bind your portfolio
Choose Bind portfolio. Binding matches your CCNs against the CMS universe and, only then, renders the coverage panel: how many facilities resolved, and — facility by facility — what the federal filings can and cannot tell you about each one (fully disclosed, partial, dead-end, or no enrollment data).
The coverage panel puts disclosure limits up front: before you rely on the watchlist, you already know which facilities have complete disclosed chains and which dead-end in the filings.
On a trial, portfolios are capped; if your table holds more facilities than your plan allows, FacilityGuard binds a set and reports the over-cap count — nothing is silently dropped.
6. Review your watchlist
Open Change watchlist. It fills immediately from the full detection history — every ownership change for your bound facilities, graded so the validated low-noise signal leads and noisier disclosure churn stays one filter away.
A quiet portfolio is normal: the strong-signal baseline is roughly 1% of facilities per month, so a 25-facility book may surface an alert only every few months. The history is how you evaluate the product — replay what would have alerted over the past couple of years.
How to confirm it's working: the run log on the Settings & export page records your bind with the exact source dates it used. If it shows your bind, FacilityGuard is wired up — and a portfolio with zero current alerts is an expected outcome, not an error. Widen the date range or include the watchlist tier to replay more history.
Troubleshooting
The table picker doesn't show my facility table
Cause: the role you're using in Snowsight can't read that table, or you don't hold FacilityGuard's Admin role.
Fix:
Switch to a role that can read the facility table.
Confirm the Admin role was granted to that role (step 2).
Re-open Connect your facility list — the picker lists only tables your current role can see.
Fewer facilities bound than my table holds
Cause: your portfolio is over your plan's facility limit, or some CCNs didn't match the CMS universe.
Fix:
Check the bind summary — the over-cap count and any unmatched CCNs are reported explicitly.
Verify unmatched CCNs are real 6-character facility CCNs (typos won't match).
To bind a larger book, see Security & Plans.
A facility shows "no ownership data"
Cause: expected for part of the universe — the facility isn't in the current CMS snapshot, or its enrollment discloses no ownership. The filings simply go no further.
Fix: treat the flag as the finding. Absence of federal disclosure is itself information, and FacilityGuard shows it rather than hiding it.
The change watchlist looks empty
Cause: a small, stable portfolio — at the ~1%-per-month baseline, months with zero alerts are normal.
Fix: widen the date range to the full history (a couple of years) to see the replay, and include the watchlist tier alongside the strong signal for lower-stakes moves.
Next steps
Tour the five screens in workflow order: Using the App
Understand the grades, the backtest, and the coverage limits: Methodology
See what FacilityGuard monitors: What FacilityGuard Checks
FacilityGuard docs: Overview · Using the App · Methodology · What FacilityGuard Checks · Security & Plans
Last updated