Terminology


Before you get started, there are some terms that we frequently use. Let's start to get familiar with them:

User Accounts

User accounts represents the users of Apervita. Users can be both consumers and creators, using the Apervita platform to make and use Computable Knowledge. Every user belongs to at least one Organization and Workspace, but can belong to multiples of each. Users may also create their own Organizations and Workspaces.

Organizations and Workspaces

Apervita allows customers to create ‘organizations’ and ‘workspaces’ each with one or more privileged administrators. An organization can contain one or more workspaces and an administrator can securely invite users into the appropriate workspaces. A workspace acts as a way to manage a group of users such as a department; a group of activities, such as a project; or a queue of work, such as content ready for review. The organization is the billing entity and is responsible for all transactions of its users. The organization holds the current invoicing information for the enterprise. Organizations and Workspaces also provide the security tools and management which make Apervita a secure, HIPAA compliant home for Computable Knowledge.

Executions

An execution is a single analytic running against a single patient or subject on the Apervita platform. An execution is the atomic level billing unit used on the Apervita platform.

User Groups

User groups facilitate easier management of user roles and permissions. New/existing users can be assigned to one or more groups with pre-configured permissions. Different workspaces can have different user groups.

APIs

Every analytic asset on Apervita automatically comes with a dedicated web service to execute and deliver results via RESTful APIs. The administrator or their delegate can activate and manage the APIs. Apervita also provides APIs for many other purposes, such as data, assets and execution.

Knowledge Assets

Apervita enables knowledge assets (or types) to accommodate common functions, such as:

 

Knowledge Asset

Knowledge Type

      Description

Algorithm

Analytic

  • Create simple rules and highly sophisticated algorithms.
  • Chain and bundle algorithms together.

Measure

Analytic

  • Build and maintain standard or custom measures of all types.
  • Import and export HQMF/QDM.

Cohort

Analytic

  • Build and maintain population cohorts.
  • Filter by concepts, values, and time with reusable and chainable cohort definitions.

Rule

Analytic

  • Build and maintain simple or complex rules.

Order Set

Analytic

  • Create static orders and order sets.
  • Create dynamic orders and order sets driven by algorithms.

Pathway

Analytic

  • Create pathways customized to individual patients using algorithms.

Concept Set

Connector

  • Build and maintain standard or custom concept sets (e.g. code sets).
  • Connect many analytics to many data sources with different schemas.

Value Set

Connector

  • Build and maintain standard or custom values sets.
  • Import from standard, such as VSAC.
  • Harmonize semantics and definitions between sites, systems, standards (e.g., SNOMED, ICD10).

Ontology

Connector

  • Traverse and subsume standard or custom ontologies in analytics or create other connectors.

Population

Data

  • Integrate and enable data of any type (e.g. patient, provider drug, disease, facility) with any schema.

Sub-Population

Data

  • Apply cohort filters to populations for targeted analytics.

Reference Table

Data

  • Create or import custom reference tables to link to algorithms.

 

 

Back to top