provider-ops-ontology-starter

Provides a governed acute-care operations ontology for TextQL/Ana with entity spine and classification.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/TextQLLabs/ontology-starter-kits --skill provider-ops-ontology-starter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: provider-ops-ontology-starter
Source: https://github.com/TextQLLabs/ontology-starter-kits/tree/main/provider-ops
Command: npx skills add https://github.com/TextQLLabs/ontology-starter-kits --skill provider-ops-ontology-starter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides a prebuilt, governed provider / health-system operations ontology, saving time and resources by eliminating the need to build an ontology from scratch.

Core Features & Use Cases

  • Prebuilt Ontology: Offers a ready-to-use ontology with a defined structure for acute-care operations data.
  • Entity Spine: Covers patients, providers, facilities, departments, encounters, bed census, OR cases, appointments, and charges.
  • Classification: Includes MS-DRG, NUBC-disposition, and service-line classification.
  • Governance: Incorporates HIPAA PHI minimum-necessary and small-cell suppression.
  • Use Case: For a hospital, health system, or academic medical center looking to quickly implement an ontology for acute-care operations data.

Quick Start

Connect this repo to Ana via the Git connector, then connect your health system's warehouse. Validate and adapt the ontology, and start asking questions using the skill.

Frequently Asked Questions about provider-ops-ontology-starter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is an acute-care operations ontology and why do hospitals need one?

An acute-care operations ontology structures healthcare data into a governed entity spine covering patients, providers, and encounters. Hospitals need it to standardize operations data, eliminate building from scratch, and enable consistent analytics.

How do I implement a provider ontology for health-system operations data?

To implement a provider ontology, connect your repository via the Git connector to Ana, link your health system's warehouse, validate the prebuilt entity spine against your schemas, and adapt the terminology to start querying.

Does this healthcare ontology include classification systems for MS-DRG and service lines?

Yes, the healthcare ontology includes built-in classification for MS-DRG, NUBC-disposition, and service-line categories. These governed metric surfaces allow standard grouping of acute-care encounters and operational reporting.

Can I use this hospital operations ontology with my existing warehouse schema?

Yes, you can use the hospital operations ontology with your existing warehouse, but it requires configuration. You must adapt the prebuilt entity spine and terminology to match your specific warehouse schemas for accurate results.

How does the ontology handle HIPAA PHI minimum-necessary rules for hospital data?

The ontology handles HIPAA PHI minimum-necessary rules by incorporating governed metric surfaces with small-cell suppression. This ensures acute-care operations analytics automatically restrict sensitive patient data exposure.

What are the limitations of using a prebuilt ontology for acute-care operations?

The limitation of a prebuilt ontology for acute-care operations is that it is not instantly plug-and-play. It requires manual configuration and adaptation to align with your specific warehouse schemas and terminology before querying.